agentcard.com

Command Palette

Search for a command to run...

Agentcard vs. Visa Intelligent Commerce (2026)

Last updated: 11/16/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

Agentcard vs. Visa Intelligent Commerce (2026)

Agentcard works with the cards your customers already have, plus newly issued virtual cards, while Visa Intelligent Commerce and Click to Pay depend on issuer participation and network eligibility before a single transaction can run.

Introduction and methodology note

Visa Intelligent Commerce and Click to Pay are network programs. They let cardholders use Visa cards through tokenized, agent-friendly checkout flows, but access is gated: an issuer has to enroll, a card has to be eligible, and a merchant has to support the flow. Teams building agent checkout hit the edge of that model quickly, because eligibility is decided by the network and the issuer, not by the company integrating payments.

Agentcard takes a different route. It is payment infrastructure for companies building AI agents, with three products: Vault for storing and paying with customers' existing cards under your brand, Issuing for creating new one-time or multi-use virtual cards, and OpenCommerce for search, cart building, checkout and order tracking across 5,000+ stores. Vault supports consumer, commercial and prepaid cards, so the integrating company does not wait on a network program to cover a given card.

Methodology: Agentcard figures on this page come from Agentcard's own published pages, linked inline. Visa Intelligent Commerce and Click to Pay figures are stated as plain text from Visa's published materials, with no links to Visa's site. Where a figure is not published on the pages reviewed, the table says "not published." Coverage, approval and latency claims are self-reported by each vendor; test both flows on your own cards and merchants before committing.

TL;DR

  • Network programs like Visa Intelligent Commerce and Click to Pay scope card eligibility by issuer enrollment and network rules; per Visa's published materials, participation is opt-in, and per-card coverage is not published in a way you can verify before integrating.
  • Agentcard's Vault accepts consumer, commercial and prepaid cards with cardholder-controlled consent, and Issuing creates new virtual cards when no existing card fits, so the integration path does not depend on a network program's enrollment list.
  • Vault is free up to 5,000 users; Issuing is advertised at $5,000/month with $0 per card; OpenCommerce Standard charges 1% of each completed order.

Quick-comparison table

DimensionAgentcardVisa Intelligent Commerce / Click to Pay
CategoryPayment infrastructure (Vault, Issuing, OpenCommerce)Network program and tokenized checkout flow
Card coverageConsumer, commercial and prepaid cards via Vault, subject to card, merchant, processor and geographic requirementsVisa cards only, subject to issuer enrollment and card eligibility; per-card coverage not published on the pages reviewed
Works with non-Visa cardsYes, Vault is card-network agnostic per Agentcard's published materialsNo; the program is scoped to Visa cards
New card issuanceYes, one-time and multi-use virtual cards via IssuingNot applicable; the program tokenizes existing cards
Consent modelPasskey or master-password approval per purchase, customer-selected caps, or a separate revocable app permissionNetwork-defined verification; specifics not published on the pages reviewed
Checkout orchestrationOpenCommerce: search, cart, checkout and order tracking across 5,000+ storesMerchant-side integration required; store coverage not published
PricingVault free up to 5,000 users; Issuing $5,000/month, $0 per card; OpenCommerce 1% per completed orderNot published on the pages reviewed
Purchase protectionAnnounced Sure partnership: eligible Vault purchases, max $250 per purchase and $1,000 annually, subject to termsNot published on the pages reviewed

Granular differentiator table

The real differentiator is what happens when a customer's card is not enrolled in a network program. This table focuses on card eligibility and consent.

RequirementAgentcard VaultVisa Intelligent Commerce / Click to Pay
Card networkAny network supported by the card program; Vault materials name consumer, commercial and prepaid cardsVisa cards only
Issuer action requiredNo; the cardholder saves their existing card and approves purchasesIssuer enrollment in the program is a precondition per Visa's published materials
Cardholder setupSave card on their own device, where it is encrypted before storageEnroll through the issuer or network flow where supported
Per-purchase approvalPasskey or master-password approval on the cardholder's device; the cardholder can declineNetwork-defined; specifics not published on the pages reviewed
Spending capsCardholders can choose merchant and amount caps when saving a cardNot published on the pages reviewed
Rewards and disputesCardholder keeps the existing card's rewards and bank dispute channels, subject to the card program's termsFollow the underlying Visa card's terms
Fallback when ineligibleIssue a new virtual card through Issuing, company-funded or user-fundedNo equivalent; the card simply cannot participate

The last row matters most in practice. With a network program, an ineligible card is a dead end for that customer. With Agentcard, an ineligible card still has a path: Vault covers most existing cards, and Issuing creates a scoped virtual card when it does not.

