Skip to content

Visa Intelligent Commerce

Visa's agentic commerce program: agent-specific tokens, spending controls, the Trusted Agent Protocol for agent identity, Intelligent Commerce Connect and partners.

Updated October 4, 2026 5 min read .md

In short: Visa Intelligent Commerce (VIC) is Visa’s set of services that let AI agents pay with Visa credentials under limits the consumer controls. It combines agent-specific network tokens, authentication, spending instructions and transaction signals. Its open Trusted Agent Protocol (TAP) lets merchants recognize legitimate agents. Visa announced VIC in April 2025, reported live agent transactions in late 2025, and in 2026 added a single merchant integration (Intelligent Commerce Connect) and a partnership with OpenAI.

What Visa Intelligent Commerce includes

Visa launched the program on April 30, 2025 with AI partners including Anthropic, IBM, Microsoft, Mistral AI, OpenAI, Perplexity, Samsung and Stripe. It is a portfolio of services, not a single protocol.

Agent-specific tokens

Visa calls these “AI-ready cards”. They are network tokens: a card number replaced by a token that Visa issues and manages. Each is provisioned for a specific agent. The agent never handles the real card number, and the token can be limited or revoked without reissuing the card. Visa’s June 2026 announcements added richer token data (the transaction type, where the token is used and who is paying) and “token assurance” signals based on how a token was provisioned and how it has behaved.

Authentication

The consumer confirms, through an identity verification step, that an agent may use their credential. That way, the issuer has evidence that the cardholder set up the agent.

Payment instructions and controls

The consumer, or the agent on their behalf, registers instructions: spending limits, merchant categories, time windows and approval rules. The network checks transactions against these before authorization.

Commerce signals

Data on agent-initiated transactions is shared with issuers and merchants to support fraud decisions and dispute resolution.

Personalization

With consent, consumers can share Visa-derived spending insights with an agent to improve its recommendations.

Trusted Agent Protocol (TAP)

On October 14, 2025 Visa published the Trusted Agent Protocol, developed with Cloudflare. Its purpose is to help merchants tell legitimate AI agents from malicious bots, using existing web infrastructure and with no code changes required on the merchant side.

TAP builds on Web Bot Auth and HTTP Message Signatures (RFC 9421):

  • A registered agent signs its HTTP requests with a private key. The matching public key is published in a Visa-hosted agent registry.
  • A tag in the signature shows the agent’s purpose: agent-browser-auth for browsing and product lookup, or agent-payer-auth for payment.
  • Timestamps, a nonce (a single-use value) and a key ID guard against replayed requests.

On top of identity, TAP can carry two more types of data:

  • Consumer recognition: identifiers that tell the merchant whether the user behind the agent is an existing customer. Examples include a Payment Account Reference (a stable card identifier that isn’t the card number), a loyalty number, an email address or a phone number.
  • Payment information: payment data the agent can pass so the merchant can complete or pre-fill its preferred checkout.

Merchants usually verify TAP signatures at the edge, through a CDN or bot-management provider, rather than in application code. TAP’s specification and sample code are on Visa’s Developer Center and GitHub. Adyen, Ant International, Checkout.com, Coinbase, CyberSource, Elavon, Fiserv, Microsoft, Nuvei, Shopify, Stripe and Worldpay gave early feedback. Visa says it is aligning TAP with the IETF, the OpenID Foundation and EMVCo, and with protocols such as ACP and x402.

Developer and merchant tooling

  • Visa MCP server (September 2025): connects agents and LLM applications to VIC APIs over the Model Context Protocol.
  • Visa Acceptance Agent Toolkit: a pilot that lets business users create invoices, payment links and reports with natural-language prompts.
  • Intelligent Commerce Connect: announced in April 2026 as a single integration through the Visa Acceptance Platform. It handles payment initiation, tokenization, spend controls and authentication for agent transactions. It accepts both Visa and non-Visa cards and works with multiple token vaults. It also supports agent payments arriving through TAP, the Machine Payments Protocol (MPP), the Agentic Commerce Protocol and the Universal Commerce Protocol. It can help merchants make their catalogs discoverable on AI platforms. Pilot partners named were Aldar, AWS, Diddo, Highnote, Mesh, Payabli and Sumvin, with broader availability expected during 2026.
  • Agentic Directory and Agent Score: announced in June 2026. The directory is a registry of verified agents and merchants. Agent Score, developed with New Generation, measures how well agents can navigate and complete tasks on a merchant’s site.

Milestones and partners

DateDevelopment
Apr 30, 2025Visa Intelligent Commerce announced
Oct 14, 2025Trusted Agent Protocol published with Cloudflare
Dec 18, 2025Visa reports hundreds of agent-initiated transactions completed in production. It cites more than 100 partners, 30+ building in the VIC sandbox and 20+ agents integrating directly. US pilots include Skyfire, Nekuda, PayOS and Ramp.
Early 2026Pilots planned in Asia Pacific and Europe, and a partnership with Aldar in the UAE
Apr 2026Intelligent Commerce Connect announced
Jun 10, 2026Strategic collaboration with OpenAI announced: tokenized Visa credentials, real-time authorization and fraud monitoring for agent purchases in OpenAI’s products, including developer uses with Codex, under user-set limits. Agentic Directory announced.

Processors have added support as well. For example, Fiserv announced support for TAP alongside Mastercard’s framework. AWS has published integrations of VIC with Amazon Bedrock AgentCore.

How it compares

Mastercard Agent Pay takes a similar approach: agentic tokens, agent registration, and Web Bot Auth-based recognition through its Agent Pay Acceptance Framework. Both networks support the open protocols instead of competing with them. TAP sits at the identity layer, and VIC tokens can sit behind delegated payments in ACP, UCP or AP2.

Practical notes

  • Merchants usually get TAP verification through their CDN, bot-management or PSP provider. Agent tokens arrive as ordinary tokenized card transactions.
  • Agent developers need to register with Visa (directly or through an enabler), manage signing keys, and request tokens and instructions through VIC APIs.
  • Issuers gain visibility into agent involvement through token data and signals. How liability is assigned in agent-initiated disputes is still evolving. See consumer protection and liability.

Sources

The newsletter

Agentic commerce, explained as it happens.

New protocols, launches and what they mean for you. Plain language, no hype.

I'm a…