x402 adopts acceleration: Why giants like Google, Cloudflare, and Stripe are collectively entering the market

Source: PayAI Network; Compiled by Jinse Finance Claw

The x402 protocol has transformed from an open-source experiment into a standard supported by giants in technology and payments in just over a year.

This article will delve into who is developing with x402, why the adoption rate is accelerating, and what it means for developers and builders positioning the “Agentic Economy.”

Core Summary

• x402 has strong backing: Google, Cloudflare, Stripe, Visa, Amazon Web Services (AWS), and Circle have all taken actions to support or integrate the x402 protocol, marking its transition out of the experimental phase.

• An official foundation has been established: Cloudflare and Coinbase jointly founded the x402 Foundation in September 2025, with founding members from the fields of cloud computing, payments, and infrastructure.

• AI is the catalyst: The intelligent agent AI market is projected to grow from $7.3 billion in 2025 to $324 billion by 2034, creating significant demand for “Machine-Native Payment Rails.”

• Solana leads in settlement: With fees of less than $0.01 and a confirmation speed of 400 milliseconds, Solana has become the dominant blockchain for high-frequency x402 micropayments.

• Start building immediately: Open-source SDKs and facilitator infrastructure (including the Solana-focused toolkit launched by PayAI Network) allow developers to start monetizing APIs and AI services right now.

x402 Adoption is Accelerating: Who is Developing with It

When Coinbase officially released the x402 protocol specification in May 2025, it activated the long-dormant HTTP 402 (Required Payment) status code for direct stablecoin payments embedded in web requests. In just a few months, its adoption has far surpassed the crypto-native circle.

By September 2025, Cloudflare and Coinbase jointly established the x402 Foundation, with Google, Visa, AWS, and Circle joining as founding members. Intelligent agent payments are no longer a future concept; they have now become a cross-industry alliance spanning cloud computing, global payments, and internet infrastructure.

What differentiates this moment from previous attempts at crypto payments is “convergence”: infrastructure providers, payment processors, and AI platforms are all gravitating towards x402 in synchrony. The payment layer of the internet is being restructured for the agentic era, and the giants have chosen to build together.

Google and x402: The Search Giant Enters Internet-Native Payments

Google’s involvement with x402 goes far beyond just displaying a logo on the foundation’s webpage. The company has collaborated with Cloudflare and partners like Accenture, PayPal, and MetaMask to develop the Agent Payments Protocol (AP2). AP2 positions x402 as the underlying settlement mechanism for “agent-initiated procurement” and “machine-to-machine” transactions operating on Google Cloud infrastructure.

This is crucial for two reasons: first, Google Cloud is one of the largest platforms for deploying AI workloads, and agents powered by Gemini are becoming increasingly autonomous. These agents need a way to pay for external services (such as data, computing power, and API calls) without human intervention. x402 provides precisely this possibility: a payment handshake that occurs within standard HTTP requests.

Google’s joint participation in the x402 Foundation with Visa, AWS, and Circle sends a clear signal to enterprise buyers: intelligent agent commercial systems are not merely a crypto industry niche; these companies plan to provide production-grade infrastructure that can collectively serve billions of users.

Cloudflare and x402: Payment at the Edge

Cloudflare’s adoption of x402 may be the most architecturally significant move in the ecosystem. The company launched a “Pay-per-crawl” feature that allows website owners to charge AI bots and crawlers a fee for accessing content through stablecoin micropayments, turning security risks into revenue streams.

As Cloudflare acts as a reverse proxy for millions of websites, embedding x402 payment support at the network edge means that any site using Cloudflare can monetize traffic without changing application code. For developers building applications on Workers or Pages, this eliminates significant friction.

Cloudflare CEO Matthew Prince has publicly stated that x402 has the potential to become the foundational internet protocol for machine-to-machine payments, comparing its trajectory to that of HTTP and HTTPS. When a non-crypto-native infrastructure company with such extensive coverage regards payment primitives as a first-class feature, it signifies a paradigm shift.

Stripe and x402: Traditional Payments Meet New Standards

Stripe’s move towards x402 can be seen as the strongest validation signal for mainstream adoption. The company launched a preview of machine payments integrated with x402, enabling AI agents to use USDC to pay for API calls and digital services, with payments settling in fiat currency to the merchant’s Stripe balance.

This “bridging” function is critical. Stripe processed over $1 trillion in payments in 2024, serving as the payment backbone for millions of internet businesses. Its support for x402 means that existing merchants can access stablecoin-based micropayments without needing to rebuild their payment stack or learn about crypto infrastructure.

For the millions of SaaS platforms, marketplaces, and API providers already using Stripe, this offers a pragmatic entry point. They can receive x402 payments from AI agents while continuing to manage revenue through the familiar Stripe dashboard. This is precisely how the protocol scales: interfacing with enterprises where they are.

AWS Deepens Commitment to Intelligent Agent Payments: Integrating x402 into Core Services

To avoid falling behind cloud competitors, Amazon Web Services (AWS) has significantly increased its investment in the agent economy by integrating x402 support into its Lambda and API Gateway services.

In a recent announcement, AWS stated that developers can now natively configure the API Gateway to return a 402 status code for non-authenticated or unpaid requests, utilizing AWS Lambda to facilitate the negotiation and settlement of x402 payments through the PayAI Network facilitator.

This move greatly reduces friction for millions of AWS developers monetizing their serverless functions and data streams, positioning x402 as a first-class feature of on-demand cloud services.

As a founding member of the x402 Foundation, AWS is providing production-grade tools to ensure that agents running on platforms like Amazon Bedrock can seamlessly pay for resources across the entire cloud ecosystem.