The Linux Foundation has formally activated the x402 Foundation, bringing 40 financial-services, payments, cloud-computing and blockchain organizations into an open-governance group focused on establishing a common protocol for payments conducted directly through internet interactions.

The operational launch follows an initial announcement in April that the Linux Foundation intended to create a neutral home for x402 and accept the protocol from Coinbase. The latest step completes that contribution and places the project under a formal governance structure intended to allow financial institutions, developers, infrastructure providers and other participants to influence its technical direction.

The foundation is seeking to standardize payments over HTTP, the core request-and-response framework used by websites, applications and application programming interfaces. Its central premise is that software should be able to request, authorize and complete a payment during the same type of interaction it already uses to retrieve data or invoke an online service.

That capability is becoming increasingly relevant as companies deploy artificial-intelligence agents capable of searching for information, purchasing services and performing operational tasks without direct human involvement at every stage. Existing payment experiences are largely designed for people, relying on registration forms, checkout pages, stored credentials, authentication prompts and manual approval. Those steps can be difficult for autonomous software to navigate reliably.

The x402 protocol is built around the HTTP 402 status code, designated “Payment Required.” Although the status code has long existed within the HTTP framework, it historically lacked a broadly adopted standard for communicating payment terms and completing transactions. The x402 project seeks to turn that unused component into a practical mechanism for programmatic commerce.

Under a typical x402 interaction, a client requests a digital resource from a server. If the resource requires payment, the server returns a 402 response containing information about the amount, supported payment methods and settlement requirements. The client selects an accepted option, creates a signed payment payload and resubmits the request with the required authorization.

The resource provider can verify and settle the payment directly or use a facilitator that performs those functions on its behalf. After successful verification, the server completes the requested work, settles the transaction and returns the resource to the client. That resource could be an API response, a data file, computing capacity, access to an online tool or a piece of paywalled content.

The model is designed to support small, usage-based transactions that may be uneconomic or operationally cumbersome under conventional billing arrangements. An AI agent, for example, could pay for one database query, one weather-data request, one model inference or a limited amount of computing capacity rather than establishing a subscription or prepaying for a large block of credits.

Support from large financial and technology companies gives the project a wider base than many earlier internet micropayment initiatives. The foundation’s premier members are Adyen, Amazon Web Services, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Monad Foundation, MoonPay, Ripple, Shopify, Solana Foundation, Stellar Development Foundation, Stripe and Visa.

General members include Aleo, Fireblocks, Galaxia Moneytree, Hecto Financial, Injective, KakaoPay, Kite AI, LayerZero Labs, Merit Systems, NEAR Foundation, Orthogonal, Polygon Labs, Quant Network, SKALE, t54 labs, utexo, World Liberty Financial and zerohash. The associate tier includes BSV Association, Cardano Foundation, Casper, the Japanese Contents Blockchain Initiative and OMA3.

The membership composition gives the foundation representation from several parts of the payments value chain. Visa, Mastercard and American Express bring experience in global card-network rules and merchant acceptance. Adyen, Fiserv and Stripe operate payment-processing and acquiring infrastructure. Circle, Coinbase, MoonPay and Ripple provide digital-asset, wallet or stablecoin capabilities, while AWS, Google and Cloudflare operate infrastructure used by developers and online businesses.

Blockchain foundations in the coalition may also help x402 support multiple settlement environments rather than becoming tied to a single digital asset or distributed ledger. The project describes itself as network-, token- and currency-agnostic. Its stated objective is to accommodate both blockchain-based and traditional payment methods while giving servers and clients flexibility over the rails they use.

The Linux Foundation said the protocol can support payment types ranging from cards to stablecoins. That breadth is strategically important because enterprise adoption is unlikely to depend on one settlement method. Some developers may favor stablecoins for fast, low-value, cross-border transactions, while established businesses may require familiar card, bank or regulated payment-processing arrangements.

Bringing those options under one protocol would allow applications to negotiate payment requirements without embedding a separate integration for every provider. A merchant could theoretically present multiple accepted payment methods through the same HTTP-based interaction, while the buyer or software agent could choose a compatible route based on cost, speed, currency, network availability or internal policy.

The foundation’s vendor-neutral structure is intended to reduce the risk that one company controls the rules, intellectual property or access conditions for the protocol. Coinbase developed x402 and initially worked with Cloudflare and Stripe on the project’s governance, but its contribution to the Linux Foundation transfers stewardship to a broader industry organization.

That transition could be important for banks, card networks and large enterprises that are reluctant to build critical payment infrastructure around a standard controlled by a direct competitor. Linux Foundation governance is designed to provide transparent technical participation, shared development processes and a framework in which multiple companies can contribute without surrendering the protocol to a single commercial platform.

