---
title: "Payment Orchestration"
url: "https://mahouse.world/glossary/payment-orchestration"
type: "glossary term"
topic: "Payment orchestration"
author: "Ihor Vlasov"
reviewed: "2026-09-20"
published: "2026-08-10"
---

# Payment Orchestration

Payment orchestration is a software layer between a merchant and its payment providers that connects to several acquirers, PSPs, fraud tools and payment methods through one integration and decides, per transaction, where to send it — by cost, approval rate, availability, geography or risk — with the tokens, reconciliation and reporting unified across them. It is the merchant's answer to PSP lock-in and single points of failure, sold by independent platforms and, increasingly, by the PSPs themselves.

**Also known as:** Orchestration layer, Payment orchestration platform, Multi-PSP routing

## Key facts

- **Used at:** merchants large enough to run two or more acquirers — typically above €50–100m of annual volume — and marketplaces and platforms operating across many countries; below that, one PSP is cheaper
- **Binding:** a platform contract with per-transaction fees; the orchestrator holds the token vault and is a PCI service provider; it does not hold the money — the acquirers behind it do
- **Typical functions:** unified API and checkout; token vault portable across providers (network tokens where possible); routing rules and models (cost, approval, risk, failover, cascading); consolidated reconciliation and reporting; a single point for fraud tools, 3-D Secure and methods
- **Typical pricing:** €0.02–0.10 per transaction plus platform fees, independent of the acquirers' pricing; the case is that the approval uplift and cost savings across providers exceed it
- **Parties:** the merchant, the orchestrator, the acquirers and PSPs behind it (which become interchangeable — their objection), the fraud and 3DS vendors plugged in, and the schemes whose tokens make portability possible

## How payment orchestration works in practice

A retailer with acquirers in the US, the EU and the UK, a fraud vendor, two 3-D Secure providers and eight local payment methods integrates them all through an orchestration platform. Its checkout talks to one API. For each transaction the platform reads the card, the country, the amount and the merchant's rules: US cards to the US acquirer, EU debit to the cheapest EU route, high-risk transactions through the fraud vendor first, a soft decline cascaded to the second acquirer, a timeout failed over to the third. Stored cards live in the platform's vault as network tokens usable on any route. At month end the platform's reconciliation matches every provider's settlement to the orders in one file.

The value is control and optionality: the merchant negotiates with acquirers as replaceable suppliers, adds a method or a country by configuration, and survives any one provider's outage. The cost is the layer's fee and the fact that the merchant now runs a payments function rather than buying one — routing rules need owners, and a platform with the wrong weights routes to the cheapest route and loses sales. PSPs responded by building orchestration features into their own products, which works until the merchant wants to route away from them.

For payments M&A the orchestrators are targets for PSPs that want to sit above their rivals, and for merchants' software vendors that want payments inside the platform.

## Example

A marketplace processing €400m a year across nine countries on one PSP at a blended 1.35% and an 87% approval rate moves to an orchestration platform with three acquirers and its existing PSP as a fourth route. Year one: acquirer margins renegotiated to interchange-plus, a blended cost of 1.05% (€1.2m saved); approval rate 90.5% through routing and cascading (€14m of additional sales); failover invoked twice; the platform's fees €280,000. The payments team grew from two to five people, which the finance director counts against the €1.2m and the commercial director counts against the €14m. The incumbent PSP, now a route among four, cut its price to keep 40% of the volume.

## Common mistakes

- Adopting orchestration below the volume where two acquirers pay for themselves.
- Routing rules set once by a consultant and never revisited against the data.
- A token vault that is the orchestrator's own proprietary format, which recreates the lock-in one level up.
- Treating the orchestrator as a PSP; it moves messages, and the money is with the acquirers.
- PSPs' built-in "orchestration" that routes only within the PSP, sold as the same thing.

## Related terms

- [Smart Routing](https://mahouse.world/glossary/smart-routing.md)
- [Cascading](https://mahouse.world/glossary/cascading.md)
- [Failover](https://mahouse.world/glossary/failover.md)
- [Cost-Aware Routing](https://mahouse.world/glossary/cost-aware-routing.md)
- [Payment Service Provider](https://mahouse.world/glossary/payment-service-provider.md)
- [Network Token](https://mahouse.world/glossary/network-token.md)

— Ihor Vlasov, M&A FinTech Expert. Last reviewed 2026-09-20. https://mahouse.world/authors/ihor-vlasov