Payment orchestration in practice: Lessons from global businesses

Payment orchestration is a layer that sits between a business and its payment service providers. It's designed to improve overall payment performance by:

• Routing transactions between multiple providers

• Supporting alternative payment methods and local payment methods

• Applying smart routing logic

• Redirecting payments when a primary route fails

 Many businesses use payment orchestration to streamline how they manage multiple providers through a single integration, rather than building and maintaining separate connections to each one.

What payment orchestration doesn't do

It's also worth flagging that payment orchestration doesn't:

• Eliminate outages

• Remove the need for PSP integrations

• Guarantee improved authorisation rates, conversion rates, costs, or customer experience

• Remove the need to manage contracts, relationships, and operational overhead across the PSPs sitting behind it

How much value you get depends on how the orchestration layer is set up and run. That's why different businesses often reach very different conclusions about whether it's worth it. In reality, even large organisations can find that building true resilience takes more time and effort than expected. Orchestration doesn't remove complexity. It shifts how that complexity needs to be managed. 

Payment orchestration vs. a payment gateway

There's sometimes confusion around these terms, so to clarify:

• A payment gateway typically connects a business to one primary acquiring or processing setup, handling transaction requests and responses.

• Payment orchestration goes further by introducing logic across multiple providers, helping businesses manage payment systems at scale. That added flexibility can be powerful, but it also increases architectural and operational complexity.

Payment orchestration means different things to different businesses. Its value depends on considerations such as:

• How revenue is generated

• What the money flows look like

• Where cash is at risk, and what happens when payments fail

 During a recent Adyen Experience event, we hosted a panel discussion featuring three different businesses. Here's how they see payment orchestration:

Media and entertainment business: "We can't afford for our payments to go down at a critical moment."

For a global media and entertainment business running subscriptions and pay-per-view, the biggest risk is something going wrong at the worst possible moment. Live sport and one-off events create short, high-stakes windows where even a minute of downtime can mean significant lost revenue.

They initially adopted a third-party payment orchestrator to improve resilience. But, in practice, the orchestrator introduced its own reliability issues, adding risk rather than removing it. The business has since moved away from third-party orchestration. It eventually plans to build orchestration capabilities in-house, though this will take considerable time and resources.

 Travel retailer: "Isn't it just a redistribution of risk?"

For the digital travel retailer, payments sit at the heart of a complicated funding flow. Customers may only pay a small deposit upfront, while the business has to pay suppliers such as airlines, hotels, and operators in full, much earlier. That creates a gap where cash goes out long before it fully comes back in.

In that environment, payment reliability is critical. The business needs partners it can trust, with the balance-sheet strength to support those flows. From that perspective, orchestration feels less like added protection and more like another layer of risk, especially when it's run by a younger company with less financial backing.

Insurer: "Not a priority for us."

Payment orchestration is typically discussed in the context of routing, failover, and authorisation. For an insurer, however, the most critical customer moment is often payouts, not collections. A delay or failure when paying a claim has regulatory and reputational consequences that far outweigh marginal improvements in how premiums are collected. For them, orchestration competes with other priorities such as faster payments infrastructure, payout reliability, reconciliation and visibility, and regulatory change.

Payment orchestration comes with both benefits and drawbacks. The table below summarises the potential benefits and the practical challenges businesses should weigh up before moving ahead.

Table: Pros and cons of payment orchestration

One of the biggest trade-offs you'll face with payment orchestration is the fragmentation of your payments stack. This can impact your payment operations and overall performance in several ways:

You won't benefit from full-funnel conversion

Some payment providers handle the entire payment flow from gateway to acquiring end-to-end, giving them access to data across both your checkout and the card schemes to optimise conversions. With a multi-acquirer strategy, transaction data is distributed across providers. That means the full-funnel view sits with no single party, which can make it harder to recognise returning customers, apply consistent retry logic, or personalise the payment experience.

Learn more about full-funnel conversion >

It will be harder to distinguish good customers from fraudsters

