Google's Agent Payments Protocol (AP2) is not a checkout you build or a plugin you install — it's a trust layer that gives an AI agent's purchase a cryptographic paper trail, proving a shopper actually authorized this exact cart at this exact price. For a WooCommerce merchant that reframes the whole thing: AP2 reaches your store through your payment processor and the card networks, not through your admin panel, and the single part of it that touches your own data is the Cart Mandate — the signed record that freezes the price and items a shopper agreed to.
The reason that Cart Mandate keeps our attention is that we spend our days on the data underneath it. We build Contexta, a WooCommerce plugin, and the defect we find most often is a product whose price disagrees across its page, its schema and its feed — a harmless-looking inconsistency that AP2 quietly turns into a signed, auditable one. So here is AP2 from the merchant's side: what it solves, how its three mandates actually work, and the one thing it asks of your store today.
What is AP2, and what problem does it actually solve?
AP2 is Google's open protocol — announced September 16, 2025 and donated to the FIDO Alliance on April 28, 2026 — for letting AI agents pay on a person's behalf without anyone downstream having to trust the agent blindly. It solves one hard problem: when software spends your money, how does everyone in the chain prove you agreed to it? AP2's answer is a non-repudiable audit trail that, in Google's own framing, settles three questions — authorization (did the user grant this specific purchase), authenticity (does the agent's request reflect the user's real intent), and accountability (who is responsible if it goes wrong).
Notice what that is and isn't. AP2 doesn't find the product, build the cart, or move the money; it sits between the cart and the payment rail and proves consent. It's a single rung of a taller stack, and seeing where AP2 fits among ACP, UCP and x402 is the wider picture — this article is the rung itself. That the FIDO Payments working group now steering it is co-chaired by Mastercard and Visa tells you where this is heading: the card networks intend to build their agentic rules on top of AP2's mandate format.
How do the three AP2 mandates work?
AP2 chains three cryptographically signed mandates — Intent, then Cart, then Payment — each a W3C Verifiable Credential signed by the party responsible for it. Together they turn a vague "my agent bought this" into a precise, tamper-proof record of who approved what.
Intent Mandate
The shopper signs their instruction: "white running shoes under $150." Sets the auditable context and any spending limits.
Cart Mandate
The shopper signs the exact cart — SKU, price, tax, shipping, total — approving "what you see is what you pay."
Payment Mandate
Links the funding method (card token, wallet, bank token) to the approved cart and flags the transaction as agent-driven.
The chain runs two ways depending on presence. In a human-present purchase, you approve the cart in real time and sign the Cart Mandate on the spot. In a human-not-present purchase — added in the v0.2 release — you sign a detailed Intent Mandate upfront with the rules of engagement (price ceiling, timing, conditions), and the agent generates the Cart Mandate automatically the moment those conditions are met, so it can buy the concert tickets the second they drop without you on the call.
Do WooCommerce merchants install AP2 themselves?
No — and as of mid-2026 there is no supported path to. AP2 is consumed on the payment side: Mastercard maps its mandates onto Agentic Tokens, Visa onto Trusted Agent signed-intent payloads, and processors such as Stripe and Adyen fold it into their agentic offerings. WooCommerce appears on none of AP2's launch-partner lists, so a self-hosted store's exposure to it runs entirely through whichever processor and commerce integration you already use.
That's the same structural absence that shapes what a WooCommerce store can actually do with UCP: the protocol was designed with centralized platforms and payment networks that can switch it on for millions of merchants at once, and self-hosted stores inherit it secondhand. The Cart Mandate is described as being produced by "the merchant or merchant-side agent," but for a Woo store that merchant-side agent is realistically your commerce-layer integration and processor, not code you write. Chasing an "AP2 plugin" in 2026 is looking for a switch that doesn't exist on your side of the wire.
What does the Cart Mandate mean for your WooCommerce product data?
It turns price consistency from an SEO nicety into a payment-integrity requirement. The Cart Mandate binds the exact SKU, price, tax, shipping and total a shopper approved into what Google calls "a secure, unchangeable record" — so if the price your store hands an agent disagrees with the price in your structured data or your feed, the shopper can sign off on a number you never meant to charge, and now there is cryptographic proof of the mismatch attached to the order.
Before
A mismatch today
- A stale schema price is a soft SEO problem
- Worst case, a shopper emails about the wrong number
- You quietly fix it; no record survives
After
The same mismatch under AP2
- The wrong price is frozen into a signed, unchangeable record
- The shopper holds cryptographic proof of what they approved
- The discrepancy is now an auditable accountability question
This is exactly where WooCommerce stores are fragile, because three systems generate the price independently — core emits the JSON-LD, a feed plugin builds the feed, and the theme renders the page — and nothing forces them to agree. A sale price live on the page but stale in the schema is the classic case, and it's the root of product descriptions quoting a price that no longer exists. Reconciling that across a few hundred SKUs by hand is the job nobody finishes, which is what Contexta's Commerce Readiness audit is built to close: it checks each product for the fields an agent freezes — price, availability, tax-relevant attributes, GTIN — and hands back a per-product fix link, so the number in the mandate is the number you meant.
Does AP2 protect merchants from chargebacks and fraud?
Not yet, and any vendor implying otherwise is running ahead of the rules. As of mid-2026, card networks still classify agent traffic as card-not-present with no liability shift — which, if anything, pushes more chargeback exposure onto the merchant — and AP2's cryptographic identity is not recognized as a liability shift on its own. The signed mandate makes the facts of a disputed purchase clear, but clarity about who approved what is not the same as the network absolving you of the loss.
The dispute rules are being actively drafted, not settled: the FIDO Payments working group co-chaired by Mastercard and Visa is writing the agent-attributed chargeback framework, and Mastercard's own Agent Pay currently keeps liability on the standard tokenized-transaction path, with consumer chargeback rights intact. So AP2's fraud benefit for merchants is a promissory note the networks are still filling in — real in direction, unbankable in mid-2026. The honest posture is to welcome the audit trail and assume the liability math won't move in your favor for a while. The gap is not theoretical: Amazon's Buy for Me agent already completes purchases on independent stores' own checkouts, and of the four AI shopping surfaces it is the one that has published no merchant-facing answer on who owns the chargeback when a bot-placed order is disputed.
What should a WooCommerce merchant do about AP2 today?
Nothing to install, one thing to fix: make sure the cart data an agent could freeze into a mandate can never contradict itself. Reconcile price, tax, shipping and availability across your page, your JSON-LD and your feed so all three agree; confirm those values render without JavaScript, since several agents build their record before any script runs; and keep an eye on your payment processor's roadmap for when its agentic support actually ships.
That work isn't AP2-specific, which is the point — it's the same clean, consistent product record every AI shopping agent reads whether it arrives to browse, to cite, or to buy. AP2 will land on your store through your processor whether you prepare or not; the only variable in your control is whether the catalog it transacts against is one an agent, and the signed mandate behind it, can trust. Fix the data, and you're ready for the protocol before it's ready for you.
FAQ
Do I need to install AP2 on my WooCommerce store?
No, and as of mid-2026 there is no supported way to. AP2 is a payment-authorization layer adopted by card networks and processors — Mastercard Agent Pay, Visa Trusted Agent, Stripe, Adyen — not a plugin you add, and WooCommerce isn't an AP2 launch partner. Your practical job is keeping product and cart data consistent so a signed Cart Mandate can't freeze a price you didn't mean to charge.
What are the three AP2 mandates?
AP2 uses three cryptographically signed mandates: the Intent Mandate (what you authorized the agent to do), the Cart Mandate (the exact items and price you approved), and the Payment Mandate (linking your funding method to that cart). Together they form a non-repudiable audit trail answering who authorized a purchase, for what, and at what price — each one a W3C Verifiable Credential signed by the responsible party.
Does AP2 reduce chargebacks for agent purchases?
Not reliably yet, as of mid-2026. Card networks still classify agent traffic as card-not-present with no liability shift, and AP2's cryptographic proof isn't recognized as a liability shift on its own; the dispute rules are still being drafted by the FIDO Payments working group co-chaired by Mastercard and Visa. Treat AP2's fraud protection as a future benefit, not one you can bank on today.
Is AP2 the same as UCP or ACP?
No — AP2 handles payment authorization, proving the shopper approved the payment, while UCP and ACP handle discovery, cart-building and checkout. They are complementary layers designed to stack, not competitors: a single agent purchase can use UCP or ACP to build the cart and AP2 to authorize the payment underneath it, then settle over a card or a stablecoin rail like x402.