E-commerce
August 19, 2026
This page aligns fourteen cards under a single phrase: fill in address and payment, confirm the purchase on behalf of the user. This is not a ranking. This is not fourteen payment providers. Most of the cards say "checkout assistance". Only four say "automatic purchase": Gemini, VendeeX, Perplexity Buy with Pro, Amazon Buy for Me. A Honey coupon, a Klarna installment payment, a Chrome extension, and a Google rail do not do the same job there. No gross merchandise volume (GMV), no 3-D Secure rates, no accurate order rates. This article isn't either. It classifies mechanisms, not logos.
Google launched the Universal Commerce Protocol (UCP) on January 11, 2026 for a checkout flow on eligible US merchant listings in AI Mode and the Gemini app, Google Pay / Wallet, with the retailer remaining the merchant of record for the transaction. This is the named rail behind Gemini's automatic purchase badge, not proof that the other thirteen are talking about UCP. Stripe documents the Agentic Commerce Protocol (ACP) as an open standard created with OpenAI and Meta: how an agent creates a checkout session, manages a cart, passes a payment token, delegates authentication, and receives webhooks. This is the named rail behind ChatGPT. The card, however, labels ChatGPT "checkout assistance" and points to operator.chatgpt.com. Two different jobs. One logo. Lumping all fourteen into an "agentic checkout" indicator is budgeting for a mandate you don't have, or a coupon you already do.
If the idea of a software buyer is new: what agentic commerce is. The 2026 timeline: what has been delivered. The four filters: buying agents by task. The official totals remain human buying journeys: 2026 e-commerce statistics.
Summary
Three contracts, fourteen logos
Three contracts under the checkout badge. They are not configured in the same place. They do not break in the same way.
Contract | Examples in the list | Where it breaks for you |
|---|---|---|
Click on your checkout | Operator, Claude, Comet, Honey, Karma, Genspark | Theme, web application firewall, JavaScript, 3-D Secure. The human is still there, or just nearby |
Named rail (mandate) | Gemini via UCP. ChatGPT via ACP if you are integrated | Flows, eligibility, session, token, webhooks. Not your Pay button |
Other contract tied to the word | Klarna (payment schedule), Shop (Shopify checkout), VendeeX, Amazon Buy for Me, Copilot | Marketplace, installment payment, identity, or a second business line (Copilot Checkout in the US) that the badge does not mention |
Grouping what relates to a checkout makes sense. A buyer getting "help to pay" lumps it all together. Reading fourteen agents as fourteen ways to process a mandate, no. Honey applies a code. Klarna splits a payment. Shop is the Shopify consumer channel. Operator pilots a browser. This is not a ranking. It is an editorial collection.
The Instacart, DoorDash, Amazon, Walmart, Madewell, Target badges are directory examples. These are not sourced partnerships here. We do not recycle them as facts. Neither is "over 30,000 sites" for Honey.
A merchant who "chooses a checkout agent" like a payment provider has read the headline, not the cards. You do not install this page. You run a checkout, an entry point, sometimes a rail. The agents come next, or they don't.
The other directory categories remain use cases, not checkouts: product search, price comparison, bargain hunting. An agent can wear all four labels and only have a single checkout.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
Helping is not cashing in
The directory itself separates two verbs. Read them before the logos.
Checkout assist (assists checkout): Operator, Klarna, Copilot, Comet, ChatGPT, Honey, Karma, Shop, Claude, Genspark. The agent helps. Confirmation often remains human, or payment is an installment plan, a coupon, or a checkout process that is already yours.
Auto-purchase (auto-purchase): Gemini, VendeeX, Perplexity Buy with Pro, Amazon Buy for Me. The label says: the agent checks out. This is not a specification. This is not a volume. It is the strongest verb in the grid, and most often misread.
"In the user's place," in the introductory sentence, sounds like a mandate. "Checkout assist," on ten cards, sounds like a copilot. Both texts are on the same page. The first describes a buyer's ambition. The second describes, more honestly, most products. Do not budget for the first by reading the second.
ChatGPT is in checkout assist, not in auto-purchase. This is consistent with an integration into the ACP that is not automatic: implementing the specification, says the ACP ecosystem elsewhere, does not register you everywhere. The card pointing to Operator still mixes the browser and the rail. Read the product sheet, not just the filter.
Copilot is in checkout assist. Microsoft also documents a Copilot Checkout in chat, United States, English, US dollars. The badge on this page does not state this eligibility. Detail: Copilot Shopping. Here, remember: helping does not equal "already checked out in the chat for everyone."
Vocabulary (mandate, merchant of record, session): agentic commerce glossary. Here, the merchant of record is you as soon as the payment provider that sees the transaction is yours, or as soon as Google or Stripe say so for their rail. Ask the acquirer. Do not take a directory badge for legal advice.
Two public rails: Gemini via the UCP and ChatGPT via the ACP
Two platforms on the list have a public rail named in 2026. This is not "they have conquered the checkout tunnel." It is "we can read a specification."
Gemini and AI Mode: Google describes a checkout tunnel soon to be available on eligible US listings, methods already in Wallet, PayPal announced, global expansion later. The merchant remains the seller of record for the transaction. Integration customization is possible, says the post. This is publisher speak. It is also the only text, among our two sources, that places a purchase within the Google chat while the buyer is still searching.
ChatGPT via ACP: Stripe sets out five building blocks, the first of which is called agentic checkout. Sessions, logistics options, payment. Delegated payment passes a token, not a clear card number. Orders and webhooks for confirmation, shipping, refund. OpenAI is cited among the creators, and as the first agent platform in this ecosystem. Meta too. Do not merge "ChatGPT" and "Meta tunnel" just because both terms fit in the same paragraph. Each AI platform manages its own integration.
Areas where the rails diverge: how the protocols differ. UCP wants a language for the entire journey (discovery, purchase, post-purchase). ACP is focused on delegated purchasing. Neither is a protocol for Honey to enter a code. The platform framework (catalog, bots, delegated payment): what platforms must change.
The directory's Gemini card says "Buy for me agentic checkout." Amazon Buy for Me is another product, within the Shopping app, an agent on your site after an Amazon checkout page. Two similar names. Two contracts. Two stacks. Do not merge them in a slide.
Perplexity Buy with Pro features automatic purchasing and a "one-tap agentic checkout" phrase for Pro subscribers. We do not have a cited Perplexity specification here. Treat it as a directory listing, not a third public rail.
The most populated category: your product sheet, your firewall
The most populated category is still your product page. A browser agent or an extension sees roughly what a human sees, or what a headless browser manages to extract. It triggers anti-bot defenses. It misses JavaScript. It does not have its own map. This is exactly the path described for platforms, checkout funnel version.
Claude (Chrome extension) and Comet assist, compare, and then often stop for human confirmation. Operator, on its own page, pauses at sensitive steps. Honey and Karma inject a code into your form. Genspark promises an agentic flow for all merchants: card phrase, not an audit of your 3-D Secure.
In your logs, these customers look like scraper bots. New User-Agent, burst of traffic on the product page then /cart then /checkout, no mouse. Deciding who gets through is a policy, not an "agent-friendly" button sold by this page. How to read it: what needs to be logged.
A theme that assembles the Pay button in JavaScript loses the agent that does not run the script. A 3-D Secure that assumes a human is present at 3 a.m. loses the mandate, or the headless browser. A storefront that fits inside an in-app browser is still your tunnel: a Shopify storefront readable by a LLM.
Fixing the Merchant Center feed only helps Operator if it reads the feed. Often, it reads the page. Two requests. The phrase "checkout funnel" in an integrator's pitch. Ask if they are selling a theme, a web application firewall, or a rail.
Payment in installments, Shop, Amazon, Copilot: other agreements
Four cards on the list are neither a Chrome click, nor the UCP, nor the ACP. Pasting them to the keyword 'payment tunnel' makes sense for the buyer. For you, separate them from the very first line.
Klarna: a payment schedule. The directory also links search and prices to it. A split payment is not an LLM. It changes your way of paying, not your agent protocol.
Shop: Shopify cart and checkout, personalized discovery. Consumer channel, not the UCP. If you are already hosted on Shopify, part of the agent-side work is a channel in the admin interface, not a line to beat here.
VendeeX: identity, limits, returns, audit trail, auto-buy badge. This is spend governance. It is not a comparison tool, and it is not a UCP or ACP specification mentioned here.
Amazon Buy for Me: payment page in the Amazon app, then agent on your payment tunnel, distinct from Rufus. Amazon ecosystem, eligibility, not "all merchants" in the sense of open indexing.
Copilot, already mentioned, is the fifth common misunderstanding: the "checkout help" badge on this page is not Copilot Checkout eligibility. A pitch like "we put you in the Copilot tunnel" can sell a Bing feed, a Shopify button, or a chat-based purchase in the US. Three deliverables.
Honey in this category is also about bargain hunting. The code applies to the checkout, so the badge is true in the form filling sense. It is false in the mandate sense. Your margin, however, feels the difference: a code already planned is not an agentic order. It is cannibalization, sometimes.
Treating them as a single "payment tunnel 2026" stack inflates the slide and empties the contract. A payments owner for ACP is not the promo owner for Honey. An Amazon Shop Direct owner is not the web application firewall owner. The directory does not need your org chart. Your committee, however, does.
Where the payment takes place, and who the seller of the transaction is
The only finance question: where the payment takes place, and who is the merchant of record for the transaction. The badge does not say.
Mechanism | Where the buyer pays | What your payment provider sees |
|---|---|---|
Click theme or extension | Your checkout, often with a human confirming | A classic web order, sometimes a weird User-Agent |
UCP (Gemini, eligible US listings) | The Google surface, says the post | What your UCP integration sends. Not necessarily a site session |
ACP (ChatGPT, if integrated) | The agent session, delegated token | An ACP session plus webhooks. Not a last-click checkout |
Amazon Buy for Me | Consent in the Amazon app, execution on your site | Your checkout, run by an agent. Broken attribution |
Google repeats: merchants remain the merchant of record. Stripe, on the ACP side: the business remains the merchant of record in the ecosystem narrative. This is not an opinion of this site. This is the discourse of both texts. Chargebacks, 3-D Secure, Strong Customer Authentication (SCA): ask the acquirer how a mandate at 3 AM is coded. The reason codes do not say "the agent misread the size". The catalog of breakages: where agentic commerce still breaks down.
Your site's analytics pixel will not see a session of the UCP or ACP in the chat. You will have an order, a webhook, a channel line. If you judge the agent tunnel by the last site click, it disappears. Decide attribution before the button, not after the first internal disagreement.
An agent that succeeds on your product page and fails at payment is not "worse" than a Gemini via the UCP. It does not have the same contract. The first needs your theme to hold. The second needs your feed and your eligibility to hold. Fixing the wrong contract because this page put them under the same title is the trap.
What this page does not measure
This page does not measure anything that matters after "Pay".
Accuracy: an agent confirming at yesterday's feed price means an order at the wrong price. To honor or cancel: up to you.
3-D Secure / Strong Customer Authentication: designed for a present human. A headless browser or a nighttime mandate is not the original use case. No public rates here.
Two-door customer service: the buyer spoke to Gemini, Amazon, or Claude. The package leaves from your warehouse. Who answers the "where is my order" question?
Coverage: fourteen listings is not the market. It is what this site labeled as a checkout funnel on the date of the page.
Do not budget this list as a channel with a known cost-per-acquisition. We do not publish any. A Verified listing does not buy a spot in this filter.
The Operator listing labels Instacart and DoorDash. Useful as an example of grocery tasks. Insufficient as proof that your fashion funnel is in the same graph. Store labels are not an addressable market.
The "checkout-automation" label, on several cards, is a usage label. It is not a certificate. An "automatic purchase" is not an order volume. We do not recycle them as indicators.
Three actions, not fourteen cards
This week, by mechanism, not by logo.
Click / extension: product page and checkout funnel without mandatory JavaScript. Application firewall: what does a headless Chrome receive? A real promo code. A tested 3-D Secure.
UCP or ACP rail: flow parity. Eligibility (US Gemini, ChatGPT application, Shopify Agentic button if you are there). Postpone exclusive integration.
Marketplaces and buy now pay later: Amazon or Shop feeds if you sell there. Klarna is a payment method, not an agent to "beat".
The single test: would this work still be useful if the fourteenth map disappeared tomorrow? A checkout funnel that holds up without JavaScript, yes. An exclusive Genspark connector, no.
Name the owners: security plus content delivery network (CDN) for the headless browser, payments for the mandate, promo for Honey, marketplace for Buy for Me. A single "AI tunnel owner" stops at the first silo.
If you only have one hour: pay for a test order in your own checkout funnel with a headless browser or an in-app browser. Note where it breaks. Open the Agentic or Merchant Center admin interface and note what is already turned on. Read a rail sheet (Gemini or ChatGPT) and a click sheet (Claude or Honey). Two mechanisms. Not fourteen.
You do not turn on the payment tunnel agents
You don't turn on "payment tunnel agents" like a channel. Buyers open Gemini, Claude, Honey, the Amazon app. You maintain a payment tunnel and a policy. The cards on this page are not buttons.
If a seller promises to place you "in payment tunnel agents", ask: more readable theme, application firewall allowlist, integration with CAP, CUP or Merchant Center, Shopify button, Amazon feed, or directory listing. Seven deliverables. One word.
CUP and CAP are chosen late, and only if the mechanism is truly a mandate. For Honey, the protocol is already your tunnel. For Operator, it is your product sheet. Postponing the rail is not postponing the Pay button.
After confirmation, it is your dispute, your return, your 3-D Secure. The directory is no longer in the tunnel. Do not attribute a chargeback to it that it did not collect.
The product directory, if you want the grid by logo rather than by task: AI shopping agents.
An index of mechanisms, not a prize list
The checkout funnel is fragmenting. Google has not "replaced" Honey. SPC has not "replaced" 3-D Secure. This page is an index of mechanisms poorly labeled under a single word. The only card you really hold: your checkout funnel, your entry point, your data.
Treat it as a starting point: which mechanism is already hitting (coupon, headless browser, marketplace, LLM surface), where the payment takes place, which field or script breaks. Three questions. Not a checkout funnel leaderboard.
You can ignore UCP and still survive Claude. You can refuse SPC and still collect Klarna. You can be outside Amazon Buy for Me and sell via Rufus. The directory does not decide. Your eligibility and your theme, however, do.
Next, open two files, not fourteen. A named rail (Gemini or ChatGPT). A click on your checkout funnel (Claude, Comet, Honey). Ask each time: assist or collect? At your place or in the chat? What artifact do you control?
Frequently Asked Questions
What is the best checkout agent in 2026?
This page doesn't say. No public volume, accuracy, or dispute data says so either. Fourteen cards, three contracts. A ranking would be a fabrication.
Is checkout assistance the same as an automatic purchase?
No. The directory separates them. Assistance: the agent helps, the human or an existing payment method often finishes. Automatic purchase: the label says the agent processes the payment. The UCP and ACP are the two public texts describing a delegated purchase. The rest reads like a product sheet.
Do ChatGPT and Gemini form the same checkout?
No. Stripe documents ACP, with OpenAI as the first agent platform. Google documents UCP for AI Mode and Gemini, the merchant of record for the transaction, US first. Two rails. Two integrations. The ChatGPT card on this page says checkout assistance, not automatic purchase.
Are Honey or Klarna agentic commerce?
In this list, they touch the checkout, hence the badge. A coupon and a split payment are not an AP2 mandate nor a UCP checkout. Keep them separate in the P&L.
Should you allow all browser agents at the application firewall?
No by default, and yes if you don't have a policy. Blocking any headless browser stops Operator and a portion of Claude. Letting everything through opens up scraping. Whitelist or signature, not a button in this filter.
What to do this week?
Test the checkout without JavaScript and in an in-app browser. Read the logs. Check eligibility for UCP or ACP, or the Shopify Agentic channel. Do not budget fourteen channels. Postpone the exclusive connector.
Is Amazon Buy for Me the same as UCP?
No. It's an Amazon product: in-app consent, agent on your site, separate from Rufus. The Gemini sheet uses "Buy for me" for the Google checkout. Two names. Do not merge them.
Sources
Enzo
August 19, 2026
