GPoS Pre-Requisites and Integrations

GPoS Pre-Requisites and Integrations

GPoS Pre-Requisites and Integrations

This document is intended to show details of operating systems and third party applications that GPoS requires either as a requirement or as an optional add-on. 

We will follow the manufacturers 'Lifecycle Policy' and will continue to support Fidelity applications against pre-requisites and 3rd Party applications whilst they are still in a supported state. There may be occasions where in order to utilise new functionality available in up to date versions compatibility with older versions is broken. We will provide notification of these scenarios as soon as we become aware of them.

Items highlighted in red are either at or past their 'End of Support' period and as such support by Fidelity is not guaranteed

Pre-Requisites

Microsoft Applications

GPoS runs on PC's running Microsoft Windows Operating systems utilising the Microsoft .NET Framework. It also requires a Microsoft SQL Database which can be hosted locally or across the network.

Details on Microsoft's Lifecycle Policy can be found here https://support.microsoft.com/en-gb/hub/4095338/microsoft-lifecycle-policy

Operating Systems

GPoS will run on the following operating systems with local administrative rights:-
Desktop Operating Systems
Desktop Operating Systems
Windows 11 64 Bit
From Version 1.68
Windows 10 32/64bit
Windows 8/8.1 (All editions) 32/64bit No longer Tested on new releases from Version 1.68
Windows 7 (All editions) 32bitExpected end Nov 2021 - No longer Tested on new releases from Version 1.68
Windows 7 (All editions) 64bit - Service pack 1 and laterExpected end Nov 2021 - No longer Tested on new releases from Version 1.68
Windows VistaSupported up to GPoS 162 Only
Windows XP All versionsSupported up to GPoS 162 only


Server Operating Systems
Windows Server 2016 - 64bit
Windows Server 2012 R2 - 64bit
 Last version tested before EOL
Windows Server 2012 - 64bitNo longer Tested on new releases from Version 1.68
Windows Server 2008R2 - 64bit - Service pack 1 and laterNo longer Tested on new releases from Version 1.68
Windows Server 2008 32/64bit - Service pack 2 and laterSupported up to GPoS v162


Microsoft .Net Framework 

GPoS requires Microsoft .NET Framework v4.7.2 or above to run.

This is included as part of the install package

Microsoft SQL Server

The system uses a Microsoft SQL database and full DBO access to the database is required. The database MUST be held locally on the POS terminal.



GPoS Version Supported up toExtended Support End Date
SQL Server 2016
14/07/2026
SQL Server 2014
 09/07/2024
SQL Server 2012
12/07/2022
SQL Server 2008 R2
09/07/2019
SQL Server 2008
09/07/2019
SQL Server 2005
10/07/2007


SAP Crystal Reports

GPoS uses SAP Crystal Reports runtime engine for .NET Framework. GPoS v1.61 introduces support for SAP Crystal Reports Version 13 build 20.

Prior versions used SAP Crystal Reports Version 13 build 10.

Optional Integrations

EFT Payments

Verifone Payware

Contact for more information

Verifone Engage Range

(P400, V240M.....)

SagePay

No longer supported

WorldPay / YesPay

Up to and including IPC-2.3.9 the integration works. You will need GPoS v162 for this. Tested agains v169 and v170


PaymentSense / DOJO

Retail mode is currently supported.
Cashback is not supported (the integration guide says that it is but that is not correct currently 28/11/2022)
We no longer support the Pay at Table mode.

GlobalPayments

No longer supported

Ordering

Mobo2Go


Orderman

No longer tested. Confirmed as working with v1.62.  We do not intend to invest in the development of this or any lengthy fixes that may be required.

GPoS Customer Accounts

Sage

Sage Accounts (Formerly known as Line 50) is supported up to Sage Accounts 2019 (v25)

This is the last version of Sage 50 we will do an integration for

PMS

Welcome 21

Contact for more information

Resident Pro

Uses the GPoS Rooms Text file interface

Mainstay

Contact for more information

Avon Data

The Avon Data integration is removed in version 1.69 of GPoS

Payment

Debitrak

Yoyo

Paypal

No longer supported

Squid

No longer supported

Counter Solutions

No longer supported

Kappture

No longer supported

Magna Carta

No longer supported

Girovend

No longer supported

Upay Chilli

No longer supported

In-Store Payment

Paypoint

No longer supported

Booking

Sportsbooker

Supported up to October 2021

    • Related Articles

    • Verifone P400 GPoS Setup

      GPoS Setup Peripheral Setup Open GPoS Utility Open  Programming  >  System Tables  >  Peripherals Click or tap on  Add  , and give the Peripheral an appropriate name, eg “ Verifone ”, “ EFT ”, “ P400 ” etc Set the  Peripheral Type  to  Verifone ...

    • Verifone P400 Overview

      Introduction The P400 terminals are part of the Engage range, which have been introduced by Verifone to replace the VX range, which by the end of 2020 will be retired and discontinued. No additional software is needed, as the terminals communicate ...

    • Euro Payment Key

      Name: Euro Change giving Payment: Cash Monetary: Not Specified Flags: Tender compulsory Rate: 0.8 – Exchange Rate at the time. Example how the payment key works; A customer using a €50 note,  the system would work this out at 50 x (Current Rate) 0.8 ...

    • Verifone P400 Troubleshooting

      Check the Network Connection Check the Network Status 1. Press or touch the blue Verifone banner on the screen 2. Press 2 or touch Supervisor (this screenshot is from a non-integrated terminal, and shows Supervisor as option 3 due to the additional ...

    • GPoS Release Notes

      Pre-Requisites and Integrations Known Issues GPoS Version v1.72.abcd.efgh (Supporting DB Version 172) (Future Version) Type Name Description Feature GPoS - Part Tender to Debitrak Previous versions of Debitrak allowed users to part tender to ...