PAX Direct Integration
Register, configure, and integrate PAX terminals through the developer.pax.us platform and the VTX-HC application — for semi-integrated PAX deployments on Priority's gateway.
Use the PAX Direct Integration path when your deployment requires a PAX terminal running the VTX-HC payment application. Your software integrates with PAX directly through their developer platform; Priority processes the resulting payment through the MX Gateway and settles it under the merchant's MID.
Who this is for — ISVs building point-of-sale software that drives semi-integrated PAX terminals for merchants on Priority's gateway.
Supported PAX Devices
PAX offers both semi-integrated and standalone device families. Semi-integrated devices on this list can also be deployed in standalone mode.
| Device | Semi-Integrated | Standalone |
|---|---|---|
| S920 | ✓ | ✓ |
| A920 | ✓ | ✓ |
| A920 Pro | ✓ | ✓ |
| A80 | ✓ | ✓ |
| S80 | — | ✓ (existing devices may be reprogrammed; not available for new purchase) |
For standalone-only deployments, see Standalone Terminals.
What Makes the PAX Path Different
| Aspect | Detail |
|---|---|
| Integration model | Direct integration with PAX — not cloud-based |
| Application | VTX-HC — PAX's certified payment application for Priority's gateway |
| Registration | Required at developer.pax.us before development begins |
| Settlement | Through Priority's MX Gateway under the merchant's MID |
Step 1 — Register with PAX
Before writing integration code, register on PAX's developer platform.
- Go to
developer.pax.usand complete registration. - During registration, list Katelyn Torrey (
[email protected]) as your PAX Sales Representative. Naming her on the registration expedites approval. - PAX provides access to the VTX-HC application and the materials needed for semi-integrated development.
Step 2 — Activate the Terminal Through Priority
Once registration with PAX is in motion, open the activation request on Priority's side. This triggers the file build and links the device to the merchant's MID.
- Open a case in MX Connect and submit an Equipment Order Form.
- Include:
- Device serial number
- Terminal parameters
- Note explicitly in the case that this is a "MX Merchant PAX File" — this label routes the case to the correct file build path.
For the broader provisioning lifecycle that the case feeds into, see Provisioning a Terminal: From Application to Live.
Compatible MX Gateway Features (Semi-Integrated Only)
When deployed semi-integrated, PAX devices on this path are compatible with the following Priority gateway features:
| Feature | Availability |
|---|---|
| MX B2B Interchange Optimizer | Semi-integrated only — available via MX Gateway |
| MX Advantage for Surcharging | Semi-integrated only — available via MX Gateway |
These features are not available on PAX devices deployed in standalone mode.
Pricing
Current PAX device pricing is available in MX Connect → Document Library → PPS Equipment Pricing.
Support
PAX devices on this path are Class A certified. Priority provides device and integration support at:
1-844-647-3616
Where to Go Next
Overview of all Vendor-Direct paths and the responsibility split with Priority.
The shared eight-stage onboarding flow your PAX activation runs through.
For PAX deployments that don't need a software integration.