Agentic Commerce Timeline

The key milestones in agentic commerce, in order, each tied to a primary source. This page is maintained as new developments land. For a forward-looking counterpart, when this is likely to become unavoidable, see when agentic commerce becomes table stakes.

2025

29 April: Mastercard unveils Agent Pay, its agentic payments program built on agentic tokens, with launch partners including Microsoft and IBM.

30 April: Visa announces Intelligent Commerce, opening its network to AI agents through tokenized “AI-Ready Cards,” with collaborators including Anthropic, OpenAI, and Stripe.

6 May: Coinbase launches x402, an open protocol that revives the HTTP “402 Payment Required” status for stablecoin payments between software.

14 May: Perplexity selects PayPal to power agentic checkout in Perplexity Pro, one of the earliest named agent-checkout partnerships.

16 September: Google announces the Agent Payments Protocol (AP2), a payment-authorization standard backed by more than 60 organizations. PayPal announces AP2 support the same day.

23 September: Coinbase and Cloudflare announce their intent to form the x402 Foundation to steward the stablecoin protocol as a neutral standard.

29 September: OpenAI and Stripe launch Instant Checkout in ChatGPT and release the Agentic Commerce Protocol (ACP), with Etsy live first.

14 October: Walmart partners with OpenAI to let ChatGPT users buy its catalog.

28 October: PayPal adopts ACP, bringing its merchant network and wallet into ChatGPT’s Instant Checkout.

9 December: Anthropic donates the Model Context Protocol (MCP) to a new foundation under the Linux Foundation, cementing MCP as the neutral discovery layer beneath the stack.

2026

11 January: Google launches the Universal Commerce Protocol (UCP) at the NRF retail show, co-developed with Shopify, Etsy, Wayfair, Target, and Walmart, covering the full shopping journey.

March: A2A reaches v1.0, its first stable specification, adding multi-protocol bindings and version negotiation, enterprise multi-tenancy, and signed agent cards for cryptographic identity verification. It is the coordination layer UCP’s A2A checkout binding and the A2A x402 extension build on.

18 March: Stripe and Tempo launch the Machine Payments Protocol (MPP), an open standard for agents to pay services programmatically, for microtransactions and recurring payments, with payment supported in stablecoins as well as cards. It joins x402 in the machine-to-machine settlement lane. The core is specified as an HTTP authentication scheme and was submitted to the IETF the same day as draft-ryan-httpauth-payment, an individual Internet-Draft with an intended status of Standards Track that has not been taken up by a working group.

March (reported): OpenAI scales back native Instant Checkout, shifting toward ChatGPT Apps and product discovery. This was surfaced through trade reporting and an OpenAI spokesperson statement rather than a single official release.

2 April: The x402 Foundation formally launches under the Linux Foundation, with Coinbase contributing the protocol.

8 April: Visa unveils Intelligent Commerce Connect, a network, protocol, and token-vault-agnostic “on ramp” that lets merchants accept agent-initiated payments across protocols including the Trusted Agent Protocol, MPP, ACP, and UCP, launching in pilot with general availability targeted for the end of June 2026.

14 April: American Express debuts its Agentic Commerce Experiences developer kit and an industry-first Agent Purchase Protection pledge for purchases made by registered agents.

24 April: Amazon, Meta, Microsoft, Salesforce, and Stripe join what is now the UCP Shopping Tech Council, alongside founders Google, Shopify, Etsy, Target, and Wayfair, taking it to sixteen seats across ten companies, a sign the industry is converging on UCP as a shared open standard.

April: Google donates AP2 to the FIDO Alliance and releases AP2 v0.2, adding support for autonomous “human not present” payments. Mastercard’s compatible Verifiable Intent standard is contributed to FIDO alongside it.

20 May: At Google Marketing Live, Google expands UCP, extending Universal Cart to named brands (Nike, Sephora, Target, Walmart, Wayfair, and Shopify merchants) and pushing UCP into new verticals beyond retail, hotel booking and food delivery, rolling out in the US first.

