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.

24 March: The ChatGPT channel changes shape, in two first-party announcements on the same day. OpenAI says the first version of Instant Checkout “did not offer the level of flexibility that we aspire to provide,” so it is “allowing merchants to use their own checkout experiences” while it focuses on product discovery, and it expands ACP to cover discovery. Instant Checkout is narrowed rather than retired; OpenAI’s developer documentation still describes it as available to approved partners. And Shopify switches on Agentic Storefronts: “Starting this week, millions of merchants can sell to ChatGPT users,” with products “discoverable in ChatGPT by default,” no separate integration or apps, and no transaction fees beyond standard processing. Shoppers find products through Shopify Catalog and complete the purchase on the merchant’s own checkout, in an in-app browser on mobile or a separate tab on desktop, and merchants remain the merchant of record. The same Agentic Storefronts panel reaches Microsoft Copilot, where Shopify says thousands of merchants are already selling, and AI Mode in Search and the Gemini app, where select brands sell through UCP. Read together, these are one event seen from two sides: OpenAI stepped back from owning the checkout, and the largest commerce platform stepped in to supply discovery at scale while leaving checkout with the merchant. That, rather than in-chat buying, is the shape agentic shopping in ChatGPT actually took. Shopify also opened its Agentic plan globally, so brands not on Shopify can list in Shopify Catalog and reach the same AI channels.

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 the official extensions named in the release, a set that has since grown to five with Skills over MCP and OAuth Client Credentials; 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.

4 August: The US Court of Appeals for the Ninth Circuit vacates the preliminary injunction Amazon had won against Perplexity’s Comet assistant, the first US federal appellate decision on agentic AI and the Computer Fraud and Abuse Act. The panel held that it was the user, not Perplexity, who accessed Amazon’s computers for CFAA purposes, and that “however advanced the Assistant currently is, it is a tool, not a person for statutory purposes.” Read the limits as carefully as the holding: the court said expressly that it does not establish a new legal regime governing agentic AI, that it does not reach other theories such as tort claims, and that the outcome “does not impair Amazon’s ability to regulate access to Amazon.com via private terms of service for its users.” It belongs in this timeline because the underlying dispute was about an agent declining to identify itself as an agent, which is exactly the problem Visa’s Trusted Agent Protocol, Mastercard’s Verifiable Intent, and the Know-Your-Agent work exist to solve. The courtroom and the identity layer are the same story. On 10 September the court denied Amazon’s petition for rehearing en banc; the full court was advised and no judge requested a vote, so the panel’s opinion stands and the case returns to the district court. See the ruling.

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 the family is widened with a second document, draft-payment-discovery, 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; it reached revision -01 on 1 October 2026. (This draft is published on MPP’s own paymentauth.org rather than appearing on the IETF Datatracker, so it is an Internet-Draft in format rather than a submitted one.)

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, agentgateway, and Agent Router. Each project keeps its own maintainers, specification process, and release schedule. A2A’s own announcement, on 27 August, describes the governance tier as a Growth Stage project. 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 Terms and Schedules, Split Payments, and Loyalty 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, and confirms an Agentic Payments Task Force to develop its approach. The comment period closed on 30 September 2026 with no disposition of comments published. 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.

2 September: UCP seats a fourth domain body, and the first that is not a retail vertical. The Payments Tech Council welcomes Adyen, Ant International, Coinbase, Global Payments, Google, PayPal, Shopify, and Stripe as inaugural members: acquirers and processors, wallets, a stablecoin rail, and the two permanent Governing Council members. It is the governance counterpart to the structural change in v2026-08-25, which moved payment out from under shopping into a cross-vertical Common layer. Read together, the specification and the governance now treat payment as something that runs beneath every vertical rather than as part of retail checkout.

8 September: Meta launches Muse, a consumer agent that acts rather than answers, rolling out in the US on iOS, Android, and muse.ai with a free tier and paid plans. It runs on a dedicated cloud virtual machine with its own browser, can “open a browser, fill out forms, and negotiate” on the user’s behalf, and checks with the user “before sensitive actions like sending an email or making a purchase.” Payment is the detail to note: Muse checks out with Link by Stripe, whose wallet for agents issues a one-time-use card so real card details stay hidden, and Meta says Muse is the first AI agent covered by Link’s purchase protections; Shop Pay is “coming soon.” Two things follow for this map. Meta joins OpenAI, Google, and Perplexity as an operator of a mass-market buying agent, not only as a backer of ACP and UCP. And Muse buys through a browser and a wallet rather than through a commerce protocol: Meta names no ACP or UCP integration, though Shopify said in March that UCP would “soon” power checkout in some Meta experiences. It is the clearest example yet of agentic shopping that works without the merchant opting in.

9 September: Ant International, Mastercard, and Visa begin a collaboration on Know-Your-Agent interoperability, so that networks, wallets, agent platforms, and marketplaces can recognize a trusted agent without each running its own identity check. Three areas are named: cross-network operator traceability linking an agent to a validated operator, cardholder, or business; shared certification against common security and behavioral requirements; and continuous monitoring using identity and transaction signals. Each network keeps its own verification and decisioning, and the three approaches it aims to bridge stay in place: Visa’s Trusted Agent Protocol, Mastercard’s Verifiable Intent, and Ant International’s Agentic Mobile Protocol. The work runs through BuildFin.ai, an industry platform convened by the Monetary Authority of Singapore, which puts a financial regulator’s platform under an agent-identity effort for the first time. No specification, governance body, or timeline was published, so this is intent rather than standard. See the announcement.

