Intelligent Routing
Route every payment to the best processor based on business rules, live performance, cost, and fallback preferences
Hyperswitch Intelligent Routing helps merchants decide where each payment should be processed. You can use it to improve authorization rates, reduce processing cost, shift traffic across processors, and keep payments moving when a processor is unavailable.
What You Can Do
Route specific traffic to specific processors
Split traffic by percentage
Send more traffic to better-performing processors
Balance authorization rate with processing cost
Route supported debit payments through lower-cost networks
Define the backup processor order
Compare two routing setups before rollout
Let Hyperswitch tune auth-rate routing automatically
Strategy Types
Hyperswitch supports both merchant-defined routing and performance-based routing:
Rule-Based Routing: Route payments using explicit business conditions such as payment method, amount, currency, country, card type, or customer context.
Volume-Based Routing: Split traffic across processors by percentage for planned distribution or gradual rollout.
Auth-Rate Routing: Use recent authorization performance to route most traffic to the best-performing processor while keeping a small exploration share.
Multi-Objective Routing: Re-rank auth-rate results using processor cost, so a lower-cost processor can win only when expected value is better.
Least Cost Routing: Route supported debit payments through the lowest-cost eligible debit network.
Default Fallback Routing: Define the backup processor order when no routing rule applies or the selected processor is not eligible.
How A Payment Is Routed
Hyperswitch checks which processors are eligible for the payment method, currency, country, and connector configuration.
The active routing strategy ranks or filters those processors.
Optional optimization layers, such as downtime elimination, multi-objective ranking, or debit network routing, refine the choice.
If the selected processor is not eligible or available, Hyperswitch uses Default Fallback Routing.
The decision is logged so your team can review the selected processor, routing approach, and outcome.
Architecture Diagram
Recommended Rollout
Start with Default Fallback Routing, then add Rule-Based or Volume-Based Routing for business controls. Use Auth-Rate Routing once multiple processors handle meaningful traffic for the same payment segment. Add Multi-Objective Routing only after cost coverage is available, and use A/B Testing before moving a new strategy to all traffic.
For self-hosted Hyperswitch deployments, see the Self-Deployment Guide.
Last updated
Was this helpful?