A hub of basalt cubes with stepped wings reaching in different directions, its last stones being lined up to join

What is payment orchestration?

Payment orchestration is a software layer that links a business to several PSPs and acquirers through one integration and decides where each payment goes.

Alex NovozhenovCEO and co-founder, NoduUpdated October 27, 2026
integration to every provider
1
meanings: card and cross-border
2
market size in 2025, per Grand View
$2.6B

Payment orchestration is a software layer that connects a business to several payment service providers (PSPs), acquirers and payment methods through one integration, and decides which one handles each payment. It routes by cost, issuing country or approval rate, fails over when a provider is down, stores card tokens outside any single PSP, and reconciles all provider data in one place.

Most of the market uses the term in that card sense, and this guide explains it first. The word now covers a second job as well. Cross-border payment orchestration routes the money itself, from one country and currency to another, across bank and stablecoin rails. The later sections show where the 2 differ and how to tell which one your business needs.

How does payment orchestration work?

An orchestration platform puts one layer between a business and the providers it pays through. The business integrates once, usually through the platform’s payment orchestration API and client SDKs, instead of building to each PSP’s API. The platform holds the provider connections, the credentials and the business’s rules, and applies them to every transaction.

A card payment through an orchestration layer runs in 4 steps:

  1. The customer pays. The checkout sends the payment to the orchestration layer instead of straight to one PSP. On most platforms the card number is tokenized on the way in, so the business’s own systems never hold it.
  2. The platform picks a route. Routing rules decide which gateway, processor or acquirer gets the payment. They read the amount, the currency, the payment method and the card’s BIN. The BIN is the first digits of the card number, and it identifies the issuing bank, the card type and the card’s country. Live data feeds in too: each provider’s cost and its recent authorization rate on similar payments. On some platforms a machine learning model sets or adjusts the route. Vendors sell this as smart routing or intelligent routing.
  3. The acquirer sends it for authorization. The request travels through the card network to the issuer, which approves or declines it. A soft decline, such as an issuer timeout or a request for authentication, can succeed on a second attempt. A hard decline, such as a closed or stolen card, cannot. The platform retries soft declines and provider outages on a backup route. The industry calls this failover, or cascading when it runs through a sequence of providers. Routing and retries share one goal: a higher authorization rate, meaning more of the attempts that should be approved actually are.
  4. The results come back to one place. Approvals, declines, decline codes, fees and settlement files from every provider land in one data model. Finance reconciles against one set of reports rather than one per PSP.

Because the providers sit behind one layer, adding an acquirer or a local payment method becomes mostly configuration. The checkout does not change. That is the practical meaning of one integration: the business still signs a contract with each provider, but it writes code against a single API.

Try it: route a payment

EU cardfrom the checkout
Orchestrationrules, retries, 1 report
  • Acquirer Alowest cost for EU cards
  • Acquirer Blowest cost for US cards
  • Local method providerwallets and bank payments

Routed to Acquirer A: lowest cost for EU cards.

Switch a provider off to watch the payment fail over, then flip to cross-border mode to see the other meaning of the word. The card providers are illustrative.

What does a payment orchestration platform include?

Platforms differ in depth, but the established ones combine the same building blocks:

  • Provider connections. Prebuilt connectors to gateways, processors, acquirers and alternative payment methods (APMs), such as digital wallets, local bank transfers and buy now, pay later. The checkout can then offer the local methods each market expects, such as BLIK in Poland or PIX in Brazil.
  • A routing engine. Rules, and on some platforms models, that pick a provider for each transaction by cost, region, BIN, payment method or past performance.
  • Retries and failover. A second attempt with another provider when the first returns a soft decline or is unavailable.
  • Tokenization and a vault. Tokenization replaces the card number with a token held in a vault that is not tied to one processor. That makes moving stored cards between PSPs practical, and it keeps raw card data out of the business’s systems, which shrinks its PCI DSS scope. Some platforms also manage network tokens from Visa and Mastercard, which the networks can update when a card is reissued or expires.
  • Fraud prevention and authentication. Fraud screening, 3-D Secure (3DS) and chargeback handling, built in or connected from specialist vendors. In Europe, 3DS is the common way to apply the strong customer authentication that PSD2 requires for most online card payments.
  • Unified reporting. One view of authorization rates, fees, chargebacks and settlements across every provider, which feeds reconciliation. Teams can set alerts for a drop in authorization rate or a spike in declines, and A/B test routing rules to see how a change, such as turning on 3DS, affects results.

The common thread is that every block acts on a payment a customer makes to a merchant, usually at checkout.

Why do businesses use payment orchestration, and what does it solve?

