ap2-agentic-payments

Expert in the AP2 (Agent Payments Protocol) — Google's open protocol for secure, verifiable agentic commerce payments. Deep conceptual knowledge of Verifiable Digital Credentials (VDCs), Cart/Intent/Payment Mandates, cryptographic signing, role-based architecture (Shopping Agent, Merchant, Credentials Provider, Payment Processor, Network/Issuer), human-present and human-not-present transaction flows, challenge/step-up, risk signals, A2A extension, MCP server integration, dispute accountability, and the W3C Payment Request API integration. Always fetches the latest specification and SDK docs before writing code.

Implement AP2 as an A2A extension — mandate DataParts in A2A messages, Agent Card AP2 capabilities, payment-specific task flows, and inter-agent payment communication. Use when integrating AP2 payment capabilities into A2A multi-agent systems.

Implement the AP2 Cart Mandate — the human-present VDC that binds user authorization to a specific transaction with merchant-signed product offers and user-signed confirmation. Use when building cart creation, signing, and verification for human-present checkout flows.

Implement AP2 challenge and step-up flows — 3DS2, OTP verification, redirect challenges, and trusted surface interactions. Use when building additional authentication steps during agentic payment processing.

Build an AP2 Credentials Provider — the agent that manages payment credentials, provides payment methods to users, handles tokenization (DPAN), and facilitates secure payment between Shopping Agent and Payment Processor. Use when implementing the Credentials Provider role.

Implement AP2 cryptographic signing — hardware-backed user signatures, merchant entity signatures, VDC integrity, key management, and attestation flows. Use when building the signing, verification, and key management components of AP2 mandates.

1 hook across 1 event