Intelligent payment routing is the real-time choice of acquirer for each online card payment, made by scoring the card, its payment history, the health of each route and its cost. This guide is for PSPs, acquiring banks and electronic money institutions (EMIs) that run several acquiring connections and want more approvals within card-scheme retry rules.
What Is Intelligent Payment Routing?
Intelligent payment routing is the data-driven layer on top of ordinary routing: the engine reads the card, the merchant, the card’s history and the state of every route, and it moves traffic when a route degrades or reaches its limit. For the basics of how a gateway sends a payment to an acquirer, and how static and rule-based routing differ, start with our payment routing guide.
Intelligent routing keeps the paths you wrote, such as Visa cards from Germany to acquirer A, and adds context to each decision. Has this card charged back at another PSP? Is acquirer A close to its weekly limit? Did the issuer just return a soft decline that could be approved if sent through another acquirer?
Intelligent routing is narrower than payment orchestration, which also manages provider connections, tokenization, settlement reconciliation and reporting. It is wider than cascading, which is only the recovery step after a decline. On eComCharge, the Smart Routing engine sits inside the gateway, so no separate layer is needed on top.
How Does Intelligent Payment Routing Work, Step by Step?
For every payment, the engine runs one loop inside your gateway: collect the signals, match the rules, decide on protection, authentication and route, send the authorization, then read the response code. The issuer still approves or declines. Your rules decide only what reaches the issuer, through which acquirer, and what happens after the answer.
Your gateway collects the signals
The merchant’s checkout sends the card, amount, currency and shop. The gateway reads the BIN. The glossary of the Visa rules defines it as the first 6 digits for BINs licensed before 22 April 2022, otherwise the first 8.
The engine matches your rules
Rules are checked in priority order at the level where you set them: the PSP, the merchant or one shop. A rule set at the top applies to every level below it.
It makes three decisions
Protect: allow, review or reject the payment. Authenticate: force or skip 3DS. Route: choose the processing connection, or split eligible traffic between connections by weight.
The cardholder authenticates if required
Your 3DS Server runs the authentication with the issuer before the authorization leaves the gateway.
The acquirer submits, the issuer decides
The chosen acquirer sends the request through the card scheme to the issuer, which returns an approval or a decline response code.
The engine reads the response
A timeout or technical error starts failover. A soft decline can cascade to another acquirer while the cardholder waits, or be retried later. A hard decline stops.
Results feed the next decision
Approvals, declines and chargebacks go into the card’s history and into your transaction statistics, for the next decision.
Each step has an owner. You write and maintain the rules, your platform vendor runs the engine and the 3DS Server, the acquirer submits and later settles the payment, the scheme carries the message and the issuer decides.
Which Signals Does an Intelligent Routing Engine Score?
An intelligent routing engine scores five groups of signals: the card and its issuer, the transaction, the merchant, the card’s payment history and the live state of each route. Each group informs a different decision, so map signals to decisions before you write rules. A policy mapped this way is easier to audit.
Routing signals and the decisions they inform
Signal
Where it comes from
Decision it informs
BIN and issuer country
First 6 or 8 digits of the card number
Issuer-specific or domestic route
Card brand and funding source
BIN table: scheme; debit, credit or prepaid
Connections that support the card; cost rules
Amount and currency
The merchant’s request
Acquirer that settles in that currency; 3DS above a threshold you set
Merchant and shop
Your merchant set-up: contract, merchant category code (MCC), risk policy
Which connections are allowed at all
Card payment history
Your own records and network history: chargebacks, failed and successful payments
Reject, review, force or skip 3DS; trusted or untrusted channel
Route health
Gateway monitoring: errors, timeouts, response time
Failover, traffic shift
Accumulated volume
Processed amount against each connection’s limit
Notify, move traffic before the cap
Cost
The fees you contracted for each route
Cheapest route above an approval floor
Bank response code
The issuer’s answer to the last attempt
Cascade, retry later, stop or add to a blacklist
BIN data also drives cost rules: our post on BIN routing shows the savings side for gateway tenants.
Card history: the signal plain routing lacks
Card history separates a first-time card from a card with an established record. On our platform, SmartCheck tracks 16 metrics per card over 360 days, across your PSP and across the eComCharge processing network, and feeds them into Smart Routing rules with no coding.
If you run a high-risk PSP, you can keep two channels apart: one for untrusted first-time cards and one for trusted cards, because the channels differ in cost and reliability. A European high-risk PSP on our platform tripled its transaction volume in one year after card history went into its routing rules.
Issuer country and international traffic
For global traffic, the engine reads the issuer country from the BIN and prefers an acquirer in that country, falling back to a cross-border acquirer when none fits. The domestic route needs a legal basis: under section 1.5.1.1 of the Visa Core Rules, an acquirer accepts transactions only from merchant outlets in its own country of domicile, unless an exception applies.
Rules, Weights or Machine Learning: How Does the Engine Pick a Route?
The engine picks a route by one of four methods: ordered rules where the first match wins, a weighted split between eligible routes, the best recent approval rate for the segment, or a predictive model that scores each route. Static and dynamic rules and least-cost logic are covered in our payment routing guide.
Four ways an intelligent engine chooses the route
Method
How it decides
What it needs
Main risk
Ordered rules
The first rule that matches the payment selects the route
A rule table you maintain
Rules start to override each other
Weighted split
Eligible traffic is divided between routes by percentages you set, such as 70 to 30
Two or more equivalent routes
Weights go stale unless reviewed
Performance-based
The route with the best recent approval rate in the segment wins
Enough attempts per segment to compare
Small segments swing on noise
Predictive model
A model estimates the approval probability of each route
A large labelled history per segment
Hard to explain to an acquirer, a merchant or an auditor
Do you need machine learning for AI payment routing?
A predictive model needs enough labelled attempts in each segment to beat well-tuned rules. Its choice is also harder to explain when an acquirer or a merchant asks why a payment took a route. eComCharge Smart Routing uses configurable rules with weighted distribution between connections.
How Do Routing, Antifraud and 3DS Work as One Decision?
All three read the same data, so one rules engine can decide whether the payment proceeds, whether the cardholder authenticates and which acquirer receives it. Separate systems can contradict each other, for example an antifraud tool that allows a card your router sends to a channel reserved for trusted cards.
In eComCharge Smart Routing, one set of rules can route a transaction, apply an antifraud action (allow, review, reject, notify or add the card to a blacklist) and force or skip 3DS. The examples below come from the product page.
Example rules from eComCharge Smart Routing
If
Then
Decision
Merchant A, currency EUR, issuer country Germany
Route to Gateway A
Route
Repeated payment failures detected
Reject
Protect
No chargebacks within the defined period
Skip 3DS
Authenticate
Weekly processing reaches 85% of the defined limit
Notify
Processing control
Specified bank response code returned
Add to blacklist
Protect
Where PSD2 makes 3DS part of routing
In the European Economic Area, Article 97 of PSD2, the EU’s second Payment Services Directive, requires strong customer authentication when the payer initiates an electronic payment. The regulatory technical standards on authentication set exemptions, such as remote payments up to EUR 30 within cumulative limits (Article 16) and transaction risk analysis (Article 18).
Visa lists code 1A, additional customer authentication required, for its Europe and CEMEA (Central and Eastern Europe, Middle East and Africa) regions. After 1A, send the cardholder through 3DS and resubmit on the same route instead of cascading.
Skipping 3DS for trusted cards is also a rule: our post on how to process low-risk payments without 3DS shows the set-up.
Soft vs Hard Declines: Which Declined Payments Can You Recover?
A soft decline is temporary: the same card may be approved later, on another route or after authentication. A hard decline is final: the card is lost, stolen, closed or invalid, so routing cannot recover it. A hard decline needs new card details, an account updater (a scheme service that sends new details after reissue) or another payment method.
Visa decline categories
Visa decline response codes by category
Category
Example codes
Merchant reattempt limit
1: Issuer will never approve
04 pick up card, 14 invalid account number, 41 lost card, 43 stolen card, 46 closed account, R0 and R1 stop payment
Never resubmit for the same payment credential
2: Issuer cannot approve at this time
51 not sufficient funds, 59 suspected fraud, 61 exceeds approval amount limit, 91 issuer or switch inoperative, 96 system malfunction
Up to 20 attempts in 30 days
3: Data quality, revalidate payment information
54 expired card, N7 card verification value (CVV2) failure, 1A additional customer authentication required (CEMEA and Europe regions)
Up to 20 attempts in 30 days
4: Generic
All other decline codes
Up to 20 attempts in 30 days
Source: Visa Product and Service Rules, 24 October 2026, section 7.3.6.3, Table 7-2
Category 3 asks you to fix the data first. An expired date or a CVV2 failure declines again on every route until the cardholder corrects it, so a cascade only spends attempts.
Mastercard Merchant Advice Codes
A declined Mastercard payment can carry a Merchant Advice Code (MAC): guidance from the issuer or card network on the next action, as the Mastercard Gateway documentation defines it for payments and authorizations. The retry rules below say what each code asks you to do.
Good to know
Normalise decline codes first
Every acquirer returns codes in its own format. Map them into one internal set tagged stop, cascade, retry later or authenticate, so that “insufficient funds” triggers the same rule whichever acquirer returned it.
Intelligent Routing and Cascading: Cascading vs Retries vs Failover
Intelligent routing picks the first route. Failover, cascading and retries decide what happens when that route returns no approval. Failover reacts to a route that is down, cascading re-sends a soft decline to another acquirer while the cardholder waits, and a retry sends it again later. Only cascades and retries follow a decline, so only they count against scheme limits.
Three second-attempt mechanisms
Mechanism
Trigger
What happens
Who acts
Typical use
Failover
Timeout, connection or technical error
Traffic moves to another acquirer; no issuer has declined
Your gateway
Outages, slow acquirers
Cascading
Soft decline
Immediate new attempt on another eligible acquirer
Your gateway, or the merchant’s repeated request
Live checkout
Retry
Soft decline
Later attempt on a schedule, usually on the same route
The merchant’s or your billing logic
Subscriptions, recurring billing
Recovery patterns and cascade design are covered in our guide on how to recover declined transactions with cascading.
How cascading works on the eComCharge API
In the eComCharge API, cascading works for payment and authorization transactions that end in the failed status, not expired or incomplete. The merchant repeats the request with the IDs of the failed gateways in excluded_gateways and duplicate_check set to false, and the shop needs several equivalent gateways, as the cascading payments documentation describes.
For host-to-host payment transactions, your eComCharge manager can enable automatic cascading for a shop. The platform then retries a failed payment through another available gateway without a new request from the merchant, as the release note on automatic H2H cascading explains.
What Are the Visa and Mastercard Retry Rules?
Visa forbids any resubmission after a Category 1 decline and permits up to 20 attempts in 30 days after Category 2, 3 and 4 declines, under section 7.3.6.3 of the Visa Product and Service Rules. Mastercard advises per decline through the Merchant Advice Code. Count attempts for each card across every acquirer, because a cascade is still a reattempt.
Rule
Visa Product and Service Rules, section 7.3.6.3
After a Category 1 decline response code, a merchant must never resubmit an authorization request or account verification for the same payment credential. For Category 2, 3 and 4 codes, Table 7-2 states: “Reattempt permitted (up to 20 attempts in 30 days)”. Source: Visa Core Rules and Visa Product and Service Rules, edition of 24 October 2026.
Section 1.7.2.1 of the Visa Core Rules adds a rule for anyone who reattempts after a decline, whether acquirer, merchant, payment facilitator or processor: do not intentionally manipulate data elements of the original request. The list includes the acquiring identifier, the acquirer and merchant country, the MCC and the electronic commerce indicator. Agree with each acquirer how it treats a cascade under this rule before you enable one.
Mastercard’s advice comes with each decline. Stop after MAC 03 (do not try again) or 21 (payment cancellation). Retry later after MAC 02, or after the wait that MACs 24 to 30 set, from one hour to 10 days. Treat MAC 01, new account information available, as a prompt to update the card details.
Confirm that each acquirer passes MACs through to you on card payments, and ask it for the Mastercard attempt limits and any fees that apply in your region.
Illustrative example
An attempt budget for one card
The assumptions are invented for the example. A subscription PSP bills a Visa card monthly, and the shop has three equivalent gateways with cascading switched on. The example counts every attempt on the card against one budget, the cautious reading of Table 7-2.
Day
Attempt
Result
Attempts used of 20
1
First attempt, gateway A
51, not sufficient funds
1
1
Cascade, gateway B
51
2
1
Cascade, gateway C
51
3
3
Scheduled retry, gateway A
51
4
7
Scheduled retry, gateway A
Approved
5
Each cascade used an attempt from the same 30-day budget as the scheduled retries. Had gateway A returned 43, stolen card, on day 1, the budget would have been zero: no cascade and no retry.
Do
Cascade or retry only codes your map marks as recoverable.
Follow the MAC on Mastercard declines.
Count attempts for each card across all routes.
Space out retries on recurring payments.
Send 1A declines to 3DS.
Don’t
Resubmit after a Visa Category 1 code or MAC 03 or 21.
Cascade a stolen or closed card to “try another bank”.
Change the MCC, country or electronic commerce indicator to win an approval.
Retry the same request in a tight loop.
How Do Network Tokens Help Intelligent Routing?
Network tokens fix what routing cannot: stored card details that are out of date. Visa describes them as carrying up-to-date card information. 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.
Network tokens
Scheme-issued tokens replace the card number in stored-card payments.
Account updater
Updates stored card details after expiry or reissue. It answers some hard declines that no route can recover.
Token portability
To route a card-on-file payment to another acquirer, the stored card must work there. Tokens held by the gateway, not by one acquirer, make that possible.
eComCharge tokenization keeps cards in a local vault alongside Visa Token Service and Mastercard Secure Card on File, and the eComCharge team can move tokens between acquirers by extraction, conversion and re-tokenisation. When one PSP’s acquirer went offline, its tokens moved in about a week: 95% of the tokens that acquirer could share reached the new acquirer, and recurring payments continued.
Tokens also narrow your PCI DSS scope. On eComCharge, cards are tokenized in a PCI DSS Level 1 vault and your merchants store the token, not the card number. A merchant that collects card data host-to-host still handles it at checkout, and you still validate PCI DSS for your own systems and processes, so the scope is shared, not removed.
How Does Intelligent Routing Handle Outages and Processing Limits?
The engine watches each connection’s errors, response time and accumulated volume, and moves eligible traffic before checkout fails. Failover handles an acquirer that is down or slow. Limit rules handle a contract cap: the engine notifies your team or shifts traffic as volume approaches the cap you set.
A slow acquirer harms checkout as much as a dead one. On our platform a transaction has 30 seconds by default to reach a final status, and an acquirer that answers later leaves it incomplete, as our post on the 30-second transaction rule explains. In one case, an acquirer slowed to 30-second responses and was isolated in seconds through the interface.
Limits matter as much as outages. On the Smart Routing product page, a rule notifies the team when weekly processing on a gateway reaches 85% of its defined limit, so traffic can move before payments start to fail. Set the transaction limits for each connection first.
Before you rely on failover
A second acquirer that takes the same card brands, currencies and merchant categories.
Error-rate and response-time thresholds for each connection.
A volume limit for each connection, with a notification below the cap.
A reversal of the first authorization when a timeout is followed by a new attempt.
A settlement report and a reserve for each acquirer, because each one settles the payments it submitted. A multi-acquirer strategy covers both.
How Do You Measure Intelligent Routing Results?
Measure on your own traffic with split tests. Send a share of one segment to a new route, compare first-attempt approval rate and cost over the same period, then move the weights. An uplift figure without its baseline, period and traffic mix cannot be compared with your result, so do not plan on one.
Intelligent routing KPIs
KPI
How to calculate it
What it tells you
First-attempt approval rate
Approved first attempts divided by first attempts, by BIN, issuer country and acquirer
Which route wins in each segment
Decline-code mix
Share of each normalised code in all declines
How much volume is recoverable
Recovery rate
Payments approved after a cascade or retry divided by failed first attempts
What cascading and retries add
Attempts per card
Attempts on each card over the last 30 days
Early warning before the Visa limit
Cost per approved payment
All fees of a route divided by its approved payments
Cost and approval in one number
Chargeback rate per route
Chargebacks divided by settled payments
Whether more approvals bring more fraud
Count the first attempt separately from the final result, or a weak primary route looks healthy behind its cascades.
What Are the Risks of Intelligent Routing, and Who Does Not Need It?
Intelligent routing adds decisions that can fail quietly: a retry that breaks a scheme rule, a rule set nobody can explain, history data that misjudges a card. Each risk has a control, listed below. With one acquirer, or two acquirers in one market, plain rules with one backup do the job.
Intelligent routing risks and controls
Risk
What goes wrong
How to reduce it
Excessive reattempts
Cascades and retries pile up on one card and pass the Visa limit of 20 attempts in 30 days
Count attempts for each card across all routes and stop at a cap below the limit
Wrong code mapping
A hard decline mapped as soft is cascaded to another acquirer
Review the map whenever you add an acquirer, and log the matched rule for each payment
Conflicting decisions
Antifraud allows a card, 3DS is skipped and the route sends it to the trusted channel on thin history
Keep the three decisions in one engine with one rule order
Token lock-in
Stored cards held by one acquirer move to a new route only if that acquirer exports them, and only in part
Keep tokens in the gateway vault
Good to know
Who does not need intelligent routing
With one acquirer you have nothing to route, and a second contract comes first. If you are still choosing an acquirer and a licence, read how to start a payment processing company. Intelligent routing becomes useful with several acquirers, several markets or high-risk traffic that needs separate channels.
Implementing Intelligent Routing with eComCharge
eComCharge runs intelligent routing inside its white-label gateway, through the Smart Routing rules engine. Configuration follows the decision loop described above, and the steps below give the order to set it up in.
Set defaults at PSP level
You set global antifraud rules, blacklists and fallback routes once, for all merchants.
Override for each merchant and shop
You set routes, 3DS policy and limits that follow each merchant’s acquiring contracts and risk.
Map decline codes
You map each acquirer’s response codes to stop, cascade, retry later or authenticate.
Switch on cascading within scheme limits
You give each shop several equivalent gateways and a cap on attempts for each card.
Split, measure, adjust
You test routes with weights and move volume to the routes that win.
What the platform provides
More than 50 routing conditions, including BIN, geography, currency, amount, card type and 3DS status.
Sequential fallback and weighted distribution between connections.
SmartCheck card history: 16 metrics per card over 360 days.
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.
Intelligent payment routing is the real-time choice of acquirer for each online card payment. A rules engine in the gateway scores the card, the merchant, the card's payment history, the health and limits of each route and its cost, then picks the connection. For the basics of routing itself, see our payment routing guide.
Intelligent routing chooses the first route for a payment. Cascading is the recovery step after a soft decline: the payment is sent at once to another eligible acquirer while the cardholder is still at checkout. Routing decides where to start; cascading decides where to go next, and only when the decline code allows another attempt.
Under section 7.3.6.3 of the Visa Product and Service Rules, a merchant must never resubmit after a Category 1 decline, such as a lost, stolen or closed card. After Category 2, 3 and 4 codes, such as 51 (not sufficient funds), Visa permits up to 20 attempts in 30 days. Cascades count, so track attempts per card across all acquirers.
Some engines score routes with predictive models; others, including eComCharge Smart Routing, use configurable rules with weighted distribution between connections. A model needs a large labelled history in each segment to beat well-tuned rules, and its decisions are harder to explain to an acquirer, a merchant or an auditor.
The Merchant Advice Code is guidance from the issuer or card network on what to do after a decline. MAC 03 means do not try again and MAC 21 means payment cancellation, so both stop the payment. MAC 02 means try again later, and MACs 24 to 30 set a wait of one hour to 10 days. Confirm that each acquirer passes MACs through to you.
No. Intelligent routing is the decision of where each payment goes, together with related decisions on antifraud and 3DS. Payment orchestration is a wider layer that also manages provider connections, tokenization, settlement reconciliation and reporting, with routing as one of its functions. A gateway with a built-in rules engine routes without a separate orchestration layer.
Yes, on platforms built for PSPs. In eComCharge Smart Routing, rules can be set at PSP, merchant or individual shop level. A rule set at the top applies to every level below it, and each merchant can still keep its own routes, antifraud logic, 3DS policy and limits on one shared infrastructure.
It depends on your deployment model, your volume and the acquiring connections you need. On eComCharge, Smart Routing is part of the white-label gateway rather than a separate product 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.
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.
A guide for PSPs, acquiring banks and EMIs to the processing engine: what payment processing software does at each stage of a card payment, who owns each step, which interfaces and requirements apply, and how to test it.
What payment service provider software includes, who uses each module, what a multi-merchant setup needs, how fees and payouts work, build vs white label, and which compliance duties stay with you.
A guide for PSPs, banks and EMIs adding peer-to-peer transfers through an API: how the funding and credit legs work, scheme push-payment rules, EU licensing and AML obligations, KYC limits, fraud controls and integration options.
An overview of payment routing for PSPs and banks: how a gateway chooses the acquirer for each online payment, the main rule types, static vs dynamic routing, least-cost routing, failover and cascading, KPIs and risks.
How PSPs and acquirers process high-risk card payments: which merchants count as high risk, who carries the liability, Visa VAMP thresholds, reserves and limits, the gateway features you need, multiple acquirers and the risks.