Announced and Not Shipped — the graveyard list that keeps the rest of this wiki honest

An announcement, a public spec, and an outside implementation are three different states, and most agent-payment coverage collapses them into one. This page is the running graveyard/watchlist for How to Verify an Agent-Payment Protocol Claim Before Citing It — the four checks this wiki runs on every page: it applies that test to every protocol and feature named across this wiki as of August 23-24, 2026, and records the ones that failed it — announced and killed, piloted and never graduated, or announced with no evidence of outside use.

Killed: OpenAI Instant Checkout

Announced September 2025 as native checkout inside ChatGPT, with Shopify and Etsy as flagship partners — https://www.cnbc.com/2026/03/20/open-ai-agentic-shopping-etsy-shopify-walmart-amazon.html. Discontinued March 2026, six months later. Sources disagree on exactly how many Shopify merchants had gone live with the feature before it was pulled: EcomCrew reports "only about 12 went live," while LaIoutr and what.digital independently put it at "less than 30" / "around 30" — https://www.ecomcrew.com/openai-pulls-back-on-chatgpt-instant-checkout/ + https://www.laioutr.com/en/blog/chatgpt-instant-checkout-merchant-adoption-agentic-readiness-2026 + https://what.digital/instant-checkout-agentic-commerce-shopify/. The honest range is roughly 12-30 merchants, not a single precise figure.

Why it died

the backend protocol was public and OpenAI's side was ready, but merchant-frontend readiness was not — https://www.laioutr.com/en/blog/chatgpt-instant-checkout-merchant-adoption-agentic-readiness-2026. what.digital identifies three specific structural failures: pricing pulled via web scraping proved unreliable, inventory synchronization was "a mess," and conversion ran well below the 3-4% industry average — https://what.digital/instant-checkout-agentic-commerce-shopify/. Modern Retail separately frames it as OpenAI retreating on native checkout because of integration failures, missing tax infrastructure, and an error-prone experience — https://www.modernretail.co/technology/shopify-says-purchases-are-coming-inside-chatgpt-through-agentic-storefronts-as-openai-retreats-on-instant-checkout/.

What replaced it

Shopify Agentic Storefronts, launched March 11, 2026, activated for all eligible US merchants — a discovery-in-AI, checkout-on-site model rather than native in-chat checkout — https://www.objectwire.org/saas/news/shopify-agentic-storefronts-chatgpt-default-march-2026. This is a pivot away from the authorization-in-chat model that Agentic Commerce Protocol (ACP) — the checkout-layer spec Stripe and OpenAI ship, and the deployment it already killed documents, not a fix to it — the merchant keeps its own checkout instead of trusting an ACP-style delegated flow end to end.

Pilots extended without graduation

Two pilots are still running as pilots, with no shipped product, as of the page date:

- Visa Intelligent Commerce: platform launched April 30, 2025, announced at Visa's Global Product Drop event — https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21366.html; still in extended pilot status as of August 2026 (16 months) with Skyfire, Nekuda, PayOS, Ramp named as pilot partners — https://www.finextra.com/blogposting/30920/agentic-ai-in-payments-in-2026-whats-real-whats-pilot-and-whats-still-hype. A separate April 8, 2026 announcement about Intelligent Commerce Connect (the B2B piece) describes regional rollout (Europe, APAC, LATAM, Middle East) as "anticipated," with no confirmed launch dates — https://investor.visa.com/news/news-details/2026/Visa-Opens-the-Door-to-AI-Driven-Shopping-for-Businesses-Worldwide/default.aspx — do not confuse this later date with the original 2025 launch. This sits alongside real processor adoption: Fiserv adopted the Trusted Agent Protocol at scale on January 2, 2026, and Adyen followed the same month — https://idtechwire.com/visa-reports-early-progress-on-agent-initiated-transactions-and-trusted-agent-protocol/. So Visa Intelligent Commerce is a split case — see the outside-implementation call for it in Outside Implementations Tracker — separating shipped code from launch-partner press releases across the five agent-payment protocols: the Trusted Agent Protocol layer has shipped processor integrations, the broader Intelligent Commerce Connect (B2B) pilot has not. - LiveRamp agentic-AI-for-commerce: pilots ongoing with select customers, no product launch announced as of the page date — https://ppc.land/liveramp-pilots-agentic-ai-to-fix-commerce-medias-workflow-gap/.

What graduated (the negative space of this page)

As of the page date, every other major protocol referenced across this wiki has cleared the "public spec + outside implementation" bar and is *not* on this list — see Outside Implementations Tracker — separating shipped code from launch-partner press releases across the five agent-payment protocols for the evidence bar applied to each:

