PAX builds the Android terminal. Paying.co builds the software that runs on it: custom applications, payment integration, device workflows, and deployment. Where a project requires it, EMV Level 3 certification is available as a separate engagement option. Not every application needs a new certification project.
Tap, insert or swipe to continue.
We build the application and integration layer around your deployment instead of forcing one generic terminal flow everywhere. The models below are the families we work with. Support for a specific model depends on its OS and firmware, the SDK or payment application, the processor, and the region. A delivery on one model does not establish support for every model in a family.
Retail, hospitality and quick service workflows such as custom checkout, tipping, split tender, loyalty and onboarding.
Vending, parking, EV, laundry and self-service environments, connected to supported equipment through MDB or pulse interfaces.
Pay-at-table, field service and queue-busting workflows with multi-step flows and remote deployment.
The device is the starting point. We build the software around it, scoped to your confirmed requirements.
Applications built against the PAX Android SDK, with checkout workflows, loyalty, data capture, onboarding, and guided self-service journeys.
Connections from the device application to your POS, backend, and reporting systems, plus supported peripherals where the device and SDK allow.
Connections between PAX devices and compatible vending, laundry, parking, EV, and similar equipment, covered in the equipment section below.
Application QA, device and provider validation, and, where your scope requires it, EMV Level 3 certification as a separate workstream.
A PAX deployment can take payments in several ways. Which one fits depends on your processor, region, and what the device supports. We distinguish them, because they carry different approval and ownership implications.
Use a supported payment application or SDK on the device, with your application around it.
Integrate through a gateway or middleware layer. Paths we have worked with include Datacap, Worldnet, BridgePay, Cardknox, and CardConnect. Availability depends on the device, region, and your agreement.
Custom integration directly with a processor or acquirer, when your scope calls for it. Scope and approvals are defined per processor.
See Native Android vs. Flutter or React Native for Payment Applications for how SDK restrictions can shape architecture, and Mobile App Development for our broader application services.
It depends on the scope. We assess three questions together with you, and we describe our engineering and coordination work separately from approval activities performed by external parties. We do not make universal approval or timing promises.
Does the application use an existing supported payment application or integration as it is?
Does it require custom payment integration work?
Does it change the payment application, transaction behavior, or device configuration in ways that need an approval review?
Where certification is needed, see EMV Certification. Paying.co's 133 EMV Level 3 certifications are company-wide across hardware and acquirers. They are not a count of PAX-specific projects. See also the Payment Application Testing Checklist.
Connecting a PAX device to a machine needs compatible interface hardware, a compatible machine or controller, software, and configuration. Licensing software alone does not supply every component of a deployment. Payment approval, machine activation, and fulfillment feedback are separate events.
Payment connectivity for supported MDB vending and unattended equipment.
Payment connectivity for supported pulse-based equipment such as laundry and car wash.
For commercial Android devices using their own supported device-specific SoftPOS implementation. Not every PAX device uses SoftPOS, and this path is separate from the PAX payment integration paths above.
Use case, device, OS and firmware, SDK access, processor, region, and workflow requirements.
Interactive flows validated on the actual PAX device.
Android application, payment logic, backend connectivity, and equipment work where applicable.
Application QA and device and provider validation. EMV certification is a separate workstream when required.
Applications are distributed through PAXSTORE, PAX's official distribution platform, covering signing, provisioning, updates, and configuration. Account access and platform restrictions are confirmed with you during scoping.
Ownership, documentation, maintenance, and support terms are set in the engagement agreement.
Share the device model and OS or firmware, SDK or payment application and access, gateway or processor and region, required workflows and transaction types, peripheral and machine interface needs, existing application and backend status, deployment size and distribution method, target date, and any known approval or certification requirements.
Tell us about your project — we route you to the right specialist.