Payment authentication · Visa · 100+ partners, sandbox open
Visa Intelligent Commerce
The payment authentication and authorisation layer for agent-initiated transactions. Includes the Trusted Agent Protocol (TAP) for legitimate agent verification.
Abbreviation: VICVisa Intelligent Commerce is the payment authentication and authorisation layer for agent-initiated transactions. It addresses the question that every merchant asks when an AI agent attempts a purchase: is this agent legitimate, and is this transaction authorised by a real human?
VIC includes the Trusted Agent Protocol (TAP) - an open framework built on existing web infrastructure for agent authentication. TAP distinguishes legitimate AI agents from malicious bots at checkout by verifying agent identity against Visa's agent registry. In production, TAP adds less than 100ms to the checkout flow.
The platform has over 100 partners and its sandbox is open for merchant registration. Hundreds of controlled real-world agent transactions were completed in closed beta by December 2025. VIC integrates with Akamai for edge-based behavioural intelligence and bot protection, and supports Shared Payment Tokens (SPTs) with Stripe, Affirm, and Klarna for agent-native payment.
For merchants, VIC solves the fraud and identity problem that traditional bot detection cannot address. Traditional bot detection treats all non-human traffic as suspicious. VIC creates a verified category of non-human traffic - legitimate AI agents acting on behalf of authenticated humans - and provides the infrastructure to distinguish them from malicious bots.
How does a merchant verify that an agent-initiated payment is legitimate?
What VIC provides
Agent identity verification: distinguishes legitimate AI agents from malicious bots at checkout
Trusted Agent Protocol (TAP): open framework built on existing web infrastructure for agent authentication
Akamai integration for edge-based behavioural intelligence and bot protection
Shared Payment Tokens (SPTs) with Stripe, Affirm, and Klarna for agent-native payment
Hundreds of controlled real-world agent transactions completed in closed beta by December 2025
Before you begin
The following must be in place before starting VIC integration. Missing prerequisites are the most common cause of delayed or failed protocol deployments.
Merchant registration at visa.com/intelligent-commerce
Existing payment processing infrastructure compatible with Visa
Checkout flow capable of integrating TAP validation (adds less than 100ms)
Stripe integration for SPT support (optional but recommended)
What goes wrong
These are the failure modes the AXD Institute has observed across early VIC implementations. Each includes the root cause and the recommended mitigation.
TAP integration latency
while TAP adds less than 100ms in production, misconfigured implementations can add significantly more, causing checkout abandonment.
SPT configuration errors
Shared Payment Tokens require correct configuration across both Visa and your PSP (Stripe, Affirm, Klarna). Mismatched token configurations cause silent payment failures.
Agent registry staleness
TAP validates against Visa's agent registry. Agents not yet registered or with expired registrations are rejected. Ensure your agent registrations are current.
Step-by-step walkthrough
A sequenced implementation guide for VIC. Each step includes the action, the rationale, and the validation criteria for completion.
Merchant registration and sandbox access
Register for Visa Intelligent Commerce at visa.com/intelligent-commerce. Sandbox access is available to merchants with existing Visa payment processing relationships.
- •Submit merchant registration through the Visa Intelligent Commerce portal.
- •Verify your existing payment processing infrastructure is compatible with VIC requirements.
- •Obtain sandbox credentials and API documentation.
- •Review the TAP specification and SPT documentation before beginning integration.
Trusted Agent Protocol (TAP) integration
Implement TAP validation in your checkout flow. TAP verifies that a purchasing agent is registered in Visa's agent registry and is acting on behalf of an authenticated human.
- •Integrate TAP validation as a step in your existing checkout flow. TAP adds less than 100ms in correctly configured implementations.
- •Implement the TAP verification call: when an agent-initiated checkout is detected, query Visa's agent registry to verify the agent's identity and authority.
- •Handle TAP verification responses: approved (proceed with checkout), rejected (block the transaction), and unknown (apply your standard bot detection rules).
- •Ensure TAP integration does not add excessive latency. Misconfigured implementations can add significantly more than 100ms, causing checkout abandonment.
Shared Payment Token (SPT) configuration
Configure Shared Payment Tokens for agent-native payment. SPTs enable agents to carry payment credentials across protocol boundaries.
- •Determine which PSPs you will support for SPT: Stripe, Affirm, and Klarna are the current SPT partners.
- •Configure SPT support in your payment processing infrastructure. SPT configuration must be consistent across both Visa and your PSP.
- •Test SPT token creation, validation, and redemption in the sandbox environment.
- •Verify that mismatched token configurations are detected and reported rather than causing silent payment failures.
Akamai integration for bot protection
Configure the Akamai integration for edge-based behavioural intelligence that distinguishes legitimate agents from malicious bots before they reach your checkout.
- •If you already use Akamai for bot protection, configure the VIC integration to create an 'agent-verified' traffic category alongside your existing bot/human classification.
- •If you do not use Akamai, evaluate whether the VIC Akamai integration provides sufficient bot protection for your checkout, or whether you need to maintain your existing bot protection alongside VIC.
- •Configure behavioural intelligence rules that account for agent traffic patterns (high-frequency, structured requests) without flagging them as bot attacks.
- •Test the integration under load to verify that legitimate agent traffic is not throttled or blocked by bot protection rules.
Production activation and TEI monitoring
Activate VIC in production and implement Trust Erosion Index monitoring for agent-initiated transactions.
- •Activate VIC in production through the Visa Intelligent Commerce portal.
- •Implement TEI (Trust Erosion Index) tracking for agent-initiated transactions. TEI measures the rate at which trust signals degrade during agent sessions.
- •Monitor TAP verification success rates. A high rejection rate may indicate that agents interacting with your checkout are not yet registered in Visa's registry.
- •Track SPT usage patterns and failure rates. Silent payment failures from mismatched SPT configurations are the most common post-launch issue.
- •Ensure your agent registrations in Visa's registry are current. Agents with expired registrations are rejected by TAP.
Related metrics, frameworks, and essays
AXD Metrics Standard KPIs
AXD Practice Frameworks