How to Build

Before writing code, make two decisions: which integration type fits your use case, and which device to start with. These determine your architecture, API access, and testing requirements.

Choose your integration type

How your app interacts with the Moneris Go payment flow determines which integration path you take.

Add your value-added service to the Moneris Go payment flow

Built a loyalty program, gift card platform, or donation service? Commerce API is how you bring it to the Moneris Go payment flow — hooking into the payment flow at defined points and activating at the moment of payment, without disrupting the native transaction.

  • Loyalty programs
  • Gift cards
  • Donations And more
Explore Commerce API documentation

Building the end-to-end merchant experience on the terminal?

Explore App-to-App Integration


Target devices

You can start with any device and build from there. We require apps to support all devices in the Moneris Go portfolio — ensuring a consistent experience for every merchant across our hardware ecosystem.

Browse devices and full specifications

Apps can be published to all device marketplaces regardless of integration type. If you are building with Commerce API:

Check Commerce API compatible devices

Supported Devices

VendorDevices Dev SetupMarketplace
IngenicoDebug - required
QA - required
Both debug and QA required — QA cannot be tested on debug due to App Store limitations
Ingenico Marketplace
PAXDebug - required
QA - optional
PAX Marketplace

Did this page help you?