Software

Payment Routing: What It Is, How It Works and Key Strategies

Oksana Mikhailovskaya
14 min read

Payment routing is the logic a payment gateway uses to choose which acquirer and card network handle each online card payment. This guide is for payment service providers (PSPs), acquiring banks and fintechs that send merchant traffic through more than one acquiring connection and need to decide how to set the rules.

What Is Payment Routing?

Payment routing is the decision your gateway makes for every payment: which acquiring connection receives the authorization request. Rules read the card, the amount, the currency and the merchant, pick a route and name a backup. You write the rules. The issuer still approves or declines the payment.

A route is one acquiring connection: an acquirer, a merchant ID (MID) that the acquirer issued and the card scheme the acquirer reaches. With one connection there is nothing to choose. Routing starts when your white label payment gateway holds two or more connections that can take the same payment.

An illustrative setup shows the idea. You serve merchants that sell in Germany and Poland, and you hold contracts with three acquirers:

  • Cards issued in Germany go to acquirer A, which is domiciled there.
  • Cards issued in Poland go to acquirer B.
  • Every other card goes to acquirer C, your cross-border default.
  • If acquirer A times out, its traffic moves to acquirer C until A recovers.

You set these rules once for all merchants or separately for one merchant, which makes routing part of merchant management.

Note

Payment routing is not a bank routing number. A bank routing number identifies a bank for account-to-account transfers. In card payments, routing means choosing an acquirer or a network for a transaction, and a payment card carries no routing number.

How Does Payment Routing Work, Step by Step?

Your gateway routes a payment between the moment the cardholder confirms it and the moment the result appears. The gateway collects the transaction data, your rules select an acquirer, the acquirer sends the authorization through the card scheme and the issuer decides. The response then completes the payment, starts a second route or stops it.

  1. The merchant sends the payment

    The merchant’s checkout passes the card data, amount, currency and shop identifier to your gateway. The request also names one of the card transaction types, such as an authorization or a one-step payment.

  2. Your gateway reads the card

    The gateway looks up the bank identification number (BIN), the first digits of the card number. The BIN gives the issuer, the issuer country and the funding source: debit, credit or prepaid.

  3. Your rules pick the route

    The rules engine evaluates your rules in priority order. The first rule that matches selects the acquiring connection, or splits traffic between eligible connections by the weights you set.

  4. The cardholder authenticates if required

    Where 3-D Secure (3DS) applies, your 3DS Server runs the authentication with the issuer before the authorization is sent.

  5. The acquirer submits, the issuer decides

    The chosen acquirer sends the authorization request to the card scheme. The scheme passes it to the issuer, which approves or declines and returns a response code.

  6. Your gateway reads the response

    An approval completes the payment. A timeout or a technical error starts failover. A decline that the scheme allows you to send again can cascade to the next acquirer. Any other decline stops there.

  7. The same acquirer settles

    The acquirer that submitted the authorization also clears and settles the payment. Your choice of route therefore decides which acquirer pays out the funds and handles a later chargeback.

  8. You review the results

    Your team reads approvals, declines and errors for each route in the transaction statistics and adjusts the rules.

Why Does Payment Routing Matter?

Payment routing matters because acquirers, networks and credential formats do not perform alike. The same card can be approved on one route and declined on another, cost more on one network than on another, or meet an acquirer that is down. With one connection you accept whatever that connection delivers.

Two public data points and two of our own cases show the differences:

Approval depends on what you send

Visa reports that its tokenized card-not-present transactions (online payments, with no physical card) show a 4.6% lift in authorization rates globally compared with the card number. A route that cannot carry network tokens gives that difference up.

Risk depends on the network

In the Federal Reserve’s 2023 debit card data, fraud losses were 17.9 basis points of transaction value on dual-message networks, which traditionally carried signature debit, and 6.7 basis points on single-message networks, which traditionally carried PIN debit.

Availability depends on the acquirer

In one of our cases, an acquirer slowed to 30-second responses and was isolated in seconds: see acquirer failure contained in seconds.

Volume depends on where you send each card

A European high-risk PSP on our platform tripled its transaction volume in one year after card history was added to its routing rules.

An illustrative calculation

The figures below are assumptions made up for the example, not benchmarks. You process 1,000,000 authorization attempts a month with an average payment of EUR 50. One segment, cards issued in a single country, is 200,000 attempts. You move that segment to a second acquirer, through which issuers approve it more often.

