1 historical specification
Published Unknown · First observed 2026-09-28
The repository retains Protocol Version 1.
Merchant impact: Check the message version of an existing integration before adopting Version 2.
Version source ↗An internet payment standard built around HTTP payment negotiation.
An internet payment standard built around HTTP payment negotiation. Connects a resource request to payment requirements and a paid retry. Does not describe a retail order, shipping policy or return workflow. Individual merchant eligibility and deployed configuration require confirmation. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.
What this establishes
The documented role and version scope in the source ledger.
What it cannot establish
Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
Publication timestamp not established; date-like version labels are not assumed to be publication timestamps.
Scope: Protocol specification · Layer: Payments · Steward: x402 Foundation / contributors
Version 2 separates the core payment model from transport and scheme specifications.
Select a compatible transport, scheme and facilitator; do not treat payment-resource access as full retail checkout.
Public implementation evidence: Public implementations; merchant deployment Unknown
Merchant action today: Choose supported network and payment scheme.
Unknowns: Your enabled version, provider rollout, plan and region require merchant-side confirmation.
Published Unknown · First observed 2026-09-28
The repository retains Protocol Version 1.
Merchant impact: Check the message version of an existing integration before adopting Version 2.
Version source ↗Connects a resource request to payment requirements and a paid retry.
Does not describe a retail order, shipping policy or return workflow.
Individual merchant eligibility and deployed configuration require confirmation.
| Version | 2 |
|---|---|
| Discovery | Resource-specific payment requirements |
| Checkout | Outside retail checkout scope |
| Payment | HTTP 402 payment flow |
| Authorization | Scheme-dependent |
| Transport | HTTP-native |
| Adoption | Public implementations; merchant deployment Unknown |
First house observation: 28 September 2026. Earlier dates, where known, are effective dates researched retrospectively.
V1 record: Unknown; no structured prior-version timeline.
2; 2 scoped version record(s) now linked.
Merchant impact: Select a compatible transport, scheme and facilitator; do not treat payment-resource access as full retail checkout.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: HTTP payment flow
Repository says canonical development moved to x402 Foundation; Coinbase repo is a development fork.
Claim scope: Internet-native payments
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: aa6dc5e8ccc7758689945fc7502674f51cd0f21f09ec886aa1dbc4cd86bc81b6