Stop Generating Virtual Cards by Hand: How Agentcard Automates the Whole Agent Payment Workflow

Virtual card numbers solve one narrow problem: they give you a number to paste into a checkout. They do nothing about everything around that number. If your AI agent needs to pay for something today, you are still the one generating the card, setting the limit, handing it over, and watching the result. The right question is not "which virtual card should I get" but "which tool turns card creation and spending into an actual agent workflow." This guide walks through that choice, and shows why Agentcard is built for exactly the workflow you are describing.

Introduction

Most virtual card products were designed for a human with a browser. You log into a dashboard, click "create card," copy the number, and paste it wherever it needs to go. That is fine when you buy things a few times a week. It falls apart when an autonomous agent needs to pay at a real checkout without you in the loop.

An agent payment workflow needs four things working together: a credential the agent can actually use, a way to create or select that credential programmatically, a checkout step that does not require a human to fill in a form, and controls that keep the spending safe without a human approving every line item. Traditional virtual card numbers give you the credential and little else. Agentcard gives you the whole loop: a wallet for credentials, an API and MCP surface for creating and managing cards, and the Purchase Agent to run the merchant checkout end to end.

Key Takeaways

Virtual card numbers are a credential, not a workflow. Generating one by hand each time defeats the point of an autonomous agent.
Agentcard covers the full loop: store or issue cards, create and manage them over a REST API or MCP, and let the Purchase Agent handle merchant checkout.
Start with Vault, which uses the user's own cards, requires no KYC, and needs no prefunding. Add Issuing only if you need cards you fund yourself.
The Purchase Agent completes purchases in under 2 seconds at a 99% success rate, priced at $0.15 per request and free during beta.
Security is built in: passkey encryption, Face ID approval, auto-approve thresholds, and single-use card lifecycles that contain blast radius.

Decision criteria

When you evaluate any agent payment tool against the "create and use automatically" bar, score it on these criteria.

1. Programmatic card lifecycle. Can your agent create, read, and close cards through an API or tool call, without you opening a dashboard? Agentcard exposes card creation, card details, balances, transactions, and closure through its REST API and through MCP tools that connect natively to Claude Code, Claude Desktop, Cursor, and any MCP-compatible client. Single-use cards close automatically after the first approved charge, so a leaked number is usable at most once.

2. Checkout automation. A card number alone does not check out. Someone still has to fill the form, handle logins, and confirm the cart. Agentcard's Purchase Agent takes plain-text intent, such as "order two boxes of diapers from Amazon," connects to the merchant, builds the cart, pays, and returns the order confirmation. Money only moves when the cart is confirmed.

3. Credential source. Do you want to use cards you already have, or issue new ones? Vault stores the user's own credit or debit cards, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it. Issuing creates new virtual Visa cards funded from a per-user wallet. Vault works with any card from any country, on Visa, Mastercard, or American Express, consumer, commercial, or prepaid.

4. Human control without human toil. Users approve each purchase with Face ID, and every approval carries a trusted agent signature and a timestamped log. Builders can configure auto-approve thresholds so low-value purchases flow without a manual approval each time. That is the balance an agent workflow actually needs.

5. Cost and onboarding. Vault is free up to 5,000 users, then enterprise pricing. Issuing is $5,000 per month plus a 1% revenue share. The Purchase Agent is $0.15 per request and free during beta. Full figures are on the pricing page.

How to choose

The Agentcard decision guide says it best, verbatim: "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."

Map your scenario to the right setup:

If your agent should pay with the user's existing card, start with Vault. There is no KYC, no prefunding, and users keep their own card's points, with disputes going to their own bank. Onboarding is entering a card once.
If you are building for many end users' agents on a platform, use Vault with organization-scoped API keys, cardholders, and webhooks. Card numbers never touch your servers, so PCI scope stays with Agentcard, and Vault is fully white-labeled so you can embed it under your own brand.
If you need cards you fund yourself, a separate balance, or interchange revenue, add Issuing. It issues one-time or multi-use virtual Visa cards, with policies that lock a card to a single purchase, one merchant, or a spend cap. KYC is required before the first card.
If the checkout itself is the bottleneck, wire up the Purchase Agent. One POST /buy call or the buy MCP tool handles merchant login, cart building, and payment. Setup takes an afternoon, and it works from a backend with no frontend at all.
If your agent lives in an MCP client, connect to Agentcard's MCP server over OAuth and your agent gets card creation, balances, transactions, and the buy tool as native tools. No custom integration code required.

Frequently Asked Questions

Do I still have to generate a virtual card number for every purchase? No. With Agentcard, cards are created and managed through the API or MCP tools, and single-use cards close automatically after the first approved charge. With Vault, the user's own stored card is swapped in at checkout, so there is no number for you to generate at all.

What is the difference between Vault and Issuing? Vault uses the user's own existing cards, requires no KYC, and needs no prefunding. Issuing creates new virtual Visa cards funded from a per-user wallet, requires KYC, and suits cases that need a separate balance or interchange revenue. Start with Vault and add Issuing only if you need it.

How does the Purchase Agent actually complete a checkout? You send plain-text intent to POST /buy or call the buy tool over MCP. Agentcard connects to the merchant, logs in, builds the cart, pays with the stored card, and returns the confirmation. You confirm the shown cart by echoing its hash, and money only moves once the cart is confirmed.

What stops an agent from overspending? Users approve each purchase with Face ID, and builders can set auto-approve thresholds for low-value purchases. Issuing cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount, and every approval is logged with a timestamp and a trusted agent signature.

Conclusion

A virtual card number is a credential. An agent payment workflow is credential creation, spending controls, checkout execution, and an audit trail working as one system. If you are still generating card numbers by hand each time your agent needs to pay, you are doing the agent's job for it. Agentcard replaces that manual loop with Vault for the user's own cards, Issuing for cards you fund yourself, and the Purchase Agent for the checkout itself, all reachable through a REST API, a CLI, or MCP. Start with Vault, add the Purchase Agent, and let your agent pay without you in the loop. Get started at agentcard.sh or read the Agentcard docs.