In addition to missing out on conversion optimisations, you'll also find it harder to identify fraudsters. As fraudsters use AI to become ever-more sophisticated, anti-fraud measures like 3D Secure or chargeback handling and static risk rules will only take you so far. Modern fraud detection tools rely on rich payment data to recognise patterns and identify suspicious behaviour in real-time, without impacting legitimate customers. By splitting the payment data across PSPs, you'll miss opportunities to spot and stop known fraudsters.

Learn more about how modern ecommerce fraud prevention tools work >

You risk losing key customer insights

The travel retailer raised an important concern: with payment orchestration, who owns your customer tokens? If tokenisation is spread across providers, customer identity and payment history can become fragmented. That can lead to a less joined-up experience, deprive you of important customer insights, and make loyalty harder to manage.

Payment orchestration makes sense under specific conditions. Based on the feedback from our merchant panel, the following examples show when the trade-offs might be worth it.

When downtime risk materially outweighs operational cost

For the global media and entertainment business, orchestration initially felt like the right move because the downside of failure is so high. Live sport and pay-per-view create intense, time-critical moments where even short outages can be costly. In that situation, orchestration looks like a form of insurance.

But insurance has a premium. Before committing, it's worth quantifying the full cost: the orchestration layer itself, the added payment processing costs across multiple providers, and the operational overhead of managing a more complex setup. Only when that total is weighed against a realistic estimate of downtime risk does the case for orchestration become clear.

When you have the resources to manage a multi-layer setup properly

Orchestration is not a switch you turn on. As the media business discovered, true resilience requires multiple layers: an orchestration platform, multiple PSPs, and direct integrations as a fallback if the orchestrator itself fails.

Without dedicated ownership, a complex setup like this can introduce new points of failure instead of reducing them. This approach only works if your organisation can invest in people and process. In the media business's case, this meant more than 50 people across product and engineering dedicated to managing payments.

When you are solving a clearly defined failure scenario

The strongest orchestration use case in the discussion was tightly scoped. The media business was using orchestration to protect against a specific failure scenario. It's most effective when it's addressing a known risk, rather than being used as a general improvement layer with no clear success criteria.

The examples below highlight situations where orchestration may add complexity without delivering proportional benefit.

When payments already perform well

If your existing payment setup is reliable and delivering strong results, orchestration may offer limited value. The additional complexity can quickly outweigh any marginal gains. Before adding orchestration, it's worth asking whether you're solving an active problem or simply preparing for a hypothetical one.

When vendor maturity and balance-sheet strength matter more than redundancy

For some businesses, the more pressing concern is where risk ultimately sits. If payment failures translate directly into a cash-flow crisis, the financial resilience of the provider becomes critical. In this case, introducing another intermediary can feel less like risk reduction and more like risk redistribution.

When priorities lie elsewhere

If your biggest risks sit around payouts, reconciliation, regulatory obligations, or operational visibility, orchestration won't address the problems that matter most. You risk diverting attention and investment away from higher-impact priorities.

When evaluating potential payment orchestration options, it's worth keeping a few things in mind:

• What happens if the orchestration layer fails? As the media business learned first-hand, removing a single point of failure can introduce a new one, unless additional fallbacks are built and maintained.

• How much ownership, complexity, and operational responsibility do we want to take on? Orchestration pushes organisations toward running payments as a capability, with ongoing ownership, tuning, and intervention. Do you have the resources to manage this effectively?

• Do the gains outweigh the consequences of fragmenting our payment data? Splitting data between providers can mean missing out on full-funnel conversion rates, targeted fraud detection, and customer insights. It's important to understand where tokens will live and who's responsible for capturing and maintaining important payment data.

Payment orchestration is often discussed in terms of internal resilience, fewer outages, better routing, and more control. But what will its impact be on your end users? Customers are interested in a smoother checkout experience with fewer interruptions, more consistent recognition over time, and access to their preferred payment options. If those outcomes are not clear, does the additional complexity translate into real value?

If you're considering payment orchestration and would like some advice on whether it's the right fit for your business, get in touch to speak to a payments expert.