Mojave is now Paying.co — same team and expertise, now with a name that reflects our core mission. Learn more →
PAX Custom Development

Custom solutions, certified on PAX Android terminals.
Built your way.

PAX builds the Android-based terminal lineup powering kiosks, retail counters, unattended payment, and self-service worldwide. Paying.co builds the software that turns those terminals into complete workflow applications — custom forms, multi-step transactions, native PAX Android development, and MDB or Pulse connectors. When EMV Level 3 certification is required, that's a separate workstream we run end to end in the same engagement.

verified 130+ EMV Level 3 certifications · Native PAX Android development · Datacap & processor integration.
paying.co · pax · android build
// Custom Paying.co app launched on PAX Android terminal
[A920 Pro]  workflow → "qsr_self_order"

// PAX payment SDK handles EMV flow natively
[PAX SDK]  tap · insert · swipe
[PAX SDK]  chip read · amount=18.42

// Paying.co routes through Datacap to your processor
[Datacap]  auth request → sent
[Gateway]  approved · ref="txn_D72A"
[A920 Pro]  tip + sign · receipt printed · 1.3s
android
Last transaction
$18.42 · a920-pro-07 · counter
check_circle Approved · PAX Android · EMV L3 certified
130+
EMV L3 Certifications
Android
Native PAX Development
MDB
& Pulse Connectors
100+
Person Engineering Team
PAX Hardware We Build On

One Android platform. Every form factor.

PAX's lineup spans countertop and retail terminals, unattended and outdoor payment kiosks, and mobile and handheld Android POS — all running on the same Android-based PAX platform with rich UI/UX capabilities. Paying.co builds custom applications, workflows, and EMV-certified integrations across the entire range. One engagement, one engineering team, one certification deliverable per processor.

♦ Family 01
point_of_sale

Countertop & Retail

A35 · A50 · A60 · A77

Retail counters, hospitality, and quick-service running PAX's countertop Android terminals — A35, A50, A60, and A77. Paying.co builds custom checkout flows, tipping and split-tender logic, loyalty enrollment, onboarding forms, and the EMV Level 3 certifications that get your application into production.

♦ Android Native ♦ Tipping & Split ♦ EMV L3
Talk to our team arrow_forward
♦ Family 02
storefront

Unattended & Outdoor

IM30 · IK30 · Aries Series

Outdoor-rated payment terminals for vending, kiosks, parking, EV charging, laundromats, and self-service. Paying.co builds the native Android application layer and MDB or Pulse connectors that bridge PAX to the machine. When the deployment also requires EMV Level 3 certification, we run that as a separate, well-scoped workstream alongside.

♦ MDB / Pulse ♦ Outdoor Rated ♦ Unattended
Unattended Systems arrow_forward
♦ Family 03
smartphone

Mobile & Handheld

A920 Pro · A920 Max · A800

Mobile and handheld Android POS for pay-at-table, field service, ridesharing, and queue-busting. PAX's A920 Pro, A920 Max, and A800 lineup — with Paying.co's custom apps, multi-step workflows, loyalty capture, and TMS deployment built on top.

♦ A920 Series ♦ Pay-at-Table ♦ Multi-Step
Mobile Development arrow_forward
What We Actually Build

Custom software. On certified hardware.

PAX builds the Android terminal. Paying.co builds everything that turns it into a deployable workflow application — from the native Android application layer down to the processor integration. One vendor, one engineering team, one engagement scope.

♦ 01
android

Native PAX Android development

Custom applications built native to the PAX Android platform — leveraging modern UI/UX, multi-touch gestures, and the rich application capabilities that come with Android, while integrating directly with PAX's payment SDK and event handlers.

♦ 02
account_tree

Custom forms & workflows

Multi-step transactions, data capture screens, loyalty enrollment, onboarding flows, cross-sell prompts, and guided self-service journeys — designed and built native to PAX terminals, with the kind of UX users actually expect from modern hardware.

♦ 03
device_hub

MDB & Pulse connectors

Custom connectors that bridge PAX terminals with legacy MDB and Pulse machine protocols. Modern cashless acceptance on vending, laundromat, EV, parking, and unattended equipment — no hardware replacement required.

♦ 04
verified_user

EMV Level 3 certification

When EMV cert is part of the project, we run it end to end — in-house, against your processor's test environment, with 130+ L3 certifications already shipped across Visa, Mastercard, American Express, and Discover scripts on PAX hardware.

