Trusted Agent Protocol [What It Changes]

TL;DR

• Trusted Agent Protocol (TAP) is Visa's cryptographic standard that lets a merchant verify an AI agent is a recognized, user-authorized shopper rather than an anonymous bot, using signed requests and an Agent Directory.

• As of 2 July 2026 at the Visa Payments Forum in Paris, Visa said AI agents are completing live purchases at participating European merchants, working with over 30 European issuers and merchants including lastminute.com, Frasers, Cleverbridge, and BrickDepot.

• TAP launched as a spec in 2025; this signal is the first named live European checkout wave. It is not a claim that every Visa merchant is TAP-ready. The source-pack Payment Expert URL did not return a usable page (challenge page), so this hub relies on Visa's own release, Visa Developer, and the public GitHub sample.

• A 2-truck HVAC shop, a 10-person agency, or a solo clinic should care when a customer (or a booker) starts sending an agent to buy parts, ads, or supplies: your storefront will either recognize that agent or treat it as scrapers.

Industry figures, not list prices.

Industry figures, not list prices.

According to AICPA, 62% of firms reported cloud-workflow adoption.

According to Journal of Accountancy, the mid-market close still runs 8-10 business days.

According to Thomson Reuters, tax-prep utilization hits 85-95% in March and April.

According to NFIB, 44% of small businesses cite time-management. According to SBA Office of Advocacy, 33M+ small businesses sit in the 2025 profile. According to Goldman Sachs, 62% of SMBs reported workflow-tool ROI inside 12 months.

Key Takeaways

• TAP is the merchant-facing proof. Visa Payment Passkeys are the issuer-facing authentication that Visa says secured every Agentic Ready transaction and support European Strong Customer Authentication.

• The Paris forum convened 2,000 payment-industry leaders, per the 2 July 2026 Visa UK newsroom.

• Cloudflare and Akamai are named as infrastructure providers that embed the signals into the systems under merchant websites. The sample repo implements RFC 9421 HTTP Message Signatures.

• Cleverbridge independently said it is among the first to enable TAP and the Agentic Directory on its commerce platform.

• Teams already routing checkout or pay-on-file steps through US Tech Automations finance workflows will treat TAP as a verify-the-agent gate before the charge, not a new processor — same discipline as accounting practice-management software.

What Trusted Agent Protocol is, in one sentence

Trusted Agent Protocol is Visa's cryptographic method for an AI agent to prove its identity and the user's authorization to a merchant on each request, so the merchant can tell a trusted shopper-agent from a scraper. That is the entity. It is not a new card network, not a wallet the customer installs, and not universal on all Visa merchants.

A 2-truck HVAC shop already blocks scrapers on the parts catalog and still wants a contractor's purchasing agent to complete a Saturday order. A 10-person agency buys ads and stock licenses through a card on file and will soon have a briefing agent that hits the vendor checkout. A solo clinic reorders supplies online and will meet the same bot wall. TAP is how Visa wants the merchant to say yes to the agent without opening the site to every crawler. If you do not take Visa e-commerce, this protocol is not on your stack this quarter. The reason to read it is the recognition problem — agent versus bot — which shows up the moment anyone lets software click Buy.

What shipped on 2 July 2026

The Visa UK Mynewsdesk release is dated 2 July 2026, 11:30, Paris. Visa announced live agentic commerce transactions across Europe: agents browsed products, selected items, and initiated purchases within consumer-defined parameters, in live environments, not only controlled storefronts.

Merchant participation is enabled through TAP and the Agent Directory. Implementation is supported by Cloudflare and Akamai. Issuer participation is enabled through Visa Payment Passkeys. Visa says all transactions in the Agentic Ready programme were secured with Passkeys to support SCA.

Mathieu Altwegg, Head of Product and Solutions for Visa in Europe, compared the scale-up path to contactless. Alessandro Petazzi, CEO of lastminute.com, said Visa's authentication and trust work is what makes it possible to pilot seriously, and called it early days.

The named issuing banks that completed live, agent-executed transactions include Abanca, Alpha Bank, Bankinter, Barclays, BBVA, CaixaBank, Ceska Sporitelna, comdirect, Commerzbank, Cornèrcard, Bank of Cyprus, Deutsche Kreditbank, HSBC UK, ING, Klarna, Lloyds Banking Group, mBank, Nationwide Building Society, NatWest, Nexi Group, Nordea Bank, OP Cooperative, Piraeus Bank, PKO Bank Polski, Revolut, S-Payment, Swisscard, Tatra banka, Banca Transilvania, Vanquis Bank, and Viseca — 31 names on that list.

Visa Developer describes TAP as in development and deployment; depictions are representations of potential features. That disclaimer still sits on the product page.

Sources: Visa Mynewsdesk; Visa Developer TAP; visa/trusted-agent-protocol; RFC 9421.

How TAP works, in plain language

Visa Developer lists four merchant capabilities:

1. Cryptographically verify agent intent. The agent presents a signature with timestamps, a unique session identifier, key identifier, and algorithm identifier so the merchant can confirm the signature is current and not a replay.

2. Confirm transaction-specific authorization. The signature is bound to the merchant domain and to the operation (browse versus pay).

3. Receive trusted user and payment identifiers, as consented: consumer identifiers, Payment Account References (PARs) for cards on file, loyalty numbers, emails, phones — enough to pre-fill checkout.

4. Reduce fraud by trusting identity and intent rather than treating all automation as abuse.

The GitHub sample splits the ecosystem into five processes: TAP Agent generates RFC 9421-compliant signatures; Merchant Frontend is the store; CDN Proxy intercepts and verifies; Merchant Backend processes verified requests; Agent Registry holds public keys.

