UCP Tech Council Doubles to 10 as Amazon, Meta, Microsoft, Salesforce and Stripe Join Google's Agentic Commerce Standard

What the Five-in-One Move Signals

Amazon, Meta & Microsoft join UCP technical council

Amazon, Meta and Microsoft join Universal Commerce Protocol council as AI shopping standard draws major backing from retailers and payments groups.

ecommercenews.com.au

Amazon, Meta, Microsoft, Salesforce and Stripe have all joined the Technical Council of the Universal Commerce Protocol (UCP), the open-source standard Google unveiled at NRF 2026. With founding members Google, Shopify, Etsy, Target and Wayfair, the council has now doubled to 10 organisations, eCommerceNews Australia reported on April 27, 2026.

The story is not just who joined, but what layer they represent. The world's largest online retailer (Amazon), the dominant social discovery surface (Meta), the front-runner in productivity AI (Microsoft), the enterprise retail SaaS incumbent (Salesforce) and the de facto online payments standard (Stripe) are now seated together. Search, advertising, fulfilment, SaaS and payments are all represented. This is less an industry-association land grab than a sign that the contest to set the rules of agent-led shopping has entered a new phase.

What the UCP and Its Tech Council Actually Govern

UCP is a shared specification that lets AI agents interact with retailers across product search, basket building, checkout and post-purchase support. Google introduced it at NRF earlier in 2026, with Shopify, Etsy, Target and Wayfair as initial backers. The promise is straightforward: instead of every retailer building bespoke integrations with every AI platform, a single open standard should connect everyone to everyone.

The council's role is far from ceremonial. It reviews technical proposals, votes on changes to identity, payments, loyalty programmes, local inventory and returns, and manages the underlying codebase. The latest release merged more than 60 pull requests, the largest since launch, adding basket building, catalogue search and lookup, signed requests and responses, revised error handling, pre-checkout discounts and risk signals to help merchants assess fraud and abuse.

Published meeting notes show members already pushing into substance. Cross-session, cross-merchant identity for shoppers is on the table. Meta's representative submitted documentation changes covering card credentials and payment compliance. Microsoft's representative landed documentation fixes. The new entrants were contributing before their seats were even announced. And Microsoft has already made UCP feeds generally available in Merchant Centre, allowing businesses to surface products through Copilot. The standard is moving from spec discussion to live infrastructure.

What Each New Member Is After — Amazon Is the Big Piece

The five names arrived together, but their motivations are not interchangeable.

The most consequential addition is Amazon. As the largest online retailer in the world and an AWS commerce supplier, Amazon has historically preferred to keep its own walled garden rather than co-author external standards. Showing up on a Google-led council is therefore notable: the calculation appears to be that shaping a likely de facto standard from the inside is cheaper than catching up from outside. Greg Smith's seat puts Amazon in direct reach of how AI agents will eventually authenticate, pay and operate carts against Amazon catalogue and checkout flows.

Meta is protecting the discovery layer it owns through Instagram and Facebook. James Andersen's early documentation work on card credentials hints at aligning Meta Pay and Shop with the UCP payment model. Microsoft's seat is largely confirmation: it has already shipped UCP feed support in Merchant Centre and is now locking in its Copilot shopping path.

Salesforce, represented by Scot DeDeo, speaks for the large enterprise retailers running on Commerce Cloud and Agentforce, ensuring enterprise-grade identity, B2B and CRM concerns make it into the spec. Stripe's participation through Prasad Wangikar is the most strategically loaded. Stripe co-designed OpenAI's Agentic Commerce Protocol (ACP) and is now seated on the rival council too. Since payments are the highest-friction part of any agentic flow, Stripe's dual-protocol position is a useful tell: it is hedging on which payment model the market will accept.

How This Stacks Up Against OpenAI's ACP

The council expansion sharpens the rivalry with the other live agentic commerce standard, OpenAI's Agentic Commerce Protocol (ACP). ACP, co-designed by OpenAI and Stripe, powers ChatGPT's Instant Checkout and launched with Etsy, Walmart, Target and Sephora as initial integrators.