9 September: The MPP core specification is refreshed in the IETF’s document system under a shorter name, draft-httpauth-payment-01, by the same Tempo Labs and Stripe authors, extending its life to 13 March 2027. Losing the author prefix from a draft name usually signals working-group adoption; here it does not. The Datatracker still records an individual Internet-Draft with no RFC stream, no intended RFC status, and no working group, and it records no formal replaces relationship with draft-ryan-httpauth-payment. The specification is being kept current inside the IETF’s document system while staying outside the IETF’s process.

24 September: Block joins the x402 Foundation and contributes Bitcoin Lightning payments to the protocol, announced on Block’s own newsroom with a quote from x402’s creator as a Technical Steering Committee member. It is the first major non-stablecoin rail inside x402, which until now settled overwhelmingly in USDC, and it widens the settlement layer rather than the commerce layer. The foundation itself had not announced it as of 1 October, so this is sourced from the contributing company.

25 September: UCP merges the first draft of the Lodging Booking capability (dev.ucp.lodging.booking) into its repository, which UCP calls the formal expansion of the protocol into the Lodging domain. Developed by the Lodging Tech Council with open-source contributors, it covers real-time pricing and availability checks, guest registration, complex payment schedules, and cross-vertical primitive interoperability. This is the entry that answers the question the July-to-September run of vertical councils raised: the councils are producing specification text, not only rosters. Two qualifications hold it in proportion. It is a draft merged outside the release cadence, so v2026-08-25 is still the current revision and there is nothing versioned to build against. And the roadmap still lists food and lodging as being developed, now worded as going “beyond Booking.”

28 September: Shopify extends WebMCP into checkout. WebMCP is a proposed web standard, which Shopify says it is helping shape alongside Google and Microsoft, that lets a site register tools a browser agent calls directly instead of reading page code or simulating clicks. On 5 August Shopify had switched on WebMCP tools for catalog search, carts, and orders on every Liquid storefront, with “nothing to install or configure”; the 28 September changelog adds checkout, so browser agents can read and update a Shopify checkout and submit it through four tools (navigate_to_storefront, get_checkout, update_checkout, complete_checkout) on eligible checkouts. The buyer stays in the loop: Shopify’s documentation says the buyer confirms the order before the agent calls complete_checkout, and control returns to the buyer for steps such as 3D Secure or Shop Pay login. The protocol detail is the one that matters for this map: Shopify describes Checkout WebMCP as implementing the UCP checkout capability over browser-registered WebMCP tools instead of server-side JSON-RPC. So the merchant-opt-in protocol and the browser agent are no longer separate routes into a Shopify store; the same checkout object now serves both. Agent support is currently limited to Chromium-based browsers.

30 September: Mastercard expands Agent Pay with trust and intelligence services, which it describes as the intelligence layer of an Agent Pay Trust Framework spanning identity, intent, controls, execution, and intelligence. The first service is a probability score indicating how likely it is that a transaction was initiated by an AI agent, so issuers can approve legitimate agent-led purchases rather than decline them as anomalies; it is “rolling out for testing in the U.S.,” not generally available. Mastercard also names Cloudflare (combining web and payment-network signals in privacy-preserving environments) and Skyfire, a Know Your Agent provider. This is the network-side answer to a problem the timeline keeps returning to: a card network that cannot tell an agent from a fraudster will decline the agent.

30 September: The EMVCo comment period on its draft agentic payments framework closes, with no disposition of comments or specification published. The fourth-quarter question the September entry posed now has a clock on it rather than an open door.

1 October: MPP reaches into the discovery layer. Two drafts are published at paymentauth.org on the same day: draft-payment-discovery-01, which adds output-schema guidance to the OpenAPI discovery mechanism, and a new document, draft-payment-transport-mcp-00, which defines how the Payment HTTP authentication scheme operates over JSON-RPC 2.0 and therefore over MCP. It maps a payment challenge to JSON-RPC error code -32042, carries credentials and receipts in _meta under org.paymentauth keys, and names tools/call, resources/read, and prompts/get as the MCP operations that can be put behind a payment. That is the settlement layer wiring itself directly into the discovery layer, and it is the most commerce-relevant thing the MPP family has produced: a merchant’s MCP server could charge per tool call. Two caveats. It is an individual Internet-Draft of intended status Informational with no working group, like the rest of the family. And it still cites MCP revision 2025-11-25, two revisions behind current, which is a fair measure of how early this is.

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 was the first test, and the IETF has now partly answered: the Datatracker records agentproto as a Proposed working group, with its charter in External Review and on the agenda of the 8 October 2026 IESG telechat; a revised text, charter-ietf-agentproto-00-04, was posted on 2 October with two Yes positions already recorded and no Block outstanding. That is a decision due days from this update rather than an open question, and the rewritten charter has narrowed the work to a baseline agentic dialog management protocol in which MCP and A2A carry the dialog context using their own mechanisms rather than being redesigned, on milestones running to March 2028. 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 industry does now that it has arrived, on two fronts at once: EMVCo’s draft framework closed for comment on 30 September, and whether Intent Services becomes a specification is the question to carry into the fourth quarter; and the Ant International, Mastercard, and Visa Know-Your-Agent collaboration announced on 9 September has to turn shared principles into something implementable. Agent identity is now being worked on in at least five places (FIDO, the MCP roadmap, Rain’s coalition, EMVCo, and this collaboration), which says more about how unsettled it is than about how close it is to settling, and the Ninth Circuit’s August ruling is a reminder that the courts will reach the question whether or not the standards bodies get there first. For how the pieces relate, see the landscape and the protocol stack.