INQUIRING LINE

Shoppers love AI assistants but barely trust them with payments — can a Visa-backed protocol close that gap?

What trust gap does Visa aim to address with this protocol?

This explores what Visa's Trusted Agent Protocol is trying to fix: the gap between how many people now use AI assistants and how few merchants and shoppers trust those assistants to actually buy things.


This explores the trust problem Visa's Trusted Agent Protocol is built to solve, and which kind of trust it can and can't provide. The corpus shows two gaps that are easy to blur together. On the consumer side, a Harris Poll for Visa found 72% of US adults use AI assistants but only 23% trust AI to make payments. When Visa's name was attached, 61% said they trusted the company to handle agent-initiated transactions Does naming a payments brand increase trust in AI transactions?. People seem to want a familiar payments brand standing between them and the AI. On the merchant side the gap is different: a retailer's website sees software arriving and can't tell a legitimate shopping agent from a scraper or a fraud bot. The protocol targets that second gap. Agents carry cryptographic signatures, built on HTTP Message Signatures and developed with Cloudflare. Those signatures encode the agent's intent, recognition of the consumer, and payment data, so a merchant can check who is knocking Can cryptographic signatures help merchants identify trusted AI agents?.

Why is merchant-facing identity its own problem? The Amazon–Meta Muse dispute shows what happens without it. Amazon blocked Meta's shopping agent, and because there was no standard way for an agent to identify itself and prove it was authorized, enforcement fell back on terms-of-service blocks instead of negotiated rules What identity standards do shopping agents actually need?. A related argument makes a point that's easy to miss. Storing a card securely in a vault protects the consumer, but it does nothing to make the agent visible or understandable to the retailer Can credential vaulting alone solve merchant-facing agent identification?. Visa's signatures are an attempt at that missing visible layer.

TAP isn't the whole answer, and it isn't meant to be. One framework treats ACP, Google's AP2, UCP, Visa's TAP and Mastercard's Web Bot Auth as stacked layers rather than rival standards. TAP covers identity, and other protocols cover governance, discovery and the application itself Do agentic commerce protocols compete or complement each other?. AP2, for example, deals with a different question: not *who is this agent?* but *did the user really approve this cart?* It answers with a chain of signed mandates that leaves an audit trail the user can't later deny How can signed mandates prevent payment fraud by agents?.

The less obvious point is that verified identity doesn't mean the agent is trustworthy. Sierra and Meta's Personal Agent Protocol controls what access an agent has, but an agent funded by merchant referral fees could hold valid authorization and still steer you toward the merchant's interests Can a protocol split agent access from agent incentives?. Consent settings can also undo safeguards from the inside. A single 'allow always' checkbox reportedly let Muse complete a sale and share a user's address without checking back Do broad consent settings pose bigger risks than prompt injection attacks?. A signature can tell a merchant the agent is legitimate. It can't tell the shopper the agent is acting in their interest.

The consumer trust gap may also close faster than the survey suggests. Instinct reports that 40% of its users give their AI agent a credit card within three weeks How fast do users trust AI agents with payment data?. If that's typical, the bottleneck may soon be merchants rather than shoppers, and the merchant side is exactly where Visa's protocol is aimed.


Sources 9 notes

Does naming a payments brand increase trust in AI transactions?

A Harris Poll survey found 72% of US adults use AI assistants, but only 23% trust AI to execute payments. When Visa's name was attached, 61% reported trust in the company to handle agent-initiated transactions—suggesting consumers prefer a recognized intermediary over AI alone.

Can cryptographic signatures help merchants identify trusted AI agents?

Visa developed Trusted Agent Protocol with Cloudflare to enable merchants to authenticate AI agents through agent-specific cryptographic signatures carrying intent, consumer recognition, and payment data. The protocol builds on HTTP Message Signatures and aims to bridge the gap between AI-assistant adoption and merchant trust.

What identity standards do shopping agents actually need?

Amazon's block of Meta's Muse reveals that AI agents need standardized ways to identify themselves and prove authorization to retailers—separate from consumer-side credential security. Without such protocols, retailers enforce access through terms-of-service blocks rather than negotiated standards.

Can credential vaulting alone solve merchant-facing agent identification?

Secure credential storage is a unilateral consumer-security control that prevents agent exposure of secrets, but it cannot substitute for a visible, retailer-legible self-identification protocol that both the account holder and merchant must agree to separately.

Do agentic commerce protocols compete or complement each other?

Boboev argues ACP, AP2, UCP, TAP, and Web Bot Auth each solve different layers—application, governance, discovery, and identity—creating a capability ladder merchants stack rather than choose between, with each layer absorbing different levels of fraud risk.

Show all 9 sources
How can signed mandates prevent payment fraud by agents?

Google's Agent Payments Protocol chains signed Intent and Cart Mandates into tamper-proof records of user authorization. Built with 60+ payment firms, the protocol captures user intent upfront and verifies cart contents before payment, establishing accountability for agent-led transactions.

Can a protocol split agent access from agent incentives?

Sierra and Meta's protocol uses OAuth to let consumers authorize agents and companies restrict agent capabilities, but it does not address misaligned incentives like merchant referral fees. A merchant-paid agent could hold valid authorization while steering purchases for its own profit.

Do broad consent settings pose bigger risks than prompt injection attacks?

A single "allow always" checkbox can override advertised per-transaction approval safeguards, allowing agents to complete sales and share personal data without checking back first, as shown in a reported case where Meta's Muse closed a sale and gave out a user's address without confirmation.

How fast do users trust AI agents with payment data?

Instinct's CEO reported 40% of users share credit cards within three weeks, with 80% retention following any sensitive data disclosure. This behavioral follow-through on $1 billion in transaction volume suggests trust barriers to agent commerce fall faster than stated-preference measures indicate.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.