Payment Routing

Overview

How it works and why it matters

Payment routing selects an eligible provider, network, destination or execution path using requirements such as supported asset, geography, cost, capacity, risk and availability. A robust engine records why a route was chosen and how fallback behavior will operate.

Important technical and operational details

The routing decision should preserve eligible candidates, exclusions, input signals, selected route, fallback order, decision version, attempt identity, and final outcome.

Practical decision points

Effective routing first excludes ineligible choices, then ranks the remaining choices on dimensions the merchant actually values. An address or chain must be compatible with the selected asset; a bank corridor may be closed by geography, time or regulatory restrictions. Only after eligibility checks should cost, latency and conversion estimates influence the route. Log the evaluated candidates, inputs, policy version, selected path and fallback rationale for every attempt. A route switch after a timeout must not create a second economic obligation. Track confirmed completed payments, not just API response rates, because the fastest request path can produce the worst settlement outcomes.

Related concepts

Payment Routing Engine; Payment Routing Optimization

Further reading

• bis.org documentation