01
Choose one environment
Keep the facilitator endpoint, XRPL network id, and RPC/WS endpoints from the same environment.
XRPL_FACILITATOR_URL=https://xrpl-facilitator-mainnet.t54.ai XRPL_NETWORK=xrpl:0XRPL AI Infrastructure
Secure machine paymentson XRP ledger
XRPL x402 Facilitator verifies and settles presigned payment transactions so your API can charge per request without API keys, custodial wallets, or custom payment glue.
Protocol
x402 v2
HTTP 402-native
Security
No Custody
No server-side signing
Settlement
XRPL Exact
Presigned transaction flow
Live endpoint
https://xrpl-facilitator-mainnet.t54.aiXRPL_NETWORK=xrpl:0Payer-signed XRPL Payment blobs
Invoice binding and replay protection
Settle XRP and IOU assets (RLUSD, USDC)
Use this hosted mainnet facilitator URL in server middleware. Buyer clients call your protected resource URL and use XRPL RPC/WS plus a network filter.
Ecosystem fit
Built for the XRPL payment stack and trust layer.
Integration flow
Drop-in setup
The facilitator slots into existing x402 middleware. Your Service Server keeps full control over pricing and release rules while payment verification is delegated. Buyer clients call your protected resource URL rather than the facilitator URL.
Need end-to-end examples?Follow the Quickstart guide
02
Define payment terms
Choose asset, destination address, price, and invoice-level metadata in your resource server.
asset=XRP price=1000 payTo=rYourAddress03
Serve paid resources
Middleware returns HTTP 402 and final content after verify + settle passes.
requirePayment({ path: '/hello', facilitatorUrl, payToAddress })Core capabilities
Built for secure x402 settlement
Every payment request stays inside standard HTTP semantics while the facilitator handles verification, submission, and settlement status.
Presigned XRPL Payment
Payer signs a standard XRPL Payment transaction and sends it in x402 payload.
Invoice binding
Transaction is tied to invoiceId using MemoData or InvoiceID hash to prevent replay.
Guardrails before submit
Rejects unsupported payment patterns and high-fee tx before ledger submission.
Validated settlement mode
Optionally wait for validated ledger result before releasing paid resource.
No custody model
Facilitator never signs payer transactions and never holds customer private keys.
Spec-compatible endpoints
Supports /supported, /verify, /settle flow with x402-xrpl clients and middleware.
For sellers
Merchant integration paths
Pick your server stack and expose paid resources with deterministic pricing and settlement checks.
For buyers
Client SDK integration
Build autonomous paid calls that detect 402 challenges, sign payloads, and retry automatically.
Documentation