Leadership1 publisher2 min readPublished
Google's AP2 replaces the buy click with a cryptographically signed mandate
Google's Agent Payments Protocol makes an agent's authority to pay a cryptographically signed mandate holding price limits, timing and other conditions. Whoever drafts those conditions is setting spend policy.
The Board Room · Leadership desk
What happened
- Google announced the Agent Payments Protocol, or AP2, an open protocol for agent-led payments that can be used as an extension of the Agent2Agent protocol and the Model Context Protocol.
- Google says it is working with more than 60 organizations on agentic payments, naming Mastercard, American Express, PayPal, Adyen, Worldpay, Coinbase, Salesforce, ServiceNow, Etsy, Intuit and others.
- With a user present, an initial Intent Mandate captures the request and the user's approval of the presented cart signs a Cart Mandate fixing the exact items and price.
- For delegated tasks the user signs an Intent Mandate upfront specifying price limits, timing and other conditions, and the agent generates the Cart Mandate itself once those conditions are met.
Compiled by The Board RoomSomething wrong?How this is made
Why it matters
- decision A company that lets agents buy has to fix numbers before it writes any integration code: the price ceiling, the timing window and the conditions under which an agent may sign a cart with nobody watching.
- exposure A non-repudiable trail is usable by both sides of a dispute, and a payer whose agent bought within limits the payer signed has a weaker case than one whose user never approved anything.
- constraint The collaborator list records participation in shaping the protocol, so a buyer who sees Mastercard or Worldpay on it has no launch date and no support commitment to plan against.
- precedent Offering agent payments as an extension of A2A and MCP moves the question into the protocol stack, so agent-framework choices begin to carry payments consequences.
The difference between the two flows is where the human judgement sits relative to the price. In the delegated case it happens before the price is known: the post's example instruction is "Buy concert tickets the moment they go on sale" [10]. Google describes the resulting sequence, from intent to cart to payment, as a non-repudiable audit trail that answers authorization and authenticity and provides a clear foundation for accountability [11].
That kind of evidence works in both directions. A merchant can produce the signed mandate. So can an acquirer, when a buyer disputes a purchase that its own agent made inside limits the buyer signed in advance.
Google names 16 organizations out of the more than 60 it says it is collaborating with [3][12], roughly a quarter of the group [13], and it describes the relationship as helping to shape the future of agentic payments [3]. It does not say which of them will support AP2, or when [16]. The evidence format is specified in detail: mandates are tamper-proof, cryptographically signed digital contracts, signed by verifiable credentials, and Google says they act as the foundational evidence for every transaction [6].
For a company that has not wired an agent to a payment method, nothing about this week changes. The decision that arrives before any integration is who writes the conditions inside an Intent Mandate and how tight they are. AP2 is payment-agnostic and supports credit and debit cards, stablecoins and real-time bank transfers [5], so that same drafting job has to name the rails an agent may use. Google's shopping example has a customer telling an agent "I really want this jacket in green, and I'm willing to pay up to 20% more for it", and the agent then monitors prices and buys the moment that variant appears [14].
Google's stated reason for building this is that today's payment systems generally assume a human is directly clicking "buy" on a trusted surface, and an agent that can initiate a payment breaks the assumption [8]. AP2 addresses three questions, the post says: authorization, authenticity and accountability [4]. The first two are properties of the signature. The third depends on the price ceiling and the conditions a company put in writing before its agent went shopping. Stavan Parikh, Google's VP/GM for payments, and Rao Surapaneni, VP/GM for the Business Applications Platform at Google Cloud, signed the post [15].
What to watch
- A named collaborator shipping AP2 in production. That would turn the list of 60-plus into evidence of adoption.
- Whether card network and acquirer dispute rules start treating a signed Cart Mandate as authorization evidence.
- A competing agent-payment specification from a non-Google group. That would make this a choice between standards.