Added

Ripple (XRPL) Support

The platform now supports XRP Ledger (XRPL) as a settlement chain alongside the existing EVM chains. XRPL accounts are created through the API rather than deployed on-chain, settle in RLUSD, and execute withdrawals immediately without the two-phase ExecutionDelayPolicy flow used on EVM. Select XRPL with the X-Chain-Id header.

What's included

  • Account creationPOST /api/v1/accounts creates a multisig XRPL account from the user's public key and returns its wallet_address. This replaces Smart Wallet deployment, module installation, and on-chain registration. Wirex funds the XRP base reserve and opens the RLUSD trust line.
  • WithdrawalsPOST /api/v1/withdrawal/execute sends RLUSD to a classic r-address and returns the transaction_hash. Execution is immediate: there is no withdrawal request, no time-lock, and no user signature.
  • Action confirmationsPOST /api/v1/confirmation/signature/verify accepts a new public_key field, required on XRPL because the signer's address cannot be recovered from an XRPL signature. ed25519 and secp256k1 keys are both supported. The field is ignored on EVM and Stellar.
  • Addresses — Classic r-addresses are accepted wherever an address is supplied, including X-User-Address.
  • Cards — Card issuance, management, transactions, 3DS, and top-up work unchanged. Card issuance fees are paid through POST /api/v1/withdrawal/execute rather than a transfer submitted from the user's wallet.

Requirements

XRPL onboarding produces two addresses. The account address returned by POST /api/v1/accounts holds the funds; the owner address derived from the user's public key is what POST /api/v2/user and the X-User-Address header expect. Provisioning is asynchronous — wait for the wallets webhook before using a new account.

Confirm the X-Chain-Id value for your environment with Wirex. XRPL has no EIP-155 chain ID, so the identifier is assigned per environment.

Limitations

  • X-addresses are not supported. Use classic r-addresses.

Documentation