Asset Routing

Overview

Asset routing selects the path, network, provider, liquidity venue, wallet, account, or conversion sequence used to move a particular asset from source to destination. The decision can reflect support, price, fees, speed, limits, risk, and settlement requirements.

Distributed payment workflows cannot always undo a completed external action. Systems therefore use idempotency keys, immutable event history, state machines, ordering rules, and compensating transactions to recover without erasing facts.

Asset Routing should remain distinct from Payment Routing and reconciliation, because each can represent a different stage, record, control, or financial outcome.

The control environment must anticipate race conditions, double spending or allocation, out-of-order events, stale routing data, non-idempotent retries, invalid state transitions, hidden partial completion, and compensation that creates a second error. Important failure modes include loops, duplicate attempts, stale performance data, route concentration, unsupported currencies or geographies, provider outages, and optimization that ignores settlement or fraud outcomes.

Controls should prevent unsafe retries, distinguish business declines from technical failures, enforce provider and network eligibility, and record why a route was selected or skipped. The routing decision should preserve eligible candidates, exclusions, input signals, selected route, fallback order, decision version, attempt identity, and final outcome. For Asset Routing, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Asset Routing should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome. Changes affecting Asset Routing should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention.