--- title: "AP2 Lets AI Agents Buy on Your Customer's Behalf. Most Marketing Sites Aren't Ready for the Mandate It Requires." description: "Google's Agent Payments Protocol lets AI agents complete purchases using cryptographically signed mandates instead of a human clicking buy. Here's what that mandate chain actually requires from your product data, checkout flow, and attribution stack." author: LETSGROW Dev Team date: 2026-09-28 category: AI Tools tags: ["AP2", "Agentic Commerce", "AI Agents", "Payments", "Marketing Technology"] url: "https://letsgrow.dev/blog/agent-payments-protocol-ap2-marketing-readiness" --- # AP2 Lets AI Agents Buy on Your Customer's Behalf. Most Marketing Sites Aren't Ready for the Mandate It Requires. The checkout button you spent three years optimizing is about to become optional. Google's Agent Payments Protocol, AP2, went live in 2026 with more than 60 payments and commerce companies behind it, and it does something no A/B test on your buy button ever will: it removes the human from the transaction entirely and replaces "click to confirm" with a cryptographically signed contract called a mandate. If your product data, checkout flow, and attribution model still assume a person is the one clicking, you are optimizing for a customer that is starting to disappear. This is not a hypothetical future protocol sitting in a GitHub repo nobody reads. American Express, Mastercard, PayPal, Salesforce, Adobe, Coinbase, and dozens of others are already building against it. In April 2026, Google handed ownership of AP2 to the FIDO Alliance, the same body that governs passwordless authentication standards, which is exactly what a company does when it wants a protocol to stop looking like a corporate side project and start looking like infrastructure. ## What AP2 Actually Requires AP2 solves a problem traditional payment rails were never built for: proving that an autonomous agent acting on a customer's behalf actually has permission to spend their money, and proving it in a way a merchant, a card network, and a court can all verify later. It does this with mandates, tamper-proof digital contracts signed with verifiable credentials. There are two flows that matter for marketers. In the "human present" flow, the customer asks an agent to find something, reviews the actual cart, and signs a Cart Mandate that locks in the exact items and price before payment fires. In the "human not present" flow, the customer pre-signs an Intent Mandate with conditions instead of a specific cart: buy the concert tickets the moment they go on sale, spend up to $150. The agent watches, builds the cart itself when conditions are met, and completes the purchase with no real-time approval at all. That second flow is the one that should worry anyone who thinks conversion happens because of what your landing page said in the moment. ## This Is an Infrastructure Problem, Not a Checkout UX Problem Every existing "AI shopping agent" post treats this as a checkout-readiness question: can your site render cleanly for a browser agent, is your form fillable, is your CTA findable. AP2 makes that framing obsolete. A Human Not Present transaction never touches your rendered checkout page at all. The agent is not filling out a form, it is presenting a signed mandate to a merchant endpoint and expecting a machine-readable response. If your commerce stack only knows how to talk to a browser, it has nothing to say to an agent holding a valid Cart Mandate. ::compare-table title: "Two AP2 Flows, Two Different Marketing Problems" columns: ["Flow", "Who Signs the Mandate", "When Marketing Can Influence It", "What Breaks If You're Not Ready"] rows: - ["Human Present", "Customer, at the moment of purchase", "Product copy, pricing, cart contents can still sway the decision", "Slow or non-machine-readable cart data delays or kills the mandate signing"] - ["Human Not Present", "Customer, in advance, on conditions only", "Only the pre-signed intent matters; nothing you show later changes the outcome", "You never get a moment to influence the sale, only to fulfill it correctly"] :: That second row is the uncomfortable one. There is no landing page, no urgency banner, no cart abandonment email in a Human Not Present flow. Influence has to happen before the intent is signed, which means it happens in whatever channel convinced the customer to set that condition in the first place, not at the point of sale. ## What This Breaks in Your Funnel Three things stop working quietly, not loudly. First, your add-to-cart event. An agent assembling a Cart Mandate programmatically does not fire the same client-side events a human browsing session does, so your funnel reporting will start showing a purchase with no upstream engagement data behind it. Second, session-based personalization. A pre-signed Intent Mandate executes later, possibly on a different device, with no cookies or session state tying it back to the browsing history you used to build a segment. Third, your attribution model. If the mandate was signed a week before the agent executed it, the "last touch" your dashboard credits could be entirely disconnected from the moment that actually drove the decision. None of this shows up as an error. It shows up as a conversion that happened correctly, on time, at the right price, with no explanation your existing analytics stack can give you for why it happened. ## What to Build Now You do not need to rebuild your commerce stack around a protocol that is still maturing. You do need to stop being blind to it. ::checklist title: "AP2 Readiness Checklist for Marketing Teams" items: - Audit whether your product feed exposes structured, machine-readable price and availability data an agent can act on without rendering your page - Ask your commerce or engineering team whether your checkout can accept a signed Cart Mandate via API, not only a filled-out form - Add a distinct conversion event type for mandate-based purchases so they stop silently polluting session-based funnel reports - Identify which of your current offers are conditional enough to be worth a pre-signed Intent Mandate, like price-drop alerts or restock notifications, and package them that way - Assign ownership of the verifiable-credential and fraud-liability question to legal or trust and safety before an agent-initiated dispute forces the conversation - Track the FIDO Alliance's AP2 spec directly instead of waiting for a vendor's summary, since governance no longer sits with Google alone :: ## The Sale You Can't See Coming Is Still a Sale Marketing teams have spent two years arguing about whether AI agents will replace search traffic. AP2 is a quieter and more concrete shift: it is the plumbing that lets an agent hold real purchasing authority, with a legal trail to back it up, at scale. You do not have to build for every edge case of agentic commerce this quarter. You do have to stop assuming every transaction in your reports came from a person who saw your page and decided in that moment. Some of them were decided a week earlier, by a mandate you never saw, for a condition you never tracked. Build the visibility into that now, while it is still a small percentage of revenue, not after it is the transaction type you can't explain.