PAX Development

PAX Application Development and Payment Integration

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.

ILLUSTRATIVE · APP LAYERCustom workflow on a PAX Android device.Example flow: loyalty capture, transaction, tip, receipt. Screens are illustrative, not a specific delivered project.
EXAMPLE ORDERQuick Service
SAMPLE
WORKFLOW STEP 03 / 05

Payment

Tap, insert or swipe to continue.

Amount due$18.42Sample data
PAX ANDROID
PAX ANDROID SDKPAYMENT INTEGRATIONMDBPULSEDEPLOYMENT
Native Androidapplications on PAX devices
Defined pathsSDK, gateway, processor
MDB + Pulsefor supported equipment
Certification optionalassessed for your scope
01 · Devices and deployment environments

Handheld, countertop, and unattended PAX devices.

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.

FAMILY 01

Countertop and retail

A35 · A50 · A60 · A77

Retail, hospitality and quick service workflows such as custom checkout, tipping, split tender, loyalty and onboarding.

ANDROID NATIVECHECKOUT
FAMILY 02

Unattended and outdoor

IM30 · IK30 · ARIES

Vending, parking, EV, laundry and self-service environments, connected to supported equipment through MDB or pulse interfaces.

MDB / PULSEUNATTENDED
FAMILY 03

Mobile and handheld

A920 PRO · A920 MAX · A800

Pay-at-table, field service and queue-busting workflows with multi-step flows and remote deployment.

HANDHELDPAY-AT-TABLE
02 · What we build

Applications that turn PAX hardware into a business tool.

The device is the starting point. We build the software around it, scoped to your confirmed requirements.

01

Native PAX Android applications

Applications built against the PAX Android SDK, with checkout workflows, loyalty, data capture, onboarding, and guided self-service journeys.

02

Backend connectivity

Connections from the device application to your POS, backend, and reporting systems, plus supported peripherals where the device and SDK allow.

03

MDB and pulse equipment connectivity

Connections between PAX devices and compatible vending, laundry, parking, EV, and similar equipment, covered in the equipment section below.

04

Testing and certification options

Application QA, device and provider validation, and, where your scope requires it, EMV Level 3 certification as a separate workstream.

03 · Payment integration paths

Different paths, different responsibilities.

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.

PATH 01Device SDK or payment application

Use a supported payment application or SDK on the device, with your application around it.

PATH 02Gateway or middleware

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.

PATH 03Direct processor work

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.

04 · Application versus certification

Does your application need a new certification?

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.

Q1

Existing integration?

Does the application use an existing supported payment application or integration as it is?

Q2

Custom payment work?

Does it require custom payment integration work?

Q3

Changes needing review?

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.

05 · Equipment integration and SoftPOS

MDB, pulse, and commercial Android devices.

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.

SUPPORTED EQUIPMENTMDB Pay Connect

Payment connectivity for supported MDB vending and unattended equipment.

SUPPORTED EQUIPMENTPulse Pay Connect

Payment connectivity for supported pulse-based equipment such as laundry and car wash.

SEPARATE PATHCommercial Android COTS

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.

06 · How we deliver

From concept to deployment.

01

Discovery

Use case, device, OS and firmware, SDK access, processor, region, and workflow requirements.

02

Design and prototype

Interactive flows validated on the actual PAX device.

03

Development

Android application, payment logic, backend connectivity, and equipment work where applicable.

04

Testing and certification

Application QA and device and provider validation. EMV certification is a separate workstream when required.

05

Signing and distribution

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.

06

Handoff and support

Ownership, documentation, maintenance, and support terms are set in the engagement agreement.

Common questions

PAX development, answered plainly.

Do all PAX models and firmware versions work with the same integration?
No. Support depends on the device model, OS and firmware, SDK or payment application, processor, and region. A delivery on one model does not establish support for every model in a family. We confirm the exact combination during scoping.
Does a custom PAX application need a new EMV Level 3 certification?
Not necessarily. It depends on whether the application uses an existing supported payment integration unchanged, or changes the payment application, transaction behavior, or device configuration in ways that need an approval review. We assess the actual scope with you. Where a certification is required, it is a separate engagement option, and approval activities performed by external parties are not ours to promise or time.
Can you connect a PAX device to a vending or laundry machine?
For supported equipment, yes, through MDB or pulse interfaces. It needs compatible interface hardware, a compatible machine or controller, and configuration. See MDB Pay Connect and Pulse Pay Connect for products, and note that licensing software alone does not supply every component a deployment needs.
Do you use PAXSTORE for deployment?
Yes. PAXSTORE is PAX's official distribution platform, and we use it for signing, provisioning, distribution, and updates. Account access, platform restrictions, and who holds which access are confirmed during scoping.
Who owns the application and documentation?
Ownership, documentation, handoff, and maintenance terms are set in the engagement agreement.
Scoping inquiry

Tell us which PAX device and payment environment you're building for.

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.

Start your project

Sales online

Tell us about your project — we route you to the right specialist.

person
error_outlinePlease enter your name.
business
mail
error_outlinePlease enter a valid email address.
call
link
tune
error_outlinePlease tell us a bit about your project.

lock Your details go straight to our sales engineers — never shared or sold.