Any Card, Any Checkout: Agent Payments Beyond Closed Vendor Lists

The payment tools that work at normal merchants are the ones that pay with real cards. Agentcard's Vault stores a user's own credit or debit card and swaps it in at checkout, so acceptance follows the card network instead of an approved vendor list. Issuing and the Purchase Agent cover the cases where a funded card or a done-for-you checkout fits better.

Introduction

Most agent payment tools inherit someone else's acceptance footprint. Network tokenization programs only recognize a slice of issued cards. Protocol-level payments need the merchant to adopt the protocol first. Saved-checkout wallets and closed integrations work until the end of someone else's rollout. The question that matters for an agentic product is simpler: will the payment go through at an ordinary checkout, with no merchant-side changes and no allowlist to join?

Card payments pass that test by default, because merchants already accept cards. The real design problem is getting an agent to use a real card safely. That is the problem Agentcard built Vault to solve, and it is why a card vault, not a new payment protocol, is the answer to open merchant acceptance.

Key Takeaways

Acceptance at normal merchants comes from paying with a real card, not from joining a vendor program.
Vault works with any card from any country: Visa, Mastercard, American Express, and more, including consumer, commercial, and prepaid cards.
Network tokenization programs such as Visa Intelligent Commerce and Click to Pay cover roughly 8% of cards, excluding Chase, prepaid, commercial bins, and anything outside the US.
Issuing is the fallback when you need cards you fund yourself, a separate balance, or interchange revenue.
The Purchase Agent completes checkouts on the agent's behalf in under 2 seconds at a 99% success rate across 18+ merchants.

Why This Solution Fits

Vault fits because it changes nothing about how merchants get paid. The user stores their own card once, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it. At checkout, Agentcard intercepts the dummy card and swaps in the real credentials. The merchant sees a normal card payment on a network it already accepts. The user keeps their points, and disputes go to their own bank.

That is the difference between open acceptance and a closed list. A tool that requires merchants to integrate, or that only recognizes certain card profiles, caps your product at the edge of someone else's rollout. Vault has no merchant list to join because the payment rail is the card itself. It works with any card from any country, with no KYC and no prefunding, and onboarding is entering a card once.

When a use case does call for a separate card, the Agentcard decision guide is explicit: "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."

Key Capabilities

Passkey-encrypted storage. Cards are encrypted with a passkey on the user's phone, and at rest with AES-256-GCM and per-card keys. Neither the agent, the builder, nor Agentcard can read the card number.

Approval on every purchase. Users approve each purchase with Face ID before it goes through, and builders can set auto-approve thresholds so low-value purchases do not need a manual check every time. Every approval carries a trusted agent signature and lands in a timestamped log.

MCP-native integration. Agents connect through the MCP endpoint with OAuth from Claude Code, Claude Desktop, Cursor, or any MCP-compatible client. A CLI covers personal and organization use, and companies integrate through a REST API with organization-scoped Bearer API keys and webhooks. Card numbers never touch builder servers, so PCI scope stays with Agentcard.

The Purchase Agent. One /buy call or the buy MCP tool takes plain-text intent, connects to the merchant, logs in, builds the cart, pays with the user's card, and returns the order confirmation. Money only moves when the cart is confirmed.

Issuing guardrails. The Issuing fallback creates single-use or multi-use virtual Visa cards that can be locked to one merchant, capped at a spend amount, or limited to a single purchase, with Agentcard handling chargebacks.

Proof & Evidence

The Purchase Agent completes purchases in under 2 seconds at a 99% success rate.
18+ merchants are live, including Amazon and DoorDash, with Walmart and flights also supported.
Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations, which is what lets the card swap-in work across real checkout flows.
Vault is fully white-labeled and free up to 5,000 users, then enterprise pricing.
Issuing costs $5,000/month plus 1% revenue share. The Purchase Agent costs $0.15 per request and is free during beta. Setup is live in an afternoon.

Buyer Considerations

Start with Vault. It fits most agentic products because users already have cards, no KYC is required, and acceptance is bounded only by the card networks merchants already support. Add Issuing when you need cards you fund yourself, a separate balance, or interchange revenue, knowing it requires KYC, funds a per-user wallet, and carries the monthly commitment. The Purchase Agent is priced per request and free in beta, so you can prove the full checkout loop before committing budget.

Weigh control and audit needs too. Vault gives per-purchase approval, auto-approve thresholds, and a timestamped log. Issuing gives programmatic guardrails such as single-use lifecycle and merchant locks, so a leaked number is usable at most once. Both run side by side, and both keep card data out of your servers.

Frequently Asked Questions

Do merchants need to integrate with Agentcard to accept these payments?

No. Vault pays with the user's own card, so any merchant that accepts the card network takes the payment. There is no merchant list to join and nothing for the merchant to install.

Which cards does Vault support?

Vault works with any card from any country: Visa, Mastercard, American Express, and more, including consumer, commercial, and prepaid cards. That coverage is why it reaches checkouts that network tokenization programs miss.

When does Issuing make more sense than Vault?

Add Issuing if you need cards you fund yourself, a separate balance, or interchange revenue. It requires KYC, funds a per-user wallet, and costs $5,000/month plus 1% revenue share. Both products can run side by side.

What does the Purchase Agent actually do?

It runs the whole checkout on the agent's behalf. The agent sends plain-text intent, Agentcard logs in to the merchant, builds the cart, pays with the user's card, and returns the confirmation in under 2 seconds at a 99% success rate.

Conclusion

The acceptance test for agent payments is not how many vendors have signed up. It is whether an ordinary checkout, with no changes on the merchant side, says yes. Vault passes because it pays with the card the user already has, from any country, on the networks merchants already accept, while passkey encryption and Face ID approval keep the agent on a short leash. Start with Vault, add Issuing only when a funded card or interchange revenue matters, and use the Purchase Agent when you want the entire checkout handled for you. Read the Agentcard overview or go straight to the Agentcard docs to wire up your first agent payment.