Key Takeaways
- Agentic checkout is where AI agents execute payment on the user's behalf, splitting into three patterns in 2026.
- Every design boils down to three tensions: authorization strength, refund liability, and friction level.
- For merchants, riding Shopify, Stripe, or Adyen defaults beats custom builds on cost and quality.
Checkout Gets Rebuilt Without a Single Form Field
Checkout is the most conversion-critical step in an ecommerce experience — and also the most calcified in its design. For twenty years the debate has been "how do we cut form fields?", "should we allow guest checkout?", "where does Apple Pay go?". Agentic checkout upends the entire premise: no human fills a form at all.
This article maps the canonical agentic checkout patterns as of 2026 and the design decisions merchants should make. For the protocol overview, see protocol comparison; for consumer-side behavior, see agentic shopping.
Three Implementation Patterns
Agent-mediated checkout falls into roughly three patterns today.
Delegated Token. The user pre-issues the AI agent a scoped authorization token — "this card, up to this limit." Mastercard Agentic Tokens and Visa TAP delegation tokens are the canonical examples. The agent uses its token; the network enforces scope.
Pass-through. The agent temporarily receives the user's existing payment info and settles directly. OpenAI's ACP and Shopify's Agentic Checkout are in this camp. Agent providers don't retain payment info long-term — they receive it per transaction and discard it.
On-chain. Settlement happens on-chain using stablecoins or similar, bypassing card networks entirely. Skyfire + ERC-8004 is the archetype. It's ahead in AI-to-AI transactions and micropayments but still a minority for general ecommerce.
These aren't mutually exclusive. Large merchants often default to Delegated Token and use On-chain selectively for specific use cases.
Three Design Tensions
Three tensions show up in every agentic checkout design.
Authorization strength. How do you prevent agents from buying expensive things on their own? AP2's Mandates (Intent / Cart / Payment) answer with "staged approval." A broad upfront intent ("travel gear under $500") and a per-cart confirmation just before payment combine to give flexible-but-not-loose authorization.
Refund and chargeback liability. When something goes wrong in an agent-mediated purchase, who's on the hook? Visa TAP shifts part of the chargeback liability to Visa for transactions carrying TAP signals, which is a win for merchants. Pass-through patterns where the agent handles payment info directly leave some ambiguous liability gaps.
Friction level. The stricter your authorization, the clunkier the UX. Confirming every cart is safe but kills the "hands-free" benefit of agentic shopping. Merchants have to pick where on this spectrum they want to sit. A staged model — stronger authorization for high-ticket items, looser for low-cost consumables — is usually the realistic answer.
Implementation Choices for Merchants
Three broad paths to agentic checkout support.
Easiest: ride Shopify Plus. Shopify Plus merchants get Storefront MCP and agentic checkout equivalents turned on automatically, no extra implementation needed. UCP support is handled at the platform level. For SMB to mid-market merchants, this dominates on ROI.
Second: Stripe Agent Toolkit. Merchants already using Stripe can add Visa TAP-capable agent payments in a few dozen lines by integrating Stripe Agent Toolkit. Not tied to a specific commerce platform, so it works across ecommerce stacks outside Shopify.
Third: build your own. Rarely worth it in 2026. Combining AP2, Visa TAP, Mastercard Verifiable Intent, and UCP yourself is complex, and the platform path wins on both quality and cost in most cases. Reserve custom builds for real industry-specific requirements (regulated sectors with extra compliance steps).
The Returns Blind Spot
Something that gets missed in the agentic checkout discussion: returns design. Return requests on agent-mediated purchases are more frequent than on human-mediated ones — the agent receives more "ordered it but wrong in reality" feedback than expected.
Two approaches run in parallel at major platforms. Delegate returns to the agent too: the user says "return it" and the agent generates the return label and refund. Or keep returns human-in-the-loop: purchases run through the agent, but returns escalate to a human for any judgment calls.
On the merchant side, differentiating these in your API design simplifies operations. Flag agent-originated purchases and route their return handling either to automatic processing or to support escalation.
Conclusion — Invisible Checkout
Agentic checkout assumes a new UX: checkout without a screen. For merchants the important shift is moving off of form-optimization as the competitive axis and onto building APIs and data that help agents succeed.
The right starting point for most merchants isn't custom implementation but the default patterns in established platforms. Shopify Plus, Stripe, and Adyen have all reached usable quality by early 2026 — a safer bet than building from scratch. The room to differentiate is not in the payment flow itself but on either side of it: product information, reviews, and the returns experience.