Teams adopt it for control and resilience, and these are the problems it solves. These are the reasons a payments lead usually puts in the business case:

  • Less vendor lock-in. With the vault and the routing rules outside any one PSP, a business can move volume when a provider has an outage, raises its pricing or tightens its risk appetite. No single provider is a single point of failure.
  • Higher authorization rates. Card platforms aim to recover revenue that one provider would lose, by sending each transaction to the acquirer most likely to approve it and retrying soft declines elsewhere.
  • Lower cost per transaction. Least-cost routing sends each payment to the cheapest provider able to take it, for that card type, country or method.
  • Faster entry into new markets. A local acquirer or APM can go live as a configuration change rather than an integration project.
  • More completed checkouts. Customers expect the methods they know. Primer cites research that 69% of consumers abandon their cart when their preferred payment method is missing.
  • Headroom at peak. Spreading volume across processors means a traffic spike does not rest on one provider’s capacity.
  • One view of the data. Finance and payments teams compare providers on the same metrics, which is also the evidence they bring to the next pricing negotiation.

When is payment orchestration not worth it?

The trade-offs and challenges of orchestration come down to cost and ownership. The platform charges a fee on top of each provider’s pricing. Setup still takes real integration work, and someone has to own the routing rules after go-live. The business keeps a contract, an onboarding process and a relationship with every provider behind the layer. Handling card data also brings PCI DSS duties that the platform and the business share, even when the vault narrows them. Data protection rules such as the EU’s GDPR apply as well.

For a business that sells in one market through one PSP that performs well, orchestration often adds more complexity than it removes. The case gets stronger with a second provider, a second region, or enough volume that a small gain in authorization rate or a lower fee per transaction pays for the platform. Solidgate, which sells orchestration, puts the point where it starts to pay back at about $400,000 a month in volume, or at 2 or more markets or providers.

The layer also brings risks of its own. If the orchestration platform goes down, every route behind it can stop, so its own uptime matters as much as any PSP’s. Splitting volume across providers splits the data too, which can make returning customers and fraud patterns harder to spot. New payment methods also arrive on the orchestrator’s release schedule rather than yours.

How is it different from a gateway, a processor or a PSP?

The 4 terms name different layers of the same card stack:

  • A payment gateway carries payment data from the checkout to a processor and returns the approval or decline. It does not choose between providers, and it does not settle funds.
  • A payment processor handles the authorization and settlement of each transaction, working with the acquiring bank that holds the merchant account. Fiserv, Worldpay and Global Payments are processors, and PSPs such as Adyen and Stripe run their own processing.
  • A payment service provider (PSP) bundles a gateway, processing and usually a shared merchant account into one contract.
  • A payment orchestration platform sits above several gateways, processors and PSPs and decides which one handles each payment. Most orchestration platforms do not process payments themselves.

In short, a gateway carries a payment, the processor and the acquirer authorize and settle it, and orchestration decides where it goes. The guide on payment orchestration vs payment gateway compares the 2 side by side.

Who uses payment orchestration?

Card orchestration starts to pay off once a business works with more than one PSP or sells in more than one region. The typical users are:

  • Global merchants with acquirers in several regions, who want local acquiring in each.
  • Subscription businesses, where every failed renewal is lost revenue, so retries and network tokens matter most.
  • Marketplaces and software platforms that accept payments on behalf of many sellers.
  • PSPs and payment facilitators that spread volume across their own acquiring partners.

Card orchestration is built for collections. In an Adyen merchant panel, an insurer said its most critical moment is paying claims, where a delay carries regulatory and reputational consequences, and routing card payments does not address that.

Cross-border orchestration has a different user base: businesses that move money for others. Fintechs and neobanks send international payments for their users. PSPs and marketplaces settle with sellers abroad. Payroll and B2B platforms pay contractors and suppliers in other countries. Exchanges and wallets need on-ramps and off-ramps between fiat and stablecoin. Many of them never touch a card.

What is cross-border payment orchestration?

Cross-border payment orchestration routes the money itself, not a card authorization. It takes a payment that starts in one country and currency and ends in another, and decides every step between: the source of funds, the rail, the currency conversion, the compliance checks and the last-mile payout. Some providers call this global payment orchestration. When the border is crossed on stablecoins, the industry also calls it stablecoin orchestration.

The problem it solves is different too. In its G20 work on cross-border payments, the Financial Stability Board names 4 frictions: high cost, low speed, limited access and insufficient transparency. Each has a mechanical cause. The cost of an international payment is the stated fee plus the FX spread, the gap between the rate the customer gets and the mid-market rate. Comparing providers therefore means comparing the all-in cost on the amount that arrives, not the headline fee. Speed and cost both trace back to correspondent banking. To pay out in a currency, a bank pre-funds nostro accounts abroad or relies on a correspondent that does, and each hop in the chain can add a fee and a delay. A business that pays suppliers, contractors or customers abroad meets all 4 frictions. A card orchestration platform is not built for them, because it routes card charges at checkout, not money moving between countries.

The all-in cost of a cross-border payment

You send$10,000
Stated fee$15
FX spread vs mid-market1.5%
Arrives, at mid-market value
$9,835
Lost in the spread
$150
Stated fee
$15

All-in cost: $165, or 1.65% of what you sent. The spread is 91% of it, and it never shows up as a fee.

Put in the numbers from a real quote. The spread is the part of the price that never appears on the invoice.

