Merchant Services
September 11, 2026
The Checkout Page Isn't Dying — It's Moving to the Back End
Stripe's president of technology says checkout is dying. It isn't — it's moving from a front-end page to backend, API-driven payment infrastructure.
No, the checkout page is not "dying" in the sense of payments disappearing. What Stripe's Will Gaybrick actually described is a front-end-to-back-end shift: the visible checkout page is being replaced by invisible, API-driven payment infrastructure that runs behind an AI agent or a product page, while the underlying work, authentication, fraud screening, payment capture, tax, and fulfillment, keeps running exactly as before.
A LinkedIn post quoting Stripe's president of technology and business, Will Gaybrick, went viral with a simple, alarming headline: the checkout page is dying.
The comment came from a recent episode of the a16z Podcast, where Gaybrick argued that it's already trivially easy to click through to a checkout page and complete a purchase, so easy, in fact, that he questions whether the page needs to exist at all. In his view, the ideal future experience is closer to saying "buy this" on a product page, or inside a conversation with an AI agent, and having the transaction complete without ever routing a person through a dedicated payment form.
Framed that way, "checkout is dying" makes a great headline. It's also a reasonably accurate summary of a genuinely important shift happening in agentic commerce, AI agents that browse, compare, and buy on a person's behalf. But it's an imprecise way to describe what's actually changing, and the imprecision matters if you're a merchant, a payments provider, or anyone building commerce infrastructure for the next five years.
Here's the more accurate framing: the checkout page is not dying, the checkout process is migrating from the front end to the back end. Those are two very different claims.
Gaybrick's own comments support the second reading, not the first. He isn't describing a world where merchants stop collecting payment information, screening for fraud, or calculating sales tax. He's describing a world where all of that logic gets pushed into backend infrastructure that agents and platforms call via API, instead of being rendered as a page a human has to navigate, read, and fill out by hand.
Pro Tip: If a vendor or a headline tells you a category is "dying," check whether they mean the function or the interface. The two get conflated constantly, and the difference determines whether you should be worried or simply planning ahead.
To see why "backend, not extinct" is the right read, it helps to look at what's actually shipping today rather than what's being predicted for tomorrow.
Stripe's Agentic Commerce Protocol (ACP), co-developed with OpenAI, already powers Instant Checkout in ChatGPT and a similar experience inside Microsoft Copilot. The mechanics look like this:
Nothing in that flow eliminates payment authentication, fraud screening, tax remittance, or order fulfillment. Every one of those steps still happens, they simply happen through machine-to-machine API calls instead of a rendered web form. As Stripe's own announcement puts it, merchants can accept or decline the order, charge the payment method, calculate and remit sales tax, and handle fulfillment and returns, as they normally would. That's the front-end-to-back-end shift in practice, not in theory.
| Checkout step | Front end today | Back end tomorrow |
|---|---|---|
| Payment entry | Card number typed into a hosted form | Shared Payment Token issued to the agent |
| Checkout surface | Dedicated checkout page or redirect | Chat interface or product page, no redirect |
| Fraud screening | Visible challenge (3-D Secure, CAPTCHA) | Backend risk signals scored via API, no user-facing challenge |
| Order confirmation | Rendered confirmation page | Confirmation returned to the agent, surfaced in-chat |
There's a reason "checkout is dying" spreads faster on LinkedIn than "checkout is being re-architected as backend infrastructure." It's shorter, punchier, and fits the broader narrative arc that AI is making entire job categories and product categories obsolete.
It's also worth noting that this narrative isn't coming from a neutral observer. Stripe is actively building and selling the exact infrastructure, the Agentic Commerce Protocol, Shared Payment Tokens, agent-facing APIs, that this vision depends on. "The checkout page is dying, so you'll need our backend rails to replace it" is not just a prediction, it's a product pitch. That doesn't make the observation wrong, but it's a reason to read the framing with a healthy amount of skepticism rather than taking the headline at face value.
Consumer behavior also complicates the "dying" narrative on a shorter timeline. A mid-2026 survey from Commerce and PayPal found that while consumers are increasingly open to agentic shopping, a majority still want a human approval step before an AI agent completes a purchase on their behalf. That's a meaningful gap between "the technology exists to remove the checkout page" and "consumers are ready to let a page disappear without any visible confirmation step."
If you sell online, or you provide the infrastructure other businesses sell through, the practical takeaway isn't "checkout pages will vanish next quarter." It's that the checkout page is becoming one of several checkout surfaces, not the only one, and the backend has to work without a human present.
Merchants keep asking whether they need to rebuild their checkout experience for AI agents. Not yet, but their gateway and fraud rules do need to work without a page in front of them to catch mistakes, and that's the part worth fixing before volume forces it.
— Joshua Benedetti
Pro Tip: Don't wait for agentic commerce volume to force the issue. Confirm with your gateway and processor now whether your current setup supports headless, API-driven checkout, so you're not retrofitting fraud and tax logic under pressure later.
Will Gaybrick isn't wrong that the checkout page, as most people currently experience it, is on a path toward disappearing for a meaningful share of transactions. But "dying" overstates the claim and undersells what's actually interesting about the shift.
The more accurate, if less viral, version of the story is that checkout is being decoupled from the page. The front-end artifact goes away. The back-end function, payment collection, authentication, tax, fraud, fulfillment, not only survives the transition, it becomes the thing that has to get more sophisticated, more machine-readable, and more resilient, precisely because there's no longer a human in the loop to paper over its gaps.
That's a story about infrastructure maturing, not about checkout disappearing.
Not in the sense of payments disappearing. What's changing is the visible checkout page being replaced by backend, API-driven payment processing that runs behind an AI agent or a product page, while the checkout function itself, authentication, fraud checks, tax, and fulfillment, still happens.
Will Gaybrick, Stripe's president of technology and business, made the comment on a recent episode of the a16z Podcast, in the context of discussing agentic commerce and Stripe's Agentic Commerce Protocol.
Agentic commerce refers to AI agents, like those built into ChatGPT or Microsoft Copilot, browsing, comparing, and completing purchases on a person's behalf, typically using tokenized payment credentials and merchant APIs rather than a traditional checkout page.
A Shared Payment Token is a secure, scoped payment credential issued on behalf of a buyer and tied to a specific merchant and cart total, so an AI agent can complete a purchase without exposing the buyer's actual card details to the merchant or the agent.
Unlikely, at least in the near term. High-consideration purchases, financed transactions, and anything requiring identity verification or multi-step configuration will likely keep a visible checkout experience, while low-friction, well-defined purchases move fastest toward invisible, agent-driven checkout.
Merchants should prioritize API-first, headless payment infrastructure, keep product and pricing data machine-readable via feeds or real-time hooks, and work with payment and risk providers who can distinguish legitimate agent-initiated transactions from fraudulent ones.
Start protecting your revenue from chargebacks today — schedule your complimentary consultation with CARDZ3N’s dispute management specialists.