Routing Logic

Routing logic is the set of rules that decides where a payment should go.

When a merchant connects to more than one acquirer, gateway, PSP, or payment method, routing logic tells the system what to do with each transaction. It can be simple (send all EUR payments to one acquirer) or layered across country, BIN, provider performance, risk score, cost, and authentication status.

Routing logic sits inside a payment orchestration layer. The layer connects the merchant to multiple providers; the routing logic decides how traffic moves between them.

Key Takeaways

• Routing logic is the rule set behind payment route selection.
• It is the configuration that decides how routing behaves, not the routing itself.
• Common rules cover cost, success rate, geography, risk, authentication, weighting, and fallback.
• Strong routing logic needs regular review as fees, providers, and fraud patterns change.
• In Europe, routing logic is also shaped by PSD2 SCA, co-badged card choice, and scheme fee pressure.

Routing Logic vs Dynamic Routing

‍

Dynamic routing is the action. Routing logic is the decision model behind it.

Types of Routing Logic

Most setups combine several rule types depending on the merchant's markets, volume, risk profile, and provider stack.

‍

Cost-based routing is often one of the more straightforward rule types to measure. According to the Reserve Bank of Australia found that merchants with least-cost routing enabled paid nearly 20% less on average to accept debit card transactions than merchants without it, although the result varied by merchant size and pricing plan. Reserve Bank of Australia

How Routing Logic Works in Practice

Routing engines usually evaluate rules in a priority order. In most configurations, the first match wins.

A typical hierarchy:

• Blocking rules: stop unsupported currencies, blocked BINs, sanctions.
• Authentication rules: decide between frictionless flow, SCA exemption, or step-up to 3DS.
• Primary route rules: send the payment through the preferred provider for that segment.
• Override rules: adjust the route for certain issuers, countries, amounts, or risk scores.
• Fallback rules: retry only specific recoverable failures through another provider.
• Default route: catch transactions that match no specific rule.

Among the most common operational mistakes are retrying hard declines like lost or stolen cards, cascading too aggressively on the same card, and letting old rules stay live after scheme fees, provider coverage, or fraud patterns change.

Routing Logic and European Regulation

In Europe, routing logic is not only a performance tool. It also touches regulatory and compliance decisions.

Under PSD2, Strong Customer Authentication applies to many electronic payments in the EEA unless a valid exemption applies. Routing logic decides whether to attempt a Transaction Risk Analysis exemption, treat the payment as merchant initiated, or step up the customer. Operators should verify their exemption strategy with qualified legal and compliance teams.

According to the 2025 joint EBA and ECB payment fraud report total payment fraud in the EU and EEA reached approximately €4.2 billion in 2024, and card fraud rates were reported to be significantly higher when the counterpart was outside the EEA. European Central Bank

Cost-based routing also depends on current fee data. According to the UK Payment Systems Regulator March 2025 that Mastercard and Visa increased core scheme and processing fees to acquirers by an estimated 25% or more since 2017 reportedly, costing UK businesses at least approximately £170 million extra per year. Payment Systems Regulator

If routing rules use stale fee data, they may keep choosing routes that no longer make commercial sense.

Rule-Based vs ML-Driven Routing

Vendor language often makes machine learning sound like the default. In practice, production routing in Europe tends to be largely rule-based, and that is not necessarily a weakness.

Rule-based routing is transparent and auditable. Operators can see exactly why a transaction was routed a certain way, test the rule, and adjust it when fees or provider performance change.

ML-driven routing can help when there is enough transaction volume and clean data, but its value depends on whether the merchant can actually measure the uplift. In many cases, effective setups combine merchant-owned rules with performance data and selective automation.

‍