Skip to content

Payment orchestration: do you need multiple acquirers?

Payment orchestration routes, retries and fails over payments across acquirers. See when you need it, build vs buy, and which metrics prove it works.

Payment orchestration is a layer between checkout and several payment service providers (PSPs) or acquirers that routes, retries and fails over payments and manages stored card tokens. It pays off when volume, markets or payment methods outgrow one provider. Most small businesses do not need it yet.

This guide explains what orchestration does, when multiple acquirers make sense, how to weigh build against buy, and which metrics prove it works, as of November 2026. An acquirer is the bank or licensed company that accepts card payments for a merchant, and a PSP bundles acquiring, a gateway and other services. BlindPay publishes this guide, and its role is limited to bank and stablecoin rails, covered in the last section.

Key takeaways

  • Orchestration adds four jobs on top of your providers: routing, retries, failover and tokenization, plus unified reporting.
  • You rarely need it with one market, one acquirer and modest volume. Outage cost, multi-country selling and local methods are the real triggers.
  • No uplift percentage is universal. A 2022 conference deck from PSE Consulting put Germany's domestic approval at 94% and its cross-border approval at 74%, which shows why local acquiring matters, but it is one country in one year.
  • Judge success by authorization rate, cost per successful payment and uptime, measured against a control group.
  • Orchestration of card acquirers and orchestration of bank and stablecoin rails are different jobs, with different tools.

What is payment orchestration?

Payment orchestration is software that connects your checkout to several PSPs, acquirers and payment methods through one integration, then decides where each payment goes. It does not process the card payment itself. The providers do.

Think of it as a traffic controller. Your checkout talks to one orchestration API. The orchestrator talks to your providers, applies your rules and returns one result. Spreedly's site describes the same idea: connect to many payment or fraud providers, own your tokens and route traffic for performance. If you want the plain-language basics, what is payment orchestration covers the category, and payment orchestration vs payment gateway explains how it differs from a gateway.

What does an orchestration layer do (routing, retries, failover, tokenization, reporting)?

It does five things: routes each payment to a chosen provider, retries failed payments, switches providers when one is down, stores card data as tokens you can reuse across providers, and combines reporting from all of them.

  • Routing: rules or models pick the provider using the card's country, amount, method and provider cost.
  • Retries: a payment that fails for a soft reason, such as a temporary issuer or network error, is sent again, sometimes through another acquirer.
  • Failover: if a provider times out or goes down, traffic moves to a backup so checkout keeps working.
  • Tokenization: a token is a stand-in for the card number. If you own the tokens in a vault, you can move cards between providers without asking customers to re-enter them.
  • Reporting: one view of approvals, declines, fees and refunds across providers.

Each job addresses a different risk: lost sales from an outage, lost sales from declines, lock-in and blind spots. Decide which risk you actually have before you buy. See how to evaluate a payment orchestration platform for a buyer's checklist.

When do you need multiple acquirers?

You need more than one acquirer when a single provider's outage would cost meaningful revenue, when you sell in countries where a local acquirer would perform better, or when a provider cannot support a payment method you need. Otherwise one acquirer is simpler.

Local acquiring means processing a card through an acquirer in the card's own country, so the transaction counts as domestic. The PSE Consulting deck from its December 2022 merchant acquiring conference reported domestic approval rates from 94% in Germany to 85% in France, against cross-border rates of 74% and 78%. That is old, country-specific data, so use it as a reason to test, not as a forecast. Local acquiring vs cross-border acquiring works through the trade-offs, and how to improve card authorization rates covers fixes to try first.

Use this checklist.

Do you need it? Count your yes answers

  1. Would an hour of provider downtime cost you more than a month of platform fees?
  2. Do you sell in three or more countries with different local acquirer markets?
  3. Do you need payment methods your current provider cannot offer?
  4. Do you see declines that a second acquirer might approve, based on decline codes?
  5. Do you want to avoid being locked to one provider's stored cards?
  6. Do you have engineers to run routing rules and read the data?

Zero or one yes: stay with one acquirer. Two or three: add a simple failover provider. Four or more: evaluate orchestration seriously.

What are the benefits and costs?

