---
type: Agentic Web Standard
title: "Agent Payments Protocol (AP2)"
description: "Did the user actually authorize what this agent is about to buy and pay for, and can the merchant prove it later?"
resource: "https://ap2-protocol.org/ap2/specification/"
tags: ["pay", "endpoint", "industry-body", "agent-checkout", "delegate-user-authority", "audit-agent-actions"]
status: draft
generated: { by: agenticweb-builder/1.0, at: 2026-10-30T00:00:00Z }
verified: { by: process:agenticweb-engine, at: 2026-10-29T00:00:00Z }
stale_after: 2026-11-28T00:00:00Z
sources:
  - id: ref-1
    resource: "https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol"
    title: "Stavan Parikh and Rao Surapaneni, Google Cloud Blog, Announcing Agent Payments Protocol (AP2) (headline \"Powering AI commerce with the new Agent Payments Protocol (AP2)\"), 2025-09-16, checked 2026-10-28: \"Today, Google announced the Agent Payments Protocol (AP2), an open protocol developed with leading payments and technology companies to securely initiate and transact agent-led payments across platforms.\" \"The protocol can be used as an extension of the Agent2Agent (A2A) protocol and Model Context Protocol (MCP).\" \"We're collaborating with a diverse group of more than 60 organizations to help shape the future of agentic payments, including Adyen, American Express, Ant International, Coinbase, Etsy, Forter, Intuit, JCB, Mastercard, Mysten Labs, Paypal, Revolut, Salesforce, ServiceNow, UnionPay International, Worldpay, and more.\" \"AP2 builds trust by using Mandates—tamper-proof, cryptographically-signed digital contracts that serve as verifiable proof of a user's instructions.\" \"These mandates are signed by verifiable credentials (VCs) and act as the foundational evidence for every transaction.\" \"your request is captured in an initial Intent Mandate.\" \"your approval signs a Cart Mandate.\" \"you sign a detailed Intent Mandate upfront.\" \"in collaboration with Coinbase, Ethereum Foundation, MetaMask and other leading organizations, we have extended the core constructs of AP2 and launched the A2A x402 extension, a production-ready solution for agent-based crypto payments.\" \"Mastercard is committed to ongoing, responsible innovation – and we are excited to be collaborating with Google, leading banks, merchants, AI platforms and other industry leaders to help shape the future of agentic commerce.\" \"American Express is excited to contribute to the creation of AP2 as a protocol intended to protect customers and enable participation in the next generation of digital payments.\" \"The AP2 protocol represents a meaningful first step in defining how agents, merchants, and payment providers can transact securely, at scale.\""
    last_modified: 2025-09-16T00:00:00Z
  - id: ref-2
    resource: "https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/"
    title: "Stavan Parikh, Google blog, Google donates Agent Payments Protocol to FIDO Alliance, 2026-04-28, checked 2026-10-28: \"we're donating the Agent Payments Protocol (AP2) to the FIDO Alliance, a renowned industry association focused on creating open standards.\" \"Transitioning ownership to the FIDO Alliance ensures AP2 remains platform-agnostic and community-led, while accelerating adoption of secure agentic payments.\" \"Today on GitHub, we're also releasing AP2 v.0.2, which introduces critical updates for autonomous transactions, including \"Human Not Present\" payments, which will allow agents to securely execute payments autonomously — like securing and purchasing limited-run tickets the moment they're on sale — based on pre-authorized user instructions.\""
    last_modified: 2026-04-28T00:00:00Z
  - id: ref-3
    resource: "https://fidoalliance.org/fido-alliance-to-develop-standards-for-trusted-ai-agent-interactions/"
    title: "FIDO Alliance, FIDO Alliance to Develop Standards for Trusted AI Agent Interactions (press release), 2026-04-28, checked 2026-10-28: \"In parallel, the FIDO Alliance is developing specifications for agent-initiated commerce within its Payments Technical Working Group, chaired by members from Mastercard and Visa.\" \"Google has contributed its Agent Payments Protocol (AP2), which introduces a model for secure delegation, verifiable authorization and trusted transaction execution.\" \"These contributions will be reviewed and further developed through the FIDO Alliance's collaborative standards process within the Payments Technical Working Group.\" \"Mastercard has contributed its Verifiable Intent framework, co-developed with Google and designed to work with AP2, enabling users to securely authorize and control actions performed by digital agents on their behalf.\""
    last_modified: 2026-04-28T00:00:00Z
  - id: ref-4
    resource: "https://www.w3.org/2026/09/ecommerce-agents/slides/Jean_Luc_Di_Manno_FIDO.pdf"
    title: "FIDO Alliance, slide deck hosted by W3C (file Jean_Luc_Di_Manno_FIDO.pdf, created 2026-09-09), slide \"FIDO Agentic Payment Specifications\", checked 2026-10-28: \"September 2026: AP2/VI specs moved to public repository for review.\" \"Targeting End 2026: Harmonize AP2 and VI specifications. Mid-2027: Publish first version of consolidated specifications.\""
    last_modified: 2026-09-09T00:00:00Z
  - id: ref-5
    resource: "https://api.github.com/repos/google-agentic-commerce/AP2"
    title: "GitHub, google-agentic-commerce/AP2 repository metadata (API): created 2025-05-30, licence Apache-2.0, homepage https://ap2-protocol.org/, checked 2026-10-28"
    last_modified: 2025-05-30T00:00:00Z
  - id: ref-6
    resource: "https://github.com/google-agentic-commerce/AP2/releases"
    title: "Google, Releases · google-agentic-commerce/AP2: v0.1.0 published 2025-09-16, v0.2.0 published 2026-04-28; the only two tags (text checked at the GitHub API copy), checked 2026-10-28: \"Create Agent Payments Protocol (AP2)\" \"This is the second release of AP2. It focuses on providing Human Not Present flows.\""
    last_modified: 2026-04-28T00:00:00Z
  - id: ref-7
    resource: "https://github.com/google-agentic-commerce/AP2"
    title: "Google, google-agentic-commerce/AP2 (README on main) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: \"This repository contains code samples and demos of the Agent Payments Protocol.\" \"A PyPI package will be published at a later time.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-8
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/ap2/specification.md"
    title: "Google, Agentic Payment Protocol (v0.2), docs/ap2/specification.md on main, checked 2026-10-28: \"The Agentic Payment Protocol (AP2) provides a protocol to secure Agent-performed payment transactions. It makes use of the Agent Authorization model.\" \"AP2 operates as a security feature within a Commerce Protocol.\" \"AP2 is designed explicitly to be compatible with the Universal Commerce Protocol (UCP) and integrates seamlessly.\" \"AP2 defines two Mandate types: Checkout Mandate and Payment Mandate.\" \"The Trusted Surface role is a UI surface that is trusted to get informed user consent for an Intent before creating a user-signed Mandate.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-9
    resource: "https://ap2-protocol.org/ap2/specification/"
    title: "AP2 documentation site, Agent Payments Protocol - AP2 - Agent Payments Protocol Documentation (rendered specification), checked 2026-10-28: \"Agentic Payment Protocol (v0.2)\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-10
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/index.md"
    title: "Google, AP2 docs/index.md on main, checked 2026-10-28: \"Our public GitHub repo hosts the lastest version of AP2 specification, documentation and SDK.\" \"Standardization of the specification will continue within the Agentic Authentication Technical and Payments Technical Working Groups in FIDO.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-11
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/faq.md"
    title: "Google, AP2 docs/faq.md on main, checked 2026-10-28: \"We are working on an SDK and a MCP server right now, in collaboration with payment service providers. Check back soon.\" \"While the Universal Commerce Protocol orchestrates the broader purchase lifecycle, AP2 is the specialized payment layer responsible for authorizing and signing transactions.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-12
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/ap2/agent_authorization.md"
    title: "Google, AP2 docs/ap2/agent_authorization.md on main, checked 2026-10-28: \"The Mandate Content for SD-JWTs contains the following claims:\" \"While this document uses SD-JWT VCs, other VDCs such as ISO mDocs COULD\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-13
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/ap2/checkout_mandate.md"
    title: "Google, AP2 docs/ap2/checkout_mandate.md on main, checked 2026-10-28: \"The Checkout Mandate is a Mandate used for authorizing the completion of a checkout.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-14
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/specification.md"
    title: "Google, AP2 v0.1.0 docs/specification.md, checked 2026-10-28: \"The primary VCs in this framework are the Cart Mandate, the Intent Mandate and the Payment Mandate.\" \"It serves as the final, non-repudiable authorization to execute a purchase in the user's absence.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-15
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/a2a-extension.md"
    title: "Google, AP2 v0.1.0 docs/a2a-extension.md (A2A extension, v0.1), checked 2026-10-28: \"The URI for this extension is https://github.com/google-agentic-commerce/ap2/tree/v0.1.\" \"Agents that support the AP2 extension MUST use this URI.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-16
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/topics/ap2-a2a-and-mcp.md"
    title: "Google, AP2 v0.1.0 docs/topics/ap2-a2a-and-mcp.md, checked 2026-10-28: \"The Agent Payments Protocol (AP2) is designed to be an extension of the Agent-to-Agent (A2A) protocol and work in concert with Model-Context Protocol (MCP).\" \"We are working on MCP servers for AP2.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-17
    resource: "https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/topics/ap2-and-x402.md"
    title: "Google, AP2 v0.1.0 docs/topics/ap2-and-x402.md, checked 2026-10-28: \"AP2 is designed to support emerging payment methods like x402\" \"which is an implementation of A2A in conjunction with the x402 standard. We will be aligning this closely with AP2 over time to make it easy to compose solutions which include all payment methods, including digital currencies.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-18
    resource: "https://github.com/google-agentic-commerce/a2a-x402"
    title: "Google, google-agentic-commerce/a2a-x402 (README) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: \"The A2A x402 Extension brings cryptocurrency payments to the Agent-to-Agent (A2A) protocol, enabling agents to monetize their services through on-chain payments.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-19
    resource: "https://singlefax.com/ap2.md"
    title: "SingleFax, SingleFax AP2 payments (ap2.md), checked 2026-10-29: \"AP2 v0.2 and purchases without the user present are not negotiated.\" \"This flow accepts Stripe Shared Payment Tokens (SPTs); it does not spend saved cards or existing account credit.\""
    last_modified: 2026-10-29T00:00:00Z
  - id: ref-20
    resource: "https://singlefax.com/.well-known/agent-card.json"
    title: "SingleFax (Monocube LLC), SingleFax A2A agent card, checked 2026-10-28"
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-21
    resource: "https://api.algovoi.co.uk/ap2/extensions"
    title: "AlgoVoi, AP2 extensions endpoint, checked 2026-10-28: \"Adds multi-chain blockchain payment methods to AP2 v0.1: Algorand, VOI, Hedera, Stellar, Base, Solana, Tempo, and ARC.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-22
    resource: "https://api.algovoi.co.uk/.well-known/agent-card.json"
    title: "AlgoVoi, AlgoVoi Payment Agent A2A agent card, checked 2026-10-28: \"gates access to resources using x402, MPP (IETF), or AP2 (Google Agentic Payments) protocols.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-23
    resource: "https://api.algovoi.co.uk/openapi.json"
    title: "AlgoVoi, AlgoVoi Gateway OpenAPI document, checked 2026-10-28"
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-24
    resource: "https://developer.paypal.com/community/blog/PayPal-Agent-Payments-Protocol/"
    title: "Prakhar Mehrotra, PayPal Developer Community Blog, Agent Payments Protocol: Building Verifiable Trust for Agentic Commerce, 2025-09-16 (the live page served a captcha to scripted fetches on 2026-10-28, so this quote was checked against an Exa API fetch of the same URL; the earlier direct fetch the same day had the same text), checked 2026-10-28: \"Today, PayPal announced its support for the Agent Payments Protocol (AP2), an open, interoperable extension to Agent2Agent (A2A) protocol and the Model Context Protocol (MCP) that defines a common standard for agent-driven payments.\""
    last_modified: 2025-09-16T00:00:00Z
  - id: ref-25
    resource: "https://www.adyen.com/knowledge-hub/adyen-google-collaborate-agent-payments"
    title: "Adyen, Adyen to Collaborate with Google on Agent Payments Protocol, 2025-09-16, checked 2026-10-28: \"Today, Adyen is proud to take our relationship a step further as a collaborator on Google's initiative developing the Agent Payments Protocol, a new open framework that enables AI agents to securely initiate and transact payments.\""
    last_modified: 2025-09-16T00:00:00Z
  - id: ref-26
    resource: "https://www.coinbase.com/developer-platform/discover/launches/google_x402"
    title: "Coinbase Developer Platform, Google Agentic Payments Protocol + x402: Agents Can Now Actually Pay Each Other, 2025-09-16, checked 2026-10-28: \"Agents can already talk to each other. And now, with x402 within Google's new AP2, they can pay each other too.\""
    last_modified: 2025-09-16T00:00:00Z
  - id: ref-27
    resource: "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol"
    title: "OpenAI and Stripe, agentic-commerce-protocol/agentic-commerce-protocol (README) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: \"The specification is maintained by OpenAI and Stripe and is currently in beta.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-28
    resource: "https://github.com/visa/trusted-agent-protocol"
    title: "Visa, visa/trusted-agent-protocol (README) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: \"Visa's Trusted Agent Protocol provides a standardized, cryptographic method for an AI agent to prove its identity and associated authorization directly to merchants.\""
    last_modified: 2026-10-28T00:00:00Z
  - id: ref-29
    resource: "https://thepaypers.com/payments/news/google-donates-agent-payments-protocol-to-fido-alliance"
    title: "Sinziana Albu, The Paypers, Google donates the Agent Payments Protocol to FIDO Alliance, 2026-04-29, checked 2026-10-28: \"Alongside the transfer, Google has published AP2 v0.2 on GitHub, introducing new capabilities for autonomous transactions.\""
    last_modified: 2026-04-29T00:00:00Z
  - id: ref-30
    resource: "https://arxiv.org/abs/2601.22569"
    title: "Tanusree Debi, Wentian Zhu and Pranjol Sen Gupta, arXiv:2601.22569, Whispers of Wealth: Red-Teaming Google's Agent Payments Protocol via Prompt Injection, submitted 2026-01-30, checked 2026-10-28: \"Using a functional AP2 based shopping agent built with Gemini-2.5-Flash and the Google ADK framework, we experimentally validate that simple adversarial prompts can reliably subvert agent behavior.\""
    last_modified: 2026-01-30T00:00:00Z
  - id: ref-31
    resource: "https://arxiv.org/abs/2608.23858"
    title: "Avital Aviv, Parth A. Gandh, Ron Bitton and Asaf Shabtai, arXiv:2608.23858, Beyond the Mandate: A Systematic Security Analysis of the Agent Payments Protocol (AP2), submitted 2026-08-24, checked 2026-10-28: \"Because no complete public AP2 deployment was available, we build a testbed spanning all five architectures and develop five proof-of-concept demonstrations covering all eight High-risk threats and their mitigations.\" \"Our analysis shows that valid mandate signatures alone do not ensure that an agent-mediated transaction reflects the user's intent when its pre-authorization context is manipulated.\""
    last_modified: 2026-08-24T00:00:00Z
  - id: ref-32
    resource: "https://ucp.dev/latest/specification/payment/extensions/ap2-mandates/"
    title: "Universal Commerce Protocol, AP2 Mandates Extension, specification version 2026-08-25 (\"latest\"), checked 2026-10-29: \"Businesses declare support by adding dev.ucp.common.payment.ap2_mandate to their capabilities list in /.well-known/ucp.\" \"The business MUST include ap2.merchant_authorization in all checkout responses.\" \"The business MUST NOT accept a complete_checkout request that lacks ap2.checkout_mandate.\""
    last_modified: 2026-10-29T00:00:00Z
  - id: ref-33
    resource: "https://ucp.dev/2026-01-11/specification/ap2-mandates/"
    title: "Universal Commerce Protocol, AP2 Mandates Extension, specification version 2026-01-11, checked 2026-10-29: \"dev.ucp.shopping.ap2_mandate\""
    last_modified: 2026-10-29T00:00:00Z
  - id: ref-34
    resource: "https://www.allbirds.com/.well-known/ucp"
    title: "www.allbirds.com, UCP profile at /.well-known/ucp (JSON), checked 2026-10-29: \"\"version\":\"2026-08-25\"\""
    last_modified: 2026-10-29T00:00:00Z
  - id: ref-35
    resource: "https://www.ikea.com/.well-known/ucp"
    title: "www.ikea.com, UCP profile at /.well-known/ucp (JSON), checked 2026-10-29: \"\"version\":\"2026-08-25\"\""
    last_modified: 2026-10-29T00:00:00Z