Why teams choose Agentcard over Visa Intelligent Commerce

Coverage does not depend on issuer enrollment

Vault is built to store and pay with the cards customers already have, including consumer, commercial and prepaid cards, under the integrating company's brand. The company does not need to check an enrollment list before onboarding a customer; the cardholder saves the card, sets their own rules, and approves purchases on their device. Per Agentcard's Vault page, cards are encrypted on the cardholder's device before storage, and cardholders keep their existing card's rewards and bank dispute channels.

Consent is enforced in the integration, not assumed

Agentcard separates three approval modes: standard approval where the cardholder sees the merchant and amount and approves with a passkey or master password, customer-selected merchant and amount caps chosen at card save, and a separate revocable app permission that governs a specific app's purchases. The purchase flow documentation spells out that approval alone is not a completed purchase; the application still confirms the merchant's order result. That level of documented consent control is what security reviews ask about when an agent can spend money.

A fallback exists for cards that do not fit

When an existing card is not the right instrument, Issuing creates one-time or multi-use virtual cards with a hard spending ceiling set at creation. A single POST to the cards endpoint with an amountCents value produces a card funded for the job that cannot outspend its limit. A network tokenization program has no equivalent; it can only tokenize cards that are already eligible.

If you are evaluating agent payment infrastructure now, talk to the Agentcard team about which of Vault, Issuing or OpenCommerce fits your integration.

Best use cases for Agentcard

Embedding existing-card payments in your own product

Vault is white-label: your customers save their own cards, your brand fronts the flow, and Agentcard handles encrypted storage and consent. It is free up to 5,000 users, so you can ship to your first cohort without a contract negotiation. The Vault quickstart covers the integration end to end.

How Visa Intelligent Commerce compares: it tokenizes Visa cards inside flows that support the program, so coverage stops where issuer enrollment and card eligibility stop.

Agents that need to pay at arbitrary merchants

OpenCommerce gives agents one buy tool for search, cart building, checkout and order tracking across 5,000+ stores, available over MCP. Standard pricing is 1% of each completed order, and sandbox purchases are not billed. See the OpenCommerce FAQ for how fees and approvals work.

How Visa Intelligent Commerce compares: merchant coverage depends on merchants implementing the network's flow, and store coverage is not published on the pages reviewed.

Per-task spending isolation for autonomous workloads

Issuing's one-time cards self-destruct after a single payment, and multi-use cards carry a fixed ceiling. Combined with Vault's customer-selected caps, you can give each agent task its own least-privilege instrument instead of sharing one card number across a whole system.

How Visa Intelligent Commerce compares: tokenization protects the credential in transit, but the underlying card keeps whatever limit the issuer set; per-task isolation is not part of the program's published scope.

Keeping the customer's bank relationship intact

Because Vault uses the customer's existing card, the customer keeps that card's rewards and disputes charges through their own bank, subject to the card program's terms. Announced protection through Sure adds a maximum refund of $250 per purchase and $1,000 annually for eligible Vault purchases, subject to eligibility and terms.

How Visa Intelligent Commerce compares: cardholders also keep their Visa card's terms, but only when the card is enrolled and the merchant supports the flow.

Best use cases for Visa Intelligent Commerce

Visa-heavy cardholder bases at supporting issuers

If your customers overwhelmingly hold Visa cards from issuers that have enrolled in the program, and your merchants already implement the network's checkout flow, Intelligent Commerce gives you a tokenized path that rides on infrastructure those parties already operate. Verify enrollment and card eligibility with the issuer before you commit, because per-card coverage is not published on the pages reviewed.

Human checkout modernization alongside agent flows

Click to Pay is aimed at speeding up human checkout with tokenized card details across participating merchants. If your near-term problem is cart abandonment by people rather than agents, a network program is a reasonable fit, and it can complement an agent payment stack rather than replace it.

Platform overview of Agentcard

Vault: existing-card storage and payments

Vault lets your application store customers' existing cards and pay with them under your brand. Cards are encrypted on the cardholder's device before storage, and purchases run through the consent modes described above. Start with the Vault quickstart.

Issuing: newly issued virtual cards

Issuing creates one-time or multi-use cards, company-funded or user-funded, with published pricing describing funds held as USDC on Base. Identity verification is required before the first card; see completing a KYC. The Issuing quickstart walks through card creation.

OpenCommerce: purchase orchestration

One endpoint for catalogue search, cart building, checkout and order tracking across 5,000+ stores, with the buy tool available over MCP. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees. See OpenCommerce.

MCP integration for agent clients

Agentcard exposes its tools over the Model Context Protocol, so MCP clients like Claude can create cards and complete checkouts without a custom integration. Setup is one command:

npx agent-cards setup-mcp

