Definition and scope
Cross-Currency Payments on the XRP Ledger addresses a distinct part of payments and transfers. See how a sender can spend one asset while the destination receives another.
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
Cross-currency Payments combine transfer and exchange so the source can spend one asset while the destination receives another. The payment engine evaluates trust lines, order-book offers, AMMs, transfer rates, and path constraints.
- cross-currency: verify this field, object, or component against the cited protocol documentation.
- SendMax: verify this field, object, or component against the cited protocol documentation.
- issued amount: verify this field, object, or component against the cited protocol documentation.
- payment engine: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An application specifies the destination's issued USD Amount and the sender's XRP SendMax, reviews the quoted source requirement, then reconciles both sides from validated metadata.
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
Issued assets depend on their issuer, and a successful route does not guarantee redemption or legal value. Compare delivered quantity, source cost, fees, and issuer identity.
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.