close With a generic integrator
  • cancelTreats PAX as just another Android device, not a payment platform
  • cancelEMV certification outsourced or limited in scope
  • cancelBasic or unavailable MDB and Pulse protocol support
  • cancelTemplate-based forms, limited custom UX
  • cancelSlow iterations between dev, cert, and deployment
check With Paying.co on PAX
  • check_circleDeep, PAX Android-native development across the full lineup
  • check_circle130+ EMV Level 3 certifications managed in-house
  • check_circleCustom MDB and Pulse connectors for legacy machines
  • check_circleFully custom forms, workflows, and on-terminal UX
  • check_circleOne team across dev, certification, and deployment

The terminal is Android. The application has to deliver.

PAX gave the payment terminal a true Android platform — rich UI, modern application capabilities, fast deployment, and a hardware lineup that covers everything from countertop to outdoor unattended. Operators choose PAX because the hardware is flexible, the ecosystem is open, and the platform is built for custom workflows. The application running on top of it should match that potential.

That's where Paying.co fits. We've completed numerous EMV Level 3 certifications across PAX devices, built custom forms and workflows running natively on PAX Android, and shipped MDB and Pulse connectors that bridge PAX terminals with legacy vending, laundromat, EV charging, and parking equipment. Deep integration experience with Datacap middleware, direct processor connections, and the broader payment gateway ecosystem.

The point is simple: you pick PAX because the Android-based terminal is the right tool for the job. We solve the software problem on top of it — with one team, one statement of work, and one certified deliverable per processor.

Talk to our PAX team arrow_forward
Under the Hood

Native to PAX Android. Connected to your stack.

We build where PAX actually wants applications built — native to the Android platform, integrated directly with the PAX payment SDK, and certified end-to-end through the processor's test environment. No wrappers, no middleware in the middle charging rent. The application is yours, the certification is yours, the source is documented.

  • android

    PAX Android SDK

    Direct integration with the PAX payment SDK, BroadPOS, and the Android application framework. Modern UI, multi-touch, system permissions, and rich Android capabilities — layered on top of a certified payment foundation.

  • hub

    Datacap & processor integration

    Seamless integration with Datacap middleware (NETePay, dsiEMVUS), direct processor connections, and gateways like Worldnet, BridgePay, Cardknox, and CardConnect. The connector layer is well-trodden ground for us — not a research project.

  • device_hub

    MDB & Pulse connectors

    Custom connectors that bridge PAX terminals with MDB (Multi-Drop Bus) and Pulse machine protocols. Modern cashless acceptance on traditional vending, laundromat, parking, EV charging, and unattended equipment — no hardware replacement required.

  • cloud_sync

    TMS fleet deployment

    PAXSTORE and Terminal Management System integration for remote deployment, configuration, and updates across your entire PAX fleet. New features and security patches pushed remotely — no physical access required to each terminal.

end-to-end · example: A920 Pro → Datacap → processor
// 1. Customer taps card on PAX A920 Pro at counter
[A920 Pro]  contactless · amount=18.42

// 2. PAX payment SDK handles EMV flow on Android
[PAX SDK]  chip read · cvm bypassed · approved
[PAX SDK]  app select → "Visa Contactless"

// 3. Paying.co application routes via Datacap
[Paying.co]  workflow → "qsr_singleshot"
[Datacap]  auth request → sent

// 4. Approved — tip prompt, receipt, settle
[Gateway]  approved · ref="txn_D72A"
[A920 Pro]  tip + sign · receipt printed
// Done. 1.3s end-to-end. Native PAX Android.
Processors & Middleware

Already on a processor we work with? We're already there.

Paying.co has shipped EMV-certified PAX integrations across the gateways and middleware that matter for retail, unattended, and mobile environments — Datacap, Worldnet, BridgePay, Cardknox, and CardConnect, plus direct integrations into the major processors. If your business already routes through one, we drop into that flow. Need a direct processor cert? That's our specialty.

Native integration
hub

Datacap

Deep, production-shipped integration with Datacap's NETePay and dsiEMVUS middleware on PAX terminals. The most widely deployed payment gateway in North American retail and unattended — and one we know cold.

Native integration
cloud

Worldnet

Direct integration with Worldnet's payment gateway and unattended processing rails. Certified flows on PAX hardware, configured for the international and multi-currency deployments Worldnet specializes in.

Native integration
memory

BridgePay

Native integration paths into BridgePay's gateway and tokenization platform. Built and certified on PAX terminals for ISV and ISO partners who route their volume through BridgePay.

