Trust & security

Visa Trusted Agent Protocol: how merchants recognise real shopping agents

Listen · 8 min

Narrated by an AI voice. Code examples are on the page.

Short answer

Visa's Trusted Agent Protocol (TAP) is a set of rules that lets a merchant recognise an AI shopping agent Visa has approved. The agent signs each request using the HTTP Message Signatures standard, says whether it is browsing or paying, and can carry optional data about the shopper and the payment. Visa announced it in October 2025, built with Cloudflare, and publishes the specification on its developer site and GitHub.

Key takeaways

  • TAP signatures prove a request came from a Visa-approved agent.
  • Each request is tagged as browsing or paying and expires within minutes.
  • Cloudflare and Akamai can verify TAP for merchants at the edge.

What is Visa's Trusted Agent Protocol?

The Trusted Agent Protocol (TAP) is Visa's framework for letting merchants recognise AI shopping agents that Visa has approved, and tell them apart from other automated traffic.

Visa announced TAP on 14 October 2025 and described it as "establishing a foundational framework for agentic commerce." It was developed with Cloudflare. Visa named early partners giving feedback, including Adyen, Checkout.com, Coinbase, CyberSource, Fiserv, Microsoft, Shopify, Stripe and Worldpay.

The problem it addresses is familiar to any store owner. Bot defenses are built to stop automated visitors, but an AI agent shopping for a real customer is also automated. If your defenses block it, you lose a sale. If they let everything through, you lose control. TAP gives the agent a way to prove who it is, so your site can let the right Trusted Agent traffic in.

Visa publishes TAP on its developer site and on GitHub, where it shares sample code for an agent, a merchant site, a CDN proxy and an agent registry. Visa notes that the initial specifications apply to the Visa network.

How does a Trusted Agent Protocol request work?

The agent signs each request with a private key, and the merchant checks the signature with the agent's public key, which Visa publishes.

TAP is "Built upon the foundational HTTP Message Signature standard," as Visa puts it. That standard is RFC 9421, the same base used by Web Bot Auth. Visa's specification describes two headers:

  • Signature-Input, which lists what was signed and the signature's settings.
  • Signature, which carries the signature itself.

The settings Visa requires include a creation time, an expiry time, a key ID, the signing algorithm, a nonce and a tag. A simplified example of the first header, with placeholder values:

Signature-Input: sig2=("@authority" "@path");created=1735689600;expires=1735690080;keyid="...";alg="Ed25519";nonce="...";tag="agent-browser-auth"

The key ID tells the merchant which public key to fetch. Visa's specification says Visa publishes keys at a well-known location, and merchants may cache them.

What do the browsing and paying tags mean?

They tell you what the agent is doing on this request. Visa's specification defines two:

  • agent-browser-auth for browsing, such as looking at product details, availability and the final cost.
  • agent-payer-auth for paying, at checkout.

This matters because you may want different rules for each. An agent that is only reading your prices is low risk. An agent about to pay needs more care. If neither tag is present, Visa's specification says the message "has not been signed by a trusted agent."

Why do TAP signatures expire so quickly?

Short lifetimes stop someone from copying a signed request and replaying it later.

Visa's specification sets clear limits. The creation and expiry times must be no more than 8 minutes apart, the creation time must be in the past, and the expiry time must be in the future. Merchants should remember nonces seen in the last 8 minutes and block any request that reuses one.

The practical effect: a signature has to be checked live, as each request arrives. A log entry from yesterday cannot tell you whether a signature was valid. That is why most merchants will rely on a CDN or service in front of their site to do the checking.

What else can a TAP request carry?

Besides the signature, an agent can send two optional signed objects in the request body.

  • Consumer recognition. Visa's announcement says TAP can show whether a consumer has an account or has shopped with the merchant before. The specification describes an object with a signed ID token and context such as country and postcode. Identities are not sent in the clear, so a merchant needs its own way to match hashed details to its customer accounts.
  • Payment information. An optional payment container can carry data that fits the merchant's checkout method. Visa's specification says that if verification fails, this content "should not be used for processing any payment."

