Skip to main content
Routing rules connect payment methods and countries to your gateway accounts. They are what let Orqex turn one API call into the right capture on the right provider.

​
Define a rule

A rule maps a method + country to:
  • a primary gateway account — tried first,
  • an optional fallback gateway account — used if the primary fails for a transient reason.
Only accounts that support the payment’s currency are eligible.

​
Orchestration strategy

Your project’s orchestration strategy decides how Orqex chooses among eligible accounts (follow your rules exactly, optimise for success, or distribute load). Set it in the project’s payment settings.

​
Failover

When a primary capture fails for a transient reason, Orqex automatically re-runs the payment against the fallback. You don’t configure the mechanics — just provide a sensible primary and fallback per rule.
Rules are environment- and project-scoped. Configure them for both sandbox and live.