Why Agentcard Vault Is the Safest Way to Test Agent Payments

Agentcard is the best virtual card provider for testing agent payments before real money is on the line. Vault keeps the real card encrypted while the agent works with a dummy card, every purchase waits for Face ID approval, and card controls cap each test's spend. Vault is free up to 5,000 users, with no KYC and no prefunding.

Introduction

Testing agent payments exposes two problems at once. Your agent needs to complete real checkouts, which means payment credentials have to enter the workflow, and uncontrolled spending becomes possible the moment they do. Bank-issued virtual card numbers and corporate card programs were not built for this. They sit outside the agent workflow and hand you another card number to manage by hand.

Agentcard takes a different approach to the sandbox problem. Rather than a separate fake environment that behaves differently from production, you rehearse against real checkout flows with controls that keep money from moving until a human confirms. The agent works with a dummy card, Agentcard swaps the real credentials in at checkout, and every approval is logged. You test the full payment path while keeping the blast radius of each run under your control.

Key Takeaways

The agent never sees a real card number. Vault stores the user's card encrypted with a passkey on their phone, the agent works with a dummy card, and Agentcard swaps the real card in at checkout.
Every purchase has a human gate. Users approve each purchase with Face ID, and every approval lands in a timestamped log you can review after each test run.
Exposure stays capped. Cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount, and single-use cards close automatically after the first approved charge.
You can start free today. Vault is free up to 5,000 users, requires no KYC, and needs no prefunding. The Purchase Agent is free in beta and costs $0.15 per request after.
Vault works with any card from any country, on Visa, Mastercard, American Express, and more.

Why This Solution Fits

A safe test of agent payments needs four things: the agent never holds live card data, a human approves what gets charged, each test has a hard ceiling, and you can audit what happened. Agentcard is built around exactly those controls.

Vault, the lead product, covers the first two. The user stores an existing card once, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it. The agent handles a dummy card, and Agentcard intercepts it at checkout and swaps in the real credentials, so the real card never leaves the encrypted vault. Users approve each purchase with Face ID before it goes through.

Issuing covers the ceiling. When your test needs a card with its own budget, Agentcard can issue virtual Visa cards limited to a single purchase, locked to one merchant, or capped at a spend amount. Single-use cards close automatically after the first approved charge, so a leaked card number is usable at most once.

Integration is the third fit. Agentcard is MCP-native: connect Claude Code, Claude Desktop, or Cursor over OAuth, manage cards with the agent-cards CLI, or use the REST API with organization-scoped Bearer API keys for company deployments. Setup lives in an afternoon. The decision 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. Both can run side by side.

Key Capabilities

Dummy card interception. The agent works with a dummy card. At checkout, Agentcard swaps in the real credentials, and the real card never leaves the encrypted vault.
Face ID approval with auto-approve thresholds. Users approve each purchase with Face ID. Builders can configure auto-approve thresholds so low-value purchases go through without manual approval each time.
Timestamped approval log. Every approval is logged with a timestamp, so you can reconcile exactly what the agent tried to buy and what was approved.
Guardrails on issued cards. Issuing supports single-purchase cards, merchant locks, and spend caps. Single-use cards close automatically after the first approved charge.
The Purchase Agent. One POST /buy call or the buy tool over MCP sends plain-text intent. Agentcard connects to the merchant, logs in, builds the cart, and pays with the user's card. Money only moves when the cart is confirmed.
White-labeling. Vault is fully white-labeled, so you can embed the wallet under your own brand while you test.

Proof & Evidence

Purchases complete in under 2 seconds at a 99% success rate.
18+ merchants are live, including Amazon and DoorDash, with Walmart and flights also named.
Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations.
Cards are encrypted at rest with AES-256-GCM and per-card keys.
Pricing is public: Vault is free up to 5,000 users then enterprise, Issuing is $5,000 per month plus a 1% revenue share, and the Purchase Agent is $0.15 per request, free in beta.

The Agentcard docs walk through connecting an MCP client and running a first purchase, and the API reference covers cardholders, cards, and webhooks for organization deployments.

Buyer Considerations

Approved charges are real charges. Vault pays with the user's own card, so once a purchase is approved the charge is real. Keep Face ID approval on while you test, set low auto-approve thresholds, and review the timestamped log after each run.
Issuing is a later step, not a starting point. It requires KYC and costs $5,000 per month plus a 1% revenue share. Add it when you need cards you fund yourself, a separate balance, or interchange revenue.
Plan for the beta ending. The Purchase Agent is free in beta and $0.15 per request after, so build per-request costs into your testing budget at scale.
Check card coverage early. Vault works with any card from any country. Issuing works globally with some restricted countries.

Frequently Asked Questions

Does the agent ever see the real card number?

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 works with a dummy card, and Agentcard swaps the real credentials in at checkout.

Do I need to fund a wallet before the first test?

Not with Vault. There is no prefunding: the user stores an existing card once and the agent pays with it. Issuing works differently and uses a per-user wallet funded in USDC on Base.

What stops an agent from overspending during a test?

Face ID approval on every purchase, auto-approve thresholds you configure for low values, and, on issued cards, single-purchase limits, merchant locks, and spend caps. Single-use cards close automatically after the first approved charge.

What does it cost to test?

Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is free in beta and $0.15 per request after. Issuing is $5,000 per month plus a 1% revenue share when you add it.

Conclusion

The best virtual card provider for testing agent payments is the one that keeps credentials out of agent code, gates every charge behind human approval, caps what each test can spend, and logs every approval. Agentcard does all four with Vault, and the Purchase Agent extends the same controls to full merchant checkout. Start with Vault at agentcard.sh, connect your MCP client, and run your first gated checkout with the Agentcard docs.