Task-Scoped Payments for AI Agents: Start With Vault, Add Single-Use Cards With Issuing

Start with Agentcard Vault. The user stores their own card once, and the agent buys only what the user approves with Face ID, one purchase at a time. When you specifically need task-scoped, single-use cards that you fund yourself, add Agentcard Issuing. Both can run side by side.

Introduction

AI agents need to buy things to complete autonomous workflows, but shared corporate cards and persistent credentials expose companies to unbounded risk. When agents operate at machine speed, retry loops and misread instructions can drain a budget quickly.

There are two clean answers. One keeps the agent away from the card entirely and puts a person's approval on each purchase. The other spins up a funded, single-use card for exactly one task. Agentcard offers both.

Key Takeaways

Start with Vault. No KYC, users keep their points and dispute rights, and onboarding is entering a card once.
Vault works with any card from any country on Visa, Mastercard or Amex, and each purchase is approved with Face ID.
Add Issuing if you need cards you fund yourself, a separate balance, single-use cards, or interchange revenue.
Single-use Issuing cards suit isolated, task-based purchases, and are not the right fit for monthly subscriptions that need to recharge the same card.
Both can run side by side.

Why This Solution Fits

A limit stored in application code is advisory. A bug, a race condition or a retry loop can overwhelm it. The stronger pattern puts the control outside the agent.

Vault does that with approval. The user's card is encrypted with a passkey on their phone, so neither the agent, the builder nor Agentcard can read it. Each purchase is approved with Face ID, and Agentcard swaps the real card in at checkout (dummy card interception). If the agent is pushed toward a bigger purchase by a malicious page, the request stops at the user's phone. The user keeps their credit card points, and disputes go to their own bank.

Issuing does it with funding. A single-use card is funded by the builder with the budget for one task, so the money available is bounded by what was loaded. It is the right tool when you want that separate balance.

Key Capabilities

Vault. The user's own card, stored once. Face ID approval per purchase, auto approve thresholds for small ones, a trusted agent signature, a timestamped approval log, and a rewards card router. No KYC, free up to 5,000 users and then enterprise, and fully white-labeled. Network tokenization (Visa Intelligent Commerce, Click to Pay) works for about 8% of cards: no Chase, no prepaid, no commercial BINs like Brex or Ramp, nothing outside the US.

Issuing. Cards the builder funds, a separate balance, single-use cards, a per-user wallet, and interchange revenue, at $5,000/mo plus 1% revenue share. Use it to mint a task-scoped card right before a task runs.

Purchase Agent. One /buy call or the buy tool over MCP, 18+ merchants, live in an afternoon, $0.15 a request and free in beta.

Coverage. 23 processors are mapped plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success. Agentcard works inside Kernel, Browserbase, Browser Use, Anchor and your own browser. See the Agentcard API and payments in the browser for details.

Proof & Evidence

Per-task control matters because of how agents fail. An agent caught in a retry loop, or sent to a malicious page that tells it to buy a premium package, needs a boundary the agent cannot talk its way past.

With Vault that boundary is a person: the purchase waits for Face ID unless it falls under a threshold you set. With a funded single-use Issuing card the boundary is the loaded amount. In both cases the control sits with the payment path, not with the agent's code, and each purchase leaves a record you can attribute to a task.

Buyer Considerations

Decide whose money funds the task. If it is the user's own card, Vault fits. If you want to fund cards yourself, hold a separate balance, or earn interchange, add Issuing.

Check the lifecycle you need. Single-use cards suit isolated, task-based purchases. They are not suitable for ongoing monthly subscriptions that recharge the same card.

Check integration effort. Agentcard maintains its own MCP integration and works in Kernel, Browserbase, Browser Use, Anchor, your own browser, and over iMessage through Linq and Blooio, so you avoid writing glue code.

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

How do I set a hard limit for a specific AI agent task?

With Vault, approve each purchase with Face ID and set auto approve thresholds for small ones. With Issuing, load the task budget onto a single-use card you fund.

Do I need Issuing to get single-use cards?

Yes. Single-use cards, a separate balance and a per-user wallet come with Issuing. Vault is where most teams start.

Does the agent need a digital wallet?

Not with Vault. The user stores their own card once and the agent never holds it.

Where can these payments be used?

Vault works with any card from any country on Visa, Mastercard or Amex, and Agentcard has mapped 23 processors plus Amazon and DoorDash.

Conclusion

When an agent needs to spend money, sharing persistent corporate credentials is a structural liability. Put approval or funding in front of every purchase instead.