Clover Direct Integration
Set up Clover deployments through Priority — Clover Setup Request, Clover Addendum, file build, hardware fulfillment, and final provisioning in Clover Dashboard.
Use the Clover Direct Integration path when your deployment uses Clover devices. Clover deployments require a dedicated Setup Request, the Clover Addendum, and final provisioning in Clover Dashboard — but processing, settlement, and reporting still happen through Priority's MX Gateway under the merchant's MID.
Who this is for — Partners onboarding merchants on Clover, and ISVs whose integration relies on Clover's device application ecosystem.
What Makes the Clover Path Different
Compared to the Priority Terminal API and other Vendor-Direct paths, Clover introduces vendor-specific requirements at several stages of the provisioning lifecycle:
| Lifecycle stage | Clover-specific requirement |
|---|---|
| Setup Request (Stage 3) | Dedicated Clover Setup Request case type in MX Connect — plus the Clover Addendum and the Clover Equipment Order Form. |
| File Build (Stage 4) | Built by Priority's Clover File Build Team in FDPOS. Bypass front-end accounts require a Fiserv ticket. |
| Provisioning (Stage 7) | Final serial-to-T-number linking happens in Clover Dashboard — not in Priority's terminal registry. |
The shared lifecycle stages (Application → Underwriting → Hardware Order → Shipment → Activation → Billing) are documented in full at Provisioning a Terminal: From Application to Live.
Step 1 — Open the Clover Setup Request
Once the merchant is approved through underwriting (Stage 2 of the lifecycle), the Partner opens the Clover-specific Setup Request case in MX Connect.
Required documents:
| Document | Required | Notes |
|---|---|---|
| Clover Addendum | Required | Currently under legal review for possible removal or merge into the Equipment Order Form. Required today regardless. |
| Clover Equipment Order Form | Required unless Partner-managed inventory | Specifies the Clover devices being ordered and ordering terms. Skipped if the Partner stocks Clover devices themselves — see Partner-Managed Inventory below. |
Once submitted with all required documents, the case routes to the Clover File Build Team.
Step 2 — File Build
The Clover File Build Team manually builds the T-number file in FDPOS — Priority's file build platform.
Bypass front-end variation — On Bypass front-end accounts, Priority does not have direct file-build access. The Clover File Build Team opens a ticket with Fiserv to create the file, which introduces additional delay. Flag Bypass cases early.
Step 3 — Hardware Fulfillment
Standard fulfillment runs through Priority's internal order site:
- The Clover File Build / Fulfillment coordinator places the order on Priority's internal order site. Inventory is tracked in NetSuite.
- Warehouse ships the device. Orders placed before approximately 3:00 PM generally ship the same day.
- Serial numbers and tracking are posted to the Setup Request case.
Partners cannot place orders on Priority's internal order site directly.
Step 4 — Provisioning in Clover Dashboard
This is the Clover-specific final step. The shipped device's serial number is linked to the T-number in Clover Dashboard — not in Priority's terminal registry.
| Who provisions | When |
|---|---|
| Clover File Build Team | Standard path — Priority operates Clover Dashboard for the Partner. |
| Partner | If the Partner has direct Clover Dashboard access (typically Partner-managed inventory deployments). |
Critical dependency — Provisioning must complete before the device arrives at the merchant. A delivered-but-unprovisioned Clover device will not be plug-and-go and will require a remote push to recover.
Step 5 — Activation and Billing
Once provisioned, the device boots ready to transact when the merchant powers it on. Priority Finance issues the invoice via NetSuite based on the terms captured in the Clover Equipment Order Form — or per Partner inventory terms if the Partner is invoicing directly.
Partner-Managed Inventory
Some Partners stock Clover devices themselves and have direct access to Clover Dashboard. This is a common variation worth understanding before opening the Setup Request.
What changes for Partner-managed inventory:
| Stage | Change |
|---|---|
| Setup Request | Partner may submit the file build request without the Clover Equipment Order Form. |
| Hardware Order | Skipped — Priority does not place the order. |
| Shipment & Tracking | Managed by the Partner directly. |
| Provisioning | Partner performs serial-to-T-number linking themselves in Clover Dashboard. |
| Billing | Follows the Partner's inventory terms, not the Clover EOF. |
Subscription Program
Priority offers a Subscription Program for Clover deployments. Program details, eligibility, and partner materials are maintained in MX Connect → Document Library under the Clover section. [verify — link to in-Product-Hub Subscription Program page once published]
Multi-Business-Unit Note
Merchants running Clover alongside other Priority terminal solutions (for example, MXPOS or standalone terminals) will have separate hardware sites, MIDs, and inventory paths per business unit — driven by accounting and inventory segregation, not by terminal architecture. One application per BU; reporting in MX Merchant is per-MID, with no automatic cross-BU consolidation.
Where to Go Next
Overview of all Vendor-Direct paths and the responsibility split with Priority.
The shared eight-stage onboarding flow your Clover activation runs through.
Confirm Clover is the right path for your deployment before opening the Setup Request.