What Is Payment Orchestration?

‍Payment orchestration is a software layer that connects a merchant's checkout to multiple payment processors and chooses in real time which one handles each transaction. A store selling in the US and the EU can route US cards to one processor and EU cards to a local acquirer, all from a single integration.

Your existing processors and gateways still move the money, and orchestration picks which one gets each sale.

How payment orchestration works

A routing rule runs on every transaction and picks which connected processor gets it. The rule fires before the charge leaves your checkout. Routing rules typically weigh inputs like these:

• Cost. Which processor is cheapest for this card and this currency.
• Approval rate. Which one has historically approved similar transactions.
• Currency. Whether a local acquirer will do better than a cross-border one.
• Card type. Whether the card is credit or debit, and which network issued it.
• Provider uptime. Whether the first choice is responding right now.

Many orchestrators also retry a declined charge on a different processor.

You also read every processor's approval and decline numbers in one dashboard. No logging into each one separately.

Below roughly a few hundred thousand dollars a month, though, you pay more than you save. A store that size runs too little volume across too few processors, so the routing gains stay small. That is why vendors go after mid-market and enterprise merchants first.

Payment orchestration vs. a payment gateway

A gateway moves transaction data to one processor, and an orchestrator picks which of several processors gets each sale. One connects you to a destination. The other chooses the destination.

A gateway and a processor also split the work differently, and our payment gateway vs. payment processor entry has that breakdown.

An orchestrator earns its fee once you connect a second processor. Only then is there a routing decision to make. Run one processor and you pay for the integration while the rule has one option.

The value starts with your second processor.

How a routing decision changes your chargeback risk

A routing decision changes your dispute odds two ways, through the billing descriptor your customer reads and the processor a declined charge retries on.

Customers dispute charges they don't recognize, and they read the descriptor on their statement. Send the same sale through a different processor and that descriptor can change.

Retries change the statement the same way. A declined attempt can leave a pending charge the customer still sees. The retry then clears on the next processor, so they read two entries and dispute the surprise.

Both of those are side effects of a rule tuned for cost and approval rates. So pull up your routing rules whenever you add a processor. Check which descriptor each one sends.

Catching the disputes early is a different job from routing well. Our chargeback alerts reach you while the customer is still disputing, whichever processor ran the sale. Refund inside that window and the dispute never reaches your chargeback rate.

Ask an orchestration vendor two things before you sign:

• Can you pin one descriptor across every processor? Some expose a single descriptor field, others inherit what each processor sets.
• Do dispute outcomes feed the routing rules? Confirm a chargeback changes where the next sale routes.

Run your own multi-processor dispute count through our ROI calculator to see what descriptor mismatches are costing you.

FAQ

Does payment orchestration replace my payment processor?

No, and you keep your merchant accounts and processor contracts as they are. An orchestrator ties together the integrations you already run.

Can orchestration lower my chargeback rate alone?

Only partly. Routing rules score cost and approval odds, so you still need an alert tool to catch a dispute while it's open.

Is payment orchestration only for large enterprises?

Your volume decides it, and plenty of mid-market stores qualify. Under roughly a few hundred thousand dollars a month, the fee costs more than the routing saves.