The right acquirer.
Every transaction.
Configure interchange-aware routing across your connected acquirers using 50+ data points. Route by currency, payment method, country, BIN, merchant rule or transaction value - and cascade automatically when an acquirer declines.
Routing built for approval ratios
Most PSPs work with multiple acquirers because each is strong on different geographies, methods and merchant types. Smart Routing lets you take advantage of all of them at once - and the system retries on the next configured acquirer when one declines.
Every connected acquirer
Routing that reads the transaction before it picks a terminal. Currency, method, geography, amount, card type, merchant preference and distribution ratio all feed the decision, and a decline moves it to the next eligible terminal.
50+ data points
Configure a cascade order. When the primary acquirer declines, the engine retries on the next configured acquirer automatically - until success or exhaustion.
Auto-cascade
Route to the cheapest viable acquirer for each transaction profile. Interchange-aware so you can predict per-transaction cost before it processes.
Soft vs. hard decline logic
Different decline categories trigger different next-step behaviour: soft declines retry on the same network with a different acquirer; hard declines route to a different network or method entirely.
Real-time monitoring
Watch routing decisions in real time. Identify acquirers underperforming on specific BIN ranges or geographies and adjust the cascade without waiting for a quarterly review.
How Smart Routing works
- Configure
Define your routing rules in the admin console - by merchant, currency, country, BIN or any combination of 50+ data points.
- Process
Each transaction routes through the rules engine. The engine picks the right acquirer based on rules; on decline, it cascades to the next.
- Optimise
Monitor approval ratios per acquirer per BIN range; adjust the cascade to push more volume to better-performing acquirers.
Frequently asked questions
How many acquirers can I route across?
As many as you have configured. Routing works across the acquirers enabled for your deployment, and adding one is a configuration change rather than a development cycle.
Can each merchant have its own routing logic?
Yes. Routing rules are per merchant; you can also override at the MID, terminal or BIN-range level.
How does the cascade pick the next acquirer?
The cascade follows the eligibility and priority you defined, so the next attempt goes to a terminal that can actually take the transaction rather than simply the next one in a list.
Can I do A/B testing on routing rules?
Yes. Configure parallel rule sets and route a percentage of traffic to each. Compare approval ratios and roll out the winner.
How fast does a routing rule change take effect?
Immediately. Rules are applied at the next transaction; no deploy required.
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.