You are being given this document because Fidelity are supplying an EPoS Solution to the organisation you support. This document aims to provide you with two things:-
Application Name | Application Use |
Fidelity GPoS (GPoS) | Software that runs on the point of sale hardware |
Total Control Premier (TCP) | Back of house software for product maintenance and reporting analysis |
Instant CRM/Instant Loyalty (CRM) | Back of house software that provides Loyalty/Cashless/Membership functionality |
Fidelity Fusion | Cloud hosted data analysis system |
Bartender Automation Edition | Written by Seagull Scientific but supplied by Fidelity. Used for label production. |
Application Name | Application Use |
Payware Sentinel | EFT Card Payments |
WorldPay/YesPay IPC/EasyVTerminal | EFT Card Payment |
Yoyo | Cloud Based Cashless Payments + Voucher rewards |
sQuid | Cashless Payments |
CO-OP Link | Ordering Integration |
NUSSL Catalogue | Online Product Catalogue |
Magna Carta Facility Pro | Cashless System |
PayPal | Cloud Based Cashless Payments |
Sports Booker | Online Bookings system |
G4s - Girovend | Site Based Cashless Payments |
Counter Solutions | Site Based Cashless Payments |
Debitrak | Cloud Based Cashless Payments |
Uniware uPay Chilli | Cloud Based Cashless Payments |
Kappture | Cloud Based Cashless/Loyalty Payments |
Sagepay | EFT Card Payment |
Global Payments | EFT Card Payment |
The Fidelity EPoS Solution uses a Microsoft SQL server. This can be either a full version or the express version depending on the size of the system being installed.
An ‘Application Server’ will be defined that runs Services used for many functions. This is strongly recommended to be a server but can be on a desktop PC for a small system.
The POS Terminals communicate with each other via a bespoke protocol and to the database via the Application Server using a bespoke protocol. This is all done via TCP/IP.
This specification is based on one server providing both Application Roles, Internet Information Services (For TCP's Web Interface and API) , and hosting the SQL database. It is based 20 POS terminals and 5 client PC’s.
Minimum:-
OS: Windows Server 2016
.Net Framework 4.7.1
SQL: SQL Server 2016 (Express can be used however it has a 10gb Database limit)
Memory: 16GB
CPU Type: Xeon (Quad Core)
CPU Speed: 2.0Ghz
DATA DISK: Separate HD for Data AND Separate HD for Log (50-100GB) (SSD?)
Requires a static IP address - manually assigned or DHCP reserved IP
Recommended Spec:-
Windows Server 2016 or later
Intel Xeon Quad Core 2.8ghz
32gb Ram
Raid 1 Array for the OS
Raid 5 Array for the Data
A network connection to the SQL Database
Supported Operating systems:-
Crystal Reports:-
Microsoft .NET Framework
A standard installation requires:-
We also require VNC access from the entry point (e.g. application server) to the POS terminals.
Other methods can be discussed and agreed upon between yourselves and Fidelity’s Support Manager.
Application | Usage | Port(s) | External Access Required | Compulsory |
Fidelity Licence Service | For activating software licences | Yes | Yes | |
Fidelity Software Update Service (FSUS) | For updating the GPoS software on POS terminals | The Service Communications are via update.fidelitysytems.co.uk which is a cname to fidelityupdate.cloudapp.net and the communications will be on port 443 SSL Downloads are via downloads.fidelitysystems.co.uk which is a cname to fidelityfiles.blob.core.windows.net. Port 80 is used. Port 443 SSL cannot be used for this due to an issue with Azure Blob Storage which we use for hosting the files to be downloaded. Click here for more details. To ensure the security of the download a checksum is used to ensure that the downloaded file is the file that is expected. This would prevent the system being exploited by a man-in-the-middle style attack. | Yes | Yes |
Snipe Updater | Fidelity record kit supplied on an asset manager system. The updater populates the asset system and updates with any changes made | Yes | ||
GPoS IRC | GPoS to GPoS communications | UDP/TCP 9171 | No | Yes |
GPoS to App Server – Job Controller Service | Posting of sales data and send of programming updates | TCP 9965 | No | Yes |
GPoS API Comms | For the new method of Communications between GPoS and Total Control Premier | To the server running IIS Ports 80/8080/443 | ||
GPoS to App Server – Customer Accounts Service | Customer Accounts Transactions | TCP 9181 | No | Yes |
GPoS to App Server – GPoS Loyalty Service | Instant CRM Customer lookup and transactions | TCP 9168 and TCP 9171 | No | No |
TCP Client to SQL Database | Back of House Clients opening the SQL database | Default 1433 but can be specified as part of the connection string | No | Yes |
App Server to GPoS - VNC | Remote assistance (Internal Only) | Default 5900 – can be changed | No | Yes |
TCP to E-mail | Sending of e-mails to suppliers and sending reports via e-mail | Provided by local IT | ||
Bartender / Seagull Licence Server | Label Printing | 5160 | No | Yes |
External Catalogue Link | Yes | No | ||
Skorpio HHT / MISCommunicator Service | Communicates to the TCP Application server over WiFi | 8000/9000 | No | |
Application | Type | Ports |
Verifone Payware VX Range | EFT Card Payments | Transaction - TCP outbound 91.207.36.31 ports 29006 (RSA), 29005 (Unencrypted data), 29002 (SSL) Transaction - TCP outbound 91.207.36.33 ports 29006 (RSA), 29005 (Unencrypted data), 29002 (SSL) Download - TCP outbound 91.207.36.37 ports 29006 (RSA), 29002 (SSL) |
Verifone Engage Range (p400 etc) | EFT Card Payments | Engage PEDs Production - 91.207.36.31 - 29006 Transactions, logins and configs (TCP/IP only) PED VHQ message handler - [178.21.211.75] 443 - https://vhq2.vfims.com/MessagingServer/MessageHandler.asmx (requires DNS) |
DOJO / PaymentSense | EFT Card Payments | Unique API - xxxxxxxxxxxxxxx.connect.paymentsense.cloud |
WorldPay IPC | EFT card Payments | IP range is whitelisted on the firewall & port 443 is open on the network 195.35.90.1 to 195.35.91.254 |
YoYo | 3rd Party Loyalty and Payments | https://one.justyoyo.net/api/v3/epos port 443ort 443 |
If you intend on hosting a Fidelity application in a terminal services environment you should ensure that a user licence is purchased for each intended concurrent connection.
Fidelity software packages use a major minor version system e.g. x.x.yyyy x.x is the major version and xxxxx The major version must match the version of the database being used and all clients must be running the same major version. We would advise checking other client pc’s for the version or if in any doubt to speak to Fidelity.
When installing TCP on a back of house PC you do not need to install Microsoft SQL Server, if prompted as a pre-requisite answer yes to it being a pre-requisite and then No to installing it. From TCP version 2.06.xxxxx onwards SQL is not included as part of the installer. The Instant CRM Installer doesn’t include SQL Server.
Tick the box alongside the Package that you wish to activate.
Click next and you are prevented with a box to enter the serial number you have been provided with (8 digits). Un-tick the ‘Activate now using my Internet Connection’ box and click next
The next screen displays a long KeyNumber and a box for an activation code to be entered into. Click on the black surrounding the key code it will copy it to windows clipboard. This can be pasted into a file which can be emailed to our support team at support@fidelitysystems.co.uk or it can be pasted directly into an e-mail.
Fidelity will then return an activation code to you which needs to be entered into the box below the key code (it can be pasted back in if required).
Once the code is entered click next and you will then get the message "Thank you for purchasing a fidelity product." If this errors you may need to check that you have the correct package selected and the activation code is correct.
Notes:-
When running Total Control Premier for the first time you will be prompted to setup a connection to the database. We would recommend copying a TCpConnections.xml file off an existing workstation into the C:\ProgramData\Fidelity Systems\Total Control Premier folder.
Navigate to the 'Activate Fidelity Software' application. This is found within the software’s 'Program Files' folder, accessible via the Windows start
menu.
following locations.
Note:- TCP and CRM use V2 of the registration wizard. GPoS cannot be activated successfully using V2.x
Make sure the Software package you wish to de-licence is ticked, click 'Next' at which point you
should see the screen below:
There are now two options:
On Selecting Offline, The Registration Wizard will progress to a screen displaying the Removal Key
code.
The key code *MUST* be sent to Fidelity, in order for them to reactivate the code for use on
another device. After transmitting this to fidelity, the code will be verified and the licence flagged to
allow reactivation on another device.
The preferred method of sending this is to E-mail it to support@fidelitysystems.co.uk
To copy the code into an e-mail you have two options
When removing TCP we also recommend taking a copy of the TCPconnections.xml file found in C:\ProgramData\Fidelity Systems\Total Control Premier to be re-used on a replacement PC.
When a PC will not boot, it is still possible for us to deactivate the Licence and Flag it for reactivation.
In order to do this we require the Hard Drive’s physical serial number, which we validate with our
system here.
If the serial number provided DOES NOT Match an activation on our records or the code cannot be provided, we will NOT be able do a manual void of a licence and a new Licence would need to be purchased!
There may also be label files stored on the PC, these will need copying off to be re-used again. The default location for these would be C:\Program Files (x86)\Fidelity Systems\Total Control Premier\Labels.
The Automation Edition of Bartender is required, and Bartender version 2016 onwards is supported. If using Bartender version 9.x or 10.x you will need to enable Bartender compatibility mode from within Total Control Premier’s General Options