Choose Your Integration Path

Pick your in-person integration path before you order hardware or finalize the Equipment Order Form. The path you choose determines who builds the terminal-facing software, which registry the device is provisioned to, and how much manufacturer-specific work your team owns.

📌

Who this is for — ISVs scoping their build, Partners advising merchants on hardware selection, and Priority internal teams routing setup requests to the right file-build queue.

The Decision in One Table

Regardless of path, every transaction lands in the same MX Gateway and settles to the same MID. The differences are upstream of authorization, not downstream.

Decision Flow

Walk through these three questions in order. Each answer either lands you on a path or moves you to the next question.

1. Does your software need to drive the terminal?

No — staff will key amounts directly on the terminal, and you don't need your POS to initiate or confirm transactions → choose Standalone.

Yes → proceed to question 2.

2. Is your device family supported by the Priority Terminal API?

Check the Device-to-Path Quick Reference below.

Yes — and you don't need manufacturer-specific device features → choose Priority Terminal API. You'll integrate against a single Priority API surface across all supported device variants.

No → you're in Vendor-Direct territory. Proceed to question 3.

3. Which manufacturer is your device from?

Each Vendor-Direct path has its own registration, SDK, and onboarding contact:

• PAX → Register at developer.pax.us and integrate against the VTX-HC application. See PAX Direct Integration.
• Clover → Provisioning is managed in Clover Dashboard; the Setup Request requires the Clover Addendum. See Clover Direct Integration.

Device-to-Path Quick Reference

Full device specifications — including connectivity, entry modes, and encryption — are in Supported Terminal Devices.

What You Build vs. What Priority Manages

Trade-Offs to Weigh

Before committing to a path, factor in the following.

Speed to Market

Priority Terminal API is the fastest path when your device family is supported — a single API surface, no vendor registration, no SDK download. Vendor-Direct adds vendor registration, relationship management, and SDK integration time. Standalone is the fastest of all when no software integration is needed.

Customization

Vendor-Direct unlocks manufacturer-specific device behavior and app integrations that the Priority Terminal API does not expose. Choose Vendor-Direct when those features are part of the merchant's requirements.

Vendor Relationship

Priority Terminal API lets you work entirely through Priority — no separate vendor account or sales relationship is required. Vendor-Direct requires registering with the manufacturer (for example, developer.pax.us for PAX) and typically a named sales contact on the manufacturer's side. Standalone sits between the two — no developer registration, but the Partner still coordinates with Priority on hardware.

Ongoing Support

Priority Terminal API support is funneled through Priority Customer Care and the File Build Team. Vendor-Direct support is split — Priority handles processing and settlement issues; the manufacturer handles device firmware, SDK, and hardware support. Standalone sits with Priority for processing and with the manufacturer for device-level issues.

Where to Go Next