Can orchestration fix cross-border card payments?

• Cross-border card payments are not just an e-commerce issue. A lot of the real friction happens in person, at forecourts, tills, hotel desks, kiosks, and other distributed payment points.

• Fragmented acquiring setups make performance harder to manage. Approval rates, costs, FX exposure, and reconciliation can vary across markets when each country or site has grown around different providers and payment flows.

• Orchestration adds a smarter decisioning layer. Instead of relying only on static routing rules, transactions can be assessed using context such as card type, acquirer performance, FX position, risk signals, and policy constraints.

• The biggest value is control, not replacement. PSPs and merchants do not need to rip out every existing provider. Orchestration helps connect them through one layer, so cross-border payments become easier to steer, measure, and improve.

Don't have time to read more now? Sign up to our newsletter to get the latest insights directly in your inbox. 

A fleet manager in Munich authorizes a payment at a highway stop in Lyon. The terminal routes to their usual acquirer and comes back declined - not because of fraud, not because of insufficient funds, but because the routing path wasn't optimized for a cross-border card-present transaction, leading to higher costs or lower approval rates in that market.

The payment stalls in real time as the driver is left waiting, while the manager contacts support and the acquirer records a decline. No one expected it, but the system wasn’t designed to handle that scenario efficiently.

Cross-border card payments are sold as seamless global commerce, but in reality they rarely match the promise. Transactions move across multiple acquirers, currencies, issuer jurisdictions, and compliance frameworks - all without a unified layer coordinating those decisions. 

For PSPs and finance teams operating at scale, these moments add up. They show up in approval rate variance across markets, in FX exposure that's harder to manage than it should be, and in reconciliation that takes days when it should take hours.

The issue is that too many payment environments still rely on static rules and fragmented integrations to manage decisions that increasingly need to happen in real time.

That’s where payment orchestration comes in: not as a replacement for every provider in the chain, but as a way to apply smarter decisions at the point each transaction happens.

When a cardholder and a merchant operate in different countries (or when a payment crosses acquiring, issuing, or currency boundaries), it becomes a cross-border payment. That can trigger scheme fees and FX costs, while also bringing additional compliance requirements depending on how the payment is routed and where it settles.

Much of the current conversation focuses on e-commerce flows, but that misses out a large part of the picture. Card-present cross-border payments (in-person transactions where the card and merchant sit in different countries) work differently:

• And in unattended or distributed environments (fuel forecourts or hotel kiosks), there's no staff member to resolve a failed transaction.

For a retailer operating across five European markets, these differences stack up quickly. The same applies to the PSP managing that estate, and the finance team trying to make sense of the resulting settlement flows.

On paper, cross‑border card payments should be a solved problem: the global schemes connect issuers and acquirers almost everywhere, and most large merchants already accept international cards. In practice, card‑present cross‑border transactions are still slower, more expensive and less reliable than domestic ones.

Let’s look at an example: a retailer enters Germany with a local acquirer. A year later it expands into France and adds another provider, and Spain follows with a different setup again. Each decision makes sense locally, but over time the payment environment becomes harder to manage as one connected whole. 

That fragmentation creates problems in the places PSPs and finance teams care about most:

• Approval rates become harder to explain, because the same type of transaction may perform differently depending on the acquirer, issuer or local setup.
• Costs become harder to control, especially when foreign-issued cards trigger less efficient routing or higher cross-border fees.
• FX and settlement become harder to forecast, as transactions settle across different currencies, providers and timeframes.
• Reconciliation becomes harder to trust, because payment data arrives from multiple systems in inconsistent formats.

You see the same pattern in fuel, travel and hospitality, where card-present payments often involve international customers, unattended devices, mobile journeys and local payment preferences. At the terminal it looks simple, but behind it sits a chain of routing and processing decisions that decide how and where that payment actually moves.

This is why cross-border card payments stay messy. Card networks may connect the ecosystem, but they don’t automatically coordinate the operational choices around acquiring, cost, currency, compliance and reporting. 

The result is a cross‑border card environment that remains messy by design - and one that traditional routing tools weren’t designed to handle this level of complexity.

If the previous section describes the mess, orchestration is the control layer that sits above it.

Orchestration, at its simplest, is a routing layer - deciding which acquirer, which currency, and which processing path to use for each transaction in real time, not via static rules written months ago.

The reason a single routing rule fails is that no two cross-border transactions are the same. An orchestration layer accounts for that by reading several variables at once:

Those inputs sit inside clear guardrails: PSPs, merchants, and treasuries still decide which providers can be used where, which currencies and accounts are acceptable, and what risk and compliance checks are non‑negotiable. Each transaction is routed based on the conditions in the network at that moment. 

Want to understand how payment orchestration works under the hood? Read our guide to in-person payment orchestration.

Cross-border payment examples from retail, travel and fuel

Most of the noise about cross‑border payments still focuses on e‑commerce, but much of the real friction sits in the physical world: at forecourts, tills and hotel desks. The customer sees a quick tap or dip - but behind it, there are different acquirers and local behaviors at work in each market.

For a fuel operator running unattended forecourts across Europe, that plays out day to day. Local drivers tend to use domestic debit, while fleet and international customers rely on fuel cards or foreign-issued credit cards. Each site has grown up with its own mix of terminals and provider arrangements, so one change to pricing, routing or reporting can turn into three or four separate projects. 

Approval rates and costs vary by route, but it’s hard for PSP and finance teams to see, let alone control, what is happening across the network as a whole. An in‑person orchestration layer gives those sites a single control point: new devices and providers plug into one platform, and each authorization can be steered over the most suitable route for that card and context - while finance keeps a grip on FX and settlement.

In each case, orchestration turns a patchwork of local setups into a single, controllable environment.

What this means for PSPs, merchants and finance teams

For PSPs, cross-border orchestration changes the product conversation. Instead of wiring each acquirer, device, market and network directly into their own stack, they can offer merchants a single layer that removes that complexity. 

They keep the contracts and risk controls, but gain the ability to plug in new providers faster and to turn smart routing and resilience into products.

For merchants, orchestration means they are no longer locked into one PSP or one setup per market. They connect once and get access to multiple PSPs, acquirers and local payment methods, with orchestration routing each transaction based on what delivers the best outcome at that moment. 

For finance teams, the value is visibility and control. A single view of performance across markets makes it easier to see how payment decisions affect cash flow, instead of leaving finance teams to piece the story together from delayed settlement files and mismatched reports.

For most PSPs and merchants, the right move is not a rip-and-replace, but a controlled pilot in one cross‑border‑heavy market or vertical. Start by mapping where your approval rates, costs or operational pain are highest, then use orchestration in “assist” mode, recommending routes and providers, before letting it automate more decisions.

From there, it comes down to defining what “good” looks like. Set benchmarks for approval rates, FX costs, cash visibility, reconciliation speed, and settlement timing, then measure against them before scaling. 

But that only works if the underlying data is reliable. Routing depends on the transaction data it learns from, so fragmented records across acquirers or inconsistent references in settlement files will quickly reduce performance. 

It’s not the most glamorous work, but it's the foundation everything else sits on.

Ownership also needs to be explicit. Without clear accountability for who defines the routing policy and who monitors outcomes, pilots stall when they should scale.

When those pieces are in place, orchestration becomes a practical way to turn messy cross‑border card payments into something you can actually steer.

Want to explore what a more unified approach to cross-border card payments could look like for your estate? Get in touch with our team.