Native integration
payments

Cardknox

Direct integration with the Cardknox gateway and developer platform. Production-shipped on PAX hardware with full EMV L3 certification and tokenization support for retail and unattended.

Native integration
credit_card

CardConnect

Built to CardConnect's CardPointe and CoPilot platforms. We've certified PAX terminals into CardConnect's processing rails for ISV partners and direct merchant deployments alike.

Custom build
alt_route

Direct processor cert

Need a direct EMV Level 3 certification straight to TSYS, Worldpay, Fiserv, Global, Elavon, or another acquirer? That's our day job. 130+ L3 certs shipped across the Western Hemisphere.

Where PAX Goes

PAX Android, across every vertical.

PAX's Android-based lineup powers retail counters, vending floors, parking lots, transit gates, restaurants, and self-service kiosks. Paying.co builds the application and workflow layer for those same environments — certified, deployed, and supported as one engagement.

local_parking

Parking & Transit

Unattended payment kiosks for parking garages, transit systems, and tolling infrastructure on PAX outdoor-rated hardware.

shopping_cart

Self-Service Kiosks

Custom checkout flows for self-ordering, retail, and food service kiosk deployments running native on PAX Android.

local_gas_station

Vending & Petroleum

Unattended payment terminals for vending machines, EV charging, and fuel dispensers — with MDB and Pulse connectors bridging legacy equipment.

confirmation_number

Ticketing & Events

Guided multi-stage user journeys for ticket purchase, event check-in, and access control on PAX terminals.

store

Retail POS

Custom POS applications with loyalty capture, onboarding forms, and advanced payment workflows on countertop PAX terminals.

restaurant

Restaurant & QSR

Self-ordering terminals and pay-at-table flows with tipping, splitting, and integrated kitchen display connectivity.

local_laundry_service

Laundry & Services

Pay-per-use terminals for laundromats, car washes, and other service-based businesses with Pulse and MDB protocol support.

apartment

Property Management

Tenant payment kiosks, visitor check-in, and package locker access terminals built on the PAX Android platform.

How We Deliver

From concept to deployment.

Every Paying.co PAX engagement runs against a documented Statement of Work, with named owners on both sides, a defined certification milestone, and a deployment plan. Custom forms and workflows land in 4–8 weeks. MDB and Pulse connector projects land in 8–16 weeks. EMV Level 3 certification — a separate workstream with its own scope — typically runs 6–12 months depending on processor and card brand scope. You always know where the project stands.

forum
♦ Step 01

Discovery & requirements

We understand your business needs, target use cases, and existing infrastructure. Our team evaluates the right PAX hardware family — countertop, unattended, mobile — and maps the workflow architecture for your specific deployment scenario.

brush
♦ Step 02

Design & prototyping

Custom forms, multi-step workflows, and user interfaces optimized for PAX Android terminals. Interactive prototypes validate the user journey on actual hardware before we commit to full development.

build
♦ Step 03

Native development & integration

Our engineers build PAX-native Android applications with seamless Datacap, processor, and middleware integration. Payment logic, backend connectivity, MDB/Pulse connectors, and compliance handled across the build cycle.

verified_user
♦ Step 04

EMV certification & testing

When certification is in scope, we run the complete EMV Level 3 process across PAX devices — Visa, Mastercard, American Express, Discover — ensuring end-to-end compliance with all card brands and the processor's test environment before go-live.

rocket_launch
♦ Step 05

Deployment & support

Applications deploy across your PAX fleet via PAXSTORE and TMS integration. Ongoing monitoring, updates, and technical support — smooth operation across unattended, kiosk, and retail environments.

handshake
♦ Step 06

One team, ongoing

Same engineers, same project manager, same EMV cert team for the life of the application. When your processor releases a script update or PAX publishes a firmware change, you have a phone number that already knows your stack.

Ready to Get Started?

Talk to our team.

Tell us what you're building on PAX. We'll tell you what it takes to get it certified, integrated, and shipped — and you'll hear back from a payments engineer, not a sales rep.

schedule
Response within one business day Most projects start with a 30-minute scoping call
engineering
You'll talk to an experienced sales engineer The person you brief is the person who scopes your build
handshake
No-obligation feasibility review We'll help you scope it and determine the best path forward that matches your budget and timeline
language
We speak your language English, Spanish, and Polish — fluent across our team and project leads
groups
Partners power our growth Much of our success comes from strong partnerships — if you're exploring one, we'd love to talk