Payment routing is the process of deciding which payment provider receives each transaction your business processes. Every card payment, bank transfer, and digital wallet transaction follows a route. The question is whether that route is chosen by default or by logic.
Most businesses don’t give payment routing much thought until something goes wrong: a processor goes down, a batch of transactions gets declined for no clear reason, or an expansion into a new market produces frustratingly low approval rates. By that point, the costs are already visible. This guide explains what payment routing is, how the two main approaches differ, and what the business case for smart routing actually looks like in numbers.
What Is Payment Routing?
Payment routing is the decision layer that sits between your payment integration and the processors that authorize transactions. When a customer pays, your system needs to send that transaction somewhere, to a specific payment processor, bank network, or acquirer. Routing is what makes that choice.
A routing system can be as simple as “always send transactions to Provider A” or as sophisticated as “evaluate each transaction against current approval rates, processing fees, card type, and issuer geography, then select the optimal provider.” The first is static routing. The second is dynamic routing.
The distinction matters because approval rates and processing costs are not fixed. They vary by processor, by card type, by geography, by time of day, and by what each provider is currently doing with their infrastructure. A routing decision made on stale assumptions, or no assumptions at all, leaves money on the table.
Key point: According to Worldpay’s C-Suite Guide to Authorization Rates (2025), the global average card authorization rate is 85-90%. Optimized merchants achieve 91-96%. Top-tier Worldpay clients reach 97% or higher. For a business processing $1 billion in annual transactions, each 1% improvement in authorization rate equals $10 million in recovered revenue without acquiring new customers or increasing marketing spend.
Static vs dynamic routing: the critical difference
Static routing assigns transactions to a fixed processor or set of processors, configured once and left alone. The logic is simple: transaction comes in, goes to Provider A. If Provider A is experiencing elevated declines or is temporarily unavailable, the transaction fails. There is no fallback, no performance comparison, and no adaptation.
The appeal of static routing is its simplicity. For a business processing modest volumes through one payment method in one geography, it works. The problems emerge as volume grows, payment methods multiply, and markets expand.
Static routing has three specific failure modes that matter at scale:
- Performance blind spots: a processor’s approval rate for Mastercard debit in Germany may be running at 78% today due to a technical issue on their side. Static routing doesn’t know this and keeps sending transactions there. Dynamic routing detects the drop and shifts traffic.
- Cost inflexibility: processing fees aren’t uniform across providers. Some networks charge less for specific card types or transaction categories. Under the Durbin Amendment in the United States, debit cards must be enabled on at least two unaffiliated networks, and merchants have the right to route to the less expensive one. Static routing leaves that cost reduction unclaimed.
- Geography mismatch: routing a Brazilian customer’s transaction through an international acquirer instead of a domestic one drops the approval rate from 70-90% to 30-50%, a gap of over 20 percentage points (Solidgate, 2024). This is not a small variance; it’s the difference between a healthy checkout and a broken one in that market.
| Factor | Static routing | Dynamic routing |
|---|---|---|
| Processor selection | Fixed, configured once | Per-transaction, based on real-time signals |
| Performance response | None — no awareness of approval rate changes | Shifts traffic when a processor’s rate drops |
| Cost optimization | None — same provider regardless of fee differences | Routes to lowest-fee eligible network per transaction type |
| Geography handling | Same provider for all markets | Selects acquirer with local relationships for each market |
| Failure handling | Transaction fails if provider is down | Evaluates alternatives before sending |
Static routing is sufficient for low-volume, single-market operations. The performance gap widens as transaction volume, payment methods, and geographies increase.
Dynamic routing evaluates each transaction individually before it’s sent. The routing engine checks current approval rates across connected processors, the fee structure for this card type, the geographic match between the card’s issuing country and available acquirers, and any business rules set by the merchant. It then selects the processor most likely to authorize the transaction at the lowest cost.
The difference between the two approaches isn’t philosophical, it’s quantifiable. Adyen’s intelligent routing pilot with 20+ enterprise merchants, including eBay and Microsoft, delivered 26% average cost savings on US debit transactions, with some merchants saving up to 55% (Adyen, 2024). One merchant saved $600,000 in the first 30 days alone.
The business case for dynamic routing
The case for dynamic routing rests on three business outcomes that are measurable and convertible into budget terms.
The first is authorization rate recovery. Failed payments account for up to 15% of lost ecommerce sales (Adyen Retail Report, 2024). Card declines cause 9% of checkout abandonment (Baymard Institute, 2024). In the United States, false declines, which are valid transactions incorrectly rejected, cost merchants an estimated $20 billion annually (Checkout.com, citing Javelin Strategy & Research). Worldpay’s smart routing and retry tools deliver a 9.3% average lift in authorization success across their merchant base (Worldpay, 2025). Capgemini research, cited by Gr4vy (2025), puts the average authorization rate improvement from payment orchestration with dynamic routing at 2-3 percentage points.
The arithmetic is straightforward. Take your monthly transaction volume, apply your current authorization rate, then model what a 2% improvement adds back. For most mid-sized businesses, this is a conversation that belongs in a board meeting, not a technical spec.
The second is processing cost reduction. Routing isn’t just about approvals; it’s also about what each approved transaction costs. Different processors charge different fees for the same card type. Routing to the cheapest eligible network for each transaction type reduces the per-transaction cost without changing anything visible to your customers. Adyen’s 26% debit routing cost reduction wasn’t achieved through negotiation; it was achieved by routing transactions to the least-cost eligible network, which Durbin Amendment rules make a merchant right in the US. For detail on how cost optimization through routing works, see reducing payment processing costs through routing.
The third is subscription churn prevention. For businesses running subscription revenue, payment failures carry a compounding cost. Research across multiple studies shows that 20-40% of churn in subscription businesses is involuntary, meaning customers who never intended to cancel but lost access because a payment failed (FlyCode, 2024). Smart routing’s contribution here is proactive: by selecting the processor most likely to approve a renewal transaction based on the cardholder’s bank and card type, it reduces the failure rate that triggers dunning sequences and, ultimately, cancellations.
There is also a market expansion dimension. The Brazil domestic-vs-international acquirer example above isn’t unique to Brazil. Every cross-border market has its own approval rate dynamics tied to which acquirers have local relationships with issuing banks. Routing to the right acquirer for each market is the difference between entering that market successfully and experiencing approval rates that make the expansion commercially unviable. For more on cross-border approval rate dynamics, see how a multi-processor strategy can improve your authorization rates.
What routing decisions are based on
A dynamic routing engine makes decisions using a combination of static rules and real-time signals. Understanding what data feeds into routing helps business leaders ask sharper questions when evaluating routing capabilities.
Input What it covers Transaction attributes Card type (credit, debit, prepaid), card network (Visa, Mastercard, Amex), transaction amount, merchant category code Geographic data Issuing bank’s country, cardholder’s billing address, merchant location — determines which acquirer has local relationships Real-time performance data Current approval rates, latency, and error rates for each connected processor, monitored continuously Cost rules Fee structures from each processor, weighed against expected approval rates; optimizable for cost, approval rate, or both Regulatory signals In European markets, eligibility for SCA-exempt flows under PSD2 for low-value or low-risk transactions
Routing decisions combine all of these inputs in milliseconds, before the transaction is sent to any processor. From the customer’s perspective, nothing is visible.
Routing to a domestic acquirer in markets where local relationships matter materially changes the outcome. Real-time performance data is what separates dynamic routing from a sophisticated static configuration. A processor performing at 96% this morning may be at 84% this afternoon. A routing engine that updates its signals in real time shifts traffic before the decline rate shows up in your reporting.
How payment orchestration enables smart routing
Knowing that dynamic routing is better than static routing is a different problem from actually implementing it. Building a routing engine in-house requires integrating with multiple payment processors, maintaining those connections, writing the routing logic, testing across card types and geographies, and updating the logic as processor performance changes. Estimates from engineering teams put a custom routing build at 6-12 months, with each new processor connection adding 3-6 weeks of development, testing, and certification (Crafting Software, 2025).
Corefy’s State of Payment Maturity (2024), based on 793 merchant questionnaires, found that 59% of businesses operate at the “fragmented” stage, with disconnected systems and no unified routing strategy. The same research found that 42% of businesses report frequent payment processor disruptions. The gap between knowing routing optimization matters and having the routing infrastructure to act on it is where most businesses stall.
| Factor | Build in-house | Orchestration platform |
|---|---|---|
| Initial build | 6-12 months | Weeks to go live |
| Each new processor | 3-6 weeks of dev, testing, certification | Configuration |
| Routing logic updates | Your team, per provider | Platform handles |
| Ongoing maintenance | Engineering capacity consumed | Platform absorbs |
The comparison that matters is orchestration cost vs. the full cost of building, maintaining, and operating routing logic internally — not vs. your current processor cost.
Payment orchestration closes that gap. An orchestration platform provides a single connection to multiple payment processors and handles routing logic automatically. Rather than your team building and maintaining routing rules for each processor relationship, the platform evaluates transactions across your connected providers and selects the best path based on your configuration. Orchestra’s intelligent payment routing operates this way: one integration that routes transactions across multiple processors without requiring your team to manage each provider connection individually.
Routing happens server-side, between your integration and the processors. Your customers see nothing change. Checkout UI, payment form, and customer experience remain identical. The developer’s guide to payment routing covers the technical specifics for teams evaluating implementation options.
For a fuller explanation of how orchestration affects the engineering burden, see how payment orchestration simplifies payments.
Frequently Asked Questions
What is the difference between static and dynamic payment routing?
Static routing sends every transaction to the same predetermined processor regardless of conditions. Dynamic routing evaluates real-time data, including provider approval rates, processing costs, and geographic performance, and selects the optimal route per transaction. Static routing is simple to configure and sufficient for low-volume, single-market operations. At scale, the performance and cost differences between the two approaches become substantial.
What is the difference between payment routing and a payment gateway?
A payment gateway captures and encrypts the transaction data at the point of payment. Payment routing decides which processor or network receives that transaction for authorization. The gateway is the entry point; routing determines the path after the transaction enters your payment infrastructure. Many businesses use a gateway without any active routing logic, sending all transactions to a single processor by default.
How does dynamic routing improve authorization rates?
Dynamic routing monitors approval rates across connected processors in real time and shifts transactions to the provider currently performing best for a given card type, geography, and transaction profile. When a processor’s approval rate drops due to a technical issue or capacity constraint, the routing engine detects the change and redirects traffic before the decline rate builds up. Worldpay reports that smart routing and retry tools deliver a 9.3% average lift in authorization success (Worldpay, 2025).
What is payment cascading?
Cascading is a reactive fallback. When a transaction is declined by the primary processor, the system automatically retries it through a secondary processor within the same checkout session. Dynamic routing is proactive: it selects the best provider upfront, before the first attempt. Cascading handles failures after they occur; routing aims to reduce failure rates in the first place. The two mechanisms complement each other in a well-configured payment infrastructure.
How much can smart routing reduce payment processing costs?
Adyen’s intelligent routing pilot achieved 26% average cost savings on US debit transactions across 20+ enterprise merchants including eBay and Microsoft, with some merchants saving up to 55% (Adyen, 2024). Cost savings come from routing to the lowest-fee networks eligible for each transaction type, particularly US debit under Durbin Amendment network eligibility rules. The magnitude varies by transaction mix and processing volume.
What is payment orchestration and how does it enable smart routing?
Payment orchestration platforms provide a single integration to multiple payment processors and handle routing logic automatically. Instead of building routing rules in-house, a 6-12 month project that adds 3-6 weeks per additional processor connection, the platform routes transactions across your connected providers through one integration. The orchestration layer handles the complexity of managing multiple processor relationships while giving you control over routing configuration.
Can I implement payment routing without changing my checkout?
Yes. Routing decisions happen server-side between your payment integration and the processors. Customers never see routing occur. Adding or changing routing logic through an orchestration platform requires no changes to your checkout UI or customer-facing payment form.