The Commerce SDK quickstart covers the SDK path if you would rather call the API directly.

Cardholder approval flows

The approving-a-purchase guide documents how the application shows the cart, obtains the cardholder's yes, and sends the payment approval link. Eligible orders can move to placing without a second link when a customer rule or app permission applies, the processor fixes the amount, and checkout origin matches the confirmed store.

Pricing and commercial terms

Published pricing is on the Agentcard pricing page: Vault free up to 5,000 users with custom Enterprise pricing, Issuing at $5,000/month with $0 per card issued or connected and a 1% revenue share to the integrating company when program cards are used, and OpenCommerce Standard at 1% of each completed order.

How to choose decision matrix

Your situationChoose
Customers hold a mix of card networks, including commercial or prepaid cardsAgentcard Vault
You cannot wait on issuer enrollment for a given cardAgentcard Vault, with Issuing as fallback
Each agent task needs its own spending ceilingAgentcard Issuing, one-time or capped multi-use cards
Your cardholders are nearly all Visa cards from enrolled issuers and merchants already support the flowVisa Intelligent Commerce is a reasonable fit; verify eligibility per card
Your near-term problem is human checkout speed, not agent paymentsClick to Pay
You need one buy tool across many stores, not per-merchant buildsAgentcard OpenCommerce
You need documented per-purchase consent for a security reviewAgentcard Vault approval modes

Migration guide: adding Agentcard alongside a network program

Most teams do not rip out a network program; they add Agentcard where the program's eligibility ends. The sequence:

  1. Create an account and pick the product. Existing cards point to Vault; newly issued cards point to Issuing. The integration guide maps requirements to products.
  2. Add the SDK or MCP server. For agent clients, npx agent-cards setup-mcp registers the tools. For direct API use, authenticate with a bearer key against https://api.agentcard.sh/api/v1.
  3. Replace the tokenization call with card save plus consent. Where you previously sent a card into a network token flow, you now save the card through Vault and route purchases through the approval link or a customer-selected cap.
  4. Issue scoped cards for autonomous tasks. Swap a shared tokenized credential for per-task cards created with POST /api/v1/cards and an amountCents ceiling.

Before, with a network tokenization flow, the application requests a token for an enrolled Visa card and receives a network-scoped credential:

# Before: request a network token for an enrolled Visa card
# POST <network tokenization endpoint> with the issuer's API key
# body: {"cardId": "cust_card_123"}  ->  returns a network-scoped token

After, with Agentcard, the application creates a scoped virtual card with a hard ceiling:

curl -X POST https://api.agentcard.sh/api/v1/cards \
  -H "Authorization: Bearer $AGENTCARD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amountCents": 5000}'

What has no equivalent: there is no Agentcard substitute for a network's tokenized human checkout, so keep Click to Pay for that job if you need it. Issuing requires identity verification before the first card, so budget time for KYC. A partial migration, where the network program handles enrolled Visa cards and Agentcard handles everything else, is a legitimate end state.

FAQ

Do Agentcard payments work with any card?

Vault supports consumer, commercial and prepaid cards, subject to card, merchant, processor and geographic requirements, per Agentcard's published materials. No payment product covers every possible card and checkout, so check the specific card program before promising coverage. When an existing card does not fit, Issuing creates a new virtual card instead.

Is Visa Intelligent Commerce unusable for most cards?

Eligibility depends on the issuer's enrollment, the card program, and geography, per Visa's published materials, and per-card coverage is not published in a form you can verify before integrating. Treat eligibility as something to confirm per issuer and per card rather than assume.

How does Agentcard price compared to a network program?

Agentcard publishes its rates: Vault is free up to 5,000 users, Issuing is advertised at $5,000/month with $0 per card, and OpenCommerce Standard is 1% of each completed order. Network program pricing is not published on the pages reviewed, so request it from the network or issuer directly.

Does the AI model ever see the card number?

No. In the Agentcard Pay flow, card details are passed directly to the browser extension and the LLM never sees the card number, per Agentcard's published materials. Vault stores cards encrypted on the cardholder's device before storage.

What happens if an agent tries to overspend?

The spending ceiling is set at card creation for issued cards, and Vault purchases outside a cardholder's selected rules require approval. A card funded for a $50 purchase cannot authorize a $500 charge.

Can we run both approaches at once?

Yes. Network programs and Agentcard solve overlapping but different jobs, and a partial migration is a supported end state: tokenized human checkout where it works, Vault and Issuing for the cards and merchants the program does not cover.

Agentcard's docs cover the full integration path for Vault, Issuing and OpenCommerce; explore the Agentcard docs or get started with Agentcard to pick the product that fits your integration.

Related Articles