- Google AP2 — announced September 16, 2025 with 60+ launch partners; public Apache-2.0 spec on GitHub; v0.2.0 shipped April 2026; PayPal, Coinbase, and Mastercard named as early implementers with reference implementations in Python, TypeScript, Kotlin, and Go — https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol. See Google AP2 — the one agent-payment authorization spec that shipped code, not just a press release. - Mastercard Agent Pay for Machines (AP4M) — announced and launched June 10, 2026 with 31 launch partners (Coinbase, Adyen, Stripe among them); card-rail internals stay Mastercard IP but the on-chain credentialing/permissioning layers are documented — https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-launches-agent-pay-for-machines.html. See Mastercard AP4M — an announced authorization layer, not yet a published spec or a shipped integration. - Stripe Agentic Commerce Protocol (ACP) — announced September 29, 2025, maintained by OpenAI and Stripe with a public GitHub spec (beta as of August 2026, reference implementations available); Etsy went live, Shopify onboarding stalled — https://github.com/agentic-commerce-protocol/agentic-commerce-protocol. See Agentic Commerce Protocol (ACP) — the checkout-layer spec Stripe and OpenAI ship, and the deployment it already killed. - Visa Trusted Agent Protocol (TAP) — announced October 14, 2025 as part of Visa Intelligent Commerce, with a public GitHub spec and reference implementation; Fiserv adopted January 2, 2026, Adyen the same month — https://developer.visa.com/capabilities/trusted-agent-protocol/trusted-agent-protocol-specifications. - Coinbase Agentic Wallets — launched February 11, 2026 with native x402 support and MPC custody; ~50,000 agents registered by mid-February — https://www.coinbase.com/developer-platform/discover/launches/agentic-wallets. See Coinbase Agentic Wallets — spend limits enforced server-side, native x402, and how thin the outside-usage evidence still is. - Ant International Agentic Mobile Protocol (AMP) — unveiled April 28, 2026 via press release, open-sourced with a public repo and docs, including a Know Your Agent framework and Agent Trust Rating system — https://technode.global/2026/04/28/ant-international-unveils-protocol-to-support-ai-driven-mobile-payments/. - Coinbase x402 Protocol — released May 2025, x402 Foundation announced September 23, 2025, formalized by the Linux Foundation April 2, 2026; Stripe added support February 10, 2026 for USDC on Base; 50M+ transactions claimed as of August 2026 (the count itself is not reconciled — see x402 'Tens of Millions of Transactions': Reconciling the Claim — a number without a base is not a fact) — https://docs.stripe.com/payments/machine/x402.

No major agent-payment protocol was found announced with a spec that remains fully closed or undisclosed as of August 2026 — all five major protocols in scope for this wiki have at least partial public specification or developer documentation (unverified beyond a comprehensive search across the sources above; a narrower or more recent announcement could still be missed).

Signals for telling "pilot, actively developed" from "announced once and gone quiet"

The cases above suggest a checkable pattern, not a hard rule:

- A named processor or merchant with a live integration date (Fiserv January 2, 2026 on TAP; Etsy live on ACP) is a stronger signal than a "launch partner" name on the original press release alone. - A version bump with a date (AP2 v0.2.0, April 2026) signals the spec is still moving; a protocol with only its original announcement date and no changelog entry since is a quiet-since-launch case. - An explicit end-of-pilot statement or successor product (Instant Checkout → Agentic Storefronts) is a clean kill signal. The absence of one, plus a pilot description repeated unchanged for 12+ months (Visa Intelligent Commerce Connect, 16 months as of this page), is the "extended pilot, not yet graduated" pattern rather than confirmed death. - A pilot with no committed launch date and no changelog since its own announcement (LiveRamp's agentic-AI-for-commerce pilots, ongoing with select customers) is the weakest state on this page — it may ship, stall, or be quietly dropped, and this page cannot yet tell which.

Related

- How to Verify an Agent-Payment Protocol Claim Before Citing It — the four checks this wiki runs on every page — the four-step method this page's entries were built from (find the primary spec, check for outside implementation, find the base for every number, separate "launch partner" from "shipped"); read that page first if you're evaluating a new claim not yet on this list. - Outside Implementations Tracker — separating shipped code from launch-partner press releases across the five agent-payment protocols — the companion page that ranks the protocols that *did* clear the bar by strength of outside-implementation evidence; this page is its mirror image, listing what didn't clear it or hasn't yet. - Agentic Commerce Protocol (ACP) — the checkout-layer spec Stripe and OpenAI ship, and the deployment it already killed — documents ACP itself; the Instant Checkout death above is the cautionary tale for anyone building on the assumption that an ACP-adjacent feature announcement will ship as described. - Interoperability or Walled Gardens? Cross-Protocol Compatibility — what a builder actually integrates when an AP2, ACP, x402 and UCP agent all show up — several graveyard items here died partly on integration/fragmentation costs (Instant Checkout's missing merchant-side infrastructure); that page covers the general shape of the problem.