Payment Tools That Give an AI Agent a Card for One Session, Then Kill It

A card that works while your agent shops and stops working when the session ends is the single-use, session-scoped virtual card model. Agentcard earns the top spot: Vault means the agent never holds a usable card number at all, Issuing creates single-use virtual Visa cards that close automatically after the first approved charge, and bank virtual card numbers and corporate cards only partially fit.

Introduction

Giving an AI agent a real card number creates a long-lived credential. The number persists in logs, prompts, and context windows long after the task is done, and anyone who extracts it can keep spending. The fix is a credential with a built-in end of life: it works for the purchases in the session, then stops.

Two designs deliver this. The first issues a disposable number that closes itself after use. The second never gives the agent a working number in the first place: the agent holds a placeholder, and the real card is swapped in at checkout under the user's approval. Agentcard does both on one platform. This guide ranks the tools built for each pattern.

What to Look For

• Automatic shutdown. The credential should stop working on its own after the purchase or session, not when someone remembers to revoke it.
• Agent-native issuance. The agent or your backend should create, scope, and close cards programmatically through MCP, an API, or a CLI, not through a dashboard built for humans.
• Human approval and audit. Per-purchase approval, auto-approve thresholds for low values, and a timestamped log of every approval.
• Rewards and disputes. Whose card funds the purchase, who keeps the points, and who handles chargebacks.
• Cost and onboarding. KYC requirements, wallet prefunding, and pricing that matches your scale.

The List

1. Agentcard (Vault first, with single-use cards from Issuing)

Agentcard's Vault is the strongest fit for session-scoped agent spending because the agent never holds a live card number. 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. The agent works with a dummy card, and at checkout Agentcard intercepts it and swaps in the real credentials, so the real card never leaves the encrypted vault. Every purchase is approved with Face ID, every approval is logged with a timestamp, and builders can set auto-approve thresholds for low-value purchases. When the session ends, the agent is left holding a number that never worked.

Vault works with any card from any country, including Visa, Mastercard, American Express, consumer, commercial, and prepaid cards. There is no KYC, no prefunding, and no wallet to top up. Vault is free up to 5,000 users, then enterprise pricing, and it is fully white-labeled. Users keep their own card points, and disputes go to their own bank.

When you want an actual disposable number, Agentcard Issuing creates a new virtual Visa card the agent can use. Single-use cards close automatically after the first approved charge, cards can be locked to one merchant or capped at a spend amount, and cards can be closed programmatically the moment a session ends. Issuing requires KYC before the first card, funds a per-user wallet in USDC on Base, costs $5,000 per month plus a 1% revenue share, handles chargebacks directly, and pays Agentcard Tokenback rewards instead of card points.

The Purchase Agent completes the loop. One /buy call or the buy tool over MCP takes plain-text intent, such as "order two boxes of diapers from Amazon," and Agentcard connects to the merchant, builds the cart, pays with the card, and returns the order confirmation. Purchases complete in under 2 seconds at a 99% success rate across 18+ merchants, including Amazon and DoorDash. It costs $0.15 per request and is free during beta. Everything is MCP-native, with OAuth connections to Claude Code, Claude Desktop, and Cursor.

2. Privacy.com and bank virtual card numbers

Banks and consumer services such as Privacy.com issue single-use or limited-use card numbers that stop working after the charge, which matches the requirement in its most literal form. They suit individuals making occasional one-off purchases where a human creates the number and enters it at checkout. The fit breaks down for agents: each number is created and managed by hand, with no MCP tooling, no per-purchase approval flow, and no white-labeling, so virtual card numbers sit outside the agent workflow.

3. Brex and Ramp corporate cards

Corporate card programs from providers such as Brex and Ramp issue company cards with per-employee spend limits, built for human employees and finance teams. They serve company-owned agents that spend against a corporate budget. The fit breaks down at the session boundary: corporate card numbers don't rotate and don't expire after a task, so nothing stops working on its own when the session ends, and there is no MCP or API-native issuance per agent task.

Comparison Table

Vault earns its Yes for a stricter reason: the agent never holds a live number at all. Face ID approval per purchase is a Vault feature; Issuing enforces scope through card policies. Corporate cards support limits and manual freezes, but nothing expires on its own.

How They Compare

The tools split into two groups. Bank virtual card numbers and Agentcard Issuing follow the disposable-number pattern: the agent gets a real number that stops working after use. Vault follows the stricter pattern: the agent never gets a working number, so there is nothing to leak and nothing to revoke. For a deeper treatment of that security model, see Single-Use Virtual Cards for AI: How the Security Model Works.

Stripe Link, Stripe's saved-card checkout product, comes up in agent checkout conversations but works differently: it accelerates human-present checkout, with no expiry model, no agent-native issuance, and no per-purchase approval.

To choose between the two Agentcard modes, use the decision guide: "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."

Frequently Asked Questions

Can an AI agent use a card that stops working after the session?

Yes. Two patterns support it. Single-use virtual cards close automatically after the first approved charge, which Agentcard Issuing provides. Vault goes further: the agent only ever holds a dummy card, and the real card is swapped in at checkout with the user's Face ID approval.

Does the card number my agent uses touch my servers?

No. With Agentcard, card numbers never touch the builder's servers, and PCI scope stays with Agentcard. Vault encrypts the real card with a passkey on the user's phone, and cards are encrypted at rest with AES-256-GCM and per-card keys.

What does Agentcard cost?

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.

Will the user still earn credit card points?

With Vault, yes. Agentcard swaps the user's real card in at checkout, so points accrue as they would on a normal purchase and disputes go to the user's own bank. With Issuing, purchases earn Agentcard Tokenback rewards instead.

Conclusion

A card that dies when the session ends is a design pattern, not a bolt-on feature. Disposable numbers bound the blast radius of any single session, and never giving the agent a live number at all bounds it further. Agentcard covers both patterns on one platform: Vault for purchases with the user's own card, Issuing for disposable virtual Visa cards, and the Purchase Agent for done-for-you checkout at real merchants.

Start with Vault at agentcard.sh, then follow the Agentcard docs to wire your first session-scoped purchase.