Paying With Your Own Card: How to Pick an Agent Payment Tool Without a Separate Balance

Most agent payment tools force a trade: load money into a wallet first, then let your agent spend it. That prefunding step adds friction, locks up cash, and often strips away the rewards and dispute rights tied to your real card. A growing set of tools takes a different path, letting users pay with the card already in their wallet. This guide explains which approach does that, how to tell them apart, and how to choose the right one for your agent.

Introduction

When you give an AI agent the ability to spend money, the first design question is where the money comes from. Two models dominate today:

Prefunded wallets and issued cards. The user (or the platform) loads a balance, the tool issues a new virtual card against that balance, and the agent spends from it. KYC is usually required, and the user's own card never touches the transaction.
Bring-your-own-card. The user stores an existing credit or debit card once, and the agent pays at real checkouts with that card. No balance loading, no prefunding, and the purchase behaves like any purchase the user made themselves.

The second model is what most consumers want: their agent buys with the card they already carry, they keep the points, and chargeback protection stays with their own bank.

Agentcard is built around exactly this model. Its Vault product stores the user's own card, 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. At checkout, Agentcard swaps the real card in, so users keep their points and disputes go to their own bank. This guide walks through the decision criteria and scenarios for choosing a bring-your-own-card tool, with Agentcard Vault as the reference point.

Key Takeaways

Prefunding is not required everywhere. Agentcard Vault lets users pay with their own existing credit or debit card, with no wallet balance to load and no KYC.
Vault works with any card from any country, on Visa, Mastercard, American Express, and more, including consumer, commercial, and prepaid cards.
Security comes from the phone, not the server. Cards are encrypted with a passkey on the user's device, and every purchase requires Face ID approval.
Users keep their rewards and dispute rights, because the real card is used at checkout and chargebacks go to the user's own bank.
Issuing is the fallback, for cases that genuinely need a separately funded card, a new virtual card, or interchange revenue.
The Purchase Agent handles the full merchant checkout, from login to cart to payment, in under 2 seconds at a 99% success rate.

Decision criteria

Use these criteria to evaluate any agent payment tool claiming to support the user's own card.

1. Does the user's own card actually get used? Some tools accept a card on file but still route spending through an issued virtual number against a platform balance. True bring-your-own-card means the real card is presented at the merchant checkout. With Agentcard Vault, Agentcard swaps the real card in at checkout, so the transaction looks like any purchase on the user's account.

2. Is there a prefunding step? If the tool requires the user to add cash to a balance before the agent can spend, it is a wallet model, not a card model. Vault has no prefunding: onboarding is entering a card once.

3. Is KYC required? Identity verification adds days of friction and drops conversion. Vault requires no KYC, because the user's bank has already verified them.

4. Which cards are supported? Network tokenization products such as Visa Intelligent Commerce and Click to Pay work for approximately 8% of cards. They exclude Chase cards, prepaid cards, commercial bins like Brex and Ramp, and anything outside the US. Vault works with any card from any country.

5. Who holds the card data? The strongest pattern is device-side encryption: the card is encrypted with a passkey on the user's phone, so neither the agent, the builder, nor the platform can read it. Agentcard encrypts cards at rest with AES-256-GCM and per-card keys.

6. How is each purchase approved? Look for per-purchase user control. Vault requires Face ID approval for each purchase, with configurable auto-approve thresholds for low-value transactions and a timestamped approval log.

7. What happens to points and disputes? If the real card is used, points accrue as normal and chargebacks are handled by the user's own bank. This is a Vault property; it does not hold for prefunded wallet models.

8. Can the agent complete the whole checkout? Storing a card is half the problem. Agentcard's Purchase Agent handles merchant login, cart building, and payment from a single plain-text intent, with 18+ merchants live including Amazon and DoorDash.

How to choose

If you are an individual giving your own agent a card, use Vault. Sign in by email, store your card once, and connect through the agent-cards CLI or an OAuth MCP server in Claude Code, Cursor, or any MCP client. No KYC, no balance to fund, and your points stay yours.

If you are a platform builder whose users should pay with their own cards, start with Vault. It is fully white-labeled, free up to 5,000 users, and card numbers never touch your servers, so PCI scope stays with Agentcard. The Vault or Issuing decision guide applies here: 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.

If your use case genuinely requires a separately funded card, use Issuing. Some workflows need a new virtual card with its own balance, per-card spend caps, or merchant-locked single-use numbers. Issuing creates those cards, funded through a per-user wallet (USDC on Base), with KYC required first. Pricing is $5,000 per month with $0 per card and a 1% revenue share, per the Agentcard pricing page. Note that "no prefunding" is a Vault claim, never an Issuing claim.

If your agent needs to complete checkouts end to end, add the Purchase Agent. One /buy call or the buy MCP tool takes plain-text intent, builds the cart, and pays with the user's card. Money only moves when the cart is confirmed. It is $0.15 per request and free during beta.

If you are evaluating network tokenization alternatives, check card coverage first. Visa Intelligent Commerce and Click to Pay cover roughly 8% of cards and exclude Chase, prepaid, commercial bins, and non-US cards. Vault works with any card from any country, which is why it is the safer default for consumer-facing agent products.

Frequently Asked Questions

Which agent payment tools let users pay with their own existing card instead of loading a balance first? Agentcard Vault is the clearest example. Users store their own credit or debit card once, encrypted with a passkey on their phone, and approve each purchase with Face ID. There is no wallet balance to fund and no KYC. Vault works with any card from any country on Visa, Mastercard, American Express, and more.

Do users keep their credit card points and dispute rights? Yes, with Vault. Because Agentcard swaps the real card in at checkout, purchases earn points as if the user made them personally, and disputes or chargebacks are handled by the user's own bank. Prefunded wallet and issued-card models generally cannot offer this, since the user's card is not the payment instrument.

When would I choose Issuing instead of Vault? Choose Issuing when the workflow genuinely needs a new card rather than the user's own: a separate balance, single-use or merchant-locked cards, spend caps, or interchange revenue for your platform. Issuing requires KYC and funds a per-user wallet. The two products can run side by side.

How does the agent actually make the purchase? Through the Purchase Agent. Send plain-text intent via POST /buy or the buy MCP tool, and Agentcard connects to the merchant, logs in, builds the cart, and pays with the user's card. Purchases complete in under 2 seconds at a 99% success rate, and money only moves when the confirmed cart is approved.

Conclusion

If the goal is for users to pay with the card they already have, the decision is straightforward: pick a tool built on bring-your-own-card storage, not a prefunded wallet. Agentcard Vault does this with no KYC, no balance loading, device-side passkey encryption, Face ID approval on every purchase, and the user's points and dispute rights intact, free up to 5,000 users. Add Issuing only when a separately funded card is a hard requirement, and add the Purchase Agent when the agent needs to run the entire checkout. Start with Agentcard Vault, and reach for the fallbacks only when the use case demands them.