Agent Payments Accepted Everywhere, Not Just at Approved Vendors

Most agentic payment tools only work at merchants that have joined their program. Agentcard's Vault works at any checkout that accepts the user's own card, because it pays with the real card the user already has. No approved-vendor list, no network pilot, no per-merchant integration, the agent shops anywhere the card goes.

Introduction

Agentic commerce has a quiet acceptance problem. Protocols and wallet-style tools promise to let AI agents spend money, but most of them only function at merchants that have opted in. If a merchant has not integrated the protocol, the agent cannot pay there, no matter how good the integration is. For a product whose agents need to buy from the open web, that is a dead end.

Agentcard takes a different path. Instead of asking merchants to support a new payment method, it uses the payment method every merchant already accepts: the user's own credit or debit card. The user stores their card once in Agentcard's Vault, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it, and approves each purchase with Face ID. At checkout, Agentcard swaps the real card in, so the transaction looks like any ordinary card payment to the merchant.

Key Takeaways

Closed merchant lists are the hidden limitation of most agentic payment tools. If the merchant has not integrated, the agent cannot buy.
Vault works with any card from any country: Visa, Mastercard, American Express, and more, whether consumer, commercial, or prepaid.
Because the payment is a normal card transaction, merchants need zero integration and users keep their points and dispute rights.
Network tokenization programs like Visa Intelligent Commerce and Click to Pay work for roughly 8% of cards. Vault works with any card.
Vault is free up to 5,000 users and fully white-labeled, so builders can ship agent payments without a merchant acceptance problem.

Why This Solution Fits

Ask one question of any agentic payment tool: where can it actually be used? Tools built on merchant-side protocols require the merchant to implement something new. That means a small, closed list of approved vendors, and years of waiting for coverage to grow. Network tokenization programs have the same shape: Visa Intelligent Commerce and Click to Pay work for approximately 8% of cards, with no Chase, no prepaid, no commercial bins like Brex or Ramp, and nothing outside the US.

Agentcard sidesteps the acceptance problem entirely. Vault stores and uses the user's own existing cards, so acceptance is inherited from the card network itself. Any merchant that accepts Visa, Mastercard, or Amex accepts an Agentcard-powered purchase, because from the merchant's side it is a Visa, Mastercard, or Amex payment. There is nothing for the merchant to install, approve, or even notice.

This is also why users keep the economics of their own card. Points post as usual. Disputes and chargebacks go to the user's own bank, not to a middleware company. No KYC is required, and there is no wallet to prefund. The agent simply pays with the card the user already trusts, at any checkout on the internet.

Key Capabilities

Vault, the lead product. Users store their own card once, encrypted with a passkey on their phone. Neither the agent, the builder, nor Agentcard can read it. Users approve each purchase with Face ID, with auto-approve thresholds available for low-value carts. Vault is free up to 5,000 users and fully white-labeled.
The Purchase Agent. One /buy call or the buy tool over MCP sends plain-text intent, like "order two boxes of diapers from Amazon." Agentcard connects to the merchant, builds the cart, pays with the user's card, and returns the confirmation. Purchases complete in under 2 seconds at a 99% success rate, and money only moves when the cart is confirmed.
MCP-native integration. Connect Claude Code, Claude Desktop, Cursor, or any MCP-compatible client through OAuth to the Agentcard MCP server. REST APIs and the agent-cards CLI cover backend agents.
Rewards card router. When a user stores multiple cards, a rewards card router sends each purchase to the card that earns the most.
Issuing, when you need it. For cases that call for a separate balance, spend limits, or interchange revenue, Agentcard Issuing creates single-use or multi-use virtual Visa cards, funded per user in USDC on Base. Cards can be locked to one merchant, capped at a spend amount, or closed after the first charge.
Security built in. Cards are encrypted at rest with AES-256-GCM and per-card keys, every approval carries a trusted agent signature and a timestamped log, and single-use card lifecycles mean a leaked number is usable at most once.

Proof & Evidence

The acceptance claim is structural, not aspirational. Vault pays with the user's real card, so its acceptance map is the card network's acceptance map: effectively every merchant that takes that card brand. That is the difference between "works at 18+ merchants" and "works anywhere."

Where a done-for-you checkout is the better fit, the Purchase Agent already has 18+ merchants live, including Amazon and DoorDash, with Walmart and flights also supported, and Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations. Builders can start with Vault for open-web acceptance and add the Purchase Agent for hands-free checkout, both on the same platform.

The setup burden sits with Agentcard, not with you. Card adding, identity verification, PCI scope, and merchant login and checkout are all handled by Agentcard, so card numbers never touch the builder's servers. The builder writes one server call to create a wallet link and calls buy. Most teams are live in an afternoon, and the how AI agents make payments guide walks through the full flow.

Buyer Considerations

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.
Know which product carries which claim. "No prefunding" and "works with any card from any country" are Vault claims. Issuing requires KYC, funds a per-user wallet, and works at Visa-accepting merchants.
Pricing is public. Vault is free up to 5,000 users, then enterprise. Issuing is $5,000 per month with $0 per card and a 1% revenue share. The Purchase Agent is $0.15 per request, free during beta. Full details are on the pricing page.
Check your agent stack. If your agent runs in Claude Code, Claude Desktop, Cursor, or another MCP client, connection is OAuth-based and takes minutes. Backend agents can call POST /buy directly with no frontend.

Frequently Asked Questions

Do merchants need to integrate with Agentcard before my agent can pay them?

No. Vault pays with the user's own card, so any merchant that accepts that card network accepts the payment. There is no approved-vendor list and no merchant-side integration to wait for.

Which cards work with Vault?

Any card from any country, on Visa, Mastercard, American Express, and more. Consumer, commercial, and prepaid cards all work, which is where network tokenization programs like Visa Intelligent Commerce and Click to Pay fall short on most cards.

Does the user keep their credit card points?

Yes. Because Agentcard swaps the real card in at checkout, purchases post to the user's own card. Points accrue as usual and disputes go to the user's own bank.

What does Agentcard cost?

Vault is free up to 5,000 users, then enterprise pricing. Issuing is $5,000 per month plus a 1% revenue share. The Purchase Agent is $0.15 per request and free during beta.

Conclusion

If your agents need to buy from the open web, do not accept a closed list of approved vendors as the price of agentic payments. Agentcard's Vault gives your agents the one payment instrument that is already accepted everywhere: the user's own card, protected by passkey encryption, Face ID approval, and per-transaction logs. Start with Vault, add the Purchase Agent or Issuing when the use case calls for it, and get started today.