Solana's x402 payments pitch reaches 200 million transactions
A Solana Foundation webinar recap cites $50 billion in x402 volume and 150,000 merchant endpoints, while the same page also uses a lower 180 million transaction count.
Solana is putting a large usage claim behind its push to make stablecoin payments native to software agents. In a webinar recap published Aug. 5, the Solana Foundation said x402 had reached roughly 200 million transactions, $50 billion in volume and about 150,000 merchant endpoints. Most transactions were described as costing less than 50 cents.
x402 uses HTTP's 402 Payment Required status as a payment challenge. A server can return a price for a page, API call or other resource, and an agent can decide whether the request fits its budget before paying in a stablecoin such as USDC. Access and payment then happen inside the same request flow, without a human entering card details or provisioning an API key.
The standard is moving beyond a demo
The recap points to pay.sh, a Solana-built directory of x402 endpoints, and AWOL, a Coinbase wallet client. In the demonstrations, an agent paid one cent for a market-data request and chained several paid tools into a short video workflow. Those examples show the intended loop: discover a service, inspect its price, pay, receive the result and use that result in the next step.
Solana also says x402 is hosted by the Linux Foundation and is referenced in the documentation or workflows of Cloudflare, Stripe and AWS. That distribution matters because a payment protocol needs both sellers who expose paid endpoints and clients that can authorize small transfers. A large transaction total by itself does not show how many services are active or how often users return.
The count needs a definition
There is an evidence wrinkle in the same source. The article's headline metrics use roughly 200 million transactions, but a later section says x402 has processed over 180 million since launching about a year ago. The page does not explain whether the figures use different measurement windows, include different networks or reflect a revised dashboard total.
That distinction will decide how much weight to put on the adoption story. The next useful record is a methodology that separates successful settlements from failed attempts, identifies active endpoints and shows how volume is denominated.
