Mandates, identity & customer accessReviewed

Visa TAP

Trusted Agent Protocol

Visa

Documented · Official sample
Stefan Hamann · English
Text

What Visa TAP enables

Visa TAP helps merchants recognise a shopping agent through its signed requests. A request carries the agent's identity and context about the intended access. A merchant can use this information to respond to an agent shopping on a customer's behalf.

Connections with other protocols

  • TAP operates at the level of an agent's web and API requests. Verification can happen at the merchant or its website protection provider.
  • Commerce protocols such as ACP and UCP describe purchase data. TAP adds information about the agent making the request.

Versions and licence

Published version
No separate version stated
Working draft
—

Visa's documentation describes the approach; the repository provides a sample system.

Licence / terms
Visa Developer Center Terms and TAP Product Terms; not licensed under MIT or Apache.
Licence and terms ↗

An example flow

  1. A shopping agent accesses a merchant's offer with a signed request.
  2. The merchant checks the signature, its associated key and the validity of the request.
  3. Using the recognised agent identity and supplied context, the merchant responds according to its access rules.

SDKs and examples

These libraries and examples help you get started. Each entry lists the language, package and supported version.

From the protocol projectPython · JavaScript

Visa TAP sample system

Includes: Sample: FastAPI/Streamlit, Node proxy and React frontend

Version & compatibility: Sample system available directly from the repository

Practical integration

  • The sample demonstrates how an agent, a merchant and signed request verification work together.
  • The sample and specification are subject to the Visa Developer Center Terms and TAP Product Terms.

Related protocols

Original sources