Which conditions can a routing rule use?
Issuer country, payment method, transaction amount, MCC, BIN and sales channel. A single rule can combine several conditions, and all of them must match for the rule to fire. Rules are ordered, so the first match wins and your merchants keep control of precedence.
In detail
A routing rule can use issuer country, payment method, transaction amount, MCC, BIN and sales channel. These are the variables that most often explain why a transaction is authorized by one provider and declined by another.
How conditions combine
A single rule can combine several conditions, and all of them must match for the rule to fire. A rule for domestic cards above a certain amount on the web channel, for example, uses three conditions at once.
How rules are evaluated
Rules are ordered and evaluated top to bottom, and the first match wins. Your merchants control precedence by reordering rules, which takes effect on the next transaction. When no rule matches, a named default route applies, so no transaction falls through without a defined path.
What a rule can do
- Send matching transactions to one provider.
- Split them across several providers in set percentages.
Working with other layers
Routing works alongside other controls. Exclusion rules on a contract can keep it out of specific cases, even when a routing rule points to it. Fallback policies decide what happens after a decline, including whether a retry goes to the same provider or another one. Together, they let your merchants send each transaction to the provider most likely to authorize it, and recover when it does not.