Nodu’s cross-border payment orchestration is one example of this second kind, built as payment infrastructure for businesses that move money for their own customers. A payment can start from a bank account, a crypto wallet or a balance held with Nodu. Where the corridor needs it, the money converts to stablecoin, crosses the border in minutes without correspondent banks or pre-funded accounts, and converts back to local currency on delivery. On fiat-to-fiat routes, the sender and the recipient only ever see fiat. The fiat legs run on SEPA, Faster Payments, ACH, Fedwire and SWIFT, and the stablecoin leg on Base, Ethereum, Polygon or Tron. Delivery time follows the destination rail: minutes on crypto rails, hours for wires, up to a few days for ACH.

Why cross-border payments are slow and costly

Correspondents
  1. Sender's bankSends a SWIFT message
  2. Correspondent 1Nostro account, pre-fundedfee? delay?
  3. Correspondent 2Nostro account, pre-fundedfee? delay?
  4. Recipient's bankCredits what is left

2 correspondent banks in the chain. Each can deduct a fee and add a delay, and the sender rarely knows the total before the money arrives.

Add correspondents to see where the fees and the delays come from, then switch to the stablecoin leg that replaces the chain.

A locked quote fixes the rate and every fee for 15 minutes before the money moves, and a payment that does not match its quote is refused rather than repriced. AML and sanctions screening runs inside the payment itself. Nodu operates through a payment institution and MiCA crypto-asset service provider (CASP) licensed by Latvijas Banka, and a money services business (MSB) registered with FINTRAC in Canada.

Card orchestration vs cross-border orchestration

The 2 kinds share a name and a principle: one integration in front of many routes. They differ in almost everything else.

Card payment orchestration Cross-border payment orchestration
What gets routed A card or APM payment at checkout The money itself, across a corridor from one country and currency to another
Main choice it makes Which gateway, processor or acquirer authorizes the charge Which source, rail, conversion and payout route the money takes
Main goal Higher authorization rates, lower processing cost, no single point of failure Lower all-in cost, faster delivery and a known price for each international payment
Typical features Smart routing, failover, token vault, 3DS, fraud and chargeback tools Pay-ins, payouts, locked FX quotes, settlement rails, AML and sanctions screening in the flow
Who uses it Merchants, subscription businesses and platforms accepting payments Fintechs, PSPs, payroll platforms, marketplaces and exchanges moving money for customers
Where the money ends In the merchant account, settled by the acquirer In the recipient’s bank account or wallet, often in another currency
Examples Spreedly, Primer, Gr4vy, Yuno Nodu, and the providers in our platform comparison

A business can need both. A marketplace may orchestrate card acceptance at checkout, then use cross-border orchestration to pay its sellers abroad in their own currency. The 2 layers do not compete: one brings money in from cardholders, the other moves it out across corridors.

How big is the payment orchestration market?

Estimates vary widely, because research firms define the market differently and use different base years. Recent reports put it at about $2.6 billion in 2025: Grand View Research gives $2.6 billion in a report published in August 2026, and Mordor Intelligence gives $2.65 billion. Forecast growth ranges from about 18% a year (Mordor Intelligence, 2026 to 2031) to about 25% a year (Grand View Research, and Technavio for 2025 to 2030).

Treat any single figure with care. These reports mostly measure the card-led category described above. Cross-border money movement is usually counted in separate payments markets, so these numbers say little about it.

Market growth, by research firm

  • Mordor Intelligence2026 to 203118.31%
  • Technavio2025 to 203024.5%
  • Grand View Research24.7%
From $2.6B in 2025 (Grand View Research), growing 22% a year$7.0B by 2030
Bars are each firm's published growth rate. The slider compounds the 2025 base at the rate you pick: arithmetic, not a forecast.

Which kind of orchestration do you need?

Start from the problem you are trying to solve, not from the label.

You likely need card payment orchestration if:

  • Soft declines or provider outages are costing you approved transactions.
  • You sell in several regions and want a local acquirer in each.
  • You want to add or switch PSPs without rebuilding your checkout or collecting cards again.
  • Your volume is large enough that a small gain in authorization rate or processing cost covers a platform fee.

You likely need cross-border payment orchestration if:

  • You pay out to people or businesses in other countries and currencies.
  • You collect money in one currency and need to deliver it in another.
  • You want the all-in price of an international payment fixed before it is sent.
  • You would rather integrate with a licensed partner than pre-fund accounts and run compliance for every corridor yourself.

Choosing a provider is its own exercise, and the cross-border platform comparison sets out the criteria. If the second list sounds like your business, the cross-border payment orchestration page shows how Nodu runs every route through one API, and the stablecoin on/off-ramp page explains the settlement leg in the middle.

FAQs

A subscription business accepts cards in Europe and the US through 2 acquirers behind an orchestration platform. Its routing rules send cards with an EU BIN to the European acquirer and US cards to the American one. When a renewal gets a soft decline or the first acquirer times out, the platform retries it once on the other. The business wrote one integration, and each acquirer still settles into its own merchant account.

All guides

Ready to run every corridor through one integration?

Apply for access and read the API docs. Both take minutes.

Get startedAPI docs