Today Google donated the Agent Payments Protocol to the FIDO Alliance, and the headline writes itself. The story underneath is the list of names sitting next to Google in the announcement.
Adyen. American Express. Ant International. Coinbase. Etsy. Forter. Intuit. JCB. Mastercard. Mysten Labs. PayPal. Revolut. Salesforce. ServiceNow. UnionPay International. Worldpay. Sixty organizations in total.
Cross-industry payment infrastructure does not arrive on the same standards-body announcement by accident. The signal is that these specific competitive ecosystems aligned on one agent-payment protocol on the same day. The donation framing is the cover story.
GET WEEKLY WEB STRATEGY TIPS FOR THE AI AGE
Practical strategies for making your website work for AI agents and the humans using it. Podcast episodes, articles, videos. Plus exclusive tools, free for subscribers. No spam.
What Google Donated
AP2 v0.2 published on GitHub today. Two pieces matter for operators reading the announcement.
The first is "Human Not Present" payments. A mechanism for agents to execute pre-authorized transactions when the human owner is not on the call. Google's named example is securing and purchasing limited-run tickets at the moment they go on sale. The general case is any transaction that has to complete on a clock the human cannot be present for.
The second is "Verifiable Intent, Not Inferred Action," co-developed with Mastercard and also donated to FIDO. It is the spec's name for the cryptographic substrate. AP2 implements it through Mandates: user-signed verifiable digital credentials. A Checkout Mandate authorizes the cart and gets shared with the merchant. A Payment Mandate authorizes the payment and gets shared with the credential provider, networks, and merchant payment processor. Each Mandate exists in an Open state (capturing user constraints for autonomous execution) and a Closed state (binding to a finalized transaction). The cryptographic answer to "did the human approve this?" lives inside the protocol now, not inside vendor-specific compliance language.
Both pieces matter because they shift the conversation about agent payments from "can it work" to "what does the audit log look like and who governs the spec." Standards-body governance and tamper-proof intent logs are how regulated payment infrastructure absorbs new transaction classes. The plumbing is now in flight.
The v0.2 release also lands a PaymentReceipt primitive, X402 payment-method support inside the human-in-the-loop samples, and a Go SDK alongside the existing Python one. Each is small on its own. Together they signal that the spec is moving past prototype scope into the surfaces real implementers ask for first: receipts, crypto-rail payment methods, and a second language binding.
The 60-Organization List Is the Story
The spec defines six roles: Shopping Agent, Credential Provider, Merchant, Merchant Payment Processor, Trusted Surface, and Network and Issuer. The 60-organization list maps to those roles in the patterns below.
Walk the list by category and the structural shape comes into view.
The card networks. Mastercard sits at the center as Verifiable Intent co-developer. American Express is in the room. Visa is absent from the announcement copy and already shipping Visa TAP on a parallel track. Three of the four major US card networks are converging on the same agent-payment problem in the same week, with Visa running its own track.
The processors. Adyen, Worldpay, Forter. Three of the largest non-card-network payment infrastructure players in the western world.
The wallets and consumer-payment apps. PayPal, Revolut. PayPal carrying agent-payment language while it ships AP2 support matters. PayPal is one of the few consumer wallets where agents already have a real transaction surface today.
The crypto rails. Coinbase. Mysten Labs, the Sui foundation. Crypto-native settlement infrastructure showing up next to American Express on the same announcement page is the part most non-crypto operators will skim past, and probably should not.
The merchants. Etsy is the named merchant on a payments-protocol announcement. Retailer expectations downstream get signaled by which retailer-side names show up at this stage.
The international networks. JCB anchored in Japan, UnionPay International anchored in China, Ant International as the Alipay parent. Asia-Pacific is at the table from day one. AP2's adoption is being framed cross-jurisdictionally on purpose.
The B2B infrastructure. Intuit, Salesforce, ServiceNow. Agent-payment use cases inside SaaS vendors that handle invoicing, expense, and procurement workflows. The agent-as-buyer surface is not retail-only.
Sixty organizations on a standards announcement is what cross-industry payment infrastructure looks like when the major players decide to align before the first major regulatory frame lands.
What Operators Should Do This Week
The agent-as-buyer transaction surface has a standards-body-governed protocol layer in flight. Practitioners running e-commerce websites should expect the AP2 / FIDO stack to land in their payment-platform vendor's roadmap within the next 6-12 months. Two concrete moves work today.
Read AP2 on GitHub. The v0.2 release notes and the Human Not Present mechanics are public. One afternoon is enough to identify which integration surfaces your platform will need to support: PSP integration, checkout flow modifications, agent-identity verification.
Start the conversation with your payment platform. Ask for their AP2 integration timeline. Ask whether Verifiable Intent support will require merchant-side opt-in or whether it ships as platform-default. Ask what their Human Not Present payment policy looks like, what categories will be allowed, what spending caps will apply by default.
The platforms whose answers are vague today will lose merchant-side adoption to the platforms whose answers are specific. Which payment infrastructure your e-commerce stack runs on is becoming a competitive variable in a way it has not been since Stripe Connect launched.
The Stake
Cross-vendor alignment at standards-body level is how vendor-specific protocols become interoperable infrastructure. AP2 went to FIDO today. Standardization continues inside FIDO's Agentic Authentication Technical and Payments Technical Working Groups. Sixty organizations signed off. The agent-as-buyer protocol layer is now governed by a standards body.
The next layer that ships at this composition decides who runs agentic-commerce infrastructure for the next decade.