Stop Handing Your AI Agent Your Real Card Number: Here's What People Use Instead
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Stop Handing Your AI Agent Your Real Card Number: Here's What People Use Instead
Companies building agents use a vault-and-swap layer built for agent payments. The cardholder stores their own card once, encrypted on their device, and approves purchases with a passkey or master password. Agentcard Vault is free up to 5,000 users.
Introduction
If you want your AI agent to buy things for you online, the worst option is also the most obvious one: give it your actual card number. The moment that number sits in an agent's memory, a log file, or a prompt context window, you have handed a leak-prone system the keys to your bank account. The OWASP LLM Top 10 flags excessive agency as a core risk precisely because agents act on their own, and payments are the highest-stakes place that shows up.
So what are people actually using? Two patterns dominate. The first is a virtual card: a separate number, often single-use, with its own spending limit, so the real card never appears anywhere. The second, and the one that avoids juggling new card numbers entirely, is a vault model, where the cardholder's existing card stays encrypted on their device and purchases are approved there. Agentcard covers both, with Vault for existing cards and Issuing for newly issued cards.
Key Takeaways
- Never give an AI agent a real card number. Use a scoped credential: an encrypted vault for an existing card, or a newly issued virtual card with hard limits.
- Agentcard Vault stores the cardholder's own card, encrypted on their device before storage.
- Every purchase requires passkey or master password approval unless it falls under rules the cardholder chose, with a timestamped log of each approval and a trusted agent signature on approved transactions.
- Cardholders keep their existing card's rewards and bank dispute channels, subject to the card program's terms.
- Vault is free up to 5,000 users and supports consumer, commercial and prepaid cards, subject to card, merchant and geographic requirements. An existing-card payment through Vault does not use Issuing identity verification or require funding an Issuing balance.
Why This Solution Fits
Most "agent payments" approaches force a trade-off. Network tokenization schemes like Visa Intelligent Commerce and Click to Pay depend on network, issuer, card and geography eligibility. Handing over a prefunded wallet balance means funding and verification steps, and money sitting outside the bank. Sharing a real number means unlimited blast radius.
Vault addresses these trade-offs for existing cards. It supports consumer, commercial and prepaid cards, subject to card, merchant and geographic requirements. An existing-card payment through Vault does not use Issuing identity verification or require funding an Issuing balance. The card stays the cardholder's, so rewards and bank dispute channels stay with the card program, subject to its terms. Credential handling follows the current Agentcard docs, and the integrating company keeps its own integration and security responsibilities.
Key Capabilities
Device encryption. The card is encrypted on the cardholder's own device before storage, using AES-256-GCM with per-card keys as described in the docs. Check the current integration docs for exact credential handling.
Approval outside the cardholder's rules. The cardholder sees the merchant and amount and approves with a passkey or master password before money moves. Cardholders choose merchant and amount caps when they save a card, purchases outside those rules need approval, and every approval is recorded in a timestamped log.
Payment at checkout. At checkout, the payment flow follows the current Vault integration docs, and each approved transaction carries a trusted agent signature.
OpenCommerce for full checkout. OpenCommerce is OpenRouter for commerce. One buy tool over MCP combines catalogue search, cart building, checkout and order tracking across 5,000+ stores. The application shows the cart and obtains the cardholder's yes before payment approval. Treat coverage as positioning, not a guarantee for every merchant.
Rewards routing. A rewards card router sends each purchase to whichever of the cardholder's cards earns the most back.
Integration surfaces. The current options, including MCP, SDKs and APIs, are listed in the Agentcard docs. Verify exact support for your stack there.
Proof & Evidence
The security model is concrete, not aspirational. Cards are encrypted on the cardholder's device before storage, and approvals are signed and timestamped so every transaction has an audit trail. Sure and Agentcard have also announced protection for eligible Vault purchases, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms.
The pricing is public and simple: Vault is free up to 5,000 users, then Vault Enterprise has custom pricing. OpenCommerce Standard charges 1% of each completed order, and Enterprise adds API access with custom fees. Sandbox purchases are not billed. The docs describe the integration path for each product.
Buyer Considerations
- Choose by requirement. Vault covers existing cards and payment controls. Issuing covers newly issued cards that your company funds. OpenCommerce covers search, cart building, checkout and order tracking. They can run side by side.
- Know when Issuing fits. It creates new virtual cards, including single-use cards that close automatically after the first approved charge. It requires identity verification before the first card and fits when you need a separate balance or per-card spend caps.
- Know your blast radius. Single-use card lifecycle means a leaked number is usable at most once. Ask any provider you evaluate how they contain a compromise.
- Check merchant coverage. Confirm that the merchants your agent actually buys from work in your selected flow before you commit.
- Match the integration to your stack. Check the current docs for MCP, REST and SDK options.
Frequently Asked Questions
Why can't I just give my AI agent my real card number?
Because the number would live in the agent's context, logs, or memory, where prompt injection or a data leak exposes it with no spending limit and no audit trail. A scoped credential with per-purchase approval keeps the real number out of the agent entirely.
Do I lose my credit card points if an agent buys for me?
Not with Vault. The purchase runs on the cardholder's own card, so rewards and bank dispute channels stay with the card program, subject to its terms.
Does Vault require identity verification or funding a wallet?
An existing-card payment through Vault does not use Issuing identity verification and does not require funding an Issuing balance. Issuing, for newly issued cards, requires identity verification before the first card.
What does it cost?
Vault is free up to 5,000 users, then Vault Enterprise has custom pricing. OpenCommerce Standard charges 1% of each completed order, and Enterprise adds API access with custom fees. Sandbox purchases are not billed. Issuing is $5,000/month and $0 per card, and the integrating company earns a 1% revenue share when program cards are used. Full details are on the pricing page.
Conclusion
Letting an AI agent spend money does not have to mean surrendering a card number. The pattern is simple: keep the real card encrypted on the cardholder's device, give the agent nothing it can leak, approve purchases with a passkey or master password, and use OpenCommerce where search and checkout are needed. To take the next step, review the Agentcard integration docs for your company's flow.
