The Agent-Checkout Protocols Are Converging (ACP, AP2, Instant Checkout). The Experience Layer Is Still the Open Question.

Within a few months, two major platform camps have laid out how a purchase made by an AI agent is supposed to work technically. OpenAI and Stripe introduced the Agentic Commerce Protocol (ACP), the standard behind "Buy it in ChatGPT" and Instant Checkout. Google published the Agent Payments Protocol (AP2) in parallel, live as version 0.2 under FIDO Alliance governance since April 28, 2026. Both address the same problem: how does an agent authorize, pay for, and confirm a purchase without a human filling in the form?

That is real progress, and to many merchants it looks like the one big question the agentic commerce era had left open. It is not. The protocols converge on the part that can be standardized: the transaction. The part that cannot be standardized stays untouched, and that is exactly the part that decides brand, margin, and conversion. What the agent *shows and says* to the shopper still belongs to the merchant.

What ACP, AP2, and Instant Checkout actually standardize

It is worth being precise about what is happening here. The protocols govern the mechanics of an agentic purchase transaction, not the buying experience.

• ACP (OpenAI + Stripe) defines how an agent creates an order, hands over payment details, and receives a confirmation. "Buy it in ChatGPT" is the first visible application. Etsy is live, and roughly one million Shopify merchants were announced as the next wave. The specification is open source and in beta.
• AP2 (Google, FIDO Alliance) defines the payment and authorization layer for agents across vendors. The focus is on verifiable intent, mandates, and the question of who is liable for an agent purchase.

What matters is what does not appear in that list. No protocol standardizes which three products the agent recommends from your catalog. None specifies how a size chart, a sustainability note, or a bundle recommendation is presented. None decides whether the agent offers an alternative when an item is out of stock or simply gives up. And none owns your product data, your content structure, or your brand tone.

ACP and AP2 are payment and fulfilment rails. To the merchant they are what a payment interface has always been: necessary infrastructure that closes the sale, but not the reason someone buys from you and not a competitor.

The layer no one standardizes

Between a shopper's request and the transaction sits a layer that resists standardization, because it differs per merchant. We call it the experience layer: everything the agent shows, phrases, recommends, and justifies on behalf of your store.

This layer answers questions no protocol can answer:

• Selection. Which products does the agent pull from a catalog of 50,000 items when someone asks for a "lightweight rain running jacket"?
• Presentation. How are price, availability, variants, and return terms structured so an agent reads them correctly and repeats them correctly?
• Justification. What does the agent say about your product? Does it cite your wording, or invent its own that contradicts your brand?
• Fallback logic. What happens on out of stock, on cross-border restrictions, on age-verified products?

These are not payment questions. They are frontend and content questions. And they do not get smaller once checkout is standardized. They get larger, because the agent is now an additional channel where your brand appears without your direct control, unless you actively design this layer.

Why the experience layer stays with the merchant

There is a structural reason it stays that way. A protocol is by definition a lowest common denominator. It only works if everyone involved shares the same mechanics. That is precisely why a protocol can govern the transaction but never the differentiation, because differentiation is the opposite of a common denominator.

For the merchant this means: you can delegate payment and fulfilment to ACP or AP2. You cannot delegate the answer to "why this product, why here, in which wording" without giving up control of your brand in the agentic channel. This layer is not a rendering detail. It is the part of the storefront that carries your selection logic, your content rules, and your guardrails.

This matches a pattern we have seen in earlier platform shifts. When payment providers unified checkout, the difference between merchants did not disappear. It moved forward, into assortment, presentation, and content. The same thing happens with agentic purchases. The experience layer does not vanish. It shifts, from the page a human looks at to the structure an agent reads.

What this means for storefront architecture

When the agent becomes the buyer, the storefront has to be agent-ready. That is not a marketing formula but a concrete architectural requirement:

1. Structured data as a requirement, not an SEO extra. An agent reads Schema.org, not your CSS. Product, price, availability, and variant data must be machine-readable and unambiguous, otherwise the agent guesses, and guessing costs you margin and reputation. We covered how to make content citable for agents in Content Citation Readiness.
2. One data model across all backends. If your product data lives in Shopify, your prices in an ERP, and your availability in a separate system, the agent still has to see a single, consistent truth. A normalized frontend data layer over the backends solves exactly this.
3. Guardrails at the component level. An agent that selects and phrases on its own needs limits: which products it may recommend, which claims it may make, when it must stop. Those rules belong in the frontend layer, not in a prompt. We laid out the schema-driven approach in Agentic Frontend Guardrails.
4. The same component library for human and agent. The selection and presentation logic that serves your human shopper is the same one that feeds the agent. Maintaining two separate systems, one for the website and one for the agent, is expensive and drifts apart.

This is exactly where an Agentic Frontend Management Platform comes in. It cleanly separates the payment rails you connect to ACP or AP2 from the experience layer you keep. The composable headless frontend layer sits on top of your existing commerce stack, normalizes the data from all backends, and serves the structured, guardrail-protected content an agent can read correctly, tuned for machine-readable citation through SEO and GEO. You swap the payment mechanics without losing control of the presentation.

Bottom line

The convergence of ACP, AP2, and Instant Checkout is good news: the transaction mechanics of agentic purchases become a commodity, and no one has to build a commodity themselves. But that is also the limit of standardization. Selection, presentation, and justification, meaning everything that makes up your brand in the agentic channel, is something no protocol will handle for you.

The practical takeaway is unglamorous. Connect the payment protocols as soon as they are ready for your market. Invest in parallel in the layer no one standardizes for you: structured data, a unified frontend data model, and guardrails that define at the component level what the agent is allowed to show. The experience layer does not vanish. It stays in your hands, if you keep it there.