How Agentic Card Payments Work Without a Pre-Funded Wallet

Yes, there is a model that removes the top-up step entirely: instead of funding a separate agent wallet before anything can happen, the agent pays at real checkouts with the card the user already owns. Agentcard works this way. Its Vault stores the user's own credit or debit card once, encrypted with a passkey on their phone, and the user approves each purchase with Face ID while the agent handles checkout. No prefunded balance, no KYC, no waiting for a transfer to clear.

Introduction

Most agentic payment platforms are wallet-first by design. The typical flow: the user signs up, completes identity verification, moves money into a separate balance (often held in stablecoin), and only then can their agent start spending against it. Every purchase drains that balance, and sooner or later the user has to stop and top it up again.

That design creates real friction. The user does manual work before getting any value, funds sit locked away from their bank account, and rewards points never accrue because the purchase never touches their card. For builders, the funding step is an onboarding drop-off point and one more thing to support.

This article explains the wallet-free alternative: how agents pay on the user's existing card, what changes under the hood, and the one case where a pre-funded card still makes sense.

Key Takeaways

Pre-funded wallet platforms require users to move money into a separate balance before an agent can spend, and every purchase drains that balance.
The wallet-free model lets agents pay with the card the user already has: store it once, approve each purchase, and the real card is swapped in at checkout.
Agentcard Vault needs no prefunding and no KYC, works with any card from any country (Visa, Mastercard, American Express, and more), and is free up to 5,000 users.
Purchases run on the user's own card, so users keep their rewards points and disputes go to their own bank.
The Purchase Agent completes merchant checkouts from one /buy call or MCP tool, in under 2 seconds at a 99% success rate across 18+ merchants.
A pre-funded card still fits when you need cards you fund yourself, hard spend caps, or interchange revenue, and both models can run side by side.

Why Most Agent Payment Platforms Start With a Funded Wallet

Wallet-first platforms require a funded balance for defensible reasons. Holding stored value simplifies their compliance posture, because they move money rather than card credentials. And it plugs cleanly into crypto rails, where the balance is usually a stablecoin.

The costs land on the user and the builder. The user completes KYC, waits for funds to arrive, and manages a top-up loop forever. Money that could be spent somewhere real sits as float. If the balance runs out mid-task, the agent fails at the worst possible moment.

A second approach avoids wallets through network tokenization programs such as Visa Intelligent Commerce and Click to Pay. These route purchases through tokenized credentials instead of a stored balance, but they work for roughly 8% of cards, excluding Chase cards, prepaid cards, commercial bins, and everything outside the US. For a global user base, that is not a workable foundation.

The Wallet-Free Model: Pay With the Card the User Already Has

Agentcard's Vault inverts the flow. The user never moves money. They store the card they already carry, and the agent spends against it at normal checkouts. Here is the sequence:

The user adds their card once. They open a wallet link (web embed, iOS or React Native SDK, hosted link, or CLI) and enter an existing credit or debit card. Any card from any country works, including consumer, commercial, and prepaid cards.
The card is encrypted with a passkey on the user's phone. Neither the agent, the builder, nor Agentcard can read it, and cards are encrypted at rest with AES-256-GCM and per-card keys.
The user approves each purchase with Face ID. Builders can set auto-approve thresholds so low-value purchases skip the manual approval.
Agentcard swaps the real card in at checkout. The agent works with a dummy card number, and the real credentials are substituted at the payment step. The real card never leaves the vault.
The purchase posts to the user's own card. Points accrue as they would on any normal purchase, and disputes are handled by the user's own bank.

There is no KYC step, onboarding is entering a card one time, and the wallet is fully white-labeled, so builders can embed it under their own brand. Vault is free up to 5,000 users, then moves to enterprise pricing.

What the Agent Actually Does at Checkout

Storing a card solves the funding problem, but the agent still has to survive a real merchant checkout. That is the job of the Purchase Agent. The builder makes one POST /buy call, or uses the buy tool over MCP, and sends plain-text intent such as "order two boxes of diapers from Amazon." Agentcard connects to the merchant, logs in, builds the cart, pays with the user's stored card, and returns the order confirmation. Money only moves when the cart is confirmed.

Purchases complete in under 2 seconds at a 99% success rate across 18+ live merchants, including Amazon, DoorDash, Walmart, and flights, backed by 23 mapped payment processors plus direct Amazon and DoorDash integrations. Every approved transaction carries a trusted agent signature and a timestamped log entry, giving builders and users a full audit trail.

Integration is deliberately thin. Agentcard is MCP-native: point a client such as Claude Code, Claude Desktop, or Cursor at the remote endpoint and authenticate with OAuth using your client_id and client_secret. Tools cover card creation, details, balances, closure, transactions, and the buy purchase tool. Most teams go live in an afternoon, and the Purchase Agent costs $0.15 per request, free during beta.

When a Pre-Funded Card Still Makes Sense

The wallet-free model is the right default, not the only tool. Agentcard's own 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.

Issuing creates new virtual Visa cards for the agent, as single-use cards that close automatically after the first approved charge or as multi-use cards. It requires KYC before the first card, funds a per-user wallet in USDC on Base, and prices at $5,000 per month plus a 1% revenue share. Agentcard handles chargebacks, and users earn Tokenback rewards instead of their own card points. Both can run side by side, so platforms can offer wallet-free payments to most users and funded, capped cards to the workflows that genuinely need them.

The distinction matters when you evaluate vendors: the no-prefunding advantage belongs to the vault model specifically. Any platform that only issues cards against a funded balance still carries the top-up loop, whatever else it automates.

Frequently Asked Questions

Do users have to move money into a separate balance before their agent can pay? No. With Vault there is no balance to fund. The user stores their own card once, and the agent pays at real checkouts on that card. Prefunding only enters the picture with Issuing, the fallback for teams that want cards they fund themselves.

Does wallet-free mean handing the raw card number to the agent? No. The card is encrypted with a passkey on the user's phone, and neither the agent, the builder, nor Agentcard can read it. The agent only ever sees a dummy card number, the real credentials are swapped in at the payment step, and each purchase carries the user's Face ID approval, a trusted agent signature, and a timestamped log entry.

What about KYC and card compatibility? Vault requires no KYC and works with any card from any country on the major networks, including consumer, commercial, and prepaid cards. That coverage matters because network tokenization programs only support about 8% of cards. Issuing, by contrast, requires KYC before the first card can be created.

What does it cost to run? 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 a 1% revenue share.

Conclusion

The pre-funded wallet is a design choice, not a requirement of agentic payments. If the job is letting AI agents pay at real checkouts, the wallet-free rail is faster to onboard, keeps users' rewards and their bank's dispute protection intact, and keeps card data unreadable to everyone involved. Add the Purchase Agent on top and the agent does not just hold a payment method, it completes the entire checkout.

You can prove this out quickly. Open the Agentcard documentation, connect the MCP server to Claude Code or Cursor, store a card in Vault, and have your agent complete its first real purchase this afternoon.