“Orchestration” is one of the most used and least explained words in payments. Underneath the pitch decks it means something concrete: deciding, per transaction, which path gives it the best chance of approval at the best cost — and having more than one path available.
What routing decides
When a transaction arrives, a routing layer can choose the acquiring connection based on card brand and issuer country, transaction currency, historical approval performance for that segment, cost differences between routes, and current connection health. A European card routed through a connection with strong European issuer relationships approves more often than the same card sent down a route optimized for another region.
Failover: the underrated half
Routing gets attention for approval-rate lifts, but its plainest value is availability. Acquirers have outages. With a single connection, an outage is lost revenue for as long as it lasts; with routing, technical declines and timeouts retry down an alternate path in seconds. Customers never see it.
When it matters — and when it doesn’t
A merchant processing modest volume in one market through one acquirer gains little from orchestration overhead. The economics turn when you sell internationally (issuer-country effects get large), volume grows to where a 1% approval lift is material revenue, or downtime becomes intolerable. The point of using a gateway with multiple acquiring connections is inheriting these benefits without building the plumbing.
Questions to ask any provider
- How many acquiring connections are live, and in which markets?
- What happens to an in-flight transaction when a connection fails?
- Can routing rules reflect my mix — currencies, brands, average ticket?
- Do I see per-route performance in reporting, or is it a black box?
Payixay routes transactions across acquiring connections on gateway infrastructure with 300+ integrations, provided by our partner Akurateco. See card processing.