Validated on XRP Ledger mainnet, network xrpl:0.
Controlled acceptance test · XRPL mainnet
One payment.
One delivery.
Safe retry.
A 0.001000 RLUSD x402 payment settled to BitBooth on XRPL mainnet. BitBooth completed the paid delivery, then returned the cached result when the exact payment proof was retried. The ledger shows no second payment.
Acceptance run recorded September 8, 2026 at 21:09:02 UTC. Integration evidence, not customer traction.
The result, without the victory lap.
A narrow test should support narrow claims. These are the three outcomes captured by the September acceptance run.
The confirmed claim, consumed invoice, and successful delivery reached final state.
The original result returned without a second ledger payment or second delivery.
What BitBooth exercised.
The newer receipt covered the paid-call lifecycle from a network-specific challenge through recovery of the already-authorized result.
Challenge
A live requirement selected 0.001000 RLUSD on xrpl:0.
Settlement
The uniquely bound payment validated in ledger 106,853,343.
Delivery
BitBooth reconciled the payment and completed the paid request.
Replay
The exact proof recovered the cached result with no duplicate settlement.
Follow the receipt.
The public ledger supports the settlement claim. BitBooth's acceptance records support the delivery and replay findings.
- Transaction
2376A52292BD35B0E9242784B31463375041C9216351A04D7B6D1AB43F08F2FE- Ledger
- 106,853,343
- Amount
- 0.001000 RLUSD
- Issuer
rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De- Buyer
r4Nh7yRHfcNFNMt8GFe7yrP1qq8cLGjkFR- Merchant
rfryheo6yzFdLWj8qUQtZc7zG9MKkBkUEy- Source tag
- 804681468
- Invoice UUID
86ef9906-097e-47d2-bf62-d3d43011e19d- InvoiceID
0ACF7DD758136B7E8AA2701419ADAA09273E0D96ADF129B248C1F76D0ADA6E72
Six public integration transactions. One integration wallet.
XRPL AI indexes five earlier XRP payments and the newer RLUSD acceptance transaction. The assets stay separate because adding XRP and RLUSD does not produce a meaningful total.
0.005 XRP total, sent from the same buyer wallet.
The controlled delivery and exact-retry acceptance run.
What this proves—and what it does not.
- Real assets reached BitBooth's published XRPL mainnet merchant wallet.
- The RLUSD payment reconciled to a completed delivery.
- An exact retry returned the cached result without a second payment or delivery.
- This is not evidence of organic demand, product-market fit, six customers, or meaningful revenue.
- XRPL AI still attributes the RLUSD resource as Unknown.
- The public ledger alone does not prove response correctness or uptime.
Put the proof to work.
Discover before you spend.
Search BitBooth's free machine-readable catalog, inspect inputs and payment options, then choose the API your agent needs.
Make one JSON route agent-buyable.
Bring an existing endpoint. BitBooth can add x402 checkout, seller-owned payout routing, replay protection, discovery, and receipt-backed acceptance testing.