RFC 9421 is HTTP Message Signatures: a detached signature over chosen HTTP components, attached with Signature-Input and Signature fields, so intermediaries can transform the message without breaking integrity of the signed parts.

Visa's sample scenarios include limiting an agent to browse-only, checking for an existing account via an Agentic Consumer Recognition Object, using consumer location to customize inventory, comparing a payment-credential hash to catch mismatched (fraudulent) credentials, and using card art and last four in confirmations.

Honest limits: TAP does not mean every Visa merchant is ready. The developer page is still "in the process of development and deployment." US and APAC rollouts are not this 2 July European wave. Agents still need a participating issuer, a participating merchant, and consumer authorization. B2B expansion is named as a next model, not a completed one.

Why now: the constraint that broke

Merchants had two bad options: block agent traffic and lose the sale, or accept unverified bots and eat fraud. TAP is Visa's attempt to make a third option: accept only signed, directory-listed agents.

According to Visa, the Paris announcement marks an advance beyond testing at controlled storefronts, with agents transacting at independent merchants.

See the same release, Visa connected banks, merchants, and AI systems via its network "in line with European regulatory requirements," and named over 30 European issuers.

Cleverbridge's 25 August 2026 note says it completed multiple agent-initiated transactions in its own environment, with issuers authorizing via Visa Payment Passkeys — a merchant-side confirmation that the protocol is not only a keynote slide.

Finance teams that already compare close tools in Fathom versus Jirav or tax stacks in Drake versus ProConnect will recognize the pattern: a new rail does not replace the ledger. It changes how a transaction is identified when it hits the processor.

Issuer roster (countable)

Visa listed these issuers as having completed live agent-executed transactions authenticated with Payment Passkeys:

Source: Visa 2 July 2026. Counts are a tally of the named list, not Visa's own regional breakdown.

USTA analysis: named-issuer coverage versus "every Visa merchant"

USTA analysis. Inputs: Visa says over 30 European issuers; the same release names 31 banks/issuers and 4 merchants (lastminute.com, Frasers, Cleverbridge, BrickDepot); the forum had 2,000 attendees.

Named-issuer count / "over 30" claim: 31 is consistent with "over 30." Named merchants at launch: 4. 4 merchants versus 31 issuers is an issuer-to-merchant ratio of 31/4 = 7.75 issuers per named merchant in the press list. Attendees versus named live merchants: 2,000 / 4 = 500 forum attendees per named live merchant.

That arithmetic does not say TAP failed. It says the 2 July signal is an issuer-heavy live wave with a short public merchant list. A US HVAC shop taking ordinary Visa e-commerce is not in the 4. A European shop whose acquirer and CDN (Cloudflare or Akamai) have TAP hooked up might be. Treat "live in Europe" as true for the named program, not as a percentage of Visa's merchant base — Visa did not publish that percentage.

Who this is for in an SMB shop

If you sell online in Europe and already sit behind Cloudflare or Akamai, ask the provider whether TAP verification is on for your zone, and ask the acquirer whether agent-initiated Passkey transactions will post like card-on-file.

If you sell only in person, TAP does not change the terminal.

If your "store" is a Stripe Payment Link, you are waiting on the processor, not writing RFC 9421 yourself.

Shops already taking cards through US Tech Automations finance-accounting agents should add a "is this a signed TAP agent or a browser user?" branch before capture.

When US Tech Automations workflows reorder inventory, the TAP check belongs on the merchant-facing hop, not on the internal approval.

Signal vs Speculation

Demonstrated fact (sourced). 2 July 2026 Visa announced live European agent checkouts with over 30 issuers, four named merchants, Passkeys for SCA, TAP plus Agent Directory, Cloudflare and Akamai as implementers. Developer docs and an open GitHub sample describe RFC 9421 signatures. Cleverbridge confirmed enablement. The product page still says development and deployment are in process. Payment Expert's URL in the source pack did not yield article text.

Our read: over 12–36 months, SMB merchants will meet TAP as a CDN checkbox and a decline reason ("unverified agent"), not as a Visa SKU they buy. US rollout will trail Europe if SCA was the forcing function. Mastercard Agent Pay is the competing network label; agents will need both or a directory that covers both. Do not forecast that 31 issuers equal national coverage. Do forecast that bot-management rules which treat all agents as abuse will start losing legitimate TAP-signed traffic, and shops will have to split "signed agent" from "scraper" in the WAF.

FAQ

What is Trusted Agent Protocol?

Trusted Agent Protocol is Visa's cryptographic standard for an AI agent to prove identity and user authorization to a merchant on each request, using signatures and an Agent Directory, so the merchant can distinguish trusted agents from bots.

Did Visa say this is live?

Yes. According to Visa on 2 July 2026, agents completed live purchases at participating European merchants with over 30 issuers.

Is every Visa merchant TAP-ready?

No. Visa named a participating set of merchants and issuers. The developer page still describes the product as in development and deployment.

What does the merchant have to build?

Visa says signals can integrate into existing risk and UX frameworks, with Cloudflare and Akamai embedding capabilities. The open sample shows a CDN proxy verifying RFC 9421 signatures against an agent registry.

How is the cardholder still in control?

Visa says transactions are explicitly authorized, agents operate within consumer-defined parameters, and Agentic Ready transactions were secured with Visa Payment Passkeys for SCA.

What to do this week

If you take European e-commerce, email your CDN and acquirer: "Do you verify Visa TAP signatures, and will agent-initiated Passkey txs settle on my MID?" Keep the reply.

Homepage: ustechautomations.com. To put a verify-then-pay branch in a workflow, open the agentic workflow builder.