Routing rules you can read, test and defend.
Smart routing is where routing strategy is actually expressed. Ordered rules, explicit precedence, live provider health as an input, and simulation against historical traffic before anything changes in production.
A routing table nobody understands is a liability
Routing logic tends to accumulate: an exception for one market, a workaround for one provider, a rule nobody remembers adding. Smart routing is deliberately legible. Every rule states its condition, its action and its fallback, rules are ordered with visible precedence, and you can see which rule decided any given transaction.
From request to reconciled
Define the dimensions
Choose what the decision is allowed to consider: currency, country, BIN attributes, method, amount band, MID, customer type or provider health.
Order the rules
Rules evaluate in order with explicit precedence, so the outcome of any combination is predictable rather than emergent.
Set fallbacks
Each rule declares where traffic goes if its preferred route is unavailable, which is what makes failover deterministic.
Simulate
Replay a historical traffic sample through a proposed configuration and see which transactions would have taken a different path.
Release and measure
Deploy at full weight or as a weighted split, then compare approval, cost and latency against the previous configuration.
What smart routing covers
Currency rules
Route by transaction and settlement currency, including rules specific to the currencies you settle in.
Country rules
Route by issuing country and by customer market, which is the single biggest driver of domestic versus cross-border treatment.
BIN attributes
Issuer, product type, commercial versus consumer and issuing country, all available to the decision.
Method rules
Separate strategies for cards, wallets and bank methods, because they do not share cost or approval behaviour.
Amount bands
High-value transactions can take a different route from low-value ones, where cost or approval behaviour justifies it.
MID selection
Choose the merchant ID by brand, entity, descriptor or volume distribution.
Weighted splits
Distribute traffic by percentage across routes, for volume commitments or for a controlled ramp.
Provider health inputs
Live availability, latency and decline-rate signals can suppress a route automatically.
Precedence & conflict handling
Ordered evaluation with visible precedence, so two overlapping rules have a defined, inspectable outcome.
Simulation
Test a configuration against historical traffic before it affects a live payment.
Per-transaction explainability
Every payment records the rule that selected its route and the fallback chain that followed.
Why teams choose it
- Predictable behaviour. Ordered rules with declared fallbacks remove the guesswork from complex configurations.
- Safe change. Simulate first, then ramp with a weighted split rather than switching everything at once.
- Explainable decisions. When someone asks why a transaction went where it did, there is an answer in the record.
How you connect
- Configured per account; no application change is required to alter routing.
- Rule changes are versioned and attributable.
- The selected route and rule are exposed on the payment record and in webhooks.
What you can accept
- Applies to every routable method on your account
Availability depends on merchant category, jurisdiction, underwriting and the applicable payment or acquiring partner.
How it is controlled
- Rule changes are versioned, attributable and reversible.
- Simulation runs against historical data and never touches live payments.
- Routing never overrides scheme, partner or compliance constraints.
Flowa Pay provides the payment technology and orchestration layer. Acquiring, scheme settlement and regulated payment services are provided by licensed acquiring and payment partners under their own authorisations.
Common questions
Orchestration is the layer: many providers behind one integration, with failover and measurement. Smart routing is the rule engine inside it: the dimensions, precedence, simulation and explainability.
Yes. Replay historical traffic through the proposed configuration, then ramp with a weighted split before committing fully.
Rules evaluate in a defined order with visible precedence, so the outcome is deterministic and inspectable rather than a surprise.
Ready to put smart routing to work?
Talk to our team about your corridors, your volumes and the routes that fit your business.