Choose one environment
Keep the facilitator endpoint, XRPL network id, and RPC/WS endpoints from the same row.
XRPL AI Infrastructure
Secure machine payments on the XRP Ledger.
The XRPL x402 Facilitator verifies and settles payer-signed presigned transactions, so your API can charge per request — no API keys, no custodial wallets, no payment glue.
No custodyInvoice bindingXRP · RLUSD · IOU
Built on
Powered by
Powered byLive endpoint
Point your middleware at the hosted facilitator
Use this hosted mainnet facilitator URL in server middleware. Buyer clients call your protected resource URL rather than the facilitator URL, and use XRPL RPC/WS plus a network filter.
Hosted mainnet
Payer-signed XRPL Payment blobs
Invoice binding and replay protection
Settle XRP and IOU assets (RLUSD, USDC)
Integration flow
Follow the QuickstartDrop-in setup for your x402 stack
The facilitator slots into existing x402 middleware. Your server keeps full control over pricing and release rules while payment verification is delegated.
Define payment terms
Set asset, destination, price, and invoice-level metadata in your resource server.
Serve paid resources
Middleware returns HTTP 402, then final content once verify + settle pass.
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
The payer signs a standard XRPL Payment transaction and sends it inside the x402 payload.
Invoice binding
Each transaction is tied to an invoiceId via Memos + InvoiceID hash to prevent replay.
Guardrails before submit
Rejects unsupported payment patterns and high-fee transactions before ledger submission.
Validated settlement
Optionally wait for a validated ledger result before releasing the paid resource.
No-custody model
The facilitator never signs payer transactions and never holds customer private keys.
Spec-compatible endpoints
Supports the /supported, /verify, /settle flow with x402-xrpl clients and middleware.
Optional risk extension · x402-secure
Risk-gated settlement, when you need it
When a buyer's agent brings Verifiable Intent, the hosted facilitator calls X402 Secure and Trustline before any money moves — returning allow, deny, or review, each with a replayable evidence trail.
Enhances, not replacesPlain XRPL x402 payments pass straight through. Risk is evaluated only when a buyer attaches x402Secure context.
Verifiable Intent L1–L3A Trustline-issued credential, an owner-signed delegation, and an agent-signed final action travel with the payment.
Allow · deny · reviewThe facilitator calls X402 Secure and Trustline before settling — and gates the transaction on the decision.
Optional by defaultEnforce per route or per tenant when a surface requires risk-checked settlement.
Integration paths
Wire it into either side of the payment
Sellers expose paid resources with deterministic pricing and settlement checks; buyers build autonomous calls that detect 402 challenges, sign payloads, and retry automatically.
For sellers · APIs
Merchant integration
Pick your server stack and start charging per request.
For buyers · agents
Client SDKs
Sign XRPL Payments and pay through the x402 flow.
Documentation