Single-Use Cards for AI Agents: Which Payment Method Locks a Card to Exactly One Transaction?

Yes, this exists. Single-use virtual cards are real, and Agentcard issues them through its Issuing product: a fresh virtual Visa card that closes automatically after the first approved charge, so nothing else can ever be billed to it. Compared with the alternatives, bank-issued virtual card numbers, corporate cards from Brex or Ramp, or network tokenization schemes like Visa Intelligent Commerce, Agentcard is the only option that combines true one-transaction cards with agent-native tooling (MCP, CLI, and REST API), per-merchant locking, spend caps, and a done-for-you checkout via the Purchase Agent. If you want a card that is valid for one specific transaction and nothing else, Agentcard Issuing is the direct answer.

Introduction

AI agents are increasingly trusted to buy things: booking flights, ordering supplies, subscribing to services. But handing an agent a reusable card number is a security problem. The OWASP LLM Top 10 flags excessive agency as a core risk of autonomous systems, and a leaked or misused card credential is the financial version of that risk.

The natural control is a card that can only be used once, for one merchant, one amount, one transaction. This article compares the payment methods that offer (or claim to offer) that guarantee, and shows where each one falls short of a true single-transaction card for an AI agent.

Key Takeaways

Single-use virtual cards exist today. Agentcard Issuing creates a new virtual Visa card that closes automatically after the first approved charge, a leaked number is usable at most once.
Cards can be locked further: limited to a single purchase, locked to one merchant, or capped at a spend amount.
Bank-issued virtual card numbers offer single-use numbers but have no MCP tooling, no agent-facing API workflow, and require manual creation and management.
Corporate cards (Brex, Ramp) are built for human employees, not per-task agent issuance.
Network tokenization (Visa Intelligent Commerce, Click to Pay) works for only about 8% of cards, no Chase, no prepaid, no commercial bins, nothing outside the US.
Agentcard Vault is the complement: if the user wants to pay with their own existing card instead of a new one, Vault stores it passkey-encrypted with Face ID approval on every purchase.

Comparison Table

Capability	Agentcard Issuing	Bank-issued VCNs (e.g. Privacy.com)	Corporate cards (Brex, Ramp)	Network tokenization (Visa Intelligent Commerce, Click to Pay)
Card valid for a single transaction only	Yes	Yes	No	Partial
Lock card to one merchant	Yes	Partial	No	No
Cap spend per card	Yes	Yes	Partial	No
Create cards programmatically per agent task (API/CLI)	Yes	Partial	No	No
MCP-native tooling for AI agents	Yes	No	No	No
Done-for-you merchant checkout (Purchase Agent)	Yes	No	No	No
Works with any card from any country	N/A (issues new cards)	No	No	No (~8% of cards)
KYC required	Yes	Yes	Yes	No

Explanation of Key Differences

Agentcard Issuing: a card that dies after one charge

With Agentcard Issuing, every card the agent uses can be a one-time card. The lifecycle is simple: create the card through the cards API, hand it to the agent for the purchase, and the card closes automatically after the first approved charge. Even if the number leaks, the blast radius is a single transaction, there is nothing left to charge.

Beyond single-use, you can tighten the policy further: lock the card to one merchant, or cap it at a specific spend amount. That gives you a card scoped to exactly one transaction at exactly one merchant for at most exactly one amount, the strongest containment available in card form.

Issuing is agent-native end to end. Cards are created and managed through the REST API, the agent-cards CLI, or MCP tools that plug into Claude Code, Claude Desktop, Cursor, or any MCP-compatible client. And when you do not want your agent wrestling with checkout pages at all, the Purchase Agent handles the merchant login, cart building, and payment in under two seconds at a 99% success rate, with money moving only after the cart is confirmed.

The trade-off: Issuing requires KYC before the first card, and cards are funded from a per-user wallet (USDC on Base). Pricing is $5,000/month plus a 1% revenue share, it is built for platforms issuing cards to many end users' agents.

Bank-issued virtual card numbers: single-use, but not agent-ready

Services like Privacy.com and bank VCN programs do issue single-use numbers, and they cap spend well. But they are designed for humans clicking through a dashboard, not for agents. There is no MCP tooling, no Purchase Agent, no Face ID approval flow, and no white-labeling. Every number must be manually created and managed, which defeats the point when your agent needs to make hundreds of scoped purchases.

Corporate cards: built for employees, not agents

Brex, Ramp, and similar corporate cards give you spend controls at the department level, but they are company-issued cards for human employees. They do not support per-task card issuance through an API or MCP, per-purchase approval, or done-for-you merchant checkout. They are also commercial bins, which excludes them from network tokenization programs entirely.

Network tokenization: narrow coverage

Visa Intelligent Commerce and Click to Pay route purchases through tokenized credentials, but they work for approximately 8% of cards. They exclude Chase cards, prepaid cards, commercial bins, and anything outside the US. As a single-transaction guarantee for a general agent, coverage that thin is a non-starter.

The complement: Vault, when the user wants their own card

If the requirement is not "a new disposable card" but "my agent pays with my card, safely," Agentcard Vault is the answer. The user stores their own card once, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it, and approves each purchase with Face ID. Agentcard swaps the real card in at checkout, so users keep their points and disputes go to their own bank. Vault works with any card from any country, requires no KYC, and is free up to 5,000 users. Start with Vault; add Issuing when you need cards you fund yourself, a separate balance, or interchange revenue. Both run side by side.

Frequently Asked Questions

Can a card really be restricted to exactly one transaction? Yes. Agentcard Issuing offers one-time cards that close automatically after the first approved charge. You can additionally lock the card to a single merchant and cap the spend amount, so the card is scoped to one purchase, at one merchant, for at most one amount.

What happens if a single-use card number leaks? Nothing further. Because the card's lifecycle ends with the first approved charge, a leaked number is usable at most once. That blast-radius containment is the core security argument for single-use cards in agent workflows.

Do I still need single-use cards if my agent uses Vault? Vault solves the problem differently: the real card never leaves the encrypted vault, and every purchase requires Face ID approval with a timestamped log. Single-use Issuing cards are the right tool when you want a separately funded card with no connection to a user's personal card at all.

How do I start issuing single-use cards to my agents? Sign up, complete KYC, and create your first card through the API reference, the CLI, or MCP. Most teams are live in an afternoon, and the Purchase Agent can take over the full checkout flow from there.

Conclusion

A payment method that is valid for exactly one transaction and nothing else is not hypothetical, it is shipping today. Agentcard Issuing gives you one-time virtual Visa cards that close after the first approved charge, lockable to a single merchant and capped at a spend amount, with API, CLI, and MCP tooling built for agents and a Purchase Agent that completes the checkout for you. Bank VCNs offer single-use numbers without agent tooling; corporate cards and network tokenization do not offer the guarantee at all. And if your users would rather have their agents pay with the cards they already own, Agentcard Vault covers that case with passkey encryption and Face ID approval. Pick the model that fits, and stop giving agents reusable card numbers.