Agentic commerce needs an identity layer: Visa TAP, Google AP2, and Mastercard Agent Pay
Blog post from Didit
Emerging standards like Visa Trusted Agent Protocol (TAP), Google Agent Payments Protocol (AP2), and Mastercard Agent Pay aim to make agent-led commerce safer by addressing various aspects of trust in transactions. TAP helps merchants recognize and verify approved agents, AP2 focuses on creating authorization evidence for user-intended purchases, and Agent Pay emphasizes agent recognition and payment credential security using tokenization. Despite these advances, there remains a need for identity proofing, risk screening, and compliance controls to ensure transaction legitimacy. Didit offers a neutral infrastructure for identity and fraud verification, with a Model Context Protocol (MCP) server that provides tools for identity verification and fraud checks, supporting these standards without being tied to any specific payment network. Developers are encouraged to consider necessary controls, such as enrollment, credential binding, and runtime risk decisions, when implementing these standards. Didit's offerings, including a REST API and an MCP server, provide flexible solutions for integrating identity verification into agent-driven payment processes, ensuring a layered and adaptable architecture that supports evolving standards.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.