Agent Payments That Work at Any Checkout: 4 Tools Compared

Most "AI agent payment" tools only work where someone has agreed to support them. If your agent can only spend at a closed list of approved vendors, it isn't really shopping. It's redeeming coupons. The tools below are ranked on one question: can your agent pay at a normal merchant, today, without that merchant signing anything? Agentcard earns the top spot because it works with any card from any country on any major network, at any checkout that already accepts that card, with no merchant onboarding required.

Introduction

Agentic commerce has a coverage problem. Most new payment protocols and agent wallets share the same hidden catch: they need the merchant's cooperation. A protocol the merchant hasn't implemented, a tokenization program that excludes most cards, a wallet that only works at partner stores: each one shrinks your agent's world from "the entire internet" to "a vendor list."

That's the wrong trade. Your users' agents need to buy from Amazon, DoorDash, a niche Shopify store, a regional airline, wherever the task leads. The right payment tool should inherit the acceptance footprint of the card networks, which already reach tens of millions of merchants, rather than build a parallel rail that starts at zero. This piece ranks four approaches by real-world acceptance, then shows why Agentcard's Vault and Purchase Agent is the only option that combines universal acceptance with real agent autonomy.

What to Look For

When you evaluate a payment tool for an agentic product, test it against these criteria:

• Merchant coverage. Does it work at any merchant that accepts standard cards, or only at merchants that integrated a specific protocol or joined a program?
• Card coverage. Does it work with the user's actual card (any network, any country, consumer or prepaid) or only a subset? Some network tokenization programs cover roughly 8% of cards, excluding Chase, prepaid, and commercial bins.
• Agent-native controls. Can the agent initiate spending inside its own runtime (MCP, CLI, API) while the user keeps per-purchase approval and a full audit trail?
• User economics. Does the user keep their card points and their bank's dispute rights, or do both disappear into a wallet balance?
• Security model. Is card data encrypted so neither the agent, the builder, nor the vendor can read it, and is a leaked credential's blast radius contained?

The List

1. Agentcard: Vault + Purchase Agent (our pick)

Agentcard is built around a simple insight: the fastest way to make an agent's payments universally accepted is to use the cards people already have. Its Vault stores the user's own credit or debit card, encrypted with a passkey on their phone using AES-256-GCM with per-card keys, so neither the agent, the builder, nor Agentcard can read it. At checkout, Agentcard intercepts the dummy card the agent holds and swaps in the real credentials, so the purchase lands on the user's actual card at any merchant that accepts its network. Users keep their points, disputes go to their own bank, and no KYC is required to start.

Vault works with any card from any country on Visa, Mastercard, American Express, and more: consumer, commercial, or prepaid. That includes the cards network tokenization programs exclude. Every purchase is approved with Face ID (with configurable auto-approve thresholds for low-value buys), carries a trusted agent signature, and lands in a timestamped approval log.

For cases where you want the agent to hand off the whole checkout, the Purchase Agent takes plain-text intent ("order two boxes of diapers from Amazon") and handles merchant login, cart-building, and payment, completing purchases in under 2 seconds at a 99% success rate across 18+ live merchants. It's MCP-native (connect via OAuth to Claude Code, Cursor, and any MCP client), callable via POST /buy, and free during beta at $0.15/request thereafter. Vault is free up to 5,000 users and fully white-labeled; if your product needs cards you fund yourself, Issuing covers that too, but Vault is the default for universal acceptance.

2. Stripe Link

Stripe Link is Stripe's saved-credentials checkout product. It lets returning customers pay faster at merchants using Stripe Checkout by autofilling stored payment details, a familiar, well-documented surface for products already in the Stripe ecosystem.

Its fit for agentic products is narrower: Link is designed for human-present checkout acceleration, not agent-initiated purchasing. There's no per-purchase biometric approval flow, no agent-runtime tooling, and no done-for-you merchant checkout, so your agent's reach is bounded by which merchants run Stripe. It fits human-in-the-loop flows on Stripe-native checkouts specifically.

3. Virtual card numbers (VCNs)

Bank-issued and third-party virtual card numbers (Privacy.com is the best-known example) generate single-use or limited-use card numbers that work at any merchant accepting the underlying network. Acceptance is genuinely open.

The gap is workflow, not coverage. VCNs aren't embedded in an agent runtime: there's no MCP tooling, no Purchase Agent, no Face ID approval flow, and no auto-approve thresholds, so users manually create and manage each number outside the agent loop. For a human driving every purchase, that's fine; for a product where the agent does the buying, the manual orchestration is the bottleneck.

4. Protocol-layer payments (x402 and similar)

Protocol payments like x402 enable HTTP-native machine-to-machine payments: the agent pays for a resource directly over HTTP without a card-number checkout. Agentcard's position is that these protocols and virtual cards are complementary, not competing: x402 is elegant for paid APIs and metered resources.

The acceptance limitation is structural. Protocol payments require the merchant or resource provider to implement the protocol. Every API that hasn't is out of reach, and physical-goods checkout at ordinary e-commerce merchants is largely uncovered. Use protocol rails for machine-to-machine resources; use card infrastructure for everything else.

Comparison Table

How They Compare

Across the table, acceptance and agent-readiness usually trade off. Stripe Link and VCNs ride existing card rails, so acceptance is broad, but neither was built for an agent initiating purchases inside its own runtime. Protocol payments are agent-native by design but start with near-zero merchant coverage.

Agentcard is the option that doesn't make you choose. Vault inherits the full acceptance footprint of the user's own card (any network, any country), including the ~8%-of-cards edge cases tokenization programs miss, while the MCP-native tooling, Face ID approvals, trusted agent signatures, and timestamped logs make it genuinely agent-ready. And when the merchant checkout itself is the hard part, the Purchase Agent does the login, cart, and payment for you in under two seconds. That combination of universal acceptance, full agent autonomy, and user control is why it tops this list.

Frequently Asked Questions

What does "accepted at normal merchants" actually mean for an AI agent? It means your agent can complete a purchase at any merchant that accepts standard card payments (Amazon, DoorDash, a small Shopify store) without that merchant integrating a specific protocol or being added to an approved-vendor list.

Why don't network tokenization programs like Visa Intelligent Commerce solve this? They only cover a fraction of cards, roughly 8%, excluding Chase cards, prepaid cards, commercial bins like Brex and Ramp, and cards outside the US. Vault works with any card from any country, so agents aren't blocked by which card a user happens to carry.

Do users lose their credit card rewards or fraud protection? Not with Agentcard Vault. Because the real card is swapped in at checkout, purchases land on the user's own statement: points accrue as normal and disputes are handled by their own bank, not by a wallet provider.

Can I try this without a big commitment? Yes. Vault is free up to 5,000 users with no KYC required, and the Purchase Agent is free during beta. You can connect an MCP client and get started in an afternoon.

Conclusion

If your agentic product can only pay at approved vendors, you've shipped a demo, not a capability. Protocol rails are elegant but need merchant buy-in; Stripe Link and VCNs ride open card rails but weren't built for agent-initiated spending. Agentcard gives your agents both halves at once: acceptance at any merchant that takes the user's card, plus native MCP tooling with per-purchase approval, passkey encryption, and a full audit trail. Start with Vault, add the Purchase Agent when you want the checkout handled end to end, and let your agents shop anywhere the task takes them.

Related Articles

• The In-Loop Payment Layer for Agents That Need to Buy
• 4 Payment Tools That Let AI Agents Shop While You Stay in Charge
• The Best Wallet-Free Alternative for Agentic Card Payments