The layer-1 blockchain becomes a core member of the Coinbase-originated payment protocol backed by AWS, Google, Visa, and Mastercard
Injective has joined the x402 Foundation as a core member, bringing its sub-second transaction finality to a payment protocol that counts AWS, Google, Visa, and Mastercard among its premier backers. The x402 protocol is now live on Injective’s network, enabling USDC payments that settle in a single block.
That block takes roughly 650 milliseconds to finalize.
What x402 actually does #
The x402 protocol started life as a Coinbase project built around a piece of internet plumbing that’s been gathering dust for decades. HTTP 402 is a status code that was reserved for “Payment Required” when the web’s foundational protocols were designed, but it was never formally implemented.
The x402 Foundation launched operations on July 14, 2025, under the governance of the Linux Foundation, with approximately 40 member organizations. The roster includes AWS and Google on the cloud side, Visa and Mastercard on the payments side, and crypto-native organizations like NEAR Foundation and Polygon Labs.
The protocol’s core purpose is to standardize programmatic, internet-native payments, particularly for artificial intelligence applications. Instead of requiring accounts, API keys, or subscription plans, x402 lets machines pay for services on a per-request basis using USDC.
Why Injective’s architecture matters here #
Injective’s network has processed more than 2.9 billion on-chain transactions, with median fees hovering around $0.0001. At that price point, a million transactions would cost about $100, which makes per-request micropayments economically viable rather than theoretical.
The blockchain’s EVM-compatible environment means developers building on Ethereum’s tooling can port their work to Injective without starting from scratch. For x402 integration specifically, Injective has released middleware libraries, including @injectivelabs/x402, that let developers wire up pay-per-request services with relatively minimal overhead. INJ, the network’s native token, handles gas fees for these transactions.
The single-block finality with deterministic confirmation is the technical feature that makes this work for machine-to-machine commerce. Deterministic finality at 650 milliseconds means the payment is confirmed, full stop, almost instantly, eliminating the latency introduced by waiting for multiple block confirmations.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our