MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

x402

Linux Foundationspecificationcore entry

Verified 2026-10-14. Status as of 2026-10-13. All entries.

Seams: S2S3S4

Status

Open payment protocol under the x402 Foundation (Linux Foundation): intent announced 2026-04-02; operational launch and completed contribution by Coinbase announced 2026-07-14, with 40 member organisations at launch. On 2026-10-13 main is at commit 6c470a8 and the core specification header reads "Protocol Version: 2" (specs/x402-specification-v2.md); no release is listed on GitHub (not found, 2026-10-13). The file ROADMAP.md, which read "(update coming soon)" on 2026-10-03, was removed from main on 2026-10-13 by PR #3789, "chore: remove outdated ROADMAP.md and PROJECT-IDEAS.md".

Relevance

The README says "x402 is an open standard for internet native payments."; the server answers 402 with a PAYMENT-REQUIRED header, the client replies with PAYMENT-SIGNATURE, and an http-message-signatures extension identifies the paying agent. The offer-and-receipt extension lets the server "cryptographically commit to the payment terms it presents in" accepts[] (the payment terms of the offer, not the commercial terms of the sale) and sign a receipt; it says "Wire shape and field placement are not considered stable". The FAQ describes the exact scheme as a push payment, "irreversible once executed".

Committed next

None declared in the sources read.

Boundary

The FAQ answers "Not natively." on credit-card deposits, placing fiat rails outside the protocol.

Sources

Overlaps

Agentic Commerce Protocol (ACP), Universal Commerce Protocol (UCP), Verifiable Intent, Payment HTTP Authentication Scheme (draft-httpauth-payment, Tempo Labs and Stripe)

Neighbours in the map

Neighbours of x402 in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (4)Share a seam (27)Payment HTTP Authentication Scheme (draft-httpauth-payment, Tempo Labs and Stripe) (IETF, context)Payment HTTP Authentica… Agentic Commerce Protocol (ACP) (Industry, core)Agentic Commerce Protoc… Universal Commerce Protocol (UCP) (Industry, core)Universal Commerce Prot… Verifiable Intent (Industry, core)Verifiable Intent W3C DID Resolution (W3C, core)W3C DID Resolution S2 W3C/GS1 Workshop on E-commerce for Humans and AI Agents (Zurich, 8-9 Sep 2026) (W3C, core)W3C/GS1 Workshop on E-c… S2 GS1 Digital Link Standard, URI Syntax 1.7.0 (GS1, context)GS1 Digital Link Standa… S2 GS1-Conformant Resolver Standard 1.2.1 (GS1, core)GS1-Conformant Resolver… S2 UN Global Trust Register, namespace urn:gtr (UN/CEFACT, context)UN Global Trust Register S2 UN Transparency Protocol, Identity Resolver (UN/CEFACT, core)UN Transparency Protocol S2 AI Catalog (Agent Card Working Group) (Linux Foundation, core)AI Catalog S2 schema.org open issues relevant to agents, bookings, product and establishment identity (Independent, core)schema.org open issues… S2 schema.org vocabulary for products, offers, sellers and lodging (current release) (Independent, context)schema.org vocabulary f… S2 W3C Agentic Web Working Group (draft charter) (W3C, core)W3C Agentic Web Working… S3 WebMCP (Draft Community Group Report, Web Machine Learning CG) (W3C, context)WebMCP S3 IETF Web Bot Auth (webbotauth WG) (IETF, core)IETF Web Bot Auth S3 IETF agentproto (Agent Communication Protocols WG) (IETF, core)IETF agentproto S3 Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge) (Independent, core)Browser vendor position… S3 S4 OpenID Foundation AuthZEN Working Group (agent authorization drafts AARP and COAZ) (Independent, context)OpenID Foundation AuthZ… S3 KYAPay (Skyfire) (Industry, core)KYAPay S3 Mastercard Agent Pay (Industry, core)Mastercard Agent Pay S3 Personal Agent Consent & Trust Protocol (PACT), published by Decagon with Instinct (Industry, core)Personal Agent Consent… S3 S4 Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta (Industry, core)Personal Agent Protocol S3 S4 Visa Trusted Agent Protocol (TAP) (Industry, core)Visa Trusted Agent Prot… S3 IETF vcon (Virtualized Conversations WG) (IETF, core)IETF vcon S4 AAIF Agentic Commerce Working Group (AAIF, core)AAIF Agentic Commerce W… S4 EMILIA Protocol (individual drafts and open-source gate) (Independent, context)EMILIA Protocol S4 Agent Payments Protocol (AP2) (Industry, core)Agent Payments Protocol S4 EMV Agentic Payments Framework for Specifications (draft for public feedback) (Industry, core)EMV Agentic Payments Fr… S4 FIDO Alliance agentic authentication and payments work (Industry, context)FIDO Alliance agentic a… S4 Shopify, MCP surfaces for buyer agents, developers and merchants (Industry, context)Shopify S4 x402

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
On 2026-10-13 (fetch of the repository, commit 6c470a8): TSC.md, README.md, the core specification header, specs/extensions/extension-offer-and-receipt.md (still "Wire shape and field placement are not considered stable"), docs/faq.md, and the state of PRs #1986, #3220, #3656, #3789 and issues #2887, #2906, #3500. x402-foundation/x402, 2026-10-03: main branch read (README, TSC.md, ROADMAP, specs, docs, Technical Charter), issues and pull requests updated since 2026-03-01, and the two Linux Foundation releases.
Not read
Slack, the tsc and wg-identity repositories, x402.org member and calendar pages, older items; usage figures on x402.org (self-reported).

Open proposals

ProposalAuthorDateStateLink
Terms extension specificationa participant2026-04-10openhttps://github.com/x402-foundation/x402/pull/1986
Authority extension: bounded, offline-verifiable spending mandatesa participant2026-08-20openhttps://github.com/x402-foundation/x402/pull/3220
Offer-receipt additions: action-receipt, v2 bindings, delivery proof, conformance (#2906 and others)a participant2026-07-19openhttps://github.com/x402-foundation/x402/issues/2906
Dispute evidence layer: working-group request (#2887), feature (#3500)a participant2026-07-17openhttps://github.com/x402-foundation/x402/issues/2887
Reviews extension: links to payment-backed reviews in 402 and settlement responsesa participant2026-10-02openhttps://github.com/x402-foundation/x402/pull/3656

Payment comparison row

Owner / governance
x402 Foundation (Linux Foundation); intent 2026-04-02, operational launch 2026-07-14; TSC.md lists Coinbase, Cloudflare, Stripe
Version and state
v1 SDK packages marked "Deprecated (v1)"; offer-and-receipt: "Wire shape and field placement are not considered stable"
What it signs
Payer signs the payment (PAYMENT-SIGNATURE); with offer-and-receipt the server commits to the offer terms and signs a receipt
Who signs
The client for the payment; the server for offer and receipt
Receipt or record
Signed receipt (offer-and-receipt), declared use "dispute evidence and auditability"; wire shape not stable
Dispute
"irreversible once executed" (exact scheme, FAQ); auth-capture: void, refund, reclaim; dispute process: not found in the pages read, 2026-10-03; the repository has changed since (head e95b066 on 2026-10-13) and a text search of 2026-10-14 finds the word dispute in 26 files, among them the offer-and-receipt specification and scheme texts, not read for a dispute process
Source
https://github.com/x402-foundation/x402/blob/main/specs/extensions/extension-offer-and-receipt.md