The benefits are resilience, better routing, negotiating power and fewer lost customers, and the costs are platform fees, integration work, another vendor to monitor and added complexity in reconciliation. The net result depends on your volume.

Here is an illustrative example, with every input stated. Monthly card volume is $2,000,000, spread evenly over 730 hours, so about $2,740 of attempts per hour. A 2-hour outage puts about $5,479 of payment attempts at risk, though some shoppers retry later, so it is not all lost sales. Assume a platform fee of $1,500 per month and a 30% gross margin on sales. The platform pays for itself if it recovers $5,000 of sales a month ($1,500 divided by 0.30), before counting integration cost.

Be careful with uplift numbers. Vendor pages often quote an authorization increase or recovered revenue without the baseline, timeframe or traffic mix behind it. A headline figure like that cannot forecast your result, which is why this guide gives none. Any figure you rely on should name its source and date.

Build or buy?

Buy if you have a few providers and want to move fast. Build if you have large volume, specialist payments engineers and needs that vendors do not meet. Most teams start with buy and rebuild only the parts that matter.

FactorBuild in-houseBuy a platform
Time to first routed paymentMonthsWeeks
Upfront costHigh engineering timeIntegration plus platform fee
Control over routing logicFullWithin vendor features
PCI scope for tokensYou carry the burdenShifted to a certified vendor
New provider connectionsYou build each oneOften pre-built
Ongoing maintenanceYour teamVendor
Best whenVery high volume, unusual needsFast launch, several providers

PCI DSS is the card security standard, and holding card data yourself brings scope. A vendor-held vault reduces it. Start with the question of which routing rules you would write on day one. If it is only "if A is down use B", you can do that with a simple switch before you buy a platform.

Which metrics prove it works (authorization rate, cost per successful payment, uptime)?

Three: authorization rate, cost per successful payment and uptime. Measure each against a control group that still uses your old setup, or the gains cannot be separated from seasonality and customer mix.

  • Authorization rate: approved payments divided by attempted payments, split by country, card type and decline code.
  • Cost per successful payment: all processing fees divided by approved payments, including retries and platform fees.
  • Uptime: the share of time checkout can accept payments, including during provider incidents.

Also track retry recovery rate and refund and chargeback ratios. Run a holdback test, sending a slice of traffic through the old path for a month. If the lift disappears, so does the case.

How do local bank rails and stablecoin rails fit into orchestration?

Card orchestration routes between card acquirers. Bank and stablecoin rails are a different layer, covering account-to-account collection, local payouts and settlement. Merchants can run both, and each needs its own connections, since cards and bank transfers do not share a rail.

Bank rails include RTP in the US (24/7, up to $10 million per transaction, per The Clearing House), Pix in Brazil and SPEI in Mexico, which Banxico says should take no more than 30 seconds. Pay by bank for merchants explains when they beat cards. BlindPay orchestrates stablecoins, instant local rails, named virtual accounts and built-in compliance through one API. A named virtual account is a bank account in the customer's own name, and deposits settle automatically to USDC or USDT. BlindPay does not orchestrate card acquirers and it is not an acquirer. It sits next to them, for collection by bank transfer, payouts and stablecoin settlement. Read Orchestrating Local Payments and Stablecoins: A Guide for Leaders for the full approach, and how stablecoins fit into payment orchestration for payouts.

For orchestration on the payout side, read payment orchestration explained.

Methodology and sources

External sources: PSE Consulting, Localisation and FX Optimisation deck, 6 December 2022, Spreedly website, undated, 2026 copyright, checked November 2026, The Clearing House, RTP network, October 2026, Banxico, SPEI, checked November 2026 and Federal Reserve, FedNow, go-live 20 July 2023. The outage and break-even example uses assumed inputs stated in the text.

BlindPay docs: Virtual accounts, Payment methods and Payouts.

What to do next

Before you buy, count the yes answers in the checklist and test one failover or local acquirer on a slice of traffic. To pick the provider you would route to, read how to choose a merchant acquirer, and for the foundations, what is merchant acquiring.

Talk to the BlindPay team about orchestrating bank and stablecoin rails, or start building.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.