GP Pay – Introduction

About

GP Pay is an application provided by Victory Pay‘ acquiring partner, Global Payments, and it provides card payment functionality on a range of PAX devices.

Integration paths

There are multiple integration paths based on where your software is going to be running.

Your software on Victory Pay terminal

If your app is going to be installed on our terminal, your options are:

Your software on another device on the same local area network

If your app is NOT going to be installed on our terminal, but the device on which it is running will be on the same local area network (e.g. if both devices are on the same Wi-Fi), you can use:

It’s important to make sure the payment terminal is using a static local IP address, as IPs assigned automatically by DHCP server (by the router) can change over time, which would result in your software no longer being able to communicate with our device, until settings in your software are updated.

Static IP can be configured in either of these two ways:

  • Configuring static IP on the device
  • Configuring static IP using WiFi router’s DHCP server

Your software in a cloud

If communication over local area network is not possible due to physical/networking constraints (e.g. your ECR software running in a cloud, and has no access to merchant’s local area network), you can relay requests to the payment app via OneHub Cloud, which provides HTTP request forwarding API.

This integration path is more complicated, as it involves implementing multiple cloud APIs in order to find the correct device you want to communicate with in the cloud, and then the HTTP request forwarding API itself.
You can learn more in the HTTP Request Forwarding API documentation.

Your options regarding protocol used to communicate with the payment app itself are limited when using cloud forwarding API, as only HTTP-based protocols are supported by the cloud.
This means your only option right now is NEXO protocol.