Six Camps Battle in Agentic Commerce Protocol War

Six Layers of Agentic Purchases

Nate Jones identifies six layers in agentic commerce where protocols compete for control: (1) who decides where the agent shops, (2) proof the agent was allowed to act, (3) who owns the payment credential, (4) rails for machine-to-machine payments, (5) enterprise governance, and (6) overall responsibility allocation. Traditional human checkout relies on shared evidence from search, cart, payment, and fulfillment, with merchants as record-holders for returns and support. Agentic commerce unbundles this, shifting focus from payment ability to proof of authorization across identity, fraud, credentials, settlement, refunds, and liability.

Checkout Protocols: ACP vs UCP

OpenAI and Stripe's Agent Commerce Protocol (ACP) enables instant checkout in ChatGPT for supported merchants; the agent assembles context, passes structured transactions to merchants without website flows, and Stripe handles payment while merchants remain responsible for fulfillment. Shopify and Google's Universal Commerce Protocol (UCP) counters by integrating full shopping paths across agents, merchants, payments, identity, and platforms, preserving merchant control over rules, loyalty, inventory, shipping, promotions, and fraud. ACP prioritizes clean agent-to-merchant flows but risks merchants losing discovery and branding; UCP addresses merchant viability in complex commerce.

Authorization, Credentials, and Rails

Authorization separates from payment: Stripe's approved payment link provides tokens for agent purchases; Google's Agent Payments Protocol (AP2) issues mandates defining task scope, constraints, and user approval proof that persist across systems. Visa's Intelligent Commerce, Mastercard's Agent Pay, and PayPal's agentic services emphasize tokenized credentials, registration, and dispute protections. Stablecoins like USDC suit micro-payments for APIs, tools, and compute; Coinbase's x402 embeds payment in HTTP 402 web requests (pay for resource access); Stripe's Machine Payments Protocol, Bridge, Privy, and Tempo support agent wallets and settlement for software-to-software transactions.

Governance and Responsibility

AWS Bedrock Agent Core, built with Coinbase and Stripe, provides enterprise runtime for budgets, approvals, vendor rules, and logs, overseeing tasks without owning rails. Responsibility varies: ACP/UCP handle checkout with merchants as record; AP2 mandates track permissions; networks secure credentials; stablecoins/x402 enable M2M rails; AWS governs runtime. Builders must audit layers for identity, permission, refunds, and liability, as unbundled flows expose trillions in value; companies defining terms win, others get sidelined.