Both objects reuse the nonce from the request signature, which ties them to that exact request.

Who verifies TAP for merchants?

Your CDN or security provider, in most cases. You are not expected to write signature checks yourself.

  • Cloudflare. In October 2025 Cloudflare wrote that Visa's Trusted Agent Protocol and Mastercard's Agent Pay both use Web Bot Auth, and that Cloudflare would validate these signatures for merchants, checking the headers, timestamps, nonce, tag and signature.
  • Akamai. On 17 December 2025 Akamai and Visa announced that merchants on Akamai can verify AI shopping agents using TAP, including, in the release's words, "whether an agent is browsing or paying."

On the payments side, Visa announced Intelligent Commerce Connect on 8 April 2026, a single integration that it says lets merchants accept payments started through the Trusted Agent Protocol, the Machine Payments Protocol, ACP and UCP. Visa said it was in pilot with select partners. For how TAP fits beside Mastercard and American Express, see how card networks handle AI agents.

What should a merchant do about TAP?

Make sure registered agents can reach you, keep the evidence intact, and set rules by what each agent is doing.

  1. Ask your CDN or bot-protection provider whether it verifies Visa TAP and Web Bot Auth signatures, and how verified agents appear in your rules.
  2. Do not strip the signature headers. Proxies between your CDN and your server should pass Signature and Signature-Input through unchanged.
  3. Treat browsing and paying differently. Allow verified browsing freely. Put limits or human review on agent purchases.
  4. Treat unsigned claims as unverified. A request that only says it is a shopping agent is a claim, not proof. Our AI agent identity guide explains the weaker checks.

How Sill helps

Sill shows you which AI agents and bots visit your site and the pages they read. It verifies signed agent requests (Web Bot Auth) on Cloudflare and WordPress installs, so you see which visitors proved who they are. When an AI agent places an order, your rules approve it, decline it or hold it for a person to review, and every decision is signed and recorded. Try the free readiness scan.

Questions people ask

Is Visa's Trusted Agent Protocol free to use?

Visa publishes the specification and sample code openly on its developer site and GitHub. Your CDN, payment provider or developer may charge for the work of verifying it.

Does TAP replace a payment protocol like UCP or ACP?

No. TAP is about recognising the agent and passing optional consumer and payment data. Checkout protocols such as UCP and ACP still describe the order itself. Visa's Intelligent Commerce Connect accepts payments started through all of them.

Does TAP work for Mastercard or Amex cards?

Visa says its initial specifications apply to the Visa network. Mastercard's Agent Pay uses the same Web Bot Auth signing approach with its own agent directory.

What happens if an agent's signature fails?

Visa's specification says the merchant should block the message, or handle it with another mechanism if the agent tags are missing. You decide what that means on your site, for example treating it as an ordinary unverified visitor.

Sources

  1. Visa: Visa introduces Trusted Agent Protocol · checked 16 Nov 2026
  2. Visa Developer: Trusted Agent Protocol · checked 16 Nov 2026
  3. Visa Developer: Trusted Agent Protocol specifications · checked 16 Nov 2026
  4. GitHub: visa/trusted-agent-protocol · checked 16 Nov 2026
  5. Cloudflare blog: Securing agentic commerce: helping AI agents transact with Visa and Mastercard · checked 16 Nov 2026
  6. Visa: Akamai and Visa collaborate to build trust in agentic commerce · checked 16 Nov 2026
  7. Visa: Visa Intelligent Commerce Connect · checked 16 Nov 2026

Written by The Sill Signals Team. Last reviewed 16 Nov 2026.

Share this articleLinkedInXBlueskyEmail

Keep reading

See which AI agents visit your site, and decide what they may do.

Scan your site free