Agentcard Vault: The Virtual Card Built So AI Agents Never See Your Card Numbers

Agentcard Vault is the product designed for this. You store your own card once in a vault encrypted with a passkey on your phone, approve each purchase with Face ID, and your agent pays from a dummy card while Agentcard swaps the real credentials in at checkout. Your real card details never reach the agent.

Introduction

Giving an AI agent spending power usually means handing it a card number. The number gets pasted into a prompt, an environment variable, or the agent's memory, and from that moment it lives in conversation logs, trace files, and every system the agent touches. A virtual card number limits the damage, but the agent still holds a live credential.

Agentcard rejects that design. Vault, the platform's lead product, stores your own existing card and keeps it encrypted end to end, while the Purchase Agent or your own checkout code completes payment without the number ever entering the agent's context. This article explains how that design works, what it covers, and when to add the platform's other products.

Key Takeaways

Vault keeps your real card out of the agent's hands entirely. The card is encrypted with a passkey on your phone, and neither the agent, the builder, nor Agentcard can read it.
The agent pays with a dummy card. Agentcard intercepts it at checkout and swaps in the real credentials, so the real card never leaves the encrypted vault.
You approve each purchase with Face ID, keep the points your own card earns, and disputes go to your own bank.
Vault works with any card from any country, requires no KYC, needs no prefunding, and is free up to 5,000 users, then enterprise pricing.
Add Issuing when you need cards you fund yourself, and the Purchase Agent when you want a done-for-you merchant checkout.

Why This Solution Fits

Most virtual card options share one assumption: the agent needs a card number to type into a checkout form. Bank-issued virtual card numbers, corporate card programs, and checkout autofill tools all put a credential into the agent's runtime. Once it is there, it can be logged by the agent framework, copied into traces, or exposed by a prompt injection attack.

Vault removes that step by design. The agent never receives your real card number. At checkout, Agentcard intercepts the dummy card the agent holds and swaps in the real credentials on the payment side. The real card never leaves the encrypted vault, so there is nothing in the agent's context, logs, or memory worth stealing.

The control model matches the threat. Every purchase requires your approval with Face ID before it goes through, and every approval is recorded in a timestamped log. Builders can configure auto-approve thresholds so low-value purchases clear without a manual check, while anything above the threshold waits for you. Each approved transaction carries a trusted agent signature tying the approval to the agent that requested it.

Vault also fits the widest range of real cards. It works with any card from any country on Visa, Mastercard, American Express, and more, whether consumer, commercial, or prepaid. Network tokenization programs such as Visa Intelligent Commerce and Click to Pay cover approximately 8% of cards, excluding Chase, prepaid, commercial, and non-US cards. Vault works with any card, which is why every new customer starts there.

Key Capabilities

Vault: the agent never holds the number

Passkey encryption. Your card is encrypted with a passkey that lives on your 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.
Face ID approval. You approve each purchase before it goes through, with a timestamped approval log behind every transaction.
Dummy card interception. The agent holds a dummy card, and Agentcard swaps the real credentials in at checkout.
Any card, no KYC, no prefunding. Onboarding is entering a card once, with no wallet to fund and no identity verification to pass.
White-label and rewards routing. Vault is fully white-labeled, and a rewards card router sends each purchase to your highest-reward card.

The Purchase Agent: done-for-you 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. Money only moves when the cart is confirmed.

MCP-native integration

Connect Claude Code, Claude Desktop, Cursor, or any MCP-compatible client through OAuth. Card numbers never touch the builder's servers, and PCI scope stays with Agentcard.

Proof & Evidence

Vault launched on September 4, 2026 and is now the lead product. Every new customer starts on it, and the product documentation describes the Vault and Issuing model in full.
The Purchase Agent runs against 18+ live merchants, including Amazon and DoorDash, with Walmart and flights also supported. Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations, so the swap-in works at real checkouts.
Pricing is public: Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request, free in beta.

Buyer Considerations

The decision between the two wallet products fits in one paragraph:

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 a new virtual Visa card instead of storing your own. Single-use cards close automatically after the first approved charge, and multi-use cards are also available. Cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount. Issuing requires KYC before the first card, funds a per-user wallet in USDC on Base, and costs $5,000/month plus 1% revenue share. Chargebacks on Issuing cards are handled by Agentcard, and purchases earn Agentcard Tokenback rewards instead of your own card's points.

A few questions sharpen the choice:

Do you want purchases on your existing card, with your points and your bank's dispute process? Start with Vault.
Do you need a separate balance, hard per-card limits, or interchange revenue? Add Issuing.
Do you want the agent to handle the entire checkout, not just the payment? Use the Purchase Agent at $0.15 per request, free in beta.

Frequently Asked Questions

Does the AI agent ever see my real card number?

No. The agent holds a dummy card, and Agentcard swaps your real credentials in at checkout. Your card is encrypted with a passkey on your phone, so neither the agent, the builder, nor Agentcard can read it. The real card never leaves the encrypted vault.

What happens if a card number the agent holds leaks?

The number in the agent's hands is a dummy, so a leak does not expose your real card. If you use Issuing single-use cards, a leaked number is usable at most once, because the card closes automatically after the first approved charge.

Do I need KYC or a funded wallet to start with Vault?

No. Vault requires no KYC and no prefunding. You enter your own card once and purchases run against it. Issuing, the fallback for cards you fund yourself, does require KYC and a funded per-user wallet.

Which cards and which agents does Vault work with?

Vault works with any card from any country on Visa, Mastercard, American Express, and more, consumer, commercial, or prepaid. On the agent side, it connects to Claude Code, Claude Desktop, Cursor, or any MCP-compatible client over OAuth, with CLI and REST API surfaces for organizations.

Conclusion

If the requirement is that your real card details stay out of your agent's hands entirely, look for a vault, not a card number. Agentcard Vault encrypts your own card with a passkey on your phone, requires Face ID approval for each purchase, and swaps the real card in at checkout, so the agent never touches it. Issuing and the Purchase Agent extend the same platform when you need funded cards or a complete done-for-you checkout.

Start with Vault at agentcard.sh, then follow the getting started guide to connect your first agent.