24 June: The American Arbitration Association-International Centre for Dispute Resolution and Integra Ledger launch the Legal Context Protocol (LCP), an Apache 2.0 standard that publishes a business’s legal terms, and the route to recourse, at /.well-known/legal-context.json. Founding contributors include Google, IBM, Circle, Wayfair, Stellar Development Foundation, Ava Labs, UiPath, Cardano, Hedera, and Mysten Labs. It is the first serious attempt at the layer every payment and checkout protocol leaves out of scope, and it is early: the v1.0 specification is a draft for community review and no protocol steward has adopted it.

Late June to early July: AWS and Cloudflare embed x402 at the edge. AWS makes x402 settlement generally available in CloudFront and AWS WAF; Cloudflare opens a waitlist for a Monetization Gateway that charges for pages, APIs, datasets, and MCP tools via x402. Both settle in stablecoins through Coinbase’s facilitator, a sign the machine-payments rail is moving from concept to infrastructure.

14 July: The Linux Foundation announces the operational launch of the x402 Foundation under formal, open governance, with Coinbase’s contribution of the protocol complete and 40 members on board. The premier tier now spans every major card network (Visa, Mastercard, American Express), payment providers (Stripe, Adyen, Fiserv), platforms (Google, Shopify, AWS, Cloudflare), and crypto infrastructure (Coinbase, Circle, Ripple), a notable mainstreaming of the stablecoin rail.

16 July: UCP seats a second domain body, the Food Tech Council, with Block (Square), DoorDash, Google, Toast, and Uber Eats as inaugural members, filling ten of sixteen seats. It is the first evidence that UCP’s per-vertical governance model is more than a diagram, and it follows the May commitment to extend the protocol into food delivery.

23 July: The IETF holds a working-group-forming BoF in Vienna, Agent Communication Protocols (agentproto), asking whether agent-to-agent and agent-to-tool communication needs standards at the IETF rather than only at vendor consortia and the Linux Foundation. It is the first time the venue question has been put formally. The draft minutes record strong sense-of-the-room support for forming a group (154 to 51) and for the IETF as the right place (158 to 30), but the proposed scope was rejected (38 for, 124 against), and the responsible Area Director confirmed a new mailing list. The results are explicitly non-binding, and the datatracker still lists the group as state BOF with no charter. MCP and A2A ran through the discussion, and a charter pull request was raised from the MCP side. Worth watching rather than acting on: if agentproto charters, the agent layer gains a third governance venue alongside FIDO and the Linux Foundation.

28 July: The 2026-07-28 revision of MCP is published as the stable specification, replacing 2025-11-25 and becoming the largest revision of the discovery layer since launch. The protocol core goes stateless (the initialize handshake and Mcp-Session-Id are retired, with protocol version, client identity, and capabilities carried in _meta on every request); Multi Round-Trip Requests replace server-initiated elicitation, sampling, and roots calls; Mcp-Method and Mcp-Name headers become required on Streamable HTTP; the Extensions framework is formalized with MCP Apps, Tasks, and Enterprise Managed Authorization as official extensions; and OAuth and OpenID Connect authorization is hardened. It contains breaking changes for existing MCP servers, and deprecates Roots, Sampling, Logging, and the legacy HTTP+SSE transport under a new twelve-month policy. All four Tier 1 SDKs shipped support the same day.

3 and 7 August: MPP widens on two fronts. On 3 August it adds relays, an optional external service that takes over payment validation and settlement so an application can accept several rails through one interface; MPP deliberately does not standardize the relay interface. On 7 August a second Internet-Draft, draft-payment-discovery-00, is submitted by Tempo Labs and Merit Systems, defining OpenAPI-based discovery so agents can find priced endpoints before requesting them. Like the core draft it is an individual submission with no working group behind it, and its intended status is Informational.

11 August: UCP seats a third domain body, the Lodging Tech Council, with Amadeus, Booking.com, Expedia, Google, Hilton, Marriott, and Trip.com as inaugural members. The roster covers the lodging supply chain end to end: global distribution and online travel agencies, hotel groups, and Google as the convening consumer surface. Three domain councils in five weeks, and the second vertical to be governed rather than only announced.

