Robert Hu
E-commerce Strategy

If Checkout Disappears, What Does the Retailer Still Own?

Robert Hu··6 min read
A checkout interface disappearing while the commerce system beneath it continues to execute

On an a16z podcast released August 17, Stripe's Will Gaybrick argued that checkout pages could disappear as agentic commerce develops.

Much of the coverage rendered that as checkout pages will go away. a16z's own description of the episode is more careful, saying they "could disappear," and Gaybrick's actual example is more interesting than either summary: "It's been very easy to get through a checkout page these days, but should you even need to go to one, or should you just be able to say buy it on a product display page? I think so."

Read that carefully. The buyer in his example is still on the merchant's product page. The thing being removed is not the retailer's site. It is the sequence of screens between deciding and paying.

That distinction is the whole subject. A checkout page can disappear while checkout becomes more consequential, because the page was never the thing doing the work.

Checkout was never the page

Ask most people what happens at checkout and they describe entering an address and a card number. That is the visible part, and the smallest.

Underneath, a checkout is a short, dense sequence of decisions. Is this item in stock in this variant right now. Is the price current. Does this promotion apply to this customer and this basket. What tax applies at this address. Which shipping options are real for these items. Is this payment legitimate. When all of that resolves, an order gets created with an owner, a fulfillment path, and a return policy attached.

The page is the interview that collects the missing inputs. It exists because the merchant needs information the customer has and the merchant does not.

Newsletter

Follow the research

Research notes and analysis on how AI, digital transformation, product discovery, and customer behavior are changing commerce.

Subscribe to Hu's Weekly Hoot

Why the page becomes negotiable

An agent changes that arithmetic, because it may already hold the inputs.

Stripe's own mechanics illustrate it. In its shared payment token model, the customer submits a payment method to the agent, the agent issues a token scoped to a specific seller with a maximum amount and an expiration, and the seller creates the charge against it. The documentation calls a token "a scoped grant to use the customer's payment method," with limits set by the agent and revocable by the agent.

If the agent carries identity, preference, address, and a payment credential, then the interview has nothing left to ask. Approval can compress into a sentence. The traditional checkout page may have much less left to collect.

That is the honest version of Gaybrick's prediction, and it is more limited than "checkout disappears." The interface disappears when the information it existed to collect is already present.

The work does not disappear

Here is where I would push back, and I do not have to reach far, because Stripe made the argument first.

In a March 2026 post on what it learned building early agentic commerce, Stripe wrote that "the messy parts of commerce don't go away, but they pop up in different places." It is worth reading because it is not a prediction. It is a list of things that turned out to be hard.

Inventory, for instance. Stripe notes that "agents will need real-time checks to confirm that a specific item or combination is actually in stock," and describes a partner that wanted verification down to the millisecond. Fraud gets harder differently: the behavioral signals merchants rely on, Stripe says, "vanish in an agentic world where there's no human buyer on the frontend." Post-purchase is barely solved. Stripe asks directly what happens if an agent confirms an order a backend later rejects, and whether a cancellation spoken to an AI surface reliably reaches the merchant.

None of that argues against agentic checkout. It argues that the assistant hides complexity from the customer rather than removing it from commerce. Somebody still executes every step, and when steps fail the question of who is accountable does not get easier because the interface got simpler.

What the retailer gives up along with the page

The strategic cost is not the page. It is what retailers had been doing on it.

Checkout has been the last surface a retailer fully controlled, and a lot rides on it: loyalty enrollment, account creation, subscription offers, warranties, the moment an anonymous session becomes a known customer. If the transaction resolves inside an assistant, some of that disappears or moves to a surface the retailer does not design.

Again, Stripe says it more plainly than I would dare. Its post calls the logged-in state "the holy grail for sellers," then explains why agentic flows complicate it: "the agent acts as proxy, and the customer's identity isn't revealed until the moment they hit 'buy.'" The consequence is stated without spin. Brands, Stripe writes, are "struggling to honor loyalty benefits, apply targeted discounts, and attribute conversion."

This is my interpretation rather than Stripe's, but the shape is familiar. I argued recently that assistants keep the discovery context while retailers get the order. Checkout was the other end of that journey, where a retailer that lost discovery could still turn a buyer into a known, reachable customer. If both ends move outside the retailer's interface, it keeps the revenue and loses both moments where relationships got built.

The merchant still sets the rules

None of this makes the retailer a passive fulfillment endpoint.

In the shared payment token flow, the seller still creates the payment, applies its own logic, and owns the resulting order. Protocols are being built to carry merchant rules into agent surfaces rather than around them, which is part of why Amazon joined the governance body it had resisted. The arrangement looks less like a takeover than a division of labor: the agent owns the interface, the merchant owns the commerce logic, a protocol moves terms between them.

Stripe's current agentic-commerce materials say the business can remain the merchant of record while retaining control over products, pricing, descriptions, and fulfillment. That matters because removing the checkout page does not necessarily remove the retailer's legal or operational ownership of the transaction. The interface can move while merchant responsibility stays put.

Stripe has a position in this future

Worth stating plainly. If commerce shifts from branded interfaces toward infrastructure calls, the companies supplying the infrastructure become more central. Stripe benefits from the world Gaybrick describes.

That does not make him wrong, and I do not think he is. It means the prediction and the roadmap point the same direction, which is a reason to weigh the evidence rather than the forecast. The most persuasive Stripe material here is not the podcast. It is the engineering post cataloguing what is still broken.

The counterargument deserves weight

The likely outcome is fewer checkout interactions, not zero checkout interfaces.

People buy differently depending on the stakes. A replenishment order is a good candidate for an agent. A mattress, a laptop, or anything with a complicated return policy is one most people will want to see before confirming. Regulated categories carry disclosure requirements that assume a human reading a screen. Shipping gets complicated when items split across fulfillment paths. And fraud systems sometimes need to challenge a buyer, which is awkward when no buyer is present.

There is also precedent for a partial version of this. When OpenAI pulled back from native checkout and let merchants use their own, the transaction economics were the reason. Agentic checkout is not automatically better or cheaper, and nobody has published evidence that customers prefer it.

The distinction worth keeping

AI may eliminate the checkout interface long before it eliminates the checkout system. The page was a data collection device. When the data arrives another way the device is redundant, and none of the underlying obligations move an inch.

That pattern keeps recurring. A visible step disappears and the system beneath it becomes more load-bearing, less forgiving of bad data, and harder to see when it fails.

If the customer chooses the product, authorizes the payment, and gets a confirmation without ever seeing a retailer's screen, where does the retailer earn the second purchase?

Follow the research

I publish research notes and analysis on how AI, digital transformation, product discovery, and customer behavior are changing commerce.

Subscribe to Hu's Weekly Hoot