Illustrative figureOne acquirerSegment moved to a second acquirer
Approval rate in the segment80%86%
Approved payments in the segment160,000172,000
Approved payments in total850,000862,000
Overall approval rate85.0%86.2%
Processed volume a monthEUR 42,500,000EUR 43,100,000

In this example one rule adds 12,000 approved payments and EUR 600,000 of processed volume a month. Your own result depends on your traffic mix, your acquirers and your starting approval rate, so measure it on a share of your traffic first.

What Are the Main Payment Routing Rules?

A payment routing rule is a condition and a target: when the payment matches the condition, it goes to the named acquiring connection. Most rule sets use eight condition types. Each reads different transaction data and serves a different goal, as the table shows.

Rule typeData it readsMain goalExample
BIN routingFirst 6 or 8 card digits: issuer, funding source, issuer countryApproval rate, costCards from one large issuer go to the acquirer that this issuer approves most often
Geographic routingIssuer country, merchant countryDomestic processingCards issued in Poland go to an acquirer in Poland
Currency routingTransaction and settlement currencyConversion costEuro payments go to an acquirer that settles in euro
Card brand and methodScheme, debit or credit, walletCoverage, costA scheme that only one acquirer supports goes to that acquirer
AmountTransaction amountRisk, feesPayments above a threshold you set go to the connection that requires 3DS
Merchant or business lineMerchant, shop, merchant category code (MCC)Contract fit, riskOne merchant’s traffic stays on the MID opened for it
Risk-basedFraud score, payment history of the cardFraud and chargebacksA card with no history is sent through 3DS
Cost-basedFees of each routeLowest costA debit card goes to the cheaper of its two networks

BIN routing

BIN rules are the most specific rules you can write, so they sit above country rules. Visa’s rules define the BIN as a 6-digit identifier for those licensed to an issuer before 22 April 2022 and an 8-digit identifier otherwise (Visa Core Rules, glossary). Your BIN table must therefore match on both lengths.

Geographic routing and local acquiring

Local acquiring means that the acquirer and the merchant are in the same country. It is not a free choice of route. Under section 1.5.1.1 of the Visa Core Rules, an acquirer accepts transactions only from a merchant outlet in its own country of domicile. A geographic rule therefore needs a merchant entity that the local acquirer may contract.

One exception is an acquirer in Europe that has passported its licence: it uses an authorisation from one EU member state to serve another.

Risk-based routing

Risk rules run before the route is chosen. They decide whether a payment is authenticated, sent to a specific acquirer or rejected, using anti-fraud tools and the card’s record. On our platform, SmartCheck card history supplies that record: 16 metrics for each card over 360 days.

What Is Least-Cost Routing?

Least-cost routing sends each payment through the cheapest route that is eligible for it. Between acquirers, it compares the fees you have contracted for the card type, region and currency. Between networks, it applies to debit cards that carry two networks, where the merchant side may choose which network processes the payment.

A cheaper route with a lower approval rate can cost more than it saves. Set an approval-rate floor for each segment and let the cost rule choose only among routes above that floor. The fee split behind each route is explained in our guide to the payment gateway business model.

US debit cards under Regulation II

In October 2022 the Federal Reserve Board finalized an update to Regulation II, effective 1 July 2023. Debit card issuers should enable at least two unaffiliated networks for every debit transaction, including card-not-present payments. The merchant side can then choose between them.

The choice changes cost. In the Federal Reserve’s 2023 data, the average interchange fee, which the acquirer pays the issuer, was more than twice as high on cards from issuers that Regulation II exempts from its interchange cap when they ran on dual-message networks as on single-message networks. On cards from issuers under the cap, single-message networks were slightly higher. The cheaper network depends on the issuer, which is why least-cost rules are written by BIN.

Co-badged cards in the European Union

In the EU, a card may carry two payment brands. Article 8 of the Interchange Fee Regulation requires routing principles for such cards to be non-discriminatory. It lets the merchant set a priority brand automatically and lets the payer override that selection. Your merchants’ checkout can preselect the cheaper brand, and it must leave the cardholder’s choice in place.

Static vs Dynamic Payment Routing: What Is the Difference?

Static routing applies fixed rules that change only when you edit them. Dynamic routing applies the same kinds of rules and also reads live data about each route, such as its error rate, response time and remaining limit. It moves traffic when a threshold you set is passed.

