How smart payment routing works

Smart routing directs each transaction to the acquirer or payment path most likely to succeed — or to succeed at the lowest cost — instead of sending everything down one connection.

What the routing engine looks at

• Card attributes: scheme, card type (debit, credit, commercial), issuing country and issuing bank.
• Transaction attributes: amount, currency, whether it is a first or repeat payment, whether 3DS was applied.
• Acquirer performance: observed approval rates for similar transactions at each acquirer, updated continuously.
• Cost: interchange, scheme fees and acquirer margin for the transaction on each path.
• Availability: real-time health of each connection.

Static rules and dynamic optimisation

Static rules are explicit: "route EU debit cards to Acquirer A", "route amounts over €2,000 to Acquirer B". Dynamic optimisation adjusts within the rules based on measured outcomes. Most setups use both — rules for compliance and cost, optimisation for approval rate.

Cascading

When a transaction is declined with a "soft" reason (issuer unavailable, do-not-honour, generic decline), it can be retried through a second acquirer. Scheme rules restrict retries after certain decline codes, so a compliant cascade only retries where permitted. Cascading typically recovers a meaningful share of soft declines.

Where the gains are

Routing does not turn a bad transaction into a good one. It removes avoidable losses: declines caused by a poorly matched acquirer, cost incurred by a suboptimal path, and sales lost to outages. For a merchant processing millions per month, a one-point approval improvement is real revenue.