Prefunded Wallets, Explained: Which Card Issuing APIs Let Agents Spend Without One?

Almost every card issuing API requires prefunding: a newly issued card has no balance until someone loads one. The APIs that skip prefunding never issue a new card at all. Agentcard's Vault stores the card your user already owns and swaps it in at checkout, so an agent can spend from the first purchase with no wallet funding.

Introduction

Build an agent on a card issuing API and the same wall appears in every onboarding flow: before the agent can buy anything, the end user has to create a cardholder, pass identity verification, and fund a wallet. Only then does the issued card have something to draw from. That sequence is not a pricing trick or an implementation detail one vendor forgot to remove. It is what issuing means.

This article explains why prefunded balances are structural to card issuing APIs, what the alternatives look like, and why one of them, storing the user's own card in a vault, removes the funding step without removing the controls. The examples use Agentcard, which runs both models: Vault with no prefunding, and Issuing with a funded wallet for the cases that need one.

Key Takeaways

Prefunding is structural to card issuing. A newly issued card is a payment instrument backed by a balance, and the issuer authorizes each transaction against funds loaded in advance.
The no-prefunding path charges a card the user already has instead of issuing a new one.
Agentcard's Vault stores the user's card once, encrypted with a passkey on their phone, and swaps it in at checkout after Face ID approval. No wallet, no balance, no KYC.
Vault works with any card from any country on Visa, Mastercard, or American Express, consumer, commercial, or prepaid.
Vault is free up to 5,000 users, then enterprise pricing, and is fully white-labeled.

Why Card Issuing APIs Are Built Around Prefunded Balances

An issuing API creates a new card number, and that number is worthless at authorization time until money sits behind it. Every issuing platform therefore builds the same sequence into its core flow: create a cardholder, fund a wallet with a bank transfer or a stablecoin deposit, then issue a card that draws the balance down. The wallet is the reserve the issuer authorizes against.

Agentcard's own Issuing product works this way by design. Each user gets a per-user wallet funded in USDC on Base, and the virtual Visa cards the agent uses draw from it. The funding step buys real properties: a separate balance you control, hard spend caps, single-use cards that close after the first approved charge, and interchange revenue for the platform. The cost is friction. Every end user must pass KYC before the first card, fund the wallet before the first spend, and manage a leftover balance when refunds land.

For a builder, that friction lands at the worst moment: the first time a user hands their agent a task and the agent stops at a payment wall.

The No-Prefunding Model: Charge the Card Your User Already Has

The other way to give an agent spending power is to not issue a card at all. Agentcard's Vault takes the card the user already keeps in their wallet and makes it agent-usable:

The user stores their card once through a white-labeled wallet link.
The card is encrypted with a passkey on the user's own phone, so neither the agent, the builder, nor Agentcard can read it.
The agent initiates a purchase, and the user approves it with Face ID.
Agentcard swaps the real card in at checkout. The user keeps their points, and disputes go to their own bank.

Nothing is loaded in advance because nothing needs to be. The user's existing credit line is the balance. Vault works with any card from any country, on Visa, Mastercard, or American Express, whether the card is consumer, commercial, or prepaid. The product overview walks through the full flow.

That last point matters because the other no-new-card approach, network tokenization through programs like Visa Intelligent Commerce and Click to Pay, works for approximately 8% of cards. It excludes Chase cards, prepaid cards, commercial bins, and everything outside the US. Vault covers all of them.

How Builders Wire It Up

The builder-side integration is one server call to create a wallet link. The user opens the link, adds their card, and the agent is ready to spend. Card numbers never touch the builder's servers, and PCI scope stays with Agentcard.

For companies, the REST API uses organization-scoped Bearer API keys with cardholders and webhooks, and the MCP server connects Claude Code, Claude Desktop, Cursor, or any MCP-compatible client through OAuth. CLI and SDK surfaces cover terminals, iOS, React Native, and backend agents with no frontend at all.

Where the Purchase Agent Fits

Vault solves the credential. The Purchase Agent solves the checkout. One POST /buy call 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 moves only when the cart is confirmed. Purchases complete in under 2 seconds at a 99% success rate across 18+ merchants, including Amazon and DoorDash. The Purchase Agent costs $0.15 per request and is free during beta.

When a Prefunded Wallet Is Still the Right Call

Prefunding is not a defect to eliminate everywhere. Some products need cards with their own balance: capped budgets, disposable single-use numbers, or interchange revenue. That is what Issuing is for.

The decision guide is simple: 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 costs $5,000 per month plus 1% revenue share.

Frequently Asked Questions

Why do card issuing APIs require users to fund a wallet first?

Because an issued card is a payment instrument backed by a balance. Until someone loads that balance, the issuer has nothing to authorize against. Agentcard's Issuing product works the same way, with a per-user wallet funded in USDC on Base.

How can an agent spend with no wallet funding at all?

Through Vault. The user stores their own 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 no balance is loaded anywhere before the first spend.

Does skipping prefunding mean giving up spending controls?

No. Users approve each purchase with Face ID, builders can set auto-approve thresholds so low-value purchases flow without manual approval, every approval lands in a timestamped log, and each transaction carries a trusted agent signature.

What does Agentcard cost without prefunding?

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

Conclusion

A prefunded wallet is a requirement of issuing new cards, not a requirement of agent payments. If your users already have cards, Vault turns those cards into agent-usable payment credentials with no funding step, no KYC, and no lost points, and the Purchase Agent handles the checkout itself. Start with Vault at agentcard.sh, then read the API reference or work through the Agentcard docs when you are ready to wire it in.