Agentic Checkout Checklist: 9 Fixes So an AI Agent Can Buy From You

Posted on Oct 21 • Originally published at zainvibes.com

Last week, Wix plugged an AI wallet into its small-business agents and PayPal put agent checkout on 60 million living-room screens. Your first thought was probably the same as mine: can an AI agent buy from my store yet, and do I need to build something for it? I spent days reading the protocols, the merchant pages, and the card-network rulebooks so you can skip the news cycle and get the checklist instead. Short version: the answer is yes, and the work is almost entirely on your own checkout - the part you already own.

Yes, an AI agent can buy from your store today - but almost certainly through your own checkout page, not inside ChatGPT or Google AI Mode. The in-chat checkouts are gated to approved platforms, mostly US-only, and exclude subscriptions and digital goods. The agents that reach a normal store - Meta's Muse, Amazon's Buy for Me, OpenAI's dots, Gemini's Task agent - browse your product pages and finish payment on your site, through your existing payment provider. So the useful question is not "which protocol do I adopt" but "can an agent actually finish my checkout." Nine fixes decide that, and most of them are configuration, not code.

Before the checklist, you need the mental model, because "an AI agent buys from you" covers three different things. This framing comes from Okane Land's October 2026 review of the assistants' merchant pages and terms, and it is the clearest cut I have seen:

If you sell physical or digital goods on your own site, you mostly live in path two. If you sell API access, path three deserves its own post. Path one is the one getting all the headlines, so let me deflate it honestly before we get to work.

Here is the part the announcements skip. I have read the current merchant terms so you can see how narrow path one really is for an independent seller:

Three honest observations from that table. First, if you are not on Shopify, Etsy, BigCommerce, Wix, or Shopware, path one is not open to you today - and implementing ACP yourself does not fix that, because the protocol's own site says each AI platform manages its own merchant onboarding. Second, everything in path one sells to US buyers; if your customers are in Pakistan, Europe, or anywhere else, path two is your only path. Third, subscriptions and digital goods are excluded across the board in path one, while path two has no such restriction - an agent can buy your course or your SaaS plan on your own checkout exactly like a human can.

AI-assisted buying is growing from a tiny base. A Frankfurt School study of 973 online shops found chatbot referrals under 0.2% of traffic. Ethercycle counted 0.10% of sessions and 0.12% of revenue from AI assistants across ten established Shopify stores in 2026 - about $131,000 out of $109.6 million. Shoppers are cautious too: about 14% of Americans trust AI to place orders (YouGov), 11% have used AI to complete a transaction, and seven in ten want the final say first (NMI). Fix your checkout because it is cheap and durable, not because a tidal wave is arriving tomorrow.

This is the section that changes the math on how much to invest. No card network has moved the risk of agent purchases onto the agent. Visa's rulebook (April 2026 edition, with agent rules added in October 2025) treats the registered provider of an agent payment as the cardholder and holds the cardholder responsible for the agent's actions as if they had made the purchase themselves - and it forbids you from requiring a buyer to waive dispute rights, agent purchases included.

Mastercard's merchant guide says standard fraud detection, chargeback rights, and dispute processes apply to agent purchases. Stripe's seller terms make you the merchant of record, responsible for disputes, refunds, and transaction fraud. Worldpay's one-line summary is the one I would tattoo on the project plan: no liability shift exists yet.

The unsettled case is the purchase that was authorized but wrong - the agent bought what the shopper did not mean. Two companies have started on it from the other side: Stripe's terms for agent operators make them answerable to Stripe for purchases caused by bugs, hallucinations, or misinterpretations, and American Express has announced a future protection for cardholders whose purchase strays from approved intent. Neither changes what you face when the chargeback arrives. So: keep your dispute evidence habits exactly as they are, and do not assume an agent's mistake is the agent's bill.

These are the fixes that decide whether an agent completes a purchase on your site. Do them in order; each one removes a failure mode I keep seeing in the agent-buying reports.

An agent cannot log into a user account it does not have, and it cannot create one reliably mid-purchase. If your checkout forces account creation before payment, you have built a wall that stops agents and annoys humans equally. Keep account creation after payment - optional, on the confirmation page, never in the critical path.

Browser-driven agents finish fastest with saved wallets. Stripe's Link is the one with documented agent support - Meta's Muse pays instantly at the million-plus businesses that accept it, using the shopper's saved payment method - and Google Pay covers the Google-side agents. If you already take Stripe, Link is usually a toggle, not a project.

If your only options are manual card entry plus a local bank transfer, an agent will stall at the payment form exactly where a distracted human would abandon the cart. This one is counterintuitive and it is the fix most stores miss. Your Cloudflare bot-fight mode, your WAF rules, your CAPTCHA on the checkout page - they do not know the difference between a scraper and a signed shopping agent, and they will block both.

