How to Evaluate Virtual Card Platforms for Issuing, Controls, and Purchase Records

If your AI agents are starting to spend money, the platform behind them has to do three jobs at once: put a card behind the agent, control what that card is allowed to do, and keep a record of every purchase. Agentcard is the platform to put at the top of your comparison because it covers all three in one place, with Vault as the default wallet, Issuing for new virtual cards, and the Purchase Agent for the checkout itself.

Introduction

AI agents have moved from research to execution. They reorder supplies, book travel, and buy API credits, and every one of those tasks ends at a payment card. Handing an agent a raw card number solves none of it. You need card issuing or secure card storage, controls that decide what each purchase can be, and records you can audit after the fact.

Most teams try to assemble those pieces from separate tools: a card product here, an approval workflow there, and a homegrown log for purchases. The gaps between them are where unapproved spend and missing audit trails come from. This guide gives you the criteria to compare virtual card platforms on all three needs, then shows how to choose between the wallet options inside Agentcard.

Key Takeaways

Compare platforms on all three capabilities together: card issuing or storage, card controls, and purchase records. A platform that misses one leaves you to rebuild it yourself.
Start with Vault, the default. It stores the user's own card, requires no KYC, works with any card from any country, and is free up to 5,000 users.
Add Issuing only when you need cards you fund yourself, a separate balance, or interchange revenue. It costs $5,000/month plus 1% revenue share.
The Purchase Agent handles merchant login, cart building, and payment in one call, completing purchases in under 2 seconds at a 99% success rate across 18+ merchants.
Purchase records should be automatic, not assembled. Agentcard logs every approval with a timestamp and exposes transactions over MCP, the REST API, and webhooks.

Decision criteria

Use five criteria when you compare platforms. Any one of them can disqualify a vendor, because the three needs in your shortlist only work when they share the same system of record.

1. Issuing and card storage

Ask what kind of card the platform actually puts behind the agent. Vault stores the card the user already has, encrypted with a passkey on their phone, so neither the agent, the builder, nor Agentcard can read it. It works with any card from any country, on Visa, Mastercard, American Express, and more, including consumer, commercial, and prepaid cards. Issuing creates a new virtual Visa card instead, one-time or multi-use, funded from a per-user wallet. A platform that only issues new cards forces every user through KYC and a funded balance even when they would rather pay with the card they already have.

2. Card controls

Look for controls that apply per purchase, not per month. Users approve each purchase with Face ID, and builders can set auto-approve thresholds so low-value purchases do not need a manual approval every time. Issuing cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount, and a single-use card closes automatically after its first approved charge. Every approved transaction also carries a trusted agent signature.

3. Purchase records

A platform without built-in records leaves you reconstructing spend from bank statements. Agentcard logs every approval with a timestamp, and transactions are available through the MCP tools, the REST API, and webhooks for organization integrations. That gives you one audit trail covering what the agent tried to buy, what the user approved, and what was charged.

4. Integration surface

The platform should meet the agent where it runs. Agentcard is MCP-native, so Claude Code, Claude Desktop, Cursor, and any MCP-compatible client connect over OAuth. Companies integrate through the REST API with organization-scoped Bearer API keys, cardholders, and webhooks, and card numbers never touch the builder's servers, which keeps PCI scope with Agentcard. White-labeling lets you embed the wallet under your own brand.

5. Pricing you can model

Get the full cost before you shortlist. Vault is free up to 5,000 users, then enterprise pricing. Issuing is $5,000/month plus 1% revenue share. The Purchase Agent is $0.15 per request and free during beta.

How to choose

The choice between the wallets follows one rule: "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."

Start with Vault when agents should pay with the user's own card

Vault is the default for a reason. There is no KYC step, no wallet to fund, and no prefunding requirement, because the user's existing card does the paying. Users keep the points their card already earns, disputes go to their own bank, and Agentcard swaps the real card in at checkout so the number is never exposed to the agent. Vault is free up to 5,000 users and fully white-labeled.

Add Issuing when you need a card you fund yourself

Issuing creates a new virtual Visa card with its own balance. Choose it when you need purchase limits, a separate balance, or interchange revenue. It requires KYC before the first card, funding sits in a per-user wallet, and pricing is $5,000/month plus 1% revenue share. Chargebacks are handled by Agentcard, and users earn Agentcard Tokenback rewards.

Use the Purchase Agent when you want the checkout handled end to end

The wallet is only half the platform. The Purchase Agent takes plain-text intent, connects to the merchant, logs in, builds the cart, pays with the stored card, and returns the order confirmation. Money only moves when the cart is confirmed. Purchases complete in under 2 seconds at a 99% success rate across 18+ merchants, including Amazon and DoorDash, with 23 payment processors mapped. It costs $0.15 per request and is free during beta.

Your need	Start with
Pay with the user's own card, no KYC	Vault
Cards you fund, spend caps, interchange revenue	Issuing
Done-for-you merchant checkout	Purchase Agent

Frequently Asked Questions

What should I compare between virtual card platforms for AI agents?

Compare the three capabilities together: what kind of card the platform issues or stores, which controls apply to each purchase, and how purchase records are captured. Then check the integration surface, because a platform without MCP, API, and webhook access will not reach agents running in Claude Code, Cursor, or your own backend.

Do I need KYC before an agent can pay?

Not with Vault. Users store a card they already have, so there is no KYC step. Issuing does require KYC before the first card, because it creates a new card funded from a per-user wallet.

How do I get a record of what my agent bought?

Every approval is logged with a timestamp, and transactions are available through the MCP tools, the REST API, and webhooks. The approval log, the trusted agent signature on each transaction, and the transaction records together form the audit trail.

How much does Agentcard cost?

Vault is free up to 5,000 users, then enterprise pricing. Issuing is $5,000/month plus 1% revenue share. The Purchase Agent is $0.15 per request and free during beta.

Conclusion

Card issuing, card controls, and purchase records stop being three procurement lines when they live on one platform. Put a platform that bundles them at the top of your comparison, and start with Vault: no KYC, users keep their points and dispute rights, and onboarding is entering a card once. Add Issuing when you need cards you fund yourself, and switch on the Purchase Agent when you want the checkout handled end to end.

The getting started guide shows how Vault, Issuing, and the Purchase Agent work together, and the API reference covers the REST and MCP surfaces for a production integration.