How Stripe is designing Checkout for AI agents
Cara Mecozzi and Steve Kaliski · 22 September 2026
Read the originalStripe made its Checkout page cheaper for AI shopping agents to use by offering them only the actions valid at each step, built on the human checkout's own code.
AI shopping agents have to pay on checkout pages built for humans, which on Stripe cost an agent 1.8 million tokens and 39 actions per purchase on average. Stripe, whose Checkout page serves over 7.8 million businesses, adopted WebMCP, an emerging browser standard that lets a page offer its actions to an agent as named tools. The page now offers only the actions valid at each step, and agents in Stripe's tests used 42 percent fewer tokens.
- A token is the unit of text an AI model reads and is billed by, so fewer tokens make a purchase cheaper. Stripe treats tokens and actions as the agent's equivalent of a person's waiting time and clicks.
- The payment button appears to the agent only once the form is complete. Choosing a payment method other than a card removes the card-number field.
- The agent's tools run on the same code and forms as the human checkout, so the two versions cannot drift apart.
- In 60 tests across six AI models on a fictional outdoor shop, every agent completed the purchase. With WebMCP, agents took 38 percent fewer actions and finished 39 percent faster.
A product can hold the rules for what is allowed next in one place, where the same rules serve people and agents. The account is Stripe's own, about its own product, and the wider application is an inference.
Give AI agents the same actions and forms that people use in the interface, and show an agent only the actions that are possible at the current step.
Derived by Working Surface from the article. Source line: We did not want to introduce an “agent-only” bifurcation that could result in drift or add toil for engineers.
24 September 2026: teams set the rules for agent-built work before it starts, and people judge what falls outside them.