17 August: A2A becomes a hosted project of the Agentic AI Foundation, moving out of the Linux Foundation’s broader portfolio into the body that already holds MCP, Block’s goose, AGENTS.md, and agentgateway. Each project keeps its own maintainers, specification process, and release schedule. It is the sharpest illustration yet of the year’s consolidation pattern: the two protocols agentic commerce leans on most, MCP for tool access and A2A for agent coordination, are now governed in one neutral place. The specification itself is unchanged.

18 August: Rain launches the Agentic Payments Alliance, a coalition of 26 founding members including Visa, Mastercard, Fiserv, Circle, Solana, Uniswap Labs, Chainalysis, Fireblocks, Shift4, Lithic, and Remitly. Its stated early work is shared research and frameworks, testing emerging standards for agent identity and authorization, and advocacy on the regulatory questions. Note what it is and is not: a working coalition run collectively by its members, with no specification of its own, arriving into a field that already has FIDO, the Linux Foundation, and a possible IETF venue. Worth tracking for whether it produces a standard or a position.

22 August: The MCP lead maintainers publish a new roadmap for the releases after 2026-07-28, with five priority areas: agentic messaging primitives, HTTP-native transport unification, agent identity and enterprise-ready security, improved primitives, and SDK developer experience. Two bear on commerce: progressive discovery, so a server with a large catalog can expose a small entry point rather than making the model pay for every tool up front, and continuing Server Card work on .well-known metadata so a server can be discovered without connecting to it. Direction rather than specification, with no dates attached.

25 August: UCP publishes v2026-08-25, its fourth release and the first since April. UCP describes it as major protocol enhancements, structural refactorings to support multi-vertical expansion, payments security improvements (3DS2), structured request constraints, independent capability versioning, and grocery shopping readiness. The structural change is the one to note: the specification is now organized as Common, Shopping, and Payment rather than shopping-first, with payment constructs lifted into the cross-vertical common layer, a Location capability for finding physical stores added under Common, and new Payment Authentication, Payment Terms, and Split Payments extensions. It carries breaking changes. Read alongside the Food and Lodging councils, it is UCP rebuilding itself so verticals can be added without forking the payment layer.

1 September: EMVCo publishes a draft, EMV Agentic Payments: Framework for Specifications v1.0, for public comment to 30 September, and confirms an Agentic Payments Task Force to develop its approach. The draft proposes Intent Services, a shared interoperable layer for registering, referencing, retrieving, and managing consumer-authorized intent before, during, and after a transaction, aimed at the cases where intent has to persist: recurring purchases, cumulative budgets, post-transaction activity. EMVCo frames it as complementing cryptographic approaches such as Mastercard’s Verifiable Intent rather than replacing them, and flags Know Your Agent and Agentic Transaction Indicators as possible later work. It is a draft framework, not a specification, but EMVCo is owned by the six card networks, so this is the card industry’s own answer to the agent-identity and persistent-intent problem, arriving alongside FIDO’s.

2 September: Anthropic publishes an open commerce agent blueprint, reference shopping and merchant agents on Claude under Apache 2.0, with Accenture, Mastercard, and Visa named as ecosystem partners and a Shopify implementation built over UCP and Sign in with Shop. The boundary is the interesting part: Anthropic supplies the agent patterns and hands payment to the merchant, contributing no rail of its own. It is the third model provider to take a position at the commerce layer, and it took it by adopting someone else’s protocol.

What to watch

The trajectory is clear: a land-grab phase of competing vendor announcements in 2025, followed in 2026 by consolidation into neutral standards bodies (the FIDO Alliance and the Linux Foundation) and a settling-out between the two commerce-layer camps, ACP and UCP. August tightened that consolidation a notch, with A2A joining MCP inside the Agentic AI Foundation. Three open questions sit at the end of this window. First, whether consolidation continues into the formal standards world: the July agentproto BoF is the first test, the IETF has not answered, and a non-working-group mailing list opened on 24 July to rewrite the charter. Second, whether the counter-movement matters: the Agentic Payments Alliance formed in August as a vendor coalition, not a standards body, which is the shape the industry was supposedly growing out of. Third, and newest, what the incumbent payments standards bodies do now that they have arrived: EMVCo’s draft framework closes for comment on 30 September, and whether Intent Services becomes a specification is the question to carry into the fourth quarter. For how the pieces relate, see the landscape and the protocol stack.