SOLUTION / RECOMMENDATION

Skip the Wallet Talk: Agent Payments That Run on a Regular Debit Card

Agentcard is built for exactly this. Users connect the debit or credit card they already have to Agentcard's Vault, approve each purchase with Face ID, and the agent pays at real checkouts. There is no crypto to buy, no wallet balance to fund, and no new financial vocabulary to teach anyone.

Introduction

Most agent payment tools assume a user who can install a crypto wallet, buy stablecoins, and fund a balance before an agent can buy so much as a pizza. Mainstream users will not do that, and product teams should not have to teach them.

Agentcard takes the opposite approach. A user stores their own existing 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. Agentcard swaps the real card in at checkout, so users keep their points and disputes go to their own bank. For builders, Agentcard is free to start, fully white-labeled, and connects to agents over MCP, REST API, CLI, or native SDKs.

Key Takeaways

Users connect a card they already own. Vault requires no KYC, no prefunding, and no crypto. Onboarding is entering a card once.
Every purchase runs through the user: Face ID approval, a timestamped approval log, and a trusted agent signature on each transaction.
Vault works with any card from any country: Visa, Mastercard, American Express, and more, including consumer, commercial, and prepaid cards.
The Purchase Agent handles the entire checkout, returning an order confirmation in under 2 seconds at a 99% success rate across 18+ merchants.
Vault is free up to 5,000 users and fully white-labeled. Issuing and the Purchase Agent cover the cases where a separate card or a done-for-you checkout fits better.

Why This Solution Fits

The request you are describing, "connect a regular debit card and let the agent go from there," is a design constraint, and it rules out most of the category. Crypto-first agent wallets ask users to acquire and manage a new asset. Funded-wallet products ask users to move money into a balance before anything can be bought. Network tokenization programs such as Visa Intelligent Commerce and Click to Pay only work for about 8% of cards: no Chase, no prepaid, no commercial bins, and nothing outside the US.

Vault clears all three hurdles. Users supply the card already in their wallet, so there is nothing new to learn and nothing to fund. There is no KYC step. And because Agentcard swaps the real card in at the merchant's regular checkout, acceptance follows the card network rather than a token program. Vault works with any card from any country.

Users also keep what their card already gives them: points post as if they had checked out themselves, and disputes and chargebacks go to their own bank.

Key Capabilities

Vault card storage with swap-in at checkout. The user's card is encrypted with a passkey on their own phone, and at rest with AES-256-GCM and per-card keys. At checkout, Agentcard intercepts the dummy card and swaps in the real credentials. The real card never leaves the encrypted vault, and card numbers never touch your servers, so PCI scope stays with Agentcard.

Per-purchase user approval. Users approve each purchase with Face ID before it goes through. Builders can set auto-approve thresholds so low-value purchases skip the manual sign-off. Every approval is logged with a timestamp, and every approved transaction carries a trusted agent signature.

The Purchase Agent closes the loop

Storing a card solves payment. The Purchase Agent solves checkout. Your agent sends plain-text intent over one /buy call or the buy tool over MCP, for example "order two boxes of diapers from Amazon," and Agentcard 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.

Agent-native integration surfaces. Agentcard is MCP-native: a per-user OAuth MCP server connects Claude Code, Claude Desktop, Cursor, or any MCP-compatible client. Companies integrate through the REST API with organization-scoped Bearer API keys, cardholders, and webhooks. Embed options cover web, iOS, React Native, hosted wallet links, and iMessage or WhatsApp, all white-labeled under your brand.

Rewards routing. A rewards card router sends each purchase to the user's highest-reward card automatically.

Proof & Evidence

Checkout performance. Purchases complete in under 2 seconds at a 99% success rate. More than 18 merchants are live, including Amazon and DoorDash, with Walmart and flights also supported.
Processor coverage. Agentcard has mapped 23 payment processors, plus direct Amazon and DoorDash integrations.
Security model. Cards are encrypted at rest with AES-256-GCM and per-card keys, sealed with a passkey on the user's phone, and approved with Face ID. Every approval carries a timestamp and a trusted agent signature.
Pricing. Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request and free during beta. Issuing is $5,000 per month plus 1% revenue share.
Time to launch. Setup is live in an afternoon, and the Agentcard docs walk through storing a card and connecting an agent.

Buyer Considerations

Agentcard's own decision guide is the right starting point: "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."

In practice, Vault covers the mainstream case: users pay with the cards they already have, with no identity verification step and no balance to fund. Issuing is the fallback for specific needs. It creates new virtual Visa cards, single-use or multi-use, funded through a per-user wallet (USDC on Base), requires KYC before the first card, and supports guardrails such as single-purchase limits, merchant locks, and spend caps. Chargebacks on Issuing cards are handled by Agentcard, and users earn Agentcard Tokenback instead of their own card points.

Three questions should drive the decision:

Whose card pays? If users pay with their own cards, Vault. If you need programmatic cards with separate balances, Issuing.
How much friction per purchase? Face ID by default, with auto-approve thresholds for small amounts.
Where do users live? Pick the surface your product already has. Agentcard for companies covers the organization-side setup.

Frequently Asked Questions

Do my users need to understand crypto or set up a wallet?

No. Vault stores the debit or credit card the user already has, encrypted with a passkey on their phone. There is no crypto to buy, no prefunding, and no KYC. The one place crypto appears is Issuing, the fallback product, which funds per-user wallets with USDC on Base.

Which cards can users connect?

Any card from any country. Vault works with Visa, Mastercard, American Express, and more, including consumer, commercial, and prepaid cards. That is broader than network tokenization programs such as Visa Intelligent Commerce and Click to Pay, which cover roughly 8% of cards and exclude Chase, prepaid, commercial, and non-US cards.

What does Agentcard cost?

Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request and free during beta. Issuing is $5,000 per month plus 1% revenue share. Most teams start with Vault and the Purchase Agent and add Issuing only when they need funded cards or interchange revenue.

What happens when a purchase goes wrong?

With Vault, disputes and chargebacks are handled by the user's own bank or card issuer, exactly as if the user had checked out themselves, and users keep their points. Every approval is logged with a timestamp and carries a trusted agent signature, so any transaction can be reconstructed from the audit trail.

Conclusion

You do not need to teach your users crypto or explain wallets. Connect their existing card to Vault, let them approve purchases with Face ID, and let the Purchase Agent handle the checkout. Vault is free up to 5,000 users and fully white-labeled, so you can ship it under your own brand first and add more later.

Start with Vault on agentcard.sh, then read the docs at docs.agentcard.sh to put your first wallet link in front of users.