---

# Agent Payments Protocol (AP2)

Agent Payments Protocol (AP2) is an agentic-web standard (endpoint) at step 7, Pay, governed by FIDO Alliance, since Google donated AP2 on 2026-04-28; its status is "Pre-1.0". It answers: "Did the user actually authorize what this agent is about to buy and pay for, and can the merchant prove it later?" Replacing or extending Signed payment authorization / purchase order, implementation status is multi-implementation (Google), last verified 2026-10-29.

# Overview

AP2 gives merchants, payment providers and credential providers signed proof of what a user authorised an AI agent to buy and pay for; that proof takes the form of mandates, which Google describes as "AP2 builds trust by using Mandates—tamper-proof, cryptographically-signed digital contracts that serve as verifiable proof of a user's instructions." [^ref-1]. Version 0.1 defined three mandates as verifiable credentials, the Intent, Cart and Payment Mandates [^ref-14], while version 0.2 defines two, the Checkout Mandate and the Payment Mandate, which the user signs through a Trusted Surface that must not be an agent [^ref-8]. Google launched AP2 as an extension of the Agent2Agent (A2A) protocol and the Model Context Protocol (MCP) [^ref-1][^ref-16], and v0.2 positions it as the payment-authorisation layer inside a commerce protocol, built to work with the Universal Commerce Protocol (UCP) [^ref-8][^ref-11]. Crypto payments go through a separate A2A x402 extension, which Google launched with Coinbase, the Ethereum Foundation, MetaMask and others [^ref-1][^ref-18].

