Payment orchestration is a software layer that connects a merchant to several payment service providers, acquirers and payment methods through one integration and decides where each transaction goes. Checkout sends every payment to the orchestration API; card data sits in the orchestrator's PSP-agnostic vault, a rules engine picks a provider by card IIN, country, currency, amount, cost and live approval rate, and soft declines are retried on a second provider where scheme rules allow. Settlement files from all providers are normalised into one view. Adding a PSP becomes configuration rather than development. Because it stores card numbers, the orchestrator must be a PCI DSS Level 1 service provider, and one that collects and pays out funds needs a payment licence.
What is payment orchestration, and why merchants use it
A merchant with one PSP depends on that PSP's approval rates, pricing, uptime and country coverage. Adding a second PSP directly means building and maintaining a second integration, a second card vault and a second reconciliation process. Orchestration makes adding a provider a configuration task rather than a development project.
Typical reasons to adopt it: selling in markets where local acquiring improves approvals, cutting fees by routing to the cheapest provider per card type, and avoiding downtime when one processor fails.
How does payment orchestration work
- Checkout sends the payment to the orchestration API, often as a single unified payment intent.
- Card data is stored in the orchestrator's own PSP-agnostic vault, so it can be sent to any connected processor.
- A routing rules engine picks a provider based on card IIN, country, currency, amount, cost and each provider's current approval rate.
- The request is translated into that provider's API format by a provider abstraction layer.
- If the provider returns a soft decline or times out, cascading retries the payment on a second provider where scheme rules allow it.
- Results, fees and settlement files from all providers are normalised into one reporting view.
Example: what routing is worth
A merchant processing €10 million a month at an 88% approval rate declines €1.2 million of attempted payments. If routing domestic cards to local acquirers and retrying soft declines lifts approvals to 90%, the merchant captures an extra €200,000 in monthly sales. Shaving 0.1 percentage points off processing cost on the same volume saves €10,000 a month.
Payment orchestration platform explained
A payment orchestration platform is usually sold as SaaS, with a per-transaction or monthly fee, and includes connectors to dozens or hundreds of PSPs, alternative payment method integrations, a 3-D Secure server, fraud tool connectors and dashboards. Large merchants sometimes build the same layer in-house.
Risks and regulatory position
The orchestrator becomes a single point of failure, so its own uptime and failover design matter. Because it stores card numbers, it must be a PCI DSS Level 1 service provider.
Most orchestrators never touch funds: money flows from acquirers straight to the merchant, so they are usually not payment institutions. An orchestrator that collects and pays out funds is providing a payment service and needs a licence. Buyers of an orchestration business should confirm which of the two models applies, and whether card tokens in the vault can be exported if a merchant leaves.