AP2 — Agent Payments Protocol

What a payments layer does here

Agent-led checkout splits naturally into two contracts: the commerce lifecycle (cart, pricing, completion, fulfillment events) and the payment credential (how an instrument is presented, scoped, and settled when software transacts on a human's behalf). On the Google stack, UCP handles the first and AP2 the second. The separation means a merchant implementing the lifecycle does not design payment-instrument handling from scratch — AP2 provides the contract and participating payment providers implement against it.

The core problem AP2 addresses is authorization and audit: proving that a given agent purchase was mandated by the buyer, bounding what the agent may spend, and leaving a verifiable trail. Google's developer materials and the protocol's published documentation are the primary sources, and the multi-partner list has been growing through the pilot period as of mid-2026.

Why it matters for ecommerce

Mostly as orientation rather than as a to-do. The payments side of agentic commerce does not live under the merchant's control — it sits between the protocol, the payment provider, and the buyer's instrument. The merchant's job remains the catalog, the feed, the endpoints (or the platform channel that wraps them), and fulfillment. Knowing where AP2 starts and stops keeps vendor conversations precise: a tool claiming to "handle AP2 for you" is describing the part of the stack merchants never touch directly.

For Shopify brands the wrapping is complete: Shopify Agentic Storefronts packages both the lifecycle and payments layers, so the merchant-side surface is a channel toggle and catalog readiness, not protocol work.

How AP2 compares to ACP's payment hand-off

The OpenAI/Stripe stack bundles payments differently: under ACP, the payment provider issues a delegated, scoped token the merchant captures against, with Stripe as the first named PSP. The Google stack separates the concern into AP2 so multiple payment providers can implement one contract without reshaping UCP. Architecturally different, same goal: the agent pays without the merchant ever holding the buyer's raw credential. Both stacks are in pilot as of mid-2026, and the shared merchant-side groundwork — accurate price, availability, and policy data — is identical.

How eCommerce Insights treats AP2

As context for readiness scoring, not as an integration surface. The agent-readability score checks the PDP and catalog signals that any agent-payment flow ultimately depends on; protocol and payments wiring are reported as informational checks where detectable. The platform does not implement checkout for any protocol — no tool should claim to.

Related terms

• UCP (Universal Commerce Protocol) — the lifecycle protocol AP2 pairs with.
• ACP (Agentic Commerce Protocol) — the OpenAI/Stripe stack with its own payment hand-off.
• Shopify Agentic Storefronts — wraps both layers for Shopify merchants.
• Agent checkout — the stage of agentic commerce these protocols mediate.
• Agentic commerce — the three-stage shift this sits inside.