AI NewsGo-to-marketReported

Visa, Mastercard, PayPal and Stripe published agentic commerce documentation with no live merchants named, and Google is the only one that names any

Slobodan Manic read every published agentic commerce document from Visa, Mastercard, PayPal, Stripe and Google and reports that Google is the only one that names live merchants, that only Stripe publishes a version number, and that not one of the five states who is liable when an agent gets a purchase wrong.

Editorial2 min read

LinkedInX

Why it mattersAnyone quoted on an agentic checkout project this year is being asked to build against protocols the vendors themselves cannot show working, so the honest state of each protocol is the input a design has to start from rather than the marketing page.

Slobodan Manic, a machine-first architect at No Hacks, read every published agentic commerce document from Visa, Mastercard, PayPal, Stripe and Google, and reports at Search Engine Journal that only Google is running the checkout with named live merchants. The piece is a status audit rather than a think piece, and the specifics are worth carrying into any project on this.

What each provider says on its own page

Visa runs two products, the Trusted Agent Protocol and Intelligent Commerce. Neither page names a live merchant, neither publishes a version number, both are declared "in the process of development." Mastercard's Agent Pay names no live merchants and publishes no version. PayPal names no live merchants and publishes no version. Stripe publishes a version, 2026-04-22.preview, lists 34 countries, and names no live merchants. Google's Agentic Checkout names Wayfair, Chewy and Quince, plus a set of Shopify merchants running it, and is live on Search and AI Mode.

What none of the five will say

Manic reports that none of the five documents state who is liable when an agent buys the wrong thing. That is the question a payment protocol exists to answer, and no vendor has yet answered it in writing. Shopify's Universal Commerce Protocol 2026-08-25 states that "no existing integrations" changes are required, meaning merchants are enrolled by default without opting in. So the storefronts already inside are inside because Shopify added them, not because they added themselves.

The mechanisms that are on the page

Three payment mechanisms appear across the documents: Stripe Shared Payment Tokens, which are merchant-scoped, amount-capped and expiring; Google AP2, which uses signed mandates; and x402, which returns an HTTP 402 with a payment header. Google's own guidance for agents currently requires human confirmation on each transaction, quoted in the piece as "Always ask permission first ... only buy after confirmation of purchase and shipping." Manic's four asks of every provider are: publish a version, declare a status plainly, name at least one live merchant, and state who owes when the agent gets it wrong.

Why it matters right now

Every earlier reading of the agentic commerce landscape has come from a vendor blog claiming imminent readiness. This one is the first published survey of what each vendor is actually shipping and what each is still refusing to say. It changes the honest starting point for any project meant to sell to an agent this year: two of the five payment networks name a mechanism and nothing else, one names 34 countries and no merchant, one names three merchants, and none of them cover liability. A team quoted to build against Visa or Mastercard is being asked to design against something the vendor itself cannot demonstrate working. The two useful moves are naming the missing pieces in the scoping document, so a decision to proceed carries the risk on the page, and building the agent flow first against Google's live Shopify path, because that is the only one you can point at.

Source

Search Engine Journal, Agentic Commerce Is Not The Next Voice Shopping, But It Is Still Unproven, by Slobodan Manic, published 21 September 2026.

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX