x402 Payment Standard’s Documented Flows Lack a Common Test for Agent Purchases

The x402 payment standard lets a service request payment over HTTP, but its documented transaction flows do not provide a common process for deciding whether an AI agent obtained a service that matched its user’s intent.

The x402 Foundation began operating July 14, 2026, after Coinbase completed its contribution of the protocol. Visa and Mastercard are Premier members. That tier has a $200,000 fee and includes an appointed seat on the Governing Board, with influence over budgets and core governance decisions. The Governing Board handles marketing, business oversight and budgets; a separate Technical Steering Committee oversees technical matters and approves project or system proposals.

With HTTP 402, or “Payment Required,” a service can ask a client to pay before it retries a web request. The standard includes exact, upto and batch-settlement schemes. In the default exact flow, payment is verified, the service handler runs, and payment settles afterward. A handler failure prevents the charge in the default flow.

An upfront option settles payment before the handler runs. The upfront flow has no specified refund procedure; the resource server decides how to remedy a failed request. The batch-settlement scheme also includes cooperative refund procedures. These options describe how payments and refunds can be handled, but they do not supply a shared way to assess whether a service fulfilled a user’s request.

A Sept. 16, 2026, proposal would organize evidence for disputes involving agent-initiated payments. It leaves dispute decisions and fund reversals outside its scope and remained open as of Oct. 29, 2026, so it does not establish an adopted Foundation process.

Related coverage has examined buyer approval in an x402 checkout and dispute handling in agentic-commerce standards.