Search is reversible. Summarizing is reversible. Paying is not. This page is about the four things that change when the last step of the loop is a purchase (irreversibility, liability, identity, and the merchant's side of the problem), and about the young, competing standards trying to make agent-initiated payments checkable.
Your retry logic was built on an assumption that just broke: that doing the thing twice is harmless. It is not. A timeout on place_order() is genuinely ambiguous: did the order go through? Retrying blindly is how one purchase becomes two. The fix has a name (idempotency) and it lives on page 02.
When an agent buys the wrong thing, somebody eats the cost: the customer, the merchant, the agent's operator, or the payment provider. That allocation is decided by contracts and by what can be proven, which is why “what did the user authorize?” must be a question the system can answer, not a question the lawyers argue about afterward.
Two different questions, often confused.
From the store's side, a helpful agent and a scraping bot look similar: automated traffic, no human rhythm, no mouse movement. Years of fraud tooling was tuned to block exactly that pattern. Merchants now need a way to tell “a customer's agent, acting with permission” apart from abuse, and to keep the sale rather than refuse it.
This is the shape of nearly every agentic purchase. Click a node: each one tells you what goes wrong there and who ends up holding the cost.
The amber node is the last cheap place to be wrong. Everything above it can be redone for free; everything below it costs money to undo.
Work down the diagram. For each step, ask the two questions this page keeps repeating: what can go wrong here, and who pays when it does.
In September 2025 two overlapping proposals appeared for making agent-initiated payments work: AP2, announced by Google with a set of payments and technology partners, and ACP, published by Stripe and OpenAI. In January 2026 Google added UCP, co-developed with Shopify, Etsy, Wayfair, Target and Walmart, which covers the whole shopping conversation rather than the payment alone. All three are early, all three are still changing, and they solve related but different problems. Treat what follows as a snapshot (checked November 2, 2026), not a settled answer.
Google's announcement frames AP2 as an open protocol for payments initiated by agents, built around mandates: signed, verifiable records of what the human authorized (the intent, the cart, and the payment), expressed as W3C Verifiable Credentials. The point is that a merchant or an issuer downstream can check the permission slip rather than take the agent's word for it, and that the record survives afterward as evidence of consent. It is positioned to sit alongside agent-to-agent and tool protocols rather than replace them (Google, 2025).
Stripe and OpenAI published ACP as an open standard for agent-initiated checkout: a documented way for an agent to hand a merchant a cart, have the merchant confirm price and availability, and complete payment, with a Shared Payment Token arrangement so the merchant continues to be the merchant of record and keeps its own relationship with the customer, rather than the agent platform taking it over. The specification is published openly (Apache-2.0 on the spec repository) so that merchants and agent builders can implement against the same shapes (OpenAI & Stripe, 2025).
Primary source — the Stripe announcement ↗ · agenticcommerce.dev ↗ · spec repo ↗
Announced by Google at NRF on January 11, 2026 and co-developed with Shopify, Etsy, Wayfair, Target and Walmart, UCP is an open standard for how an agent and a merchant talk from discovery through checkout, identity linking, order status and payment-token exchange. Its messages travel over REST, MCP or A2A, it is designed to work alongside AP2 for the payment leg, and its first home is checkout inside Google’s AI Mode and the Gemini app, paid with Google Pay. Endorsements at launch included Visa, Mastercard, American Express, Stripe and Adyen (Google, 2026).
Primary source — Google’s announcement, Jan 11, 2026 ↗ · under the hood (Google for Developers) ↗ · ucp.dev ↗ · spec repo ↗
| AP2 (Google + partners, Sept 2025) | ACP (Stripe + OpenAI, Sept 2025) | UCP (Google + retailers, Jan 2026) | |
|---|---|---|---|
| Centre of gravity | Payment authorization: proving a human permitted this spend. | The checkout transaction: a common way for an agent and a merchant to complete a sale. | The shopping session end to end: discovery, cart, checkout, order status and identity linking, with the payment leg delegated to AP2 or a network token. |
| How consent is carried | Mandates as verifiable credentials (intent → cart → payment), signed and checkable after the fact. | The buyer's confirmed cart plus a shared payment token scoped to that purchase. | The merchant confirms each step of the checkout; payment arrives as a token the merchant's processor accepts, or as an AP2 mandate. |
| Who most needs to care | Issuers, networks, wallets, and anyone who must answer “was this authorized?” | Merchants and agent platforms wiring up a working buy button inside a conversation. | Retailers and platforms that want to be found and bought from inside AI assistants, starting with Google's. |
| Openness | Published openly by Google with partner input; check the current specification before building. | Specification published on an open repository under Apache-2.0; check the repo for the current version. | Open specification at ucp.dev with an Apache-2.0 repository; co-developed by five retailers and endorsed by payment networks and processors at launch. |
| Maturity (as of this course) | All three are early. They were announced between September 2025 and January 2026, all are still being revised, and they overlap in places and complement each other in others (UCP names AP2 as one of its payment options). Nothing here says one has won, and any page that tells you which one won is guessing. | ||
Meta’s Muse, released on September 8, 2026, is the first mass-market assistant whose job description includes buying things. Follow one Muse purchase from the request to the receipt and you meet every question on this page in order: whose card is this, who approved the spend, and whether the store wanted the agent there at all. Keep one more question running underneath: one day you may manage a company’s website. Will you let agents operate on it?
A code inspection reported by ppc.land on September 9, 2026 found three checkout paths inside the Muse client: a browser mode that types card details into whatever form the merchant presents, a Shopify mode over APIs (assessed, with a hedge, as Shop Pay over the Universal Commerce Protocol), and the Stripe Link path. Three paths, three different answers to “whose card, and who can check the approval?”
Sources: Meta newsroom, Sept 8, 2026 ↗ · CNBC, Oct 3, 2026 ↗ · PCWorld, Sept 25, 2026 ↗ · ppc.land, Sept 9, 2026 ↗
Strip away the brand names and there are four designs. They differ in one thing: how far the credential has moved from “your card, in the agent’s hands” toward “a token for this one purchase that a third party can check.”
A browser agent in form-filling mode (Muse’s browser path, Comet in the Amazon case) shops inside your logged-in account or types the card you stored. To the store it looks like you. Nothing scopes the credential to this purchase, and a planted instruction on the page (Week 10) is now spending your card. Every incident story on page 04 starts here.
Link by Stripe, PayPal, Shop Pay. The wallet holds the real card and issues a single-use number for the one order the human approved; the agent passes the token along without ever seeing a card. Purchase protection and the approval record sit with the wallet, which is why Meta chose this as Muse’s default path.
Visa Intelligent Commerce and Mastercard Agent Pay (both announced in April 2025) extend the tokenization that already powers mobile wallets: a tokenized credential issued to a specific agent, with limits the cardholder set, so the issuer and the network know an agent is paying and can check the limits at authorization time rather than after the dispute.
ACP’s Shared Payment Token (a credential scoped to one agent-initiated purchase, with the merchant staying merchant of record), AP2’s signed mandates (intent, cart, payment), UCP’s checkout with payment-token exchange. The approval travels with the transaction in a form the merchant, the processor and the issuer can each verify.
Sources: Mastercard Agent Pay announcement, Apr 2025 ↗ · Visa Intelligent Commerce, developer page ↗ · Stripe, agentic commerce documentation ↗
Amazon’s complaint against Perplexity turned on one word: disguise. A browser agent that presents itself as Chrome gives the merchant no way to treat it differently, so the merchant’s only options are to serve it as a human or to block everything that looks automated. Two 2025 mechanisms try to give the store a third option.
Sources: Cloudflare blog posts on Web Bot Auth ↗, signed agents ↗ and pay per crawl ↗ · Cloudflare press release, Oct 2025 ↗ · Visa Trusted Agent Protocol on GitHub ↗
Sources: Payments Dive ↗ · GeekWire ↗ · MediaPost ↗ · Engadget ↗
Sources: Stripe, Sept 29, 2025 ↗ · Google, Jan 11, 2026 ↗ · CNBC, Oct 3, 2026 ↗
Two years from now you manage the e-commerce site of a mid-size retailer (pick one: a regional grocer, a furniture brand, a university bookstore, a B2B parts distributor). Shopping agents are a growing share of your traffic and they do not identify themselves. Choose a posture and defend it:
Whatever you choose, write the list of things you would require before an agent may place an order on your site, and the three numbers you would watch in the first month.
Produce: the posture, the requirements list, the three metrics, and one sentence on who pays when an agent-placed order goes wrong.
None of this is settled, which makes it a good place to do original work. Each question below has at least one published starting point.
Papers: The Agentic Economy ↗ · Magentic Marketplace ↗ · Virtual Agent Economies ↗ · SoK: Security of Autonomous LLM Agents in Agentic Commerce ↗ · Protocol-Level Attacks on Agentic Commerce Platforms ↗ · WebShop ↗ · τ-bench ↗ · DeepShop ↗ · UserArena ↗ · Bazaar ↗
Longer, optional: Stripe Developers, The future of agentic payments (15 min, March 2026) ↗ · Shopify Engineering, UCP and agentic commerce (40 min, May 2026) ↗.
“We told the agent not to overspend” is not a control. Each of these lives in code or configuration, outside anything the model can talk its way past: the Week 10 governance lesson, applied to money.
| Control | What it stops | Where it lives |
|---|---|---|
| Spending cap | The runaway: an agent that misreads a price, a quantity, or a loop and spends far past what anyone intended. Caps come in layers: per transaction, per day, per month. | The harness and the payment credential. Enforced before the tool runs, and again by whatever issues the funds. |
| Merchant allow-list | Purchases from places nobody vetted, including the storefront that a poisoned search result invented. If it is not on the list, the call fails. | Tool configuration. The agent cannot add to its own list. |
| Per-transaction mandate | Scope creep between approval and execution: an approval for one item at one price being reused for a different, larger purchase. | The authorization record that travels with the payment. The idea AP2 is trying to standardize. |
| Receipt | Silent action. Every completed purchase produces an artifact a human can read, tied to the approval that permitted it. | Your system of record, plus the customer's inbox. |
| Audit trail | Unanswerable questions later: what did the agent see, what else could it have chosen, why this vendor, who approved it. | Trace storage: the Week 2 evidence standard, retained for as long as a dispute could arrive. |
Do not choose between “fully autonomous” and “ask a human every time.” Sort actions into three rungs, and be explicit about the boundary between them.
Reading a catalog, checking inventory, pricing options, drafting the cart. Nothing here costs anything to undo, so gating it only teaches people to stop reading approvals. Log it; do not interrupt for it.
A repeat purchase of a previously approved item, from an allow-listed vendor, under a fixed per-transaction and monthly limit. The agent may act, but the limit is enforced in code, and hitting the cap raises an alert rather than silently failing.
New vendor, new item, amount above the cap, anything that touches a contract or a subscription. The agent proposes; a named human approves. This rung is small on purpose. A long approval queue is an approval queue nobody reads.