Agent Payment Tools That Let Users Pay With Their Own Card, No Balance Loading Required

Most agent payment tools force users to preload a separate balance before their AI agent can spend anything. Agentcard takes the opposite approach: its Vault stores the user's own existing credit or debit card once, encrypted with a passkey on their phone, and swaps the real card in at checkout, so users keep their points, disputes go to their own bank, and there is no wallet to fund and no KYC to complete.

Introduction

If you're building an AI agent that spends money, you've probably run into the same wall: nearly every payment tool on the market asks your users to load money into a balance first. Prepaid wallets, USDC funding, prefunded virtual cards, the user has to move money somewhere else before their agent can buy anything. That's friction, and friction kills adoption.

The alternative is to let agents pay with the card the user already carries. That's exactly what Agentcard Vault does. The user stores their own card once, approves each purchase with Face ID, and Agentcard swaps the real card in at checkout. No balance to load, no KYC, no new financial account. This article explains how that model works, why it fits most agent payment use cases better than prefunded alternatives, and what to consider before you integrate.

Key Takeaways

Vault lets users pay with their own existing card, any card from any country, on Visa, Mastercard, or American Express, consumer, commercial, or prepaid.
No prefunding, no KYC. Onboarding is entering a card once; there is no separate balance to top up.
Users keep their points and dispute rights. Because the real card is used at checkout, rewards accrue as normal and chargebacks go to the user's own bank.
Security is enforced at the device and network level: passkey encryption on the user's phone, Face ID approval per purchase, and AES-256-GCM encryption at rest.
Vault is free up to 5,000 users and fully white-labeled, so builders can embed it under their own brand.

Why This Solution Fits

The question most builders are really asking is: "Can my user's agent just use the card they already have?" With Agentcard, the answer is yes, and that changes the economics of agent payments entirely.

Prefunded models force users to part with their money before they've bought anything. That creates three problems: users hesitate to lock up funds in yet another wallet, builders carry compliance and custody burdens, and every top-up is a drop-off point in your funnel. Vault eliminates all three. There is no wallet to fund, no identity verification to pass, and no new account to manage: the user's existing card is the payment instrument.

The decision guide is simple: start with Vault. It's the default for every new customer because it removes onboarding friction while preserving everything users care about, their rewards, their chargeback protections, and their bank relationship. Issuing, Agentcard's fallback product, still exists for the cases where you genuinely need a new card you fund yourself, a separate balance, or interchange revenue. But for the overwhelming majority of agent payment flows, paying with the user's own card is the better answer, and Vault is the only tool in this category built around that model end to end.

Key Capabilities

Store any card, once. Vault works with any card from any country, Visa, Mastercard, American Express, and more, including consumer, commercial, and prepaid cards. By contrast, network tokenization approaches like Visa Intelligent Commerce and Click to Pay work for only about 8% of cards: no Chase, no prepaid, no commercial BINs, and nothing outside the US. Vault has no such restrictions.
Passkey encryption on the user's phone. The card is encrypted with a passkey on the user's own device, so neither the agent, the builder, nor Agentcard can read it. Cards are encrypted at rest with AES-256-GCM and per-card keys.
Face ID approval on every purchase. Users approve each transaction before it goes through, with a timestamped approval log. Builders can configure auto-approve thresholds so low-value purchases flow without manual approval each time.
Card swap at checkout. Agentcard intercepts the dummy card and swaps in the real credentials at the merchant, so the real card never leaves the encrypted vault. Users keep their points, and disputes are handled by their own bank.
The Purchase Agent does the checkout. One /buy call or the buy tool over MCP sends plain-text intent, "order two boxes of diapers from Amazon", and 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 across 18+ live merchants.
MCP-native and white-labeled. Connect via OAuth to Claude Code, Claude Desktop, Cursor, or any MCP-compatible client, or embed the wallet under your own brand with web, iOS, React Native, and hosted-link options.

Proof & Evidence

The strongest evidence is the architecture itself. Because Vault uses the user's real card at checkout, the card network's own protections apply: rewards post as they would on any ordinary purchase, and chargebacks are handled by the user's issuer, for example, their bank, rather than by a third-party platform. That's a materially better consumer position than prefunded wallets, where dispute rights and rewards depend on the wallet provider's terms.

On security, cards are encrypted with a passkey on the user's phone and at rest with AES-256-GCM using per-card keys, and every approval carries a trusted agent signature and a timestamped log. For builders, card numbers never touch your servers, keeping PCI scope with Agentcard. These controls follow the zero-trust principle of least privilege for autonomous spend, the same approach Agentcard outlines in its financial zero trust for AI agents and agent spending security checklist.

Operationally, the Purchase Agent completes purchases in under 2 seconds at a 99% success rate, with 18+ merchants live including Amazon and DoorDash. You can read the full product overview in the docs or go straight to the quickstart to see the flow yourself.

Buyer Considerations

Before you integrate, weigh the following:

Start with Vault, add Issuing only if you must. If your use case genuinely requires cards you fund yourself, a separate balance, or interchange revenue, Issuing covers it, with KYC and per-user wallet funding (USDC on Base). Otherwise, Vault's no-KYC, no-prefunding model will convert better.
Rewards and disputes stay with the user's bank. This is a feature, not a gap: users keep their card points and their issuer's chargeback protections.
Pricing. Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request and free during beta. See pricing for details.
Approval UX. Face ID on every purchase maximizes user control; auto-approve thresholds trade a little control for a smoother flow on low-value purchases. Decide which default fits your product.
Merchant coverage. 18+ merchants are live today, including Amazon and DoorDash, with 23 payment processors mapped. Confirm the merchants your agent needs are covered.

Frequently Asked Questions

Do users have to load money into a balance before their agent can pay?

No. With Vault, there is no balance to fund. The user stores their own existing card once, and Agentcard swaps the real card in at checkout. Prefunding is only a feature of Issuing, the fallback product for builders who need separately funded cards.

Does Vault require KYC?

No. Because the user pays with their own card, there is no identity verification step. Onboarding is simply entering a card once. Issuing, by contrast, requires KYC before the first card.

Which cards work with Vault?

Any card from any country on Visa, Mastercard, or American Express, consumer, commercial, or prepaid. This is a key advantage over network tokenization approaches like Visa Intelligent Commerce and Click to Pay, which work for only about 8% of cards.

What happens if a purchase goes wrong?

Disputes and chargebacks are handled by the user's own bank or issuer, exactly as they would be on a normal purchase, and users keep the points their card earns. Every approval is logged with a timestamp and carries a trusted agent signature.

Conclusion

If you want your users' agents to pay without forcing them into a prefunded wallet, Vault is the tool built for exactly that. Users store their own card once, approve purchases with Face ID, and keep their points and dispute rights, while you get MCP-native integration, the Purchase Agent's done-for-you checkout, and white-labeling under your own brand, free up to 5,000 users. Start with the quickstart, explore the API reference, or head to agentcard.sh to get your first agent paying with a real card today.