Skip to content

Why intelligent routing is a margin decision, not a technical one

Share:

For years, payment routing has lived in IT and engineering. The conversation typically revolved around one technical requirement: resilience. You set rules at implementation, point traffic toward your preferred PSPs, and build in a failover for when things go wrong. The configuration runs in the background, and the team moves on. 

Most enterprise merchants have this routing capability. That's not the gap. The gap lies between having the technical capability to route transactions and actively optimising the routing strategy with granular real-time data insights. This is a true intelligent routing strategy for cost optimisation and authorisation uplift. 

While operational resilience remains non-negotiable, something we’ve explored extensively in our Payments Resilience Playbook, viewing routing purely as a technical safety net leaves money on the table. 

The merchants leading the market today are those that view intelligent routing as a fundamental commercial strategy for protecting profit margins. In this blog, we'll explore how to transform your routing strategy from a technical failsafe into a margin-driving engine powered by real-time payment intelligence - and why it's one of the most profitable investments a payments team can make. 

The problem with static routing rules 

When routing rules are set at implementation and reviewed only when something breaks, they quickly drift out of alignment with how payments actually behave. 

Static routing ignores the fluid reality of payments: acquirer performance fluctuates, scheme fees change, and authorisation rates for specific BINs vary by the hour. When you are just setting and forgetting your routing rules, you are flying blind. As we at BR-DGE have previously discussed, most payments reporting doesn't change outcomes because it is retrospective. It tells you what you lost yesterday, rather than preventing the loss today. 

Our research shows that 71% of enterprise merchants still use manual processes to optimise routing. This means that most merchants are forced to react to problems rather than prevent them, and routing decisions are based on incomplete data instead of real-time payment signals. 

Payment routing decisions are margin decisions 

Here's the commercial reality that often gets missed in technical discussions about routing: every routing decision is also a margin decision. When you pair intelligent routing with deep data insights, the conversation shifts from "Did the payment go through?" to a series of automated, commercial query points for every single transaction: 

  • Which PSP will offer the lowest fee for this specific transaction profile? 
  • Which acquirer provides the highest likelihood of authorisation for this exact card? 
  • Should this payment be routed via a domestic or global scheme to optimise both cost and acceptance rate? 
  • If a soft decline occurs, does it trigger an intelligent retry, or does the revenue from this customer disappear? 

Our research also reveals that 54% of enterprise merchants cited cost optimisation as their top strategic priority. Yet, payment routing remains an overlooked part of their strategy, with most merchants still relying on manual processes that often involve multiple teams, instead of treating routing as a commercial lever for reducing costs and improving performance. 

There's a direct line between routing decisions and margin outcomes. The merchants who treat routing as a commercial discipline, not just a technical configuration, are the ones protecting that margin consistently and benefiting from true intelligent routing. 

What intelligent routing looks like in practice 

In reality, merchants rarely lack data. What they lack is the ability to interpret it consistently and act on it quickly. Intelligent routing is all about using granular, real-time payment intelligence to route each transaction based on the conditions that actually influence outcomes. 

For example, reporting from individual PSPs only shows what happened on a single route. It doesn't answer the "what if": what would have happened if the transaction had been routed differently, or how different PSPs compare across key performance metrics. These comparative insights are what enable continuous routing optimisation. 

Without consolidated, normalised payment data across all PSPs and acquiring routes, the signals that drive an intelligent routing strategy are not visible. Those signals include: 

  • Issuer and BIN performance: so that cards from specific issuers are sent to the acquirer or PSP with the best acceptance history for that issuer 
  • Geography and currency: so that international transactions are routed to local acquirers where they perform better and cost less 
  • Transaction value: because high-value transactions will need different routing logic to low-value ones 
  • Time of day and volume patterns: because PSP performance can vary significantly at peak hours 
  • Real-time approval rates: rather than assumed performance from last month's review 

Two illustrative examples below show how this plays out. 

You notice that corporate cards from a specific issuer have an abnormally high decline rate with your primary European acquirer, costing them roughly £50,000 a month in lost sales. 

