Your AI Agent Can Spend Money Without Ever Seeing Your Card Number

The safest way to let an AI agent spend money is to never give it your real card. Store your card once in Agentcard's Vault, hand the agent a stand-in number, and approve each purchase with Face ID. The real card stays encrypted behind a passkey only you hold, and the agent only ever holds a placeholder.

Introduction

An AI agent that cannot pay stops halfway. It finds the product, builds the cart, and picks the delivery slot, then hands the job back to you because checkout needs a card number. The common workarounds all fail the same way. Pasting card details into a prompt puts the number into model context, transcripts, and logs. Sharing it with an app puts it on someone else's servers. Generating a bank virtual card number by hand breaks down the moment your agent needs to buy something on its own schedule.

Agentcard takes a different approach. Vault, Agentcard's wallet, stores your own existing card encrypted with a passkey on your phone. Your agent works with a dummy card, you approve each purchase with Face ID, and Agentcard swaps the real card in at checkout. The agent gets spending power. The card number never does.

Key Takeaways

Never paste card details into a prompt or hand the raw number to an agent. Anything the agent holds can leak.
Vault stores your own card encrypted with a passkey on your phone. Neither the agent, the builder, nor Agentcard can read it.
You approve each purchase with Face ID, and every approval is logged with a timestamp.
At checkout, Agentcard swaps the real card in, so you keep your points and disputes go to your own bank.
Vault needs no KYC and no prefunding, works with any card from any country, and is free up to 5,000 users.

Why This Solution Fits

The risk in giving an agent your actual credit card is structural: the number ends up in places you do not control. Prompts, transcripts, screenshots, third-party tools, and log files all become copies of a live payment credential, and a leaked card works until you notice and cancel it.

Vault removes the exposure instead of managing it. Your card is encrypted with a passkey on your own phone, and at rest with AES-256-GCM and per-card keys. The agent receives a dummy card number to present at checkout. Agentcard intercepts that dummy card, swaps in the real credentials, and the real card never leaves the encrypted vault. No readable copy of the number exists for the agent, the builder, or Agentcard to lose.

Spending stays under your control. Every purchase waits for your Face ID approval before it goes through, and every approval lands in a timestamped log. Auto-approve thresholds let you wave low-value purchases through without a tap each time, while anything larger stops for your approval. Each approved transaction carries a trusted agent signature, so the purchase that reaches the merchant is the one you approved.

Vault also fits real cards and real banks. It works with any card from any country: Visa, Mastercard, American Express, consumer, commercial, or prepaid. There is no KYC step and nothing to fund ahead of time. Network tokenization schemes such as Visa Intelligent Commerce and Click to Pay cover approximately 8% of cards and exclude Chase cards, prepaid cards, commercial bins, and everything outside the US. Vault works with any card. And because payment runs on your own card, your points post as usual and disputes go to your own bank.

If you build agents for other people, the same model protects you. Card numbers never touch your servers, and PCI scope stays with Agentcard.

Key Capabilities

Passkey-encrypted storage

Your card is encrypted with a passkey on your phone and with AES-256-GCM and per-card keys at rest. The real number never appears in agent context, builder infrastructure, or Agentcard systems in readable form.

Approval on your terms

Face ID approval gates every purchase. Auto-approve thresholds let low-value purchases through without a tap, and a timestamped approval log records everything.

The Purchase Agent

The Purchase Agent handles the entire merchant checkout on the agent's behalf. One /buy call or the buy tool over MCP sends plain-text intent, for example "order two boxes of diapers from Amazon". Agentcard connects to the merchant, logs in, builds the cart, pays with your card, and returns the order confirmation. Money only moves when the cart is confirmed.

MCP-native integration

Agentcard is MCP-native. Connect Claude Code, Claude Desktop, Cursor, or any MCP-compatible client through OAuth at mcp.agentcard.sh. Personal users can also manage everything through the agent-cards CLI.

Built for products, not just individuals

Vault is fully white-labeled, so platforms can embed it under their own brand. Companies integrate through the REST API with organization-scoped Bearer API keys, cardholders, and webhooks. A rewards card router sends each purchase to the card that earns the most.

Proof & Evidence

Purchases through the Purchase Agent complete in under 2 seconds at a 99% success rate. Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations, with 18+ merchants live including Amazon and DoorDash, and Walmart and flights supported as well. Setup takes an afternoon.

Pricing is public and simple. Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent costs $0.15 per request and is free during beta. Issuing, the fallback for platforms that need cards they fund themselves, is $5,000 per month plus a 1% revenue share.

For a deeper walkthrough of the risks of giving an agent a credit card, read Should You Give Your AI Agent a Credit Card?, and for a controls checklist use the AI agent spending security checklist.

Buyer Considerations

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 creates new virtual Visa cards your agent can use. Cards can be single-use, closing automatically after the first approved charge, or multi-use. They can be limited to a single purchase, locked to one merchant, or capped at a spend amount, and a single-use lifecycle means a leaked number is usable at most once. Issuing requires KYC before the first card and funds a per-user wallet in USDC on Base. Chargebacks are handled by Agentcard, and users earn Agentcard Tokenback rewards.

A few questions to settle before you integrate:

Who approves purchases, and where do your auto-approve thresholds sit?
Do you need your users' own cards (Vault) or cards you fund and control (Issuing)?
Do you want the wallet to carry your brand? Both Vault and Issuing are fully white-labeled.

Frequently Asked Questions

Does the agent ever see my real card number?

No. The agent holds a dummy card number. At checkout, Agentcard intercepts the dummy card and swaps in the real credentials, so the real card never leaves the encrypted vault and never enters agent context, prompts, or logs.

Do I keep my credit card points and fraud protection?

Yes. Vault pays with your own card, so purchases earn points exactly as they would if you typed the number yourself, and disputes and chargebacks go to your own bank.

What does Agentcard cost?

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.

Does Vault work with cards outside the US?

Yes. Vault works with any card from any country, on Visa, Mastercard, or American Express, including consumer, commercial, and prepaid cards. No KYC is required.

Conclusion

Handing an AI agent your actual credit card means trusting every system that touches the prompt with a live payment credential. You do not need to. Store your card once in Vault, approve purchases with Face ID, and let the agent pay at real checkouts while the real number stays encrypted on your side. Start with the Agentcard overview or read the docs to connect your first agent this afternoon.