← All insights

Payment infrastructure

What is a payment orchestrator
(and when you need one)?

20 Nov 20264 min readPayment infrastructure

A payment orchestrator sits between your checkout and every payment provider you use, giving you one integration to many rails. For a single-market startup it's overkill; for a scaling business it's the difference between a payment stack that breaks and one that heals itself.

What an orchestrator actually does

Instead of wiring your checkout directly to one gateway, an orchestrator exposes a single API and routes each transaction to the best provider behind the scenes. Its core jobs are:

  • Smart routing — send each payment to the acquirer most likely to approve it, by country, card type, amount or risk.
  • Failover — if one provider goes down or declines, retry automatically on another.
  • Unified reconciliation — one view of transactions, fees and settlements across every provider.

The signs you've outgrown a single gateway

You don't need an orchestrator because it's fashionable; you need it when a single provider becomes a constraint. Watch for: approval rates dropping in specific markets, a provider outage taking your entire revenue offline, needing a backup acquirer, or entering a new region where your current gateway is weak.

What it costs versus what it saves

Orchestration adds a per-transaction or platform fee and real engineering work. The payback comes from measurable uplifts: a few extra basis points of approval, no revenue lost to downtime, and cheaper failover than negotiating with a second gateway manually. For high-volume merchants, the arithmetic usually works.

When you don't need one yet

If you operate in one market, with one acquirer, and your volumes are modest, an orchestrator is premature complexity. Start with a solid single integration; add orchestration when routing and redundancy start showing up as revenue problems, not hypothetical ones.