Smart Routing
Route every payment across multiple processors.
Send each payment to the processor best placed to approve it, and cascade it to a backup the moment one declines or goes down. One integration, every processor behind it.
Why route
One processor is a single point of failure. Several, routed well, are a strategy.
A visual rule builder
Draw routing as a graph in the dashboard: conditions, processors and failure paths. Change it without a deploy.
Automatic cascading
A declined or failed payment moves to the next processor on its path in the same checkout, so the customer never sees the first failure.
Percentage load balancing
Split traffic across processors by percentage to test a new one, spread volume, or keep a second account warm.
Eligibility checks
A processor that cannot take a payment, for its currency or card, is skipped before it is tried.
3D Secure per processor
Force 3D Secure on the processors where you want it, and leave it off where you do not.
Processor health
Response times and error counts per processor, day by day, so you can see which one is slowing down before it costs you.
Inside a routing rule
Decide where a payment goes, and where it goes next.
A rule is a graph you draw in the dashboard: conditions that pick a processor, and failure paths that pick the one after it.
Route on
- Country
- country is GB, DE or FR
- Amount
- amount greater than 500.00
- Currency
- currency is EUR
- BIN
- BIN starts 424242 (6 or 8 digits)
- IP range
- IP in 203.0.113.0/24
- Load balancer
- 70% to one, 30% to another
- Returning card
- card succeeded before for this customer
When a processor says no
- 01The exact error code
Send one specific processor response to its own path.
- 02The normalised error
The same decline reason, whichever processor returned it.
- 03Hard decline, soft decline or outage
Retry soft declines and outages elsewhere, stop on hard declines.
- 04Everything else
A catch-all path so no failure is left without a next step.
The first match wins. The payment then cascades to that path's processor, and on again if it fails there too.
How it works
From your processors to your first routed payment.
Connect processors
Add the processor accounts you already have, or open new ones, in the dashboard.
Draw your rules
Build the routing graph: the conditions that pick a processor, and where a failure goes next.
Take payments
Every payment through the API or the payment form runs your rules. Edit them any time; the next payment uses the new version.
Questions teams ask before they switch.
Smart routing sends each payment to the processor best placed to approve it, based on rules you set, and retries it on another processor when the first one fails. You integrate once and Orchestrapay talks to every processor behind you.
Show us your processors. We will draw your first rules.
Tell us which processors you use and where you sell. We will map a routing graph with failover for your volume, and show you what it costs.
- Keep the processor accounts you already have
- One integration in front of all of them
- A transparent number before you sign anything