Routing policies
Save, simulate, and publish ordered routing and cascade rules.
Updated July 29, 2026On this page
- A router
- At least one ready MID pool
Each router has one published routing policy and, optionally, one saved draft. Policy publishing is deliberate: browser edits do not auto-save, saved drafts do not affect live payments, and new operations change only after Publish.
Build a policy
Add ordered rules
Open Payments → Routing policies, select a router, and add rules in priority order. The first enabled rule whose populated conditions all match wins. Conditions can use transaction type, currency, billing or shipping country, card brand or BIN, Source Page, Checkout, product, and amount range.
Configure the route action
For each rule, choose a primary pool, optional cascade pools, a maximum attempt count, and the outcome categories that permit another attempt. Configure a default action for payments that match no rule.
Save and simulate
Choose Save draft. Use Simulate with representative transaction context to see the matching rule, eligible candidates, capacity, circuit state, and rejected MIDs. Simulation can compare the published policy with the saved draft without changing live traffic.
Publish
Choose Publish after the draft is saved and reviewed. The new version becomes active for new payment operations. Existing operations remain pinned to the policy version with which they started.
An indeterminate gateway response must stop for reconciliation. Configure cascading for explicit categories such as processor unavailable or configuration error; do not turn an unknown result into a possible duplicate charge.