The x402 payment protocol, which lets websites charge per request using stablecoins, is getting a major infrastructure push. Cloudflare has launched a gateway that handles payment verification at the edge, and AWS now supports x402 natively on CloudFront and WAF. Meanwhile, Ripple's RLUSD stablecoin went live in Japan through SBI VC Trade after receiving regulatory approval.
What x402 does
Instead of requiring subscriptions or user accounts, x402 allows a server to respond to a request with a 402 status code and a price manifest. The client then pays the listed amount in a stablecoin and returns a receipt. The server verifies the payment and serves the content. The protocol is designed for APIs, datasets, media, and tools where per-call or per-asset pricing makes more sense than monthly plans.
Cloudflare's gateway
Cloudflare's new Monetization Gateway handles the entire payment flow at the edge. It supports sub-second, rail-agnostic stablecoin settlement. The gateway processes the 402 price manifest, verifies payments, and settles in seconds. Onchain receipts make each transaction auditable — proving a request was paid, when, and for how much.
AWS's no-code support
AWS made x402 support generally available on CloudFront and WAF for USDC on Base. The configuration enables the 402 price manifest and settlement without any code changes. That means developers can add per-request pricing to their existing CloudFront distributions by flipping a few settings.
Ripple's RLUSD in Japan
Ripple's RLUSD stablecoin went live in Japan via SBI VC Trade after receiving approval from the Financial Services Agency. The move positions a regulated stablecoin option in one of the world's largest crypto markets. RLUSD can now be used as a settlement asset in x402 transactions alongside USDC on Base.
The numbers so far
In the 30 days ending July 15, 2026, x402 saw 75.41 million transactions. Total volume hit $24.24 million. About 94,060 buyers and roughly 22,000 sellers used the protocol. Those numbers suggest the model is gaining traction beyond early adopters.
How to try it
The playbook is straightforward. Start with one metered asset. Enable the gateway or CDN rule. Choose a settlement asset — USDC on Base or RLUSD both work. Publish clear pricing. The protocol handles the rest. For developers tired of managing subscriptions and user accounts, x402 offers a simpler alternative. The question now is how quickly the rest of the web infrastructure follows.
