Definition and scope
How XRPL Path Payments Work addresses a distinct part of payments and transfers. Follow a payment that converts or routes across assets and order-book or AMM liquidity.
XRPL payments range from direct XRP transfers to routed cross-currency delivery, escrows, checks, and payment channels. This collection focuses on what users and applications must verify before signing and what the validated ledger proves afterward. A payment workflow is complete only after a validated ledger proves the result. Service crediting and recovery remain off-ledger responsibilities.
How it works
A path payment can consume one asset and deliver another through trust lines, order books, and AMMs. SendMax caps source spend, Amount defines destination delivery, and Paths can supplement paths found by pathfinding.
- Paths: verify this field, object, or component against the cited protocol documentation.
- SendMax: verify this field, object, or component against the cited protocol documentation.
- Amount: verify this field, object, or component against the cited protocol documentation.
- quality: verify this field, object, or component against the cited protocol documentation.
- pathfinding: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A sender paying a USD token with XRP obtains candidate paths, applies a maximum spend and optional quality limit, submits promptly, then verifies the validated delivered amount and balance changes.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
Quoted paths can become stale as liquidity changes. A path payment does not guarantee a favorable rate, sufficient liquidity, or issuer reliability.
A payment workflow is complete only after a validated ledger proves the result. Service crediting and recovery remain off-ledger responsibilities.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.