Route each transaction
on its own merits.
Per-transaction routing decisions based on rules - by currency, payment method, country, BIN, merchant rule or transaction value. The routing engine that powers Smart Routing.
Routing decisions made transaction by transaction
Transaction Routing is the engine layer beneath Smart Routing. Every transaction enters the routing engine, gets evaluated against your rules, and routes to the chosen acquirer in real time.
Per-transaction
Every transaction is routed on its own merits rather than by a static assignment, so the same merchant can be served by different terminals depending on what is being processed.
Rules-driven
Cards, wallets, bank transfers, Open Banking, crypto - different methods route differently. Method-specific rules supported.
Real-time decision
BIN-country and shopper-country are independent inputs. Route by either or both, with rules layered on top.
Merchant-rule routing
Each merchant can have routing rules unique to its business - high-value transactions to one acquirer, recurring to another, refunds to a third.
Cascade on failure
When the chosen acquirer declines, the engine retries on the next configured acquirer per the cascade order - until success or exhaustion.
How routing decisions run
- Receive
Transaction arrives at the routing engine with all its data points - amount, currency, BIN, country, merchant.
- Evaluate
Engine evaluates the transaction against the rules in order. The first matching rule determines the chosen acquirer.
- Route
Transaction routes to the chosen acquirer. On success, the response returns. On decline, the cascade triggers.
Frequently asked questions
How fast is the routing decision?
The decision is made inline as the transaction is processed, so routing does not add a step the customer waits through.
Can rules be conditional on multiple factors?
Yes. Rules support AND/OR logic across any combination of 50+ data points.
How do I prioritise overlapping rules?
Rules carry an explicit priority, so where two could apply the outcome is defined rather than incidental, and a merchant-side override can force a specific terminal when one is genuinely needed.
Can I shadow-test new routing rules?
Yes. Apply the rule in shadow mode - the engine logs what would have happened without enforcing the route. Compare results before flipping enforcement on.
Can I see why a specific transaction routed where it did?
Yes. Every transaction carries its routing decision with the rule that fired and the data points that triggered it.
Where is data hosted?
Hosting, retention and data residency are set per deployment rather than fixed, and each brand is served from its own domain. Tell our team what your regulator and your customers require and we will confirm the arrangement in writing.