MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

Visa Trusted Agent Protocol (TAP)

Industryspecificationcore entry

Verified 2026-10-14. Status as of 2026-10-14. All entries.

Seams: S3

Status

Specification and sample code published by Visa under Visa Product Terms of October 10, 2025; the product page, read in a browser on 2026-10-14, still says "This product is in the process of development and deployment."

Relevance

The merchant specification says "this protocol is applicable to the scenario when the Agent is initially unknown to the Merchant." It defines three signatures: an agent recognition signature based on HTTP Message Signatures (RFC 9421) and aligned with web-bot-auth, a signed consumer or device identity and a signed payment container.

The product page is headed "Enhancing Visa Intelligent Commerce to improve merchant visibility.", so the protocol is presented as the merchant-facing recognition part of a wider Visa programme (read in a browser on 2026-10-14); this version has no entry for Visa Intelligent Commerce. A merchant or its site protection provider verifies them; the sample repository calls the protocol "a standardized, cryptographic method for an AI agent to prove its identity and associated authorization directly to merchants."

Committed next

None declared in the sources read.

Boundary

"Merchants are not required to use this proposal and do not necessarily have to be registered with the Payment Schemes".

Sources

Overlaps

IETF Web Bot Auth (webbotauth WG), Mastercard Agent Pay, Verifiable Intent, AAIF Agentic Commerce Working Group

Neighbours in the map

Neighbours of Visa Trusted Agent Protocol (TAP) in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (5)Share a seam (11)IETF Web Bot Auth (webbotauth WG) (IETF, core)IETF Web Bot Auth AAIF Agentic Commerce Working Group (AAIF, core)AAIF Agentic Commerce W… FIDO Alliance agentic authentication and payments work (Industry, context)FIDO Alliance agentic a… Mastercard Agent Pay (Industry, core)Mastercard Agent Pay Verifiable Intent (Industry, core)Verifiable Intent W3C Agentic Web Working Group (draft charter) (W3C, core)W3C Agentic Web Working… S3 WebMCP (Draft Community Group Report, Web Machine Learning CG) (W3C, context)WebMCP S3 IETF agentproto (Agent Communication Protocols WG) (IETF, core)IETF agentproto S3 x402 (Linux Foundation, core)x402 S3 Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge) (Independent, core)Browser vendor position… S3 OpenID Foundation AuthZEN Working Group (agent authorization drafts AARP and COAZ) (Independent, context)OpenID Foundation AuthZ… S3 Agentic Commerce Protocol (ACP) (Industry, core)Agentic Commerce Protoc… S3 KYAPay (Skyfire) (Industry, core)KYAPay S3 Personal Agent Consent & Trust Protocol (PACT), published by Decagon with Instinct (Industry, core)Personal Agent Consent… S3 Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta (Industry, core)Personal Agent Protocol S3 Universal Commerce Protocol (UCP) (Industry, core)Universal Commerce Prot… S3 Visa Trusted Agent Protocol

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
developer.visa.com (product page, merchant specifications, product terms), read in a browser on 2026-10-14 from saved copies; docs index and sample code repository (log, tree, README), 2026-10-03; terms grant a "nontransferable, revocable, limited license".
Not read
Code, Client Implementation Guide (not public), other Visa documents.
Not found
Standards-body submission: not found in Visa pages, repository 2026-10-03.

Payment comparison row

Owner / governance
Published by Visa under Visa Product Terms of October 10, 2025; the licence is "conditioned upon You implementing the most current version of the Specification in its entirety" (Product Terms, read in a browser on 2026-10-14)
Version and state
Product page: "This product is in the process of development and deployment." (read in a browser on 2026-10-14); version number or date on the specifications page: none visible in the saved text (2026-10-14); release: not found, 2026-10-03
What it signs
Three signatures: agent recognition (header, HTTP Message Signatures), signed consumer/device identity, signed payment container
Who signs
The agent, with a private key; the merchant or site protection provider verifies with the public key from a key store
Receipt or record
no record format found in the merchant specification page (read in a browser on 2026-10-14): audit has no match, and receipt appears once, for data a merchant can use "when providing receipt or order updates" to the consumer; sample README: not found, 2026-10-03
Dispute
not found in the merchant specification page (dispute, chargeback, liability: no match, read in a browser on 2026-10-14) and sample README, 2026-10-03
Source
https://developer.visa.com/capabilities/trusted-agent-protocol/trusted-agent-protocol-specifications