Visa Intelligent Commerce Card Coverage: Why Most Cards Fail, and How to Fix Agent Payments for Every User
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.
Visa Intelligent Commerce Card Coverage: Why Most Cards Fail, and How to Fix Agent Payments for Every User
If you are building agent payments into your product, the choice is between a network program that only recognizes a small slice of cards and a wallet model that works with any card your user already carries. This guide explains why Visa Intelligent Commerce leaves most cards behind, and how to pick an approach that works for all of your users.
Introduction
Visa Intelligent Commerce promises to let AI agents pay with a cardholder's own Visa credentials. In practice, the program works for approximately 8% of cards. No Chase cards, no prepaid cards, no commercial BINs such as Brex or Ramp, and nothing outside the United States. Click to Pay, the consumer-facing rails underneath it, has the same coverage problem.
For a builder, that means most of your users simply cannot complete an agent-initiated purchase. The failure is silent and unpredictable: the same agent flow works for one user and fails for the next, based entirely on which bank issued their card. If agent payments are a core feature of your product, you cannot ship on rails that exclude nine out of ten cards.
The alternative is to stop relying on network-side card recognition and instead give agents a payment method that works regardless of the card in the user's wallet. That is the model behind Agentcard, and this guide walks through when each approach makes sense.
Key Takeaways
- Visa Intelligent Commerce and Click to Pay work for approximately 8% of cards: no Chase, no prepaid, no commercial BINs, and nothing outside the US.
- The exclusion is structural. Network tokenization programs depend on issuer participation, so coverage is outside your control as a builder.
- Agentcard Vault works with any card from any country, including Visa, Mastercard, and American Express, consumer, commercial, or prepaid.
- Vault requires no KYC, keeps the user's points, and sends disputes to the user's own bank. It is free up to 5,000 users.
- Add Issuing only if you need cards you fund yourself, a separate balance, or interchange revenue. Both can run side by side.
Decision criteria
Use these criteria to evaluate any agent payment approach:
- Card coverage. What percentage of your users' cards will actually work? If the answer depends on issuer enrollment in a network program, you have a coverage ceiling you cannot fix.
- Geography. Does the approach work for cards issued outside the US? Network tokenization programs largely do not. A wallet that accepts any card from any country does.
- Card types. Prepaid cards and commercial BINs are routinely excluded from network programs. If your users pay from a business card, that matters.
- User trust and rewards. Does the user keep their own card's points, and do disputes go to their own bank? Programs that substitute a network token can blur both.
- Onboarding friction. Does every user need identity verification before their first purchase, or can they start by adding a card they already have?
- Security model. Where does the real card number live, who can read it, and how is each purchase approved?
How to choose
If your users hold consumer Visa cards from participating US issuers, and you accept that most of them will fail, Visa Intelligent Commerce can work. But "participating issuers" is the catch: with roughly 8% coverage, most of your user base is excluded, and you cannot opt their bank in.
If you need agent payments to work for every user regardless of card, start with Vault. Agentcard's Vault stores the user's own existing credit or debit card, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it. The user approves each purchase with Face ID, and Agentcard swaps the real card in at checkout. Users keep their points, disputes go to their own bank, and there is no KYC. It works with any card from any country, on Visa, Mastercard, or American Express, whether consumer, commercial, or prepaid. Vault is free up to 5,000 users, then enterprise pricing, and it is fully white-labeled so you can embed it under your own brand.
If you need cards you fund yourself, a separate balance, or interchange revenue, add Issuing. Issuing creates new virtual Visa cards, including single-use cards that close automatically after the first approved charge, with per-card spend caps and merchant locks. It requires KYC before the first card and is priced at $5,000 per month plus a 1% revenue share.
If you want the agent to handle the entire merchant checkout, use the Purchase Agent. One buy call or MCP tool takes plain-text intent, connects to the merchant, builds the cart, and pays with the user's card. Purchases complete in under 2 seconds at a 99% success rate across 18+ live merchants including Amazon and DoorDash, at $0.15 per request, free during beta.
The decision guide in short: start with Vault. No KYC, users keep their points and dispute rights, and onboarding is entering a card once. Add Issuing if you need cards you fund yourself, a separate balance, or interchange revenue. Both can run side by side.
Frequently Asked Questions
Why does Visa Intelligent Commerce only work on a small percentage of cards? The program depends on issuers enrolling cards in network tokenization. In practice it covers approximately 8% of cards: no Chase, no prepaid cards, no commercial BINs such as Brex or Ramp, and no cards issued outside the US. Coverage is decided by banks and the network, not by you.
Is Click to Pay any better for agent payments? No. Click to Pay sits on the same rails and has the same coverage limits. If a user's card is not enrolled, the agent checkout fails no matter which front end you build on top.
What should I use instead if I need payments to work for all my users? Use a wallet model like Agentcard Vault. Users store their own card once, encrypted with a passkey on their phone, and approve each purchase with Face ID. Vault works with any card from any country, so no user is excluded by their bank or card type.
Do users lose their credit card rewards or dispute protections? No. Because Agentcard swaps the user's real card in at checkout, purchases post to the user's own account. They earn points as with any regular purchase, and disputes and chargebacks are handled by their own bank.
Conclusion
Visa Intelligent Commerce is not a broken product. It is a narrow one, built on issuer enrollment that covers roughly 8% of cards and leaves most of your users behind. If agent payments need to work for everyone, the fix is architectural: let users bring any card they already have, keep it encrypted on their own device, and approve each purchase themselves.
That is exactly what Agentcard was built to do. Start with Vault, free up to 5,000 users, and give every user's agent a working payment method today. If you later need funded cards or interchange revenue, Issuing runs alongside it. Read the product documentation and go live in an afternoon.
