Gateway, orchestrator and acquirer: who does what in a digital payment?
Alpha Insights | Operational insight updated on 17 November 2026.
Distinguish the functions
Payment gateway, orchestrator and acquirer are sometimes used as if they described the same service. For project design, distinguish their functions: the gateway provides the technical integration point; orchestration coordinates connections and rules across services; acquiring concerns a merchant's acceptance of card payments within the relevant scheme and contractual framework.
One provider may cover several functions. Its platform name therefore does not identify every responsibility. Contracts, technical documentation and the operating model should describe the same arrangements.
Follow the payment lifecycle
Provider documentation distinguishes different transaction stages and statuses. A checkout outcome, subsequent transaction processing and financial reporting serve different purposes. The integration should cover the complete lifecycle and later events that may affect the operation.
Separate four questions: who receives the request, who routes it, who supplies the outcome and who provides accounting data? A single customer interface can sit above several different providers.
Build a responsibility matrix
Contracts and pricing for each function.
Merchant relationship ownership and support channels.
Handling of tokens, notifications, refunds and uncertain outcomes.
Transaction files and settlement reporting.
Coordination during incidents and service changes.
Evaluate orchestration against the use case
Orchestration may be useful when a business needs to coordinate multiple providers or payment methods. Assess its value against the actual complexity: connections to maintain, rules to govern, reporting coverage and exception management.
Alternative routing requires care when an outcome is uncertain. Before repeating a request, establish whether the previous operation was executed and how duplication will be prevented. Agree this with providers and test it.
Alpha's operational perspective: selecting suppliers from a map of functions produces more comparable offers. Architecture quality also depends on how clearly teams can respond when a transaction takes an unexpected path.
Sources and references
The sources describe the referenced frameworks and services; the design recommendations reflect Alpha's operational perspective.


Comments