The project is released under the Apache 2.0 open-source license. Reference implementations are available for widely used programming languages and server frameworks, including TypeScript, Python and Go. The repository also includes implementations for several blockchain environments and payment schemes, allowing developers to test both direct settlement and transactions handled through facilitators.

The protocol distinguishes between payment networks and payment schemes. A network identifies the infrastructure on which value moves, while a scheme defines the economic and operational structure of the transaction. The project supports exact payments for a specified amount, authorizations allowing a seller to charge up to an agreed limit and batch-settlement mechanisms intended to combine numerous small payments.

Batch settlement could be significant for services processing large numbers of low-value requests. Settling each request individually on a public blockchain may produce delays and transaction costs that undermine the economics of micropayments. A batching mechanism can record smaller charges away from the main settlement layer and redeem them collectively, reducing the number of final transactions.

Facilitators are another major component of the x402 architecture. A facilitator can verify payment payloads, interact with a payment network and confirm settlement for resource providers that do not want to operate that infrastructure themselves. The model creates opportunities for payment companies, digital-asset platforms and financial-software providers to offer managed x402 services.

Those services could include wallet management, transaction screening, foreign-exchange conversion, reconciliation, reporting and spending controls. Businesses deploying AI agents will require mechanisms that limit what an agent can purchase, establish maximum transaction values, restrict approved vendors and generate records for audit and accounting purposes.

The payments industry is increasingly treating those controls as essential to agentic commerce. Autonomous software may execute transactions more frequently and at smaller values than human buyers, creating new requirements around authorization, identity and risk management. A business may permit an agent to purchase data or computing resources but still require rules governing aggregate spending, geographic exposure and counterparties.

Open technical standards can define how payment requests and responses are exchanged, but they do not eliminate legal and regulatory obligations. Companies supporting x402 transactions may still need to comply with customer-identification requirements, anti-money-laundering rules, sanctions restrictions, consumer-protection laws, data-privacy standards and licensing requirements in the jurisdictions where they operate.

Traditional card and blockchain payments also have different approaches to finality, refunds and disputes. Card transactions can be reversed through chargeback processes, while many blockchain transfers are difficult to reverse after confirmation. A broadly adopted internet-payments protocol will need to let merchants and clients understand those differences and select payment types appropriate for each transaction.

Security will be another test. Machine-generated payments must be linked tightly to the specific service, amount and destination authorized by the client. Developers will need protection against replay attacks, duplicate transactions, manipulated payment instructions, compromised software agents and attempts to obtain a resource without providing valid payment.

The presence of major payment networks and infrastructure companies may help the foundation establish stronger operating practices, but membership should not be interpreted as a commitment by every participant to deploy x402 across its commercial products. Standards organizations often include companies seeking to observe technical development, protect interoperability interests or influence emerging rules before deciding whether to launch customer-facing services.

The coalition also enters a market where payment companies are developing their own frameworks for AI-assisted commerce. Card networks, processors, wallets and technology platforms are working on agent authentication, delegated purchasing, tokenized credentials and merchant-recognition systems. x402 will need to complement those efforts rather than require companies to abandon existing payment-security infrastructure.

Its most immediate opportunity may be among developer-focused services, where payments are already closely connected to API calls and digital resource consumption. Software providers frequently use subscriptions, monthly invoices or prepaid credit balances because conventional payment systems were not designed to charge for individual requests. An HTTP-native standard could allow them to offer more granular pricing.

That could lower barriers for smaller developers and AI agents that need temporary access to specialized services. Instead of opening an account with every provider, supplying billing information and managing multiple API credentials, a client could receive payment terms from the server and complete a one-time purchase using an approved wallet or payment method.

For sellers, the potential benefit is the ability to monetize data and software without building a full account-management and recurring-billing system. The protocol itself does not impose a transaction fee, although merchants and buyers may still incur charges from the payment or settlement network they select. Commercial facilitators may also charge for verification, compliance or operational services.

Adoption will ultimately depend on whether the standard improves economics and reliability compared with existing billing systems. Developers will assess integration costs, transaction latency, wallet availability and payment success rates. Enterprises will focus on governance, compliance, fraud protection, financial reporting and the ability to operate across multiple currencies and jurisdictions.

The foundation’s launch therefore represents infrastructure development rather than the arrival of a fully mature agentic-payments market. It establishes an organization, transfers the protocol into open governance and assembles a broad group of companies capable of shaping technical and commercial standards. The next stage will be measured by production integrations, merchant participation and transaction activity involving independent buyers and sellers.

Even so, the combination of payment networks, processors, cloud companies and blockchain providers gives x402 a credible platform from which to pursue wider adoption. If the participants can agree on interoperable security, settlement and compliance practices, the protocol could become an important connection point between conventional financial infrastructure and the growing market for software-directed commerce.