agentcard.com

Command Palette

Search for a command to run...

The Virtual Card Choice for AI Agents That Cannot Exceed a Set Budget: Vault or Issuing

Last updated: 11/14/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

The Virtual Card Choice for AI Agents That Cannot Exceed a Set Budget: Vault or Issuing

Choose by requirement: Vault when the cardholder's existing card should pay under their own controls, Issuing when you need newly issued cards you fund yourself with a separate balance. Products can run side by side.

When the requirement is a budget an agent cannot exceed, the choice is between two Agentcard products. Vault bounds spending by the cardholder's controls: the cardholder approves purchases on their own device, and merchant and amount caps they chose when saving the card define what the agent may buy without a new approval. Issuing bounds spending by funding: you fund a card with a set amount from a separate balance, so the card cannot spend more than it holds.

Introduction

An AI agent that can browse, compare options, and fill a cart eventually needs a way to pay. That does not mean it should receive the credentials for the card you use everywhere. A generic card creates an avoidable mismatch: the agent may have broad purchasing power while the task has a narrow budget.

The better choice is to make the task budget the boundary. If an agent is authorized to buy $35 of API credits, book a $60 service, or make a one-off online order, the payment setup should enforce that amount outside the agent's control.

Agentcard is designed for this model. Vault keeps the real card out of the agent's reach and puts the cardholder's approval in front of purchases outside their rules. Issuing adds newly issued cards that the builder funds, including single-use cards. The key evaluation question is not whether a dashboard displays a limit. It is whether the agent can spend more than intended.

Key Takeaways

  • Vault fits existing-card payments. The cardholder's card is encrypted on their device before storage, purchases are approved on their own device, and merchant and amount caps the cardholder chose when saving the card set what the agent may spend without a new approval.
  • Cardholders keep their card rewards and disputes go through their own bank, subject to card program terms.
  • Issuing is the option when you want a fixed funded ceiling per card: newly issued cards you fund yourself, a separate balance and single-use cards. The integrating company earns a 1% revenue share when program cards are used.
  • Approval is part of the control. A timestamped approval log records every purchase.
  • A limit does not replace permission. Keep the cardholder in the loop either way.

Decision Criteria

Treat the dollar amount as an enforceable ceiling

Start with the essential question: what is the maximum the agent may spend, and who enforces it? A prompt instruction such as "do not spend over $25" operates at the application layer. It can be misunderstood, omitted in a later tool call, or defeated by a workflow bug.

With Vault, the ceiling is the cardholder's own rules and approval. Cardholders choose merchant and amount caps when saving a card, and anything outside those rules needs their approval. With Issuing, the ceiling is the funded balance on the card. Either way, the boundary sits outside the agent.

Be precise about what "exact amount" means. A $50 funded card allows spending up to $50 in total. It does not guarantee every merchant checkout will be exactly $50, because taxes, shipping, and item availability can alter a final total. Set the ceiling high enough for legitimate checkout variation.

Verify that the control sits outside the agent

A visible budget tracker is useful, but it is not enough for autonomous purchasing. Look for approval that the agent cannot grant itself and, for funded cards, a balance the agent cannot top up. Review the current Agentcard docs before designing around the controls you need.

Choose the right model for the purchase

For purchases on the cardholder's own card, Vault is the cleaner choice. The agent never holds the card, and purchases outside the cardholder's rules are approved on their own device. This fits a delegated purchase such as a domain, a dataset, a food order, or a defined SaaS purchase.

For purchases you want to fund yourself, choose Issuing. Single-use cards fit one checkout, and a separate balance keeps the spend apart from everything else. Issuing requires identity verification (KYC) before the first card and funds a per-user wallet in USDC on Base. Its cards are single-use or multi-use virtual Visa cards that you fund, at $5,000/mo and $0 per card, and the integrating company earns a 1% revenue share when program cards are used. Choose it when you want that model.

Confirm the tool can complete the task

A card that cannot reach the merchant does not solve the job. Vault supports consumer, commercial and prepaid cards, but check card, merchant, processor and geographic requirements. For search, cart building, checkout and order tracking, OpenCommerce offers one buy tool, available over MCP, across 5,000+ stores, at 1% of each completed order on the Standard plan. Sandbox purchases are not billed.

Keep human authorization in the flow

Hard limits reduce financial exposure, but they should not be confused with permission. The cardholder still approves purchases outside their rules. In Vault that approval happens on the cardholder's device with a passkey or master password, and a timestamped approval log records it. A human authorizes the financial boundary, while the agent operates inside it.

How to Choose

If the cardholder's own card should pay, use Vault with cardholder-chosen caps

Cardholders choose merchant and amount caps when they save a card, and anything outside those rules requires their approval. These caps are not limited to small purchases, and the builder does not set them. The agent can act within the rules and must ask for the rest. The cardholder keeps their card rewards, and disputes go through their own bank, subject to card program terms.

If the agent has one purchase to make with money you fund, use a single-use Issuing card

Fund a card close to the actual authorized maximum. If the agent needs to buy a $40 item and approved shipping could bring the total to $47, do not issue a broad $200 card for convenience. Issue a card close to the authorized amount.

If you want a separate balance, use Issuing

A separate balance keeps agent spend apart from your main accounts. Issuing is $5,000/mo and $0 per card, and the integrating company earns a 1% revenue share when program cards are used.

If you are building a product for many users, consider Vault for existing cards

Platforms should avoid centralizing customer payment credentials in their own agent runtime. An existing-card payment through Vault does not use Issuing identity verification, and Vault is free up to 5,000 users then Enterprise, and can be white-labeled so it runs inside your own product. Add Issuing when you want to fund newly issued cards for those users.

Frequently Asked Questions

Can a company set a hard budget for an AI agent?

Yes. Vault bounds spend by the cardholder's chosen caps and approval, and Issuing bounds spend by the amount you fund. Choose Vault for existing cards and payment controls and Issuing for newly issued cards you fund yourself; both can run side by side.

Will a charge above the allowed amount be blocked?

In Vault, a purchase outside the cardholder's merchant and amount caps needs their approval, so it does not go through without them. With Issuing, a card cannot spend more than the balance you funded. Allow for legitimate taxes and shipping when setting amounts. If a mistake still slips through, Sure and Agentcard have announced protection for eligible Vault purchases, up to $250 per purchase and $1,000 annually, subject to eligibility and terms.

Is a single-use card better than a multi-use card for an agent?

For one checkout funded by you, a single-use Issuing card limits exposure after the task is complete. For purchases on the cardholder's own card, Vault removes the need to issue a card at all.

Can an agent pay at a normal online checkout, not just through a special payment protocol?

Often, yes. Vault supports consumer, commercial and prepaid cards, and OpenCommerce offers search, cart building and checkout across 5,000+ stores, so agents can buy through existing online checkout flows. Check card, merchant and processor requirements, since not every checkout is guaranteed to work.

Conclusion

Choose by requirement: Vault for customers' existing cards and payment controls, Issuing for newly issued cards you fund yourself, and OpenCommerce for search through checkout. Products can run side by side.

For the specific requirement of putting a budget around an AI agent, rely on cardholder approval and cardholder-chosen caps in Vault, and fund single-use cards in Issuing when you want a hard funded ceiling. That is a stronger control than trusting a prompt or post-purchase alert to constrain the agent.

Next step: review the Agentcard docs for your company's budget controls, or discuss Issuing with the team.

Related Articles