What happens to routing when a provider contract is revoked?
Every contract lists the routing rules that reference it, with the rule conditions, the user who created each one, and the transaction volume each rule sent over the last 30 days. Revocation opens up once those rules are updated or removed, so your merchants keep a working route at every step of the change.
In detail
Revocation cannot leave a merchant without a route. Every contract lists the routing rules that reference it, and revocation opens up only once those rules are updated or removed.
What the contract shows
- The routing rules that reference it.
- The conditions of each rule.
- The user who created each one.
- The transaction volume each rule sent over the last 30 days.
That gives your merchants, and your team, the full picture before acting. They can see which traffic will move, plan where it should go and update the rules in the right order.
How the change unfolds
A typical sequence is to add or activate the replacement contract and run its activation test, update the rules that point to the old contract, check that traffic now flows to the new route, and then revoke the old contract. At every step, the merchant keeps a working route.
Exclusion rules offer a gentler option. A contract can stay active while being excluded from specific cases, which lets a merchant reduce its use gradually before revoking it.
Traceability
Every change to rules and contracts is written to the audit logs with the user behind it, so the history of a provider change can be reviewed later by your team or an auditor.