The Unified Payment Orchestration Advantage

When you operate twelve digital commerce companies, you inherit twelve payment stacks. Each was stitched together by a small team taking the path of least resistance: one PSP, maybe a backup gateway, a handful of brittle retry rules. That works at single-company scale. Across a portfolio, it quietly leaves money on the table.

What payment orchestration actually does

Payment orchestration is a routing layer that sits above your acquirers, PSPs, and gateways. It is not a processor. It does not move money. It decides, transaction by transaction, which processor should handle the request, what to do if that processor declines, and how to enrich the request so the issuer is more likely to approve it. Vendors in this space include Primer, Gr4vy, Spreedly, Corefy, and Payrails, and the larger PSPs have been adding orchestration features of their own. The shared idea is simple: separate the decision of how to authorize a payment from the plumbing of who authorizes it.

The reason this matters is the authorization rate. In e-commerce, healthy auth rates sit somewhere in the 85 to 95% band, depending on category, geography, and whether the traffic is one-off or subscription. The gap between an average stack and a well-tuned one is usually one to three percentage points. On any meaningful volume, that gap is the difference between a comfortable margin and a missed quarter.

An orchestration layer pulls a handful of well-understood levers:

• Smart routing: send each transaction to the acquirer with the best historical approval rate for that BIN, country, currency, and card scheme.
• Cascading retries: when a soft decline comes back, automatically re-attempt on a second processor instead of bouncing the customer.
• Network tokens: replace the raw PAN with a Visa or Mastercard network token, which issuers approve at higher rates (Visa has publicly cited several points of uplift on card-not-present).
• 3DS exemption logic: request SCA exemptions where the risk profile allows, so low-risk transactions skip the friction step entirely.
• Fallback and failover: if a PSP is degraded or down, traffic shifts without anyone paging an on-call engineer.

None of these are exotic. The advantage is having one layer that does all of them consistently, with data from every company feeding the same routing model.

Why this compounds across a portfolio

A single merchant tuning its own stack hits a ceiling fast. The data is thin, the negotiating position with acquirers is modest, and the engineering budget for payments is whatever is left after the product roadmap. A portfolio changes the math in three ways.

First, volume is pooled at the contract level, which means better acquirer pricing and better interchange terms. Second, the routing model gets smarter because it sees more BINs, more geographies, and more decline reasons. A pattern that looks like noise inside one company becomes a clear signal across twelve. Third, every improvement ships once and benefits every brand. A new exemption rule, a new fallback path, a new tokenization flow: built in the orchestration layer, deployed to the whole group.

Centralizing this work across our twelve companies improved authorization rates by 4.2% on average and produced material savings on processing fees. The auth-rate improvement is the line item most people notice, but the operational story matters just as much. Payment incidents that used to require a per-company response now resolve at the routing layer.

What we measure

We track auth rate by company, by BIN range, by issuer country, and by card scheme, and we watch the deltas weekly. We track decline reasons in detail, because "do not honor" and "insufficient funds" need very different responses. We track the cost per successful transaction, not just the headline processing rate, since a cheaper PSP that declines more often is not actually cheaper. And we track time to integrate a new acquirer, because the value of the orchestration layer is partly in how quickly we can route around a problem.

The orchestration layer is not a silver bullet. It is a place to put the work, so the work can be done once and measured honestly. For a portfolio operator, that turns out to be most of the battle.