📅 Historical page. This content reflects minia2a as of its publication date and is kept for the record. Current model: x402 pay-per-call in USDC on Base only, 5 free trial calls per signed wallet, no credits and no top-up rail. → See current

Ten Million x402 Payments on XRP Ledger. Read the Number Carefully.

October 1, 2026

The XRP Ledger crossed 10 million x402 payments — less than three months after its first million, having added support in June 2026. RippleX head J. Ayo Akinyele puts the current rate at roughly 500,000 x402 payments a day. Settlement runs in three to five seconds for a fee near $0.0002, in XRP or RLUSD, through an implementation from t54. Ripple joined the Linux Foundation-backed x402 Foundation as a Premier Member; the foundation launched in July 2026 with about 40 members.

Separately, the Cardano Foundation said it has been integrated into the official x402 SDK, letting agents pay for API calls in ADA or Cardano Native Tokens. Every week, another chain adds the same three letters.

This is good news for the protocol, and it is worth being precise about what it is and is not good news for. A payment count is the easiest number to grow and the least informative. Here is what the six-figure daily figure counts, what it does not, and the harder numbers we publish on our own platform next to the flattering one.

What the number counts

Payments. HTTP 402 challenges that were answered with a valid settlement. Not value, not unique payers, not revenue.
Not settled value. The announcement gives no total transferred, in XRP, RLUSD, or dollars. At $0.0002 a transaction, a payment count says nothing about how much money moved — it says how many times the rail was exercised.
Not distinct paying agents. No merchant or payer count appears in the report. An automated client polling a paid endpoint 500,000 times a day and 500,000 different buyers paying once each produce the same number.
Not a floor on real commerce. Network dashboards elsewhere count zero-value probe traffic, so a headline count has to be read against on-chain settlement before it is read as adoption.

None of this is a knock on XRPL. It is the same reading discipline we apply to our own dashboard, where the number in the header is the one we trust least.

Our own dashboard, read the same way

We publish four numbers on minia2a.uk/api/stats. Only one of them is flattering, and we label it as the one not to quote:

Metric	Value (Oct 1, 2026)	What it means
Total requests served	4,726,072	Inflated. The field's own note says it counts bot polling and self-polls. Do not cite it as usage.
Real on-chain USDC	225 transactions = 6.22 USDC	193 settled pay-per-call + 32 legacy top-ups. Every transaction verifiable on Base. This is the honest size of settlement.
Real adopting agents, 7d	3	Distinct HMAC(X-Agent-ID), the identity we can actually attribute. Small, and published anyway.
Pay-per-call price	USDC on Base (eip155:8453)	One rail, stated plainly. We do not claim XRP, RLUSD, ADA or any other chain.

The gap between the first row and the second is the whole point. Any x402 platform — ours included — can grow the request counter by pointing a probe at its own catalog. The only numbers that resist inflation are the ones that cost money to produce: settled value, and the count of wallets that paid.

10,000,000

x402 payments on XRP Ledger in under three months. The right follow-up question is not "how many payments," it is "how much value, across how many distinct payers." That is the pair the headline does not give you — and the pair we put in the same JSON object as the number we tell you not to quote.

Why the rail layer winning is the quiet story

Two years ago HTTP 402 was a status code nobody implemented. Today Base, Solana, XRP Ledger and Cardano all settle it, a CDN sells it as a product, and a Linux Foundation project coordinates it. That is the part of the announcement that will matter in five years: the transport is converging, and it is converging fast.

Which means the differentiator is moving. If every chain settles x402 and every CDN can charge for a request, then "can it take my payment" stops being a feature. What stays hard is the boring half: out of everything that accepts a 402, which endpoint do I call, at what price, is it still live, and did the payment produce the thing I asked for. That is a discovery and delivery problem, not a rail problem — and it is measured in successful deliveries, not in challenges answered.

What we are and are not claiming

We cite, we did not verify. The XRPL figures are from the October 1 announcement and RippleX; we did not independently re-count their chain. The Cardano line is the Cardano Foundation's, reported by a third party.
We are not comparing rails. We settle USDC on Base and say so. We are not arguing XRP or Cardano rails are better or worse — we are arguing that a payment count is not the number to judge any of them by.
The discipline applies to us first. The 4.7M request figure on our own stats page is inflated and we say that on the page. If you only take one thing from this, take that.

Sources: XRP Ledger 10M milestone and the ~500,000/day rate (RippleX, J. Ayo Akinyele), fee and asset details, and Ripple's Premier Membership in the x402 Foundation — from the October 1, 2026 report by Maxwell Mutuma (Blockonomi); Cardano Foundation x402 SDK integration, reported via ZyCrypto. Our own figures are read live from minia2a.uk/api/stats and the field notes in that payload; no number here is estimated.

← More posts · minia2a.uk