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, terminal provisioning, batch processing, e-contract workflows, and webhook callbacks from third-party signing providers.
This is v2.31.0 of the Order Service API. See Deprecated APIs for legacy endpoints that should not be used in new integrations.
API Reference
Orders — Common
Search, retrieve, submit, cancel orders; manage e-contracts, order links, and welcome letters
Merchant Orders
Create and update merchant orders; add additional services to existing merchants
POI Orders
Create and update POI (terminal) orders and accessory orders for existing merchants
Merchant Maintenance
Update merchant entities, trading addresses, and create unapproved users
POI Maintenance
Update and delete POIs; manage multi-merchant parent/child relationships
MID/TID Generation
Generate Verifone Merchant IDs and Terminal IDs based on configured ranges
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.
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?