Products Orchestration
Product 02 · Multi-acquirer routingPayment Orchestration.
Route every transaction across 30+ acquiring banks with intelligent routing, cascading retry and multi-MID distribution — so a single acquirer decision can never take your processing to zero.
The structural problem
Why single-acquirer processing fails.
For a high-risk merchant, running all volume through one acquiring bank isn't a simplification — it's a single point of failure. Here is where it breaks, and what orchestration does instead.
One acquirer away from zero
A compliance review, a chargeback-ratio spike or an acquirer-side policy change can suspend an account with little notice. With a single acquirer, that one decision stops all processing.
Volume spread across 30+ banks
Orchestration distributes traffic across 30+ acquiring relationships. Action on one account reroutes automatically to the rest — processing continues while a replacement is arranged.
Approval rates vary by bank
The same card, country and amount can clear at one acquirer and decline at another — different issuer relationships, BIN routing and category tolerance. A single acquirer locks you to its floor.
Routed to the best bank, per transaction
Routing reads live approval-rate performance across every relationship and sends each transaction to the bank with the best expected outcome for its specific characteristics.
Soft declines are lost revenue
A soft decline — do-not-honor, refer-to-issuer — is often issuer-specific. Without a retry path through another bank, that recoverable transaction is gone, and the revenue with it.
Cascading retry recovers it
Soft-declined transactions retry automatically through a backup acquirer where a different issuer relationship can succeed. Hard declines are never retried — protecting your approval record.
Orchestration capabilities
The infrastructure that makes it work.
Routing, cascading, distribution and failover are not separate tools — they are one orchestration layer sitting between your checkout and 30+ acquiring banks.
Intelligent multi-bank routing
Each transaction is evaluated on BIN, country of issue, amount, MCC and time, then directed to the acquiring bank with the best expected approval rate — continuously updated as performance shifts.
Cascading retry on soft declines
Soft declines retry through a configured backup acquirer where a different issuer relationship may approve. Hard declines exit the flow — non-recoverable codes are never retried, preserving your AR record.
Multi-MID volume distribution
Chargeback ratios are calculated per MID. Distributing volume across multiple merchant accounts keeps any single account's ratio balanced and away from card-network thresholds.
Instant failover on downtime
When a primary acquirer slows, errors or goes offline, routing redirects to active banks in the failover chain. The shift is transparent to the cardholder — no interruption to checkout.
Real-time performance monitoring
Approval rate, decline reason, response time and error rate tracked per acquirer in real time. When a bank deviates from baseline, alerts enable rapid investigation and routing adjustment.
Configurable routing rules
Rules combine card type, BIN country, amount band, MCC, risk score and time window — and take effect without a code deployment. A/B routing evaluates a new bank before full migration.
How cascading retry works
From soft decline to recovered sale.
Good routing minimizes declines; cascade recovers the revenue that remains. Here is the path a soft-declined transaction takes — invisible to the cardholder.
Initial authorization
The transaction routes to the best acquiring bank for that card BIN, country and amount, based on its routing rules.
Best-routed bankSoft decline received
The decline code is evaluated. Soft, issuer-variable codes are eligible to cascade; hard declines exit the flow and are never retried.
Recoverable codes onlyCascade to backup
The transaction retries through the next bank in the cascade chain, where a different issuer relationship may produce a different result.
Different issuer pathAuthorization approved
Revenue recovered. The cardholder sees a seamless transaction — no sign of the routing or retry logic that ran underneath.
Seamless to the buyerRouting rule configuration
Rules that combine, not just toggle.
Each rule layers multiple criteria to send every transaction to the optimal bank for that exact combination of factors. Changes take effect without a deployment.
Card geography
EU-issued cards → EU-licensed acquirer for PSD2 alignment and higher domestic approval.
Transaction amount
High-value transactions → the acquirer with stronger approval for that amount band and card type.
Merchant category
Category traffic → a category-experienced acquirer with the appropriate MCC and risk parameters.
Card network
Amex → a specialized Amex-accepting acquirer; Visa/Mastercard → primary routing.
Time window
Off-hours routing adjusts for acquirer availability and batch-processing schedules.
Risk score
High-risk-scored transactions → an acquirer configured for enhanced 3DS2 authentication.
Orchestration + acquiring, together
More than a routing layer.
A routing platform moves transactions between providers you have to source yourself. MIDs orchestrates across acquiring relationships it structures and manages — the part that actually keeps high-risk merchants live.
Works with the stack
Products that run alongside.
Orchestration is one of five integrated layers. These work directly with it — the gateway it routes through, the scores that inform routing, and the dispute defense beneath it.
Payment Gateway
The gateway infrastructure orchestration routes through — one integration across 30+ acquiring banks.
See the gatewayFraud Management
Risk scoring that feeds routing — high-risk scores trigger enhanced authentication or alternate routes.
See fraud managementAnalytics
Approval-rate and decline-reason reporting across your portfolio — the data that informs routing.
See analyticsFAQ
Common orchestration questions.
Orchestration is the layer between a merchant's checkout and multiple acquiring banks that manages routing, cascading, failover and volume distribution across them. Standard merchants often process through a single acquirer — if it declines a transaction or suspends the account, the options are limited. High-risk merchants face elevated chargeback ratios, periodic acquirer risk reviews and approval rates that vary by geography, so multi-acquirer architecture matters directly: routing affects approval rates, cascade recovers declined transactions, and multi-MID distribution manages ratios across accounts.
Approval outcomes depend partly on the acquiring bank's relationships with card issuers. A card issued by a bank with a strong link to one acquirer but a weaker link to another can approve or decline based purely on routing. High-risk categories can also carry category-specific approval profiles that differ by acquirer. Directing each transaction to the bank with the best historical performance for that transaction's characteristics captures approval-rate gains a fixed single-acquirer setup cannot reach.
Routing is the initial decision — which acquiring bank receives the attempt, based on configured rules. Cascading is what happens after a decline — the transaction retries through a different bank when the decline reason suggests a different outcome is possible. Routing happens on every transaction; cascading only on soft, recoverable declines. Hard declines (stolen card, closed account, fraud block) do not cascade, as no routing change overcomes them. Good routing minimizes the declines that need a cascade; cascade recovers what remains.
Card-network monitoring programs calculate chargeback ratios per merchant account (per MID) as disputes divided by volume in the same period. When all volume runs through one MID, any spike — a fraud event, a renewal-dispute wave, a compliance escalation — hits that single account's ratio in full. Distributing volume across multiple MIDs spreads those events so no single account bears the whole load. Orchestration manages which transactions route to which MID in real time to keep ratios balanced.
Yes — operational continuity is one of the primary purposes of multi-acquirer orchestration. When a bank suspends or terminates an account, routing automatically directs new transactions to the remaining active banks, so you keep processing while a replacement relationship is established. Without multi-acquirer orchestration, a single suspension halts all processing until a new relationship is in place — a gap that is much harder to absorb in high-risk categories.
Rules can be configured by card BIN and country of issue, transaction amount ranges, merchant category code (MCC), card network, time of day or day of week, risk score from fraud evaluation, and specific geographic regions. Rules combine multiple criteria and apply in priority order, and changes take effect without a code deployment. A/B routing — splitting a percentage of volume to a new acquirer to evaluate performance before full migration — is supported for acquirer evaluation.
Comparing routing architectures? Talk through your acquiring setup
Ready to route across 30+ banks?
Tell us your current acquiring setup, transaction volumes and chargeback profile. We'll map the routing architecture that fits your merchant category — and the failover beneath it.