The Technical Approach Do nothing, because the acquirer is technically "online.” 
The Commercial Approach Use rich data to identify that a secondary acquirer has a 6% higher authorisation rate for those specific corporate BINs. Route only those specific BINs to the secondary acquirer. The result? Capture the lost revenue without disrupting your broader volume discounts with the primary acquirer. 

You are a UK-based merchant selling into the US. 

The Technical Approach Route all US traffic through a single global acquirer for simplicity. 
The Commercial Approach Use a payment orchestrator to dynamically route domestic US cards to a local US acquirer, bypassing cross-border interchange fees. For a merchant doing £10m in US sales, avoiding a 1.5% cross-border premium immediately rescues £150,000 in pure profit margin. 

As we’ve noted before, this is exactly how incremental optimisation can unlock millions in hidden revenue. 

To further understand the margin impact, let’s look at the illustrative table below. For the Head of Payments, this is about acceptance rates and control. For the CFO, it's basis points and net margin. Here's what both look like on the same £10m of volume: 

Metric Static Routing Intelligent Routing (Orchestrated) The Margin Impact 
Gross Attempted Volume £10,000,000 £10,000,000 
Authorisation Rate 82.5% 86.2% +3.7% 
Approved Revenue £8,250,000 £8,620,000 +£370,000 
Average Cost of Payment 1.8% 1.3% -0.5% 
Total Processing Cost £148,500 £112,060 Save £36,440 
Net Retained Margin £8,101,500 £8,507,940 +£406,440 

Every transaction presents a friction point between cost (processing fees, interchange, scheme fees) and conversion (authorisation rates). The cheapest acquirer is useless if they decline 15% of your valid transactions. The highest-converting acquirer is detrimental if their premium processing fees destroy your margin on low-value items. 

By optimising for both authorisation rates (conversion) and processing fees (cost), the merchant actively generates more top-line revenue. This dual-action optimisation in this example yields over £400,000 in protected margin on the same initial traffic. 

Building a routing strategy, not just routing rules 

To build an effective routing strategy, merchants need a structure that turns data signals into systematic improvements. A drop in approval rates may initially appear to be a regional issue. A unified view can reveal that the change is concentrated within one acquiring route, tied to a small group of issuers. Instead of investigating every provider, a strong routing strategy enables payment teams to immediately test an alternative route for the affected issuer segment. We explore this further in one of our recent blogs (see From visibility to optimisation: The model payments teams need).  

Moving from static routing rules to an active routing strategy requires three things to work together. 

  • Consolidated data: Approval rates, decline codes, issuer identifiers, and cost signals all need to be visible in a single, comparable view. Fragmented data produces fragmented routing decisions. 
  • Dynamic rules: Routing logic should respond to live performance signals, not just predetermined rules. That means the ability to adjust routing based on real-time approval rates and cost data. 
  • Speed of execution: The value of routing intelligence disappears if changes take too long to implement. The ability to adjust routing rules without an engineering cycle is what makes it a commercially efficient tool. 

Payment orchestration brings these three elements together. The orchestration layer makes data comparable across PSPs, enables routing logic to respond dynamically, and reduces the time between insight and action. 

An independent orchestrator like BR-DGE has no acquiring arm and no stake in which PSP wins the transaction, so the routing logic can be driven purely by performance data, not a hidden preference for one provider. 

The question worth asking 

Most payments teams can answer the question "do we have intelligent routing?" fairly quickly. The more useful question is:  

"Are we actively managing routing decisions with real-time data, and does our current setup let us do that?" 

If the answer involves manual reporting, scheduled PSP reviews, or routing logic that hasn't been updated since implementation, the gap is probably costing more than it looks. 

The Payments Resilience Playbook explores optimisation as one of the five building blocks of payments resilience, alongside redundancy, flexibility, interoperability and future-readiness. It includes real merchant scenarios that show what active routing optimisation delivers commercially, and what it costs to leave it as a background configuration. 

Download the Playbook to see how enterprise merchants are using data-driven intelligent routing as a margin protection strategy, not just a technical safeguard. 

Related content