The Tech Council Just Doubled
On April 24, 2026, Amazon, Meta, Microsoft, Salesforce, and Stripe joined the Universal Commerce Protocol Tech Council. The body that steers UCP, the open standard Google launched on January 11, 2026, now has ten members spanning search, marketplaces, social commerce, enterprise software, payments, and retail infrastructure.
This is not the end of the protocol war for agentic commerce. Stripe sits on the Tech Council while continuing to maintain the Agentic Commerce Protocol with OpenAI. The standards are converging, not consolidating. What changed on April 24 is more specific, and arguably more important than a winner-takes-all narrative would suggest. UCP won the governance layer. It is now the body the broadest set of commerce incumbents have agreed to sit inside, extend, and shape.
For merchants, that distinction matters. The protocol war framing implies a binary choice: pick the winner, abandon the loser. The governance framing implies something different. Prepare your data and identity surfaces to be readable by any agent, on any protocol, with the assumption that the protocols will continue to interoperate rather than displace each other.
What UCP Actually Is
The Universal Commerce Protocol is an open standard for programmatic exchange between AI agents and merchants across the full commerce lifecycle. Google launched it on January 11, 2026 in collaboration with founding Tech Council members Shopify, Etsy, Target, and Wayfair. The protocol's initial scope covers three capabilities: Checkout, Identity Linking, and Order Management.
The architectural decision that defines UCP is its interoperability stance. The protocol does not replace existing agentic standards. It composes with them.
UCP uses Model Context Protocol (MCP) for tool and data access between agents and merchant backends. It uses Agent2Agent (A2A) for coordination between independent agents, such as a buyer's shopping agent negotiating with a merchant's inventory agent. It uses Agent Payments Protocol (AP2) for payment authorisation and audit trails. UCP is the orchestration layer that sits above all three, defining how the commerce journey itself is structured.
This composability is why merchants retain control. Under UCP, the merchant remains the Merchant of Record for every transaction. Customer data, the post-purchase relationship, and the underlying commerce stack stay with the merchant. UCP defines the protocol through which an agent transacts on a customer's behalf, not the system on which the merchant operates.
Who Joined, and Why It Matters
The Tech Council is the technical body that governs UCP as an open standard. It steers specification changes, certifies implementations, and sets the direction of the protocol. Tech Council membership is the closest equivalent to a board seat in standards governance.
The five additions on April 24, 2026 are not symmetric in significance.
Amazon is the largest commerce platform on the internet. Its presence on the Tech Council means the protocol that governs agent-mediated buying will not be defined without Amazon's input.
Microsoft ships Copilot, a primary distribution surface for agentic commerce competing directly with Google's Gemini. A council seat means Microsoft is shaping the protocol it will deploy through its own AI surface, rather than building a separate standard for Copilot to compete with.
Meta runs the largest social commerce footprint in the world across Instagram and WhatsApp. Its participation signals that social commerce will not splinter off into its own agentic protocol.
Salesforce owns the enterprise commerce stack at the upper tier of B2B and B2C operators. Its membership places enterprise commerce inside the same governance body as marketplace and search-driven commerce.
Stripe is the consequential addition. Stripe co-authored the Agentic Commerce Protocol (ACP) with OpenAI, launched on September 29, 2025 as the rival open standard for agent checkout. ACP currently powers ChatGPT Instant Checkout. Stripe joining the UCP Tech Council does not mean abandoning ACP. It means Stripe is now positioned inside both governance bodies, ensuring the protocols converge on shared primitives rather than diverge into incompatible silos.
That convergence stance is the actual signal of April 24. The narrative of "UCP won, ACP lost" misreads the structural move. The infrastructure is consolidating around interoperability, not around a single winning specification.
The Stack: ACP, UCP, MCP, A2A, AP2
The proliferation of acronyms in agentic commerce obscures a relatively clean architecture. Each protocol addresses a different layer.
MCP (Model Context Protocol) is Anthropic's general-purpose standard for connecting AI models to external data sources, tools, and APIs. It is not a commerce protocol. It is the substrate that lets any agent access any tool.
A2A (Agent2Agent) governs how independent agents coordinate with each other. When a buyer's shopping agent negotiates with a merchant's inventory agent, A2A defines the communication pattern.
AP2 (Agent Payments Protocol) governs payment authorisation. It specifies how an agent proves it has permission to spend, how that permission is scoped, and how the authorisation chain is audited.
ACP (Agentic Commerce Protocol) governs single-transaction agent checkout, primarily within generative AI environments like ChatGPT. It is maintained by OpenAI and Stripe.
UCP (Universal Commerce Protocol) governs the full commerce lifecycle: discovery, cart construction, checkout, identity linking, and post-purchase order management. It composes with all of the above.
In practice, an agentic transaction may use UCP for the journey, MCP for tool access, A2A for negotiation, AP2 for payment authority, and ACP-derived primitives for checkout flows. The protocols stack rather than compete at the level of a single transaction.
Why "Winning Governance" Is the Right Framing
In open-standards history, the body that governs the standard tends to outlast any specific implementation of it. HTTP outlasted Netscape. SMTP outlasted every proprietary email system. The reason is structural. The governance body coordinates the long-term evolution of the specification, while any single implementation is locked to the priorities of one company.
UCP's Tech Council now contains the five companies most likely to define the agentic commerce surface for the next decade: Google (search and Gemini), Microsoft (Copilot), Meta (social), Amazon (marketplace), and Stripe (payments and ACP itself). Add the founding members, Shopify, Etsy, Target, and Wayfair, and the council represents the operators of nearly every commercial AI surface a Western consumer is likely to interact with.
A protocol governed by this group is unlikely to be displaced. It may evolve, fork, or absorb features from competing specifications. But the governance position is now durable.
ACP retains its specification and its OpenAI distribution channel. ACP-style checkout patterns may be folded into UCP at the spec level over time. The protocols will likely interoperate at every layer where it matters.
What Merchants Should Do
The contrarian read of April 24 is that merchants should not pick a protocol. They should prepare the data and identity surfaces that any agent, on any protocol, will need to read.
Three audits make this practical.
Product Data Liquidity
The first thing to verify is that product data is structured for programmatic agent access. UCP, ACP, and MCP all read against the same underlying merchant data layer: structured product feeds, schema markup, attribute completeness, pricing freshness, and stock availability. A merchant whose product data is incomplete or stale will be invisible to every protocol simultaneously.
This is the layer where preparation compounds. A clean product feed serves UCP onboarding via Google Merchant Center, ACP integration via Stripe's checkout endpoints, and any future protocol entrant. A broken product feed fails them all.
Identity Linking Readiness
UCP's Identity Linking capability is the mechanism by which a customer's agent can authenticate against a merchant's account system without exposing credentials. Merchants whose customer identity is fragmented across legacy systems will struggle with this transition regardless of which protocol dominates.
The audit question: can a customer's existing account on the merchant's storefront be linked to an agent identity through a standardised flow, with consent and revocation properly scoped? If the answer requires a new auth system, that work should start now.
Schema and Structured Data Coverage
LLM-mediated discovery sits upstream of the checkout protocol. Before any agent transacts via UCP or ACP, it discovers the merchant via search, recommendation, or direct query. Discovery happens through structured data, content quality, and entity recognition. Merchants whose schema markup is incomplete or whose content lacks LLM-citation patterns will not be surfaced by the agents that subsequently want to transact.
This is the AEO layer that AI Velocity has covered extensively. The Tech Council expansion does not change this priority. It increases its urgency, because more agentic surfaces will draw from the same upstream discovery layer.
The Real Battle Is the Discovery Surface
The protocol-war framing collapses on closer examination. The actual competitive surface in agentic commerce is which AI environment owns the discovery moment.
Gemini and Google AI Mode use UCP. ChatGPT uses ACP. Copilot ships through Microsoft's distribution and now sits on the UCP Tech Council. Claude is currently neutral, MCP-native, and protocol-agnostic.
Merchants need to be present, readable, and transactable on all of these surfaces. The governance question of which protocol wins is downstream of the more pressing question: is the merchant agent-ready at the data layer, regardless of which AI surface the customer is using?
Operators who treat this as a protocol bet will spend the next year picking the wrong abstraction to optimise. Operators who treat it as a data and identity readiness problem will be present on every surface as the protocols continue to converge.
What April 24 Actually Means
The expansion of the UCP Tech Council is a governance event, not a market event. No protocols were retired. No products were launched. No transaction volumes shifted overnight.
What changed is the address at which agentic commerce standards are now negotiated. As of April 24, 2026, that address is the UCP Tech Council, populated by the operators of nearly every consumer-facing AI surface in the Western market.
The protocol war is not over. The governance layer is settled. For merchants, the practical implication is the same in either reading. The agent-readability of product data, identity, and structured content is the durable investment. The protocol that finally executes the checkout will be whichever one the customer's agent is built on.