What complicates a clean rivalry is that Shopify and Etsy now sit on both councils. For them, the smart bet is not to back one standard but to remain compliant with whichever AI surface their customers actually use. That is the realistic outcome: a multi-protocol world rather than a winner-take-all standard. OpenAI itself moved in March 2026 to scale back Instant Checkout inside ChatGPT, sending purchases back to merchant apps and sites. BTIG analyst Marvin Fong argued that this reduces disintermediation risk for catalogue-style platforms like Etsy (we covered the analyst note in our BTIG analysis).

ACP was designed to absorb checkout into the AI surface itself. UCP, at least today, leans toward keeping merchant checkout intact while standardising discovery and basket building. After OpenAI's pivot, the two philosophies are closer than they looked six months ago. The remaining battlegrounds are identity, payments, loyalty and returns: whichever council produces shippable, real-world specs first will pull adoption toward it.

The council has already widened available seats to 16, signalling more entrants are expected — likely large EU/APAC retailers, Apple Pay/Google Pay-class wallet players, and loyalty platforms. OpenAI's side is layering Mastercard, Visa, Block and PayPal partnerships into ChatGPT shopping. Both camps are racing to internalise payments and identity.

The Market Stakes and the Cost of Being Outside

The UCP backers cite forecasts that agentic commerce could account for USD 190 billion to 385 billion of US eCommerce spending by 2030, or 10–20% of the market. Even on the conservative end, that is comparable in scale to today's social commerce, and large enough to make membership in the rule-setting body a strategic asset.

The simultaneous arrival of Amazon, Meta and Microsoft is best read through one lens: nobody wants to be locked out of a standard that gains broad adoption. If UCP becomes the default way AI agents talk to retailers, organisations outside the council are excluded from spec votes and forced to retrofit their products to decisions made elsewhere. It is cheaper to author a standard than to chase one, and that classical logic is driving Big Tech's behaviour here.

Vidhya Srinivasan, VP and GM of Ads and Commerce at Google, framed it this way: "The Universal Commerce Protocol is quickly paving the way for this new era of agentic commerce. We're proud to see the industry come together around this shared, open standard that will benefit businesses and consumers everywhere." Vanessa Lee, VP of Product at Shopify, was just as direct on the multi-protocol reality: "AI can enable so many new ways of shopping to flourish, but only if there's a clear standard between retailers, businesses and applications."

What Merchants Should Do Now

For merchants, the council expansion translates into three concrete moves.

First, plan for dual-track support across UCP and ACP. Betting on one standard is no longer rational. Audit which parts of your catalogue, payment stack and identity model can be reused across protocols. Shopify merchants in particular can absorb most UCP feed work as Shopify ships native support, but ACP behaviour is shaped by which PSP routes the transaction.

Second, fix structured product data before chasing protocol coverage. AI agents rank what they can read. Titles, attributes, inventory, price, fulfilment options, return policies and loyalty member pricing need to be machine-readable in production, not just on a roadmap. Microsoft's general availability of UCP feeds in Merchant Centre means feed quality now translates directly into Copilot shelf real estate.

Third, revisit PSP selection. Stripe is now embedded in both camps, while Adyen, Checkout.com and PayPal are racing to add agentic-commerce capabilities. For agent-initiated transactions, the question is no longer just rate; it is how the PSP handles tokenisation, 3DS, dispute routing and loyalty hand-off when the buyer is an autonomous agent on behalf of a verified shopper.

Closing Thoughts

The UCP Tech Council going from five to ten members is the moment agentic commerce standards stopped being a future-tense topic and became this quarter's planning input. With Amazon, Meta, Microsoft, Salesforce and Stripe alongside Google's founding cohort, UCP now has the implementation density to function as a real standard. OpenAI's ACP, after its Instant Checkout pivot, has converged toward a similar discovery-first posture, making coexistence more plausible than dominance for either side.

The pragmatic answer for merchants is not to pick a winner but to build a stack that can speak both protocols cleanly across catalogue, payments and identity. Standards are easier to influence before they harden. Operators who exercise their integrations during the testnet phase will set the pace once AI agents are routinely holding the consumer wallet.