The Argument
Checkout is the moment of truth. In traditional commerce, it is the point where browsing becomes buying. In agentic commerce, checkout is the point where delegation becomes execution - where the agent's evaluation of merchants, products, and terms culminates in a binding transaction. Most checkout experiences today are designed to fail in agent-mediated contexts. They assume a human customer who sees a cart, reviews items, enters payment details, and clicks a button. Agent checkout is fundamentally different: it is an API transaction, a machine-to-machine handshake that must validate identity, confirm authority, process payment, and establish post-purchase obligations in a single compressed interaction. The essay argues that the agent checkout is the compression point where the entire AXD framework converges.
The Evidence
The essay examines six checkout design challenges. Embedded checkout patterns must support agents that arrive via API without a browsing session - no cart page, no address form, no payment entry screen. One-step versus staged purchase flows present a design tension: agents prefer single-call transactions for efficiency, but complex purchases may require staged verification of delegation scope, payment authority, and delivery preferences.
Exception handling at checkout is where most agent transactions will fail: out-of-stock items, price changes between evaluation and purchase, payment authorisation failures, and delegation scope violations all require machine-readable error responses and programmatic recovery paths. Cart persistence across agents and sessions addresses the scenario where multiple agents or the same agent across sessions must maintain transaction state. Confirmation and receipt design must serve both the agent (structured data for its records) and the human principal (readable confirmation of what was purchased and why). The essay introduces the checkout trust test - a diagnostic framework for evaluating whether a merchant's checkout infrastructure is agent-ready.
The Implication
The agent checkout is not a feature to be added to existing checkout infrastructure. It is a fundamentally different interaction pattern that requires purpose-built design. Every AXD concept - delegation design, trust architecture, operational envelope, signal clarity, failure architecture - converges at the checkout moment. A merchant whose checkout cannot validate agent identity, confirm delegation scope, handle exceptions programmatically, and provide machine-readable confirmations will lose agent transactions regardless of how good its product data or pricing is. The checkout is where trust architecture becomes commercially binding. Design it as such.