Accept In-Person Payments
Process card-present payments through certified terminals — across three integration paths, under a single merchant account.
Accepting card-present payments at Priority involves more than a single API call. It connects merchants, partners, terminal manufacturers, and several Priority teams across hardware provisioning, file builds, and live transaction processing. This page maps the full picture so you can find the right integration path, the right contact, and the right next step before you build.
Who This Section Is For
Use the callout that matches your role to navigate the rest of the docs.
ISVs and Developers
You're building software that drives a terminal on behalf of a merchant. Start at Choose Your Integration Path to identify whether you'll call the Priority Terminal API directly, integrate with the manufacturer's SDK, or support a standalone deployment.
Partners and Resellers
You're onboarding merchants, ordering terminals, and coordinating activation. Start at Provisioning a Terminal: From Application to Live for the case workflow, file build process, and Equipment Order Form path.
Merchants
You're the business owner accepting payments. Most of this content is aimed at your partner or developer — but Supported Terminal Devices gives you the device options to discuss with your partner.
The Three Integration Paths
Priority supports three distinct integration models for in-person payments. The path you choose determines who initiates transactions, who owns the device-side experience, and how the device reaches the card network.
Priority manages device communication. Your application calls the Priority Terminal API to initiate transactions, poll for status, and retrieve payment records. Best for ISVs and merchants using Priority-supported devices such as Dejavoo Z-series, AnywhereCommerce Nomad, and select Valor models.
Your application integrates directly with the terminal manufacturer's SDK or platform — for example, PAX VTX-HC via developer.pax.us, or Clover Dashboard. Priority processes the resulting payment through the MX Gateway. Best for deployments that require manufacturer-specific features or device families that do not run through the Priority Terminal API.
The terminal operates independently — no software integration. The merchant accepts payments on the device itself, and transactions flow into Priority for settlement and reporting. Best for merchants who do not need a POS or ordering system to drive the terminal.
A full decision guide — including a device-to-path lookup — is in Choose Your Integration Path.
What Priority Manages Across All Three Paths
Regardless of the path you choose, Priority handles the same core functions:
| Function | What Priority Provides |
|---|---|
| Merchant account (MID) | Underwriting, approval, and ongoing maintenance of the merchant identifier. |
| Gateway processing | Authorization routing to card networks through the MX Gateway. |
| Settlement and funding | Batch close, settlement, and merchant funding to the configured account. |
| Reporting | In-person and card-not-present transactions appear under the same MID in MX Merchant. |
| Support escalation | Priority Account Management, Customer Care, and — where applicable — the File Build Team. |
What differs between paths is who initiates the transaction and who owns the device-side experience — not whether Priority processes the payment.
The Terminal Lifecycle at a Glance
Before any terminal can accept a payment, it moves through a sequence of provisioning steps that involve the partner, Priority's internal teams, and — for some paths — the terminal manufacturer.
- Application submitted — Partner submits the merchant application through MX Connect.
- Underwriting decision — Account is reviewed and approved; MID and T-number are issued.
- Setup request opened — Partner submits a case with the Equipment Order Form and any vendor-specific addendums.
- File build — Priority's File Build Team configures the terminal file in FDPOS — or opens a ticket with Fiserv for Bypass front-end accounts.
- Hardware order placed — Device ordered through Priority's internal inventory system, or fulfilled by the partner if they hold stock.
- Shipment — Device ships with tracking and serial number recorded on the case.
- Device provisioning — Serial number is linked to the T-number in the appropriate registry (Clover Dashboard, vendor portal, or Priority's terminal registry).
- Activation and billing — Device powers up ready to transact; invoicing reflects the order form terms.
The full step-by-step — with named actors, systems, and edge cases like partner-managed inventory and Bypass front-end builds — is in Provisioning a Terminal: From Application to Live.
Key Actors
Knowing who does what avoids most onboarding delays. Every in-person integration involves some combination of the following:
| Actor | Role | Primary Systems |
|---|---|---|
| Merchant | Owns the storefront accepting payments. | MX Merchant |
| Partner / Sales Rep | Submits the merchant application, requests terminals, coordinates setup. | MX Connect |
| ISV / Developer | Builds the integration that drives the terminal (Priority Terminal API or Vendor-Direct). | Priority Terminal API, vendor SDKs |
| Priority Underwriting | Reviews and approves the merchant account; issues MID and T-number. | Underwriting platforms behind MX Connect |
| Priority File Build Team | Builds the terminal file in FDPOS, or opens a Fiserv ticket for Bypass front-end accounts. | FDPOS, Fiserv |
| Priority Fulfillment | Orders hardware and triggers warehouse shipment. | Internal order site, NetSuite |
| Priority Account Management | Issues credentials, confirms activation, escalates blockers. | — |
| Terminal Vendor | Manufactures the device. For Vendor-Direct paths, also hosts the developer portal — for example, developer.pax.us. | Vendor portals |
Where to Go Next
Walk the full lifecycle from merchant application to a device taking its first payment.
Decide between Priority Terminal API, Vendor-Direct, and Standalone — with a device-to-path quick lookup.
See every device Priority supports, its integration path, entry modes, and connectivity.