XRPL Integration
Integrate cross-chain swaps to, from, and within the XRP Ledger using Squid. XRPL support is powered by Squid Intents — Squid's intent-based execution protocol for fast, solver-driven cross-chain settlement.
Squid Intents must be enabled on your integrator ID. Reach out to the Squid team to request Squid Intents access before integrating with XRPL.
XRPL Parameters
Chain ID
xrpl-mainnet
Supported Tokens
The following tokens are currently supported on XRPL via Squid Intents:
XRP
xrp
RLUSD
524c555344000000000000000000000000000000.rmxckbedwqr76quhesumdegf4b9xj8m5de
SOIL
534F494C00000000000000000000000000000000.rfmS3zqrQrka8wVyhXifEeyTwe8AMz2Yhw
USDC
5553444300000000000000000000000000000000.rGm7WCVp9gb4jZHWTEtGUr4dd74z2XuWhE
Integration Options
Choose the integration method that best fits your use case:
Swap Widget
A full-featured, drop-in cross-chain swap UI. The Swap Widget gives users complete flexibility to select their source chain and token, then swap into any supported XRPL token.
Best for:
dApps that want a ready-made swap interface with minimal dev effort
Flows where the user chooses both the source and destination tokens
Prototyping and testing XRPL swaps via Widget Studio
Payment Widget (Deposit Widget)
A streamlined deposit and payment flow where the destination is fixed to XRPL. The Payment Widget supports two modes: deposit (user-entered amount) for account funding, and payment (fixed amount) for checkout and invoice flows.
Best for:
Accepting cross-chain deposits into an XRPL address
Checkout and invoice payment flows with a fixed amount (e.g., pay 50 RLUSD)
On-ramp flows where users fund an XRPL account from any supported chain
API & SDK
Direct integration with Squid's routing API and TypeScript SDK for full control over the swap lifecycle. Build custom UIs and backend flows with complete flexibility over routing, execution, and status tracking.
Best for:
Custom swap interfaces and backend integrations
Programmatic routing (e.g., bots, automated flows)
Advanced use cases requiring hooks, exact output, or custom transaction handling
Transaction Types
XRPL routes use the DEPOSIT_ADDRESS_CALLDATA transaction type. This applies to:
EVM → XRPL — Direct route, no DEX swap on source
XRPL → EVM — Direct route from XRPL to any EVM chain
XRPL → XRPL — Same-chain swaps between XRPL tokens
The route response will return a transactionRequest containing the deposit address and calldata. Transfer the specified amount to the deposit address to initiate the swap.
For a full reference of all transaction types across all chains, see the Transaction Types page.
Last updated