3DS Priority Routing
Route authenticated orders to merchant accounts on gateways that accept 3D Secure data.
Not every payment gateway accepts 3D Secure data.
When an order has been authenticated and it processes on a gateway that cannot carry the authentication, the authentication is not sent with the charge.
3DS Priority Routing makes the router aware of which merchant accounts can use 3D Secure, and sending authenticated orders to those.
What counts as an authenticated order
An order carries 3D Secure if either is true:
- The authentication values were passed to Vrio on the order — see Third Party 3DS Providers
- A 3DS connection on the campaign authenticated it
Both look the same to the router.
Which gateways accept 3DS data
Vrio maintains this per gateway, so there is nothing to configure on the merchant account.
The current list is on Third Party 3DS Providers.
A merchant account inherits its gateway's support, so every merchant account on a gateway that accepts 3D Secure counts as a 3DS merchant on the router.
Turning it on
The settings are on the payment router, under Advanced Routing.
| Setting | What it does |
|---|---|
| 3DS Priority Routing | Turns the feature on for this router. With it off, nothing changes. |
| De-prioritize 3DS Merchants Without 3DS | Controls orders that have no 3D Secure. Checked, they will only be sent to merchants that do not accept 3DS data. Unchecked, they can use any merchant on the router. |
| 3DS Fallback Type | What happens when the settings leave no merchants available. |
3DS Fallback Type
| Option | Behaviour |
|---|---|
| Use Router Settings | Ignore the 3DS rules for that attempt and use any merchant on the router |
| Decline Sale | Decline with No available merchants |
Choose deliberately.
On a router where every merchant is on the same kind of gateway, one direction has nowhere to go, and the fallback is the only thing standing between that and a declined sale.
What happens to an order
With 3DS Priority Routing on and De-prioritize checked:
| The order | Goes to |
|---|---|
| has 3D Secure | merchants that accept 3DS data |
| has no 3D Secure | merchants that do not |
| finds none of either | whatever the fallback says |
Unchecking De-prioritize changes only the second row: orders without 3D Secure route normally across every merchant on the router, including the ones that accept 3DS data.
Decline reattempts
If your router reattempts declines, it works through the matching merchants first.
Once those are exhausted, the fallback decides whether the cascade continues:
- Use Router Settings — the remaining attempts use the other merchants
- Decline Sale — the cascade stops there, even if attempts remain
Seeing what the router did
Every decision is written to the Route Log on the order:
Merchants 12,14 were removed because the order has 3DS.
No non 3DS gateway merchants were available for an order that does not have 3DS. Fallback Type - Router Settings Applied.
The log names the merchants removed and why, so a sale that landed somewhere unexpected can be traced back to the rule that put it there.
Related Documentation
Updated about 2 hours ago