Who builds the routing rules, my team or my merchants?
Each merchant account gets its own Routing Matrix, an ordered set of rules evaluated on every transaction before it reaches a provider. Your merchants build and reorder those rules directly in the Console, on the conditions that match their business. You set the defaults and the boundaries they operate within, which keeps your team available for the cases that deserve attention.
In detail
Your merchants do, within the boundaries you set. Each merchant account gets its own Routing Matrix, an ordered set of rules evaluated on every transaction before it reaches a provider.
What merchants manage
Your merchants build and reorder their rules directly in the Console, on the conditions that match their business: issuer country, payment method, amount, MCC, BIN or sales channel. Rules execute top to bottom, and the first match wins. When no rule fires, a named default route applies, a provider the merchant chose explicitly. Changes take effect on the next transaction, without a deployment or a support ticket.
One rule can also split traffic across several providers in percentages the merchant sets, to balance load, stay within a processor's volume limits or reduce dependency on a single provider.
What you control
You set the defaults and the boundaries. Policies can be applied across programs, and governance controls decide what each level can change. Contracts, exclusion rules and fallback policies frame what routing can do.
Why this split works
Merchants know their business: where their customers are, which providers perform on their traffic and what each costs. Letting them translate that knowledge into rules keeps your team available for the cases that deserve attention, rather than handling routine routing requests.