CriteriaStatic routingDynamic routing
When an acquirer times outTraffic stays on the route until you edit the rule, or goes to one fixed backupThe route is switched off automatically once its error rate or response time passes your threshold
InputsCard brand, BIN, country, currency, amount, merchantThe same, plus approval rate, errors, response time and limits of each route
Traffic splitFixed weights, such as 70 to 30Weights that shift with route performance
Setup effortLow: a rule tableHigher: monitoring for each route and thresholds to maintain
FitsTwo acquirers, one or two marketsSeveral acquirers and markets, or traffic that runs around the clock
Where smart routing fits
Intelligent payment routing

Smart routing goes one step further than dynamic routing. It weighs many signals for each transaction and can also decide on anti-fraud actions and 3DS. Its own guide covers the signals and the decline handling.

What Are Failover, Cascading and Retries?

Failover, cascading and retries are the three ways a gateway makes a second attempt when the first route returns no approval. Failover answers a route that is unavailable. Cascading answers a decline while the cardholder is still at checkout. A retry sends the payment again later. Card scheme rules limit the last two.

  • Failover moves traffic to another acquirer when the first one is unreachable, times out or returns technical errors. The issuer has not declined anything.
  • Cascading sends a declined payment to the next eligible acquirer at once. Our guide on how to recover declined transactions covers the logic.
  • A retry sends the payment again later, usually on the same route. It is typical for subscriptions and other recurring charges.

The issuer’s response code decides whether a second attempt is allowed. Your gateway has to read the code before it cascades, and it has to count attempts for each card across all routes, because Visa’s limit applies to the card, not to the route.

Rule

Visa sorts decline response codes into four categories (Visa Product and Service Rules, section 7.3.6.3). After a Category 1 code, such as 14 (invalid account number) or 43 (stolen card), a merchant must never resubmit the request for the same card. After codes in Categories 2 to 4, such as 51 (not sufficient funds), reattempts are capped within 30 days.

The scheme retry rules section of our smart routing guide covers both major schemes. Confirm the current limits with each acquirer.

One decline calls for neither a cascade nor a retry: Visa code 1A (additional customer authentication required), listed for its Europe region and its Central and Eastern Europe, Middle East and Africa region. In the European Economic Area it signals that the issuer wants strong customer authentication, which Article 97 of PSD2, the EU’s second Payment Services Directive, requires. Send the cardholder through 3DS and submit the payment again on the same route.

Payment Routing vs Payment Orchestration: What Is the Difference?

Payment routing is one decision: which acquirer and network take a transaction. Payment orchestration is the layer that manages many provider connections and the whole payment lifecycle, with routing as one of its functions. Cascading is narrower than both: a recovery step inside a routing rule set.

TermWhat it doesScope
Payment gatewayAccepts the payment from the merchant’s checkout, protects the card data and passes the authorization request to an acquirerThe connection between merchant and acquirer
Payment routingChooses the acquirer and network for each transactionOne decision for each payment, made before authorization
CascadingSends a declined payment to a backup acquirer when the response code allows itA recovery step inside the routing rules
Payment orchestrationManages provider connections, authentication, tokenization, routing, reconciliation and reporting from one placeThe whole payment stack

The terms “payment gateway routing” and “transaction routing” usually mean routing that runs inside the gateway.

If your gateway already holds several acquiring connections and a rules engine, you do not need a separate orchestration layer on top. Our post on orchestration vs traditional gateways compares the two setups.

What Do You Need Before You Can Route Payments?

You need at least two acquiring contracts and a way to keep settlement, tokens, card data scope and authentication consistent across them. Rules come last. Each item below has an owner. Agree the owners before you write the first rule.

AreaWhat has to be in placeWho owns it
Contracts and MIDsA contract with each acquirer and a MID for each merchant or business line, with its schemes, currencies and volume limitsYou sign and the acquirer underwrites. The acquirer issues the MIDs
Settlement and reconciliationA payout schedule and a settlement report from every acquirer, matched to your transaction recordsEach acquirer settles the payments it submitted for authorization. You reconcile them
Chargebacks and liabilityA dispute process for each acquirer and reserves that cover each oneThe acquirer that processed the payment receives the chargeback. You stay financially liable to each acquirer for your merchants
TokensStored cards that work on every route: tokens held by the gateway, not by one acquirerYour platform vendor runs the vault. You decide which tokens to request
PCI DSS scopeCard data that stays inside the gateway whichever acquirer is usedShared: the vendor validates the platform, and you validate your own environment and processes
AuthenticationOne 3DS Server in the gateway for all routes. Confirm with each acquirer whether an authentication obtained with one acquirer’s identifiers may be submitted through anotherYou run the 3DS Server. The issuer authenticates the cardholder

