Order Service
The Order Service API enables partners and integrators to order hardware and services, provision and board devices, and manage the full lifecycle of merchant and POI entities. It supports merchant onboarding, additional service ordering, terminal provisioning, batch processing, e-contract workflows, and webhook callbacks from third-party signing providers.
API Reference
Order Management
Maintenance
For retired endpoints, see Deprecated APIs.
Internal
These endpoints are for Verifone internal use.
Internal
Verifone-internal account, status, and maintenance workflow endpoints
Users
Create unapproved merchant users for existing customer entities
MID/TID Generation
Generate Verifone Merchant IDs and Terminal IDs based on configured ranges
Purchased TIDs
Manage pre-purchased TID pools — insert, list, reserve, and update allocation status
Reseller Event Data
Manage reseller-scoped event data records used during order submission
Oracle Accounts
Search, add, update, and delete Oracle billing accounts
Batch
Verifone internal batch operations for merchant and POI maintenance
Key Concepts
An order is a collection of instructions for provisioning and ordering applications and hardware. Orders go through a draft state before being submitted for processing.
A merchant is the person or entity taking payments for goods and services. A customer is an acquirer, merchant, or other entity being charged for hardware or services from Verifone.
A service is a subscribed application, payment feature, or hardware lifecycle add-on. Additional Services let you attach these services to an existing merchant without creating a full merchant onboarding order.
The Point of Interaction (POI) refers primarily to the logical terminal — the device through which a payment is initiated and processed.
An acquirer is a bank or financial institution that processes card payments on behalf of merchants. In the Verifone model, acquirers are typically direct Verifone customers whose merchants are not.
Last updated
Was this helpful?
