POSgate is a powerful and flexible API that allows POS vendors to implement their solutions using a variety of POS solutions with connectivity options to suit most merchants’ environments. The diagrams below show typical examples of implementations used by POS vendors. If you have a variation in mind that is not shown, please contact us, as there are other options available.
The key component of POSgate is an API that the POS application uses to initiate payment requests to the PINpad. The API provides a simple interface to the POS and hides much of the communications requirements and error handling from the POS application that would otherwise need to be developed by the POS vendor.
POSgate provides many solutions to implementing an integrated solution. In most cases, a driver called PCL is used by POSgate to provide a shared communications layer between the PINpad and POSgate, as well as delivering payment requests to the bank via the POS systems LAN, wifi or 3G/4G data connection.
Phone / Tablet
This implementation is the most common method used to provide an integrated mobile POS solution. The PINpad connects to the tablet using a Bluetooth connection and uses the phone or tablet to provide connectivity to the POS application and the bank for delivering payment transactions.
Using Serial / USB
Many countertop POS systems support either serial or USB as a standard connection option for peripheral devices, such as PINpads. It is also possible to power the PINpad using a USB port. Where the POS is unable to provide power, Ingenico can provide a cable with a power injector.
In this configuration, the PINpad will send all payment messages from the PINpad to POSgate for delivery to the bank via the POS system’s LAN connection.
Using Serial / USB & IP to the Bank
Where the point of sale has a serial connection to the POS and is unable to handle the communications to the bank to process the payment, the PINpad can have an independent connection via Ethernet, wifi or 3G/4G to the bank for transaction delivery.
A common requirement in restaurants and cafés is the need to support multiple PINpads from a single POS system. The POS is able to select which PINpad to send the payment to and initiate a specific payment for a particular table.
In addition, it is also possible to implement a solution where the PINpad can request a payment for a particular table. The PINpad can send this to the POS app and the POS app initiates the payment for that table.