Tokens deserve a test before launch. When stored cards belong to one acquirer, a new route cannot charge them. In one of our cases a PSP whose acquirer went offline kept its recurring base: see tokens migrated in one week.

Authentication also differs by acquirer in the European Economic Area. Under the regulatory technical standards on strong customer authentication, a payment service provider may skip authentication for a low-risk remote card payment only while its own fraud rate stays at or below 0.13% for amounts up to EUR 100, 0.06% up to EUR 250 and 0.01% up to EUR 500. Ask each acquirer which bands it can use.

PCI DSS stays shared on every route. Outsourcing PCI DSS to a platform vendor reduces your scope and does not remove it.

How Do You Build a Payment Routing Strategy?

Build a payment routing strategy in a fixed order: constraints first, then risk, then approval, then cost. Rules are evaluated from the top and the first match wins, so the order decides the outcome as much as the rules do. Start with a small rule set and add rules only when the data asks for them.

  1. Audit your traffic

    You export approval rate and cost by acquirer, BIN, issuer country and decline code. The export shows the segments where a second route would change the result.

  2. Write the hard constraints

    You list which acquirer may take which payment: merchant, MCC, scheme, currency, country and the transaction limits of each MID. These rules sit at the top.

  3. Place the risk rules

    Your risk team decides which payments are authenticated, reviewed or rejected before a route is chosen.

  4. Add BIN rules, then country rules

    Rules for a specific issuer come first and broader geographic rules follow them.

  5. Put cost rules last

    Cost rules go below every approval rule and apply the approval floor described under least-cost routing.

  6. Name a default and a backup

    One default route catches every payment that no rule matched. Each primary route gets a failover target and, where the scheme allows it, a cascade target.

  7. Test on a share of traffic

    You send a weighted share of a segment to the new route and compare both routes over the same period before you move the rest.

  8. Review after every change

    You review the rules on a set schedule and after any change in an acquiring contract, a market or a scheme rule.

If you have not picked a platform yet, check that its rules engine supports each step above. Our guide on how to choose a white-label payment platform lists the questions to ask a vendor.

Which Payment Routing KPIs Should You Track?

Track six key performance indicators (KPIs) for every route: authorization rate, cost per approved payment, recovery rate, decline-code mix, response time and chargeback rate. A total across all routes hides the differences that routing exists to use, so break each indicator down by acquirer, BIN and issuer country.

KPIHow to calculate itBreak it down by
Authorization rateApproved authorizations divided by authorization attempts, counted on the first attempt of each paymentAcquirer, BIN, issuer country, card type
Cost per approved paymentAll fees of a route divided by its approved payments, so declined attempts show up as costAcquirer, scheme, region
Recovery ratePayments approved on a second route divided by first attempts that failedDecline code, backup route
Decline-code mixShare of each response code in all declinesAcquirer, issuer
Response time and errorsTime from request to response, and the share of timeouts and technical errorsAcquirer, hour of day
Fraud and chargeback rateChargebacks divided by settled paymentsRoute, merchant, MID

The first-attempt definition matters. If you count the final result of a cascaded payment, a weak primary route looks healthy. On our platform these reports are built in FinStatHub analytics.

What Are the Risks of Payment Routing, and Who Does Not Need It?

Payment routing adds moving parts: more contracts, more settlement reports and rules that interact. The main risks are breaches of scheme reattempt limits, duplicate charges after a timeout, volume spread too thin and rules nobody can explain. Each has a known control, listed in the table.

RiskWhat goes wrongHow to reduce it
Excessive reattemptsA cascade sends again a decline that the scheme forbids, which breaches the acquirer’s scheme obligations and your contract with the acquirerMap every response code to stop, cascade or retry, and count attempts for each card across all routes
Duplicate chargeThe issuer approved the payment through the first acquirer, but the response timed out, and failover sends the payment to a second acquirerSend a reversal to the first acquirer before the second attempt, and reconcile late responses
Volume spread too thinTraffic split across many acquirers misses the volume agreed in a contract, and each route has too little data to judgeAdd an acquirer only for a segment that needs it, and keep minimum weights where a contract requires them
Rule sprawlRules added one by one start to override each other, and nobody can say why a payment took its routeKeep the fixed order from the previous section, log the matched rule for each payment and remove rules that no longer fire
Cheaper but weaker routeA cost rule moves traffic to a route with a lower approval rateApply the approval floor before the cost rule
Good to know

Who does not need payment routing

If you work with one acquirer in one market, you have nothing to route, and a second contract is the first step. If you are still choosing an acquirer and a licence, read how to start a payment processing company first. With two acquirers and a few merchants, static rules and one fixed backup are enough.

Payment Routing with eComCharge

eComCharge runs payment routing inside its white-label gateway. The Smart Routing engine chooses the processing connection for each transaction, and the same rules apply anti-fraud actions and decide whether 3DS is needed. You manage the rules. Your merchants see your brand.

  • More than 50 routing conditions, including BIN, geography, currency, amount, card type and 3DS status.
  • A hierarchy of PSP, merchant and shop: a rule set at the top applies to every level below it.
  • Sequential fallback and weighted distribution between connections.
  • SmartCheck card history as a rule input, with no coding required.
  • A local token vault, Visa Token Service and Mastercard Secure Card on File.
  • A 3DS Server certified by Visa, Mastercard and UnionPay.

A software-as-a-service installation of eComCharge takes from 1 week and an installation on your own servers from 3 months.

eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.

The white-label payment gateway page describes the platform. Separate pages cover it for low-risk PSPs, for European banks and for iGaming and Forex PSPs.

Frequently asked questions

Payment routing is the logic a payment gateway uses to choose which acquirer and card network handle each online card payment. Rules read the card BIN, issuer country, currency, amount and merchant, pick an acquiring connection and name a backup. The issuer still approves or declines the payment.

Static routing follows fixed rules that change only when you edit them, for example all cards from one country to one acquirer. Dynamic routing uses the same kinds of rules and also reads live data about each route, so it moves traffic when an acquirer passes an error-rate or response-time threshold you set.

BIN routing uses the bank identification number, the first six or eight digits of a card number, to identify the issuer, the funding source and the issuer country. The payment then goes to the acquirer that performs best for that issuer. BIN rules are the most specific rules, so they sit above country rules.

Least-cost routing sends each payment through the cheapest eligible acquirer or, for debit cards that carry two networks, the cheaper network. Pair it with an approval-rate floor for each segment, so that a cheaper route is used only when its approval rate is about the same as the alternatives.

Payment routing chooses the first route for a transaction. Cascading is a recovery step inside the routing rules: when the issuer's response code allows another attempt, the payment is sent to the next eligible acquirer while the cardholder is still at checkout. Declines that a card scheme marks as final must not be cascaded.

Payment routing is one decision: which acquirer and network handle a transaction. Payment orchestration is a broader layer that also manages provider connections, authentication, tokenization, reconciliation and reporting, with routing as one of its functions. A gateway that holds several acquiring connections and a rules engine routes without a separate orchestration layer.

Payment routing is the general term for choosing an acquirer for each payment. Smart payment routing, also called intelligent routing, weighs many signals for each transaction, such as card history and live route performance, and can also decide on anti-fraud actions and 3-D Secure. Our intelligent payment routing guide covers it in detail.

You need at least two acquiring connections that can take the same payment, otherwise the gateway has nothing to choose between. Add a third only for a segment that needs it, such as a country or a currency, because every acquirer adds a contract, a settlement report and volume commitments to manage.

No. A bank routing number identifies a bank for account-to-account transfers. Payment routing is the process of choosing an acquirer or a card network for a card transaction. A payment card carries no routing number, and the two terms are unrelated.

It depends on your deployment model, your volume and the acquiring connections you need. On eComCharge, routing is part of the gateway and not a separate layer. eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.


Respectfully, the eComCharge Team

eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.

Request demo

Relevant guides

Software

SaaS Payment Platform: How Embedded and Recurring Payments Work

How vertical SaaS platforms and the PSPs that serve them run embedded payments: the four models and their liability, recurring billing and SCA, failed renewals, cross-border acquiring, PCI DSS scope and the revenue maths.

Oksana Mikhailovskaya
Oksana Mikhailovskaya June 20, 2025

Set up your payment processing system

in 7 days, not a year
Request demo