How do I see which providers a merchant depends on?
Each contract detail shows the routing rules that reference it, the conditions leading to its selection, the user who created each rule and the transactions routed through it over the last 30 days. That view gives you the dependency picture ahead of any lifecycle action, and it surfaces concentration on a single provider early enough to act.
In detail
From the contract detail. Each contract shows the routing rules that reference it, the conditions leading to its selection, the user who created each rule and the transactions routed through it over the last 30 days.
That view gives you the dependency picture for each provider relationship. You see not only that a contract exists, but how much of a merchant's traffic actually relies on it and under which conditions.
When it matters
- Before a lifecycle action, such as suspending, revoking or replacing a contract, you see which rules and volumes will be affected.
- When a provider has an incident, you know which merchants and flows are exposed.
- When reviewing resilience, you spot concentration on a single provider early enough to add an alternative route.
Revocation opens up only once the rules that reference a contract are updated or removed, so a merchant always keeps a working route during the change.
Working across your portfolio
Because the same information is available on every contract, your team can review dependencies across merchants and programs with the permissions it holds. Combined with fallback policies and routing rules, it helps you keep each merchant's payment flows spread across the providers that suit its markets, rather than discovering a single point of failure during an outage.