The networks have built the plumbing for exactly this: Mastercard's Agent Pay builds on Web Bot Auth, Visa's Trusted Agent Protocol aligns with it, and Cloudflare has counted signed agents as verified bots since July 1 - with one warning worth reading twice, that you may trust the intermediary operator but not every end user driving it. The practical job: check your host or CDN's bot settings and let verified agents through to the checkout, instead of discovering the block in your failed-orders log. Letting agents through does not mean letting them run wild.

An agent that retries a failing checkout can hammer your endpoints in a loop a human never would. Put per-IP and per-session rate limits on cart and checkout endpoints, and cap the retry behavior on your payment intents. This is standard hardening, but agents make it load-bearing: the first wave of agent traffic you see will include the buggy kind.

Once an agent can finish your checkout, the next question is whether it can find your products - and what you do when something goes wrong.

A checklist that only says "do" is a sales pitch. Here is the honest "don't" list, because most of the agentic-commerce noise wants your money or your weekends:

{/* MONETIZATION NOTE (not rendered): links below are official product pages, NOT affiliate links yet. Swap for affiliate links once approved into a program; never label these as affiliate links until the swap is real. For this topic the primary money path is freelance agentic-commerce integration leads via the /#contact CTA below, plus display ads on the traffic. */}

If this were my store, I would ignore every waitlist and spend one afternoon on path two. Guest checkout on, Link and Google Pay enabled, schema.org markup validated, product feed accurate, robots.txt reviewed, bot rules tuned to let signed agents through, dispute logging confirmed, and then one real agent purchase with my own card to find the snags. That is a day's work, most of it configuration, and it covers every agent that can reach a normal website today - which is nearly all of them.

The condition that flips my answer: the day a channel you actually want - a marketplace, an assistant with your buyers in it - opens merchant onboarding with real volume behind it, join it that week. Until then, the in-chat checkout story is somebody else's platform war, and your checkout page is the territory you already control. An agent that can finish your checkout is worth more than a protocol badge on a waitlist page. Fix the finish line first.

Yes, in most cases - but through your own checkout, not through a chat window. Assistants like Meta's Muse, Amazon's Buy for Me, OpenAI's dots, and Gemini's Task agent buy on merchants' own sites, paying through your existing payment provider. In-chat checkouts inside ChatGPT, Google AI Mode, and Perplexity are gated to approved platforms and US buyers.

ACP is the open standard co-developed by OpenAI and Stripe (open source, Apache 2.0) that lets an AI agent talk to a merchant's backend: create a checkout session, update it, and complete the purchase with a delegated payment token. It can be implemented as a REST interface or as an MCP server. Implementing it does not list your products anywhere - each AI platform manages its own merchant onboarding.

UCP is Google's and Shopify's answer to the same problem: an open standard covering catalog search, cart, checkout, identity linking, and order tracking, designed so platforms, agents, and businesses interoperate through one protocol. Stripe joined its governing council in April 2026. Google's AI Mode and Gemini checkouts run on it for approved Merchant Center sellers.

Probably not. Nothing in the agent-on-your-site path requires a protocol from you: what decides whether an agent finishes the purchase is your existing checkout. Allow guest checkout, accept a wallet agents use (Stripe Link, Google Pay), keep prices and availability as plain structured data, and make sure your bot protection lets verified agents through.

You do. Visa's rulebook treats the registered agent provider as the cardholder and holds the cardholder responsible for the agent's actions; it forbids merchants from requiring buyers to waive dispute rights. Stripe's seller terms keep disputes, refunds, and transaction fraud with the seller. Worldpay's summary: no liability shift exists yet.

Not through the in-chat checkouts - ChatGPT's rules allow physical goods only, Google excludes subscriptions and most digital goods, and Shopify excludes subscriptions from Copilot and Google AI Mode checkouts. The agent-on-your-site path has no such restriction: an agent can buy a subscription on your own checkout page exactly like a human can.

The three-paths framing, the in-chat program statuses, the agent behaviors (Buy for Me, Muse, dots, Gemini Task agent, Chrome auto browse), the subscription exclusions, the liability rules, and all traffic and survey figures come from Okane Land's researched review "Can an AI agent buy from you yet?" (published October 14, 2026, read October 21), which quotes the programs' own pages, the protocol docs, and the card networks' rulebooks. The Wix Symphony plus Link wallet announcement is from Wix's GlobeNewswire release of October 15, 2026; the PayPal plus Glance integration is from their October 15, 2026 press release as reported by PYMNTS. The three-gate structure of the checklist (finishable checkout, discoverability, dispute protection) is my own synthesis.

Nothing here is based on a test purchase I ran - item 9 of the checklist is the test I recommend you run yourself.

Want this done on your store instead of reading about it? I build checkout and commerce integrations for a living - tell me about your store and I will tell you honestly whether you need an afternoon of configuration or something bigger.

If AI-driven discovery is the part that interests you, start with how to get cited by ChatGPT and Perplexity and my GEO tools comparison - being found is the gate before being bought.