# Examples

```http
none none
# parse: not applicable — AP2 is a client-side/in-band mandate format, not an origin-exposed endpoint or file
# on absent: There is no generic HTTP probe for AP2: a Merchant, Credential Provider, or Merchant Payment Processor supports AP2 only if it accepts and validates AP2 Checkout/Payment Mandates inside its own commerce protocol's message flow (e.g. as a UCP payment handler), which cannot be detected by an unauthenticated GET against the origin.
```

# Knowledge Graph

* **Lifecycle Step**: [7 Pay](/category/pay/index.md)
* **Components**: [AP2 Checkout Mandate](/okf/protocols/ap2-checkout-mandate.md)
* **Builds on**: [Universal Commerce Protocol (UCP)](/okf/protocols/ucp.md)
* **Depended on by**: [Agent Decision Commitments for Payments](/okf/protocols/agent-decision-commitment.md), [AP2 Checkout Mandate](/okf/protocols/ap2-checkout-mandate.md)
* **Pairs with**: [Universal Commerce Protocol (UCP)](/okf/protocols/ucp.md), [Agentic Commerce Protocol](/okf/protocols/agentic-commerce-protocol.md), [Agent2Agent Protocol (A2A)](/okf/protocols/a2a.md), [Model Context Protocol](/okf/protocols/mcp.md), [x402](/okf/protocols/x402.md), [Machine Payments Protocol (MPP)](/okf/protocols/mpp.md)
* **Related terms**: [Mandate](/okf/terms/mandate.md), [Human Not Present](/okf/terms/human-not-present.md), [Verifiable Intent](/okf/terms/verifiable-intent.md), [Buyer of Record & Merchant of Record (Agentic Commerce)](/okf/terms/buyer-of-record.md)
* **Compared in**: [3-D Secure & Card Checkout vs AP2, ACP & UCP (classic vs agentic)](/compare/3d-secure-vs-ap2/index.md), [x402 vs Agent Payments Protocol (AP2)](/compare/x402-vs-ap2/index.md), [Agent Payments Protocol (AP2) vs Agentic Commerce Protocol](/compare/ap2-vs-agentic-commerce-protocol/index.md), [Agent Payments Protocol (AP2) vs Universal Commerce Protocol (UCP)](/compare/ap2-vs-ucp/index.md), [Agent Payments Protocol (AP2) vs EMV® Agentic Payments – Framework for Specifications](/compare/ap2-vs-emv-agentic-payments/index.md), [Verifiable Intent vs Agent Payments Protocol (AP2)](/compare/vi-vs-ap2/index.md), [KYAPay Token vs Agent Payments Protocol (AP2)](/compare/kyapay-token-vs-ap2/index.md), [Agent Commerce Kit (ACK) vs Agent Payments Protocol (AP2)](/compare/agent-commerce-kit-vs-ap2/index.md)

[^ref-1]: Stavan Parikh and Rao Surapaneni, Google Cloud Blog, Announcing Agent Payments Protocol (AP2) (headline "Powering AI commerce with the new Agent Payments Protocol (AP2)"), 2025-09-16, checked 2026-10-28: "Today, Google announced the Agent Payments Protocol (AP2), an open protocol developed with leading payments and technology companies to securely initiate and transact agent-led payments across platforms." "The protocol can be used as an extension of the Agent2Agent (A2A) protocol and Model Context Protocol (MCP)." "We're collaborating with a diverse group of more than 60 organizations to help shape the future of agentic payments, including Adyen, American Express, Ant International, Coinbase, Etsy, Forter, Intuit, JCB, Mastercard, Mysten Labs, Paypal, Revolut, Salesforce, ServiceNow, UnionPay International, Worldpay, and more." "AP2 builds trust by using Mandates—tamper-proof, cryptographically-signed digital contracts that serve as verifiable proof of a user's instructions." "These mandates are signed by verifiable credentials (VCs) and act as the foundational evidence for every transaction." "your request is captured in an initial Intent Mandate." "your approval signs a Cart Mandate." "you sign a detailed Intent Mandate upfront." "in collaboration with Coinbase, Ethereum Foundation, MetaMask and other leading organizations, we have extended the core constructs of AP2 and launched the A2A x402 extension, a production-ready solution for agent-based crypto payments." "Mastercard is committed to ongoing, responsible innovation – and we are excited to be collaborating with Google, leading banks, merchants, AI platforms and other industry leaders to help shape the future of agentic commerce." "American Express is excited to contribute to the creation of AP2 as a protocol intended to protect customers and enable participation in the next generation of digital payments." "The AP2 protocol represents a meaningful first step in defining how agents, merchants, and payment providers can transact securely, at scale." (https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol)
[^ref-2]: Stavan Parikh, Google blog, Google donates Agent Payments Protocol to FIDO Alliance, 2026-04-28, checked 2026-10-28: "we're donating the Agent Payments Protocol (AP2) to the FIDO Alliance, a renowned industry association focused on creating open standards." "Transitioning ownership to the FIDO Alliance ensures AP2 remains platform-agnostic and community-led, while accelerating adoption of secure agentic payments." "Today on GitHub, we're also releasing AP2 v.0.2, which introduces critical updates for autonomous transactions, including "Human Not Present" payments, which will allow agents to securely execute payments autonomously — like securing and purchasing limited-run tickets the moment they're on sale — based on pre-authorized user instructions." (https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/)
[^ref-3]: FIDO Alliance, FIDO Alliance to Develop Standards for Trusted AI Agent Interactions (press release), 2026-04-28, checked 2026-10-28: "In parallel, the FIDO Alliance is developing specifications for agent-initiated commerce within its Payments Technical Working Group, chaired by members from Mastercard and Visa." "Google has contributed its Agent Payments Protocol (AP2), which introduces a model for secure delegation, verifiable authorization and trusted transaction execution." "These contributions will be reviewed and further developed through the FIDO Alliance's collaborative standards process within the Payments Technical Working Group." "Mastercard has contributed its Verifiable Intent framework, co-developed with Google and designed to work with AP2, enabling users to securely authorize and control actions performed by digital agents on their behalf." (https://fidoalliance.org/fido-alliance-to-develop-standards-for-trusted-ai-agent-interactions/)
[^ref-4]: FIDO Alliance, slide deck hosted by W3C (file Jean_Luc_Di_Manno_FIDO.pdf, created 2026-09-09), slide "FIDO Agentic Payment Specifications", checked 2026-10-28: "September 2026: AP2/VI specs moved to public repository for review." "Targeting End 2026: Harmonize AP2 and VI specifications. Mid-2027: Publish first version of consolidated specifications." (https://www.w3.org/2026/09/ecommerce-agents/slides/Jean_Luc_Di_Manno_FIDO.pdf)
[^ref-5]: GitHub, google-agentic-commerce/AP2 repository metadata (API): created 2025-05-30, licence Apache-2.0, homepage https://ap2-protocol.org/, checked 2026-10-28 (https://api.github.com/repos/google-agentic-commerce/AP2)
[^ref-6]: Google, Releases · google-agentic-commerce/AP2: v0.1.0 published 2025-09-16, v0.2.0 published 2026-04-28; the only two tags (text checked at the GitHub API copy), checked 2026-10-28: "Create Agent Payments Protocol (AP2)" "This is the second release of AP2. It focuses on providing Human Not Present flows." (https://github.com/google-agentic-commerce/AP2/releases)
[^ref-7]: Google, google-agentic-commerce/AP2 (README on main) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: "This repository contains code samples and demos of the Agent Payments Protocol." "A PyPI package will be published at a later time." (https://github.com/google-agentic-commerce/AP2)
[^ref-8]: Google, Agentic Payment Protocol (v0.2), docs/ap2/specification.md on main, checked 2026-10-28: "The Agentic Payment Protocol (AP2) provides a protocol to secure Agent-performed payment transactions. It makes use of the Agent Authorization model." "AP2 operates as a security feature within a Commerce Protocol." "AP2 is designed explicitly to be compatible with the Universal Commerce Protocol (UCP) and integrates seamlessly." "AP2 defines two Mandate types: Checkout Mandate and Payment Mandate." "The Trusted Surface role is a UI surface that is trusted to get informed user consent for an Intent before creating a user-signed Mandate." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/ap2/specification.md)
[^ref-9]: AP2 documentation site, Agent Payments Protocol - AP2 - Agent Payments Protocol Documentation (rendered specification), checked 2026-10-28: "Agentic Payment Protocol (v0.2)" (https://ap2-protocol.org/ap2/specification/)
[^ref-10]: Google, AP2 docs/index.md on main, checked 2026-10-28: "Our public GitHub repo hosts the lastest version of AP2 specification, documentation and SDK." "Standardization of the specification will continue within the Agentic Authentication Technical and Payments Technical Working Groups in FIDO." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/index.md)
[^ref-11]: Google, AP2 docs/faq.md on main, checked 2026-10-28: "We are working on an SDK and a MCP server right now, in collaboration with payment service providers. Check back soon." "While the Universal Commerce Protocol orchestrates the broader purchase lifecycle, AP2 is the specialized payment layer responsible for authorizing and signing transactions." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/faq.md)
[^ref-12]: Google, AP2 docs/ap2/agent_authorization.md on main, checked 2026-10-28: "The Mandate Content for SD-JWTs contains the following claims:" "While this document uses SD-JWT VCs, other VDCs such as ISO mDocs COULD" (https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/ap2/agent_authorization.md)
[^ref-13]: Google, AP2 docs/ap2/checkout_mandate.md on main, checked 2026-10-28: "The Checkout Mandate is a Mandate used for authorizing the completion of a checkout." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/main/docs/ap2/checkout_mandate.md)
[^ref-14]: Google, AP2 v0.1.0 docs/specification.md, checked 2026-10-28: "The primary VCs in this framework are the Cart Mandate, the Intent Mandate and the Payment Mandate." "It serves as the final, non-repudiable authorization to execute a purchase in the user's absence." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/specification.md)
[^ref-15]: Google, AP2 v0.1.0 docs/a2a-extension.md (A2A extension, v0.1), checked 2026-10-28: "The URI for this extension is https://github.com/google-agentic-commerce/ap2/tree/v0.1." "Agents that support the AP2 extension MUST use this URI." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/a2a-extension.md)
[^ref-16]: Google, AP2 v0.1.0 docs/topics/ap2-a2a-and-mcp.md, checked 2026-10-28: "The Agent Payments Protocol (AP2) is designed to be an extension of the Agent-to-Agent (A2A) protocol and work in concert with Model-Context Protocol (MCP)." "We are working on MCP servers for AP2." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/topics/ap2-a2a-and-mcp.md)
[^ref-17]: Google, AP2 v0.1.0 docs/topics/ap2-and-x402.md, checked 2026-10-28: "AP2 is designed to support emerging payment methods like x402" "which is an implementation of A2A in conjunction with the x402 standard. We will be aligning this closely with AP2 over time to make it easy to compose solutions which include all payment methods, including digital currencies." (https://raw.githubusercontent.com/google-agentic-commerce/AP2/v0.1.0/docs/topics/ap2-and-x402.md)
[^ref-18]: Google, google-agentic-commerce/a2a-x402 (README) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: "The A2A x402 Extension brings cryptocurrency payments to the Agent-to-Agent (A2A) protocol, enabling agents to monetize their services through on-chain payments." (https://github.com/google-agentic-commerce/a2a-x402)
[^ref-19]: SingleFax, SingleFax AP2 payments (ap2.md), checked 2026-10-29: "AP2 v0.2 and purchases without the user present are not negotiated." "This flow accepts Stripe Shared Payment Tokens (SPTs); it does not spend saved cards or existing account credit." (https://singlefax.com/ap2.md)
[^ref-20]: SingleFax (Monocube LLC), SingleFax A2A agent card, checked 2026-10-28 (https://singlefax.com/.well-known/agent-card.json)
[^ref-21]: AlgoVoi, AP2 extensions endpoint, checked 2026-10-28: "Adds multi-chain blockchain payment methods to AP2 v0.1: Algorand, VOI, Hedera, Stellar, Base, Solana, Tempo, and ARC." (https://api.algovoi.co.uk/ap2/extensions)
[^ref-22]: AlgoVoi, AlgoVoi Payment Agent A2A agent card, checked 2026-10-28: "gates access to resources using x402, MPP (IETF), or AP2 (Google Agentic Payments) protocols." (https://api.algovoi.co.uk/.well-known/agent-card.json)
[^ref-23]: AlgoVoi, AlgoVoi Gateway OpenAPI document, checked 2026-10-28 (https://api.algovoi.co.uk/openapi.json)
[^ref-24]: Prakhar Mehrotra, PayPal Developer Community Blog, Agent Payments Protocol: Building Verifiable Trust for Agentic Commerce, 2025-09-16 (the live page served a captcha to scripted fetches on 2026-10-28, so this quote was checked against an Exa API fetch of the same URL; the earlier direct fetch the same day had the same text), checked 2026-10-28: "Today, PayPal announced its support for the Agent Payments Protocol (AP2), an open, interoperable extension to Agent2Agent (A2A) protocol and the Model Context Protocol (MCP) that defines a common standard for agent-driven payments." (https://developer.paypal.com/community/blog/PayPal-Agent-Payments-Protocol/)
[^ref-25]: Adyen, Adyen to Collaborate with Google on Agent Payments Protocol, 2025-09-16, checked 2026-10-28: "Today, Adyen is proud to take our relationship a step further as a collaborator on Google's initiative developing the Agent Payments Protocol, a new open framework that enables AI agents to securely initiate and transact payments." (https://www.adyen.com/knowledge-hub/adyen-google-collaborate-agent-payments)
[^ref-26]: Coinbase Developer Platform, Google Agentic Payments Protocol + x402: Agents Can Now Actually Pay Each Other, 2025-09-16, checked 2026-10-28: "Agents can already talk to each other. And now, with x402 within Google's new AP2, they can pay each other too." (https://www.coinbase.com/developer-platform/discover/launches/google_x402)
[^ref-27]: OpenAI and Stripe, agentic-commerce-protocol/agentic-commerce-protocol (README) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: "The specification is maintained by OpenAI and Stripe and is currently in beta." (https://github.com/agentic-commerce-protocol/agentic-commerce-protocol)
[^ref-28]: Visa, visa/trusted-agent-protocol (README) (text checked at the raw.githubusercontent.com copy), checked 2026-10-28: "Visa's Trusted Agent Protocol provides a standardized, cryptographic method for an AI agent to prove its identity and associated authorization directly to merchants." (https://github.com/visa/trusted-agent-protocol)
[^ref-29]: Sinziana Albu, The Paypers, Google donates the Agent Payments Protocol to FIDO Alliance, 2026-04-29, checked 2026-10-28: "Alongside the transfer, Google has published AP2 v0.2 on GitHub, introducing new capabilities for autonomous transactions." (https://thepaypers.com/payments/news/google-donates-agent-payments-protocol-to-fido-alliance)
[^ref-30]: Tanusree Debi, Wentian Zhu and Pranjol Sen Gupta, arXiv:2601.22569, Whispers of Wealth: Red-Teaming Google's Agent Payments Protocol via Prompt Injection, submitted 2026-01-30, checked 2026-10-28: "Using a functional AP2 based shopping agent built with Gemini-2.5-Flash and the Google ADK framework, we experimentally validate that simple adversarial prompts can reliably subvert agent behavior." (https://arxiv.org/abs/2601.22569)
[^ref-31]: Avital Aviv, Parth A. Gandh, Ron Bitton and Asaf Shabtai, arXiv:2608.23858, Beyond the Mandate: A Systematic Security Analysis of the Agent Payments Protocol (AP2), submitted 2026-08-24, checked 2026-10-28: "Because no complete public AP2 deployment was available, we build a testbed spanning all five architectures and develop five proof-of-concept demonstrations covering all eight High-risk threats and their mitigations." "Our analysis shows that valid mandate signatures alone do not ensure that an agent-mediated transaction reflects the user's intent when its pre-authorization context is manipulated." (https://arxiv.org/abs/2608.23858)
[^ref-32]: Universal Commerce Protocol, AP2 Mandates Extension, specification version 2026-08-25 ("latest"), checked 2026-10-29: "Businesses declare support by adding dev.ucp.common.payment.ap2_mandate to their capabilities list in /.well-known/ucp." "The business MUST include ap2.merchant_authorization in all checkout responses." "The business MUST NOT accept a complete_checkout request that lacks ap2.checkout_mandate." (https://ucp.dev/latest/specification/payment/extensions/ap2-mandates/)
[^ref-33]: Universal Commerce Protocol, AP2 Mandates Extension, specification version 2026-01-11, checked 2026-10-29: "dev.ucp.shopping.ap2_mandate" (https://ucp.dev/2026-01-11/specification/ap2-mandates/)
[^ref-34]: www.allbirds.com, UCP profile at /.well-known/ucp (JSON), checked 2026-10-29: ""version":"2026-08-25"" (https://www.allbirds.com/.well-known/ucp)
[^ref-35]: www.ikea.com, UCP profile at /.well-known/ucp (JSON), checked 2026-10-29: ""version":"2026-08-25"" (https://www.ikea.com/.well-known/ucp)