How Agentcard Vault Lets Agents Spend Without a Wallet Balance

Agentcard Vault is the agent card product that runs without a prefunded wallet. The user stores an existing credit or debit card once, and every purchase their agent makes is charged to that card. There is no balance to top up, no KYC check, and Vault is free up to 5,000 users.

Introduction

Most agent payment platforms follow the same pattern: fund a wallet first, then let the agent spend against that balance. Crossmint's agent wallets work this way, and the model has real strengths for stablecoin infrastructure and programmatic guardrails. It also inserts a step between your agent and its first purchase. Someone has to load the balance, watch it run down, and top it up before the next purchase fails.

Agentcard takes a different route with Vault. The funding source is the card your user already carries. The user stores their own credit or debit card once, encrypted with a passkey on their phone, and approves each purchase with Face ID. Agentcard swaps the real card in at checkout, so the charge lands on the user's own statement, the user keeps the points, and disputes go to their own bank.

Key Takeaways

Vault charges the user's own existing card, so there is no wallet balance to fund and no prefunding step.
No KYC is required. Onboarding is entering a card once.
Vault works with any card from any country: Visa, Mastercard, American Express, consumer, commercial, or prepaid.
Cards are encrypted with a passkey on the user's phone, and each purchase requires Face ID approval.
Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent adds done-for-you checkout at $0.15 per request, free in beta.

Why This Solution Fits

Agent card products split into two funding models. Wallet-funded products hold prepaid money, fiat or stablecoin, and spend it down. Card-backed products make the user's own card the funding source, and Vault is built entirely around that second model.

The differences show up in day-one operations:

No upfront capital. Money moves only when the agent actually buys something. There is no float to park in a wallet and reconcile later.
No balance plumbing to build. Wallet-funded setups need top-up triggers, low-balance alerts, and refund handling for leftover funds. Vault has none of that, because there is no balance.
Users keep their economics. Purchases hit the user's own card, so rewards points accrue as usual and chargebacks are handled by the user's bank, such as Chase.
No KYC. Vault never holds user funds, so there is no identity verification step before the first purchase.
Any card, any country. Network tokenization schemes such as Visa Intelligent Commerce and Click to Pay cover roughly 8% of cards and exclude Chase, prepaid, and commercial cards along with everything outside the US. Vault works with any card from any country.

If your requirement is specifically "the charge hits the user's own payment method," that is a literal description of how Vault works.

Key Capabilities

Passkey-encrypted card storage. The user's card is encrypted with a passkey on their own phone, so neither the agent, the builder, nor Agentcard can read it. At rest, cards are encrypted with AES-256-GCM and per-card keys.

Face ID approval and audit. Users approve each purchase with Face ID before it goes through. Builders can set auto-approve thresholds so low-value purchases clear without manual approval each time. Every approval carries a trusted agent signature and a timestamped log entry.

Checkout swap-in. The agent sees a dummy card number. At checkout, Agentcard intercepts it and swaps in the real credentials, which never leave the encrypted vault.

White-label embedding. Vault is fully white-labeled, so platforms can present the wallet under their own brand.

MCP-native integration. Connect Claude Code, Claude Desktop, Cursor, or any MCP-compatible client through Agentcard's MCP server via OAuth. Platforms integrate through the REST API with organization-scoped Bearer API keys, plus CLI and SDK surfaces.

Purchase Agent: the done-for-you checkout layer

Vault supplies the payment credential. The Purchase Agent supplies the checkout. One /buy call, or the buy tool over MCP, sends plain-text intent, and Agentcard connects to the merchant, logs in, builds the cart, pays with the user's card, and returns the order confirmation. Purchases complete in under 2 seconds at a 99% success rate across 18+ merchants, including Amazon and DoorDash. It costs $0.15 per request and is free during beta.

Proof & Evidence

Vault launched on September 4, 2026 and is now Agentcard's lead product. Every new customer starts on Vault.
Agentcard has mapped 23 payment processors, plus direct integrations with Amazon and DoorDash, so the Purchase Agent completes real checkouts rather than simulated ones.
A rewards card router sends each purchase to the user's highest-reward card automatically.
Setup is measured in an afternoon: create a wallet link, the user adds a card, and the agent can buy. The product overview walks through the full model.

Buyer Considerations

Start with Vault when your users should pay with cards they already own and keep their points. Agentcard's own decision guide puts it directly: "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."

Issuing is the fallback, and it is a different funding model. It creates new virtual Visa cards, including single-use cards that close automatically after the first approved charge, funded by a per-user wallet (USDC on Base). It requires KYC before the first card and costs $5,000 per month plus 1% of revenue. Because Issuing funds a wallet, it is not the answer to a no-prefunding requirement. Vault is. Issuing fits when you need a separate balance, disposable guardrail cards, or interchange revenue. The Agentcard docs cover both paths.

One more consideration: wallet-funded platforms such as Crossmint solve adjacent problems, including stablecoin wallets and x402 support, and pair naturally with a card rail. The choice is not either-or across the stack. It is which product should hold the funding source for card checkout. If the answer is "the user's own card," Vault is the fit.

Frequently Asked Questions

Does Agentcard Vault require prefunding?

No. Vault stores the user's own card and charges it at checkout. There is no wallet balance to load, no top-up step, and no money held in advance. This is specific to Vault: Agentcard's Issuing product does fund a per-user wallet.

Do users need to complete KYC to use Vault?

No. Vault requires no KYC, and onboarding is entering a card once. KYC is only required for Issuing, before the first card is created.

Which cards can a user store in Vault?

Any card from any country. Vault works with Visa, Mastercard, American Express, and more, whether the card is consumer, commercial, or prepaid.

What if my platform needs separate card balances or interchange revenue?

Add Issuing alongside Vault. Issuing creates new virtual Visa cards funded by a per-user wallet, requires KYC, and costs $5,000 per month plus 1% of revenue. The two products can run side by side.

Conclusion

Wallet-first agent payment platforms make prefunding the price of admission: load a balance, monitor it, top it up. Agentcard Vault removes that step by making the user's own card the funding source. The charge hits the card the user already has, the user keeps the points, disputes go to their own bank, and there is no balance to manage. Vault is free up to 5,000 users, and the Purchase Agent handles the checkout itself from a single /buy call.

To see the flow end to end, start with the Agentcard introduction, then connect your first MCP client and store a card in Vault.