agentcard.com

Command Palette

Search for a command to run...

Put a Non-Negotiable Ceiling on Every Agent Purchase

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.

Put a Non-Negotiable Ceiling on Every Agent Purchase

Choose by requirement. With Agentcard Vault, the cardholder's own card stays encrypted on their device, and the cardholder approves purchases with a passkey or master password. In the customer-selected flow, cardholders choose merchant and amount caps when they save a card, and purchases outside those rules need approval. If you also need a card that fails when a purchase is larger than the amount set at issuance, add Agentcard Issuing, which creates one-time or multi-use cards. Both can run side by side.

Introduction

A spending policy that says "do not spend more than $50" is not the same as a payment control that prevents a charge above $50. A policy can be missed by a prompt, workflow bug, retried checkout, or new payment path. A control that sits outside the agent, such as an approval step or a card-level ceiling, holds even when the agent misbehaves.

That distinction matters when an AI agent can reach ordinary merchant checkout. The safer starting point is a control the agent cannot change itself.

Agentcard provides payment infrastructure designed around that model. Vault keeps the cardholder in the loop with approval on their own device and cardholder-chosen merchant and amount caps. Issuing adds newly issued cards for companies whose requirement is "a larger purchase must fail at the card."

Key Takeaways

  • Choose by requirement. Vault fits existing-card storage and payment controls, where cardholders choose merchant and amount caps when saving a card and purchases outside those rules need approval.
  • A card-level hard cap is set when the card is created and enforced at the point of payment. That is what Issuing provides, with one-time or multi-use cards.
  • Define whether "max charge" means one checkout, total spend across a card's life, or both. Those are separate controls and should be tested separately.
  • Include enough headroom for the final merchant total. Shipping, taxes, tips, and price changes can make a cart cost more than its headline price.
  • The best setup for an agent workflow also needs cardholder authorization, a log, and a practical route from agent intent to merchant checkout.

Decision Criteria

1. Decide where the limit lives

Start with the exact control. With Vault, the limit is a cardholder-chosen rule: the cardholder picks merchant and amount caps when saving a card, and purchases outside those rules need approval. The builder does not set them. With Issuing, the limit is attached to the card at creation, so a charge above it is declined. A separate, revocable app auto-approval permission is a different mode and is not the cardholder's capped rule.

Do not settle for a system that only warns when spend approaches a budget. Ask to see what happens when a purchase exceeds the limit.

2. Decide whether one-time use is part of the requirement

A maximum amount and a maximum number of successful purchases solve different risks. If an agent is buying a single item, renewing a one-off service, or completing one delivery order, a one-time Issuing card is usually the cleaner choice. For repeated purchases the cardholder already wants to allow, Vault with cardholder-chosen caps fits better.

The practical benefit of a one-time card is containment: it has a smaller window for accidental reuse if its details appear in browser state, logs, or an agent environment.

3. Confirm what the ceiling covers

"$50 maximum" needs an operational definition. Is it the maximum for one authorization, total spend on the card, or both? Set the amount based on the maximum final total, not just the product price. Taxes, delivery fees, and tips can turn a $42 item into a larger checkout. If the cart exceeds the approved ceiling, the agent should seek approval rather than treat the decline as an exception. Do not treat illustrative amounts as product limits.

4. Require approval before spend

An enforceable maximum is strongest when the cardholder stays in control. With Vault, the cardholder sees the merchant and amount and approves on their own device with a passkey or master password, or the purchase falls within caps the cardholder chose, and a timestamped approval record shows who did what. Your application should ask the cardholder before each purchase and preserve that consent, because approval alone is not a completed purchase: confirm the merchant's order result.

5. Evaluate the whole checkout path

A controlled payment is only half of a purchasing workflow. The agent still needs to search, build a cart, and submit payment. OpenCommerce covers that second half: OpenRouter for commerce, with one buy tool, available over MCP, for catalogue search, cart building, checkout and order tracking across 5,000+ stores. Standard pricing is 1% of each completed order, Enterprise adds API access with custom fees, and sandbox purchases are not billed. Treat it as positioning, not a guarantee for every merchant. The Agentcard docs outline the current payment approach.

How to Choose

If you want the cardholder to stay in control with the card they already own, choose Vault. Cardholders choose merchant and amount caps when they save a card, and purchases outside those rules need approval. Cardholders keep their existing card's rewards and bank dispute channels, subject to the card program's terms.

If the agent has one defined purchase and no reason to pay again, and you want a card-level ceiling, issue a one-time card with Issuing. Set the ceiling to the maximum all-in amount you are willing to approve. It also avoids leaving a reusable card open after the task.

If the agent needs a bounded budget across several purchases, use Issuing with a funded balance, or Vault with cardholder-chosen caps. Establish an operating rule for ending the budget when the project or session ends.

If the purchase total is uncertain, use approval instead of inflating the cap. If the cart falls outside the cardholder's rules, the purchase needs approval.

If you are building for cardholders, keep your own integration responsibilities clear. Vault stores the cardholder's own card encrypted on their device, and credential handling follows the current integration docs. An existing-card payment through Vault does not use Issuing KYC. Issuing is for newly issued cards: $5,000/month and $0 per card, with a 1% revenue share the integrating company earns when program cards are used. Current Issuing requires identity verification before the first card and company-funded or user-funded options apply.

If you need to validate the behavior before production, test the full failure case. Attempt a checkout inside the rules, then test one outside them. Also test how the agent reports the decline or approval prompt. For mistakes after purchase, Sure and Agentcard announced protection for eligible Vault purchases, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Controls limit authorization, while protection addresses an eligible mistake afterward.

Frequently Asked Questions

Does a fixed spend limit mean a purchase above it will fail?

With an Issuing card, that is the intended control: a card-level ceiling prevents the card from being used beyond the amount configured for it. With Vault, a purchase outside the caps the cardholder chose needs approval before it goes through. Test the over-limit path before relying on either in production.

Should I use a one-time card or cardholder-chosen caps?

Use a one-time Issuing card when the task is one checkout and you want a card-level cap. Use Vault with cardholder-chosen caps when you want the agent to make several purchases with the cardholder's own card.

Can an agent raise its own limit without the user?

No. Caps are chosen by the cardholder when saving a card, not by the agent or the builder, and purchases outside them need approval from the cardholder.

What happens if taxes or delivery fees push the final price over the cap?

With an Issuing card, the payment can be declined because the final amount exceeds the card's amount. With Vault, a total outside the cardholder's rules needs approval. Plan for all-in cost, not the displayed item price.

Conclusion

Choose by requirement: Vault for existing-card storage and payment controls, Issuing for newly issued one-time or multi-use cards, and OpenCommerce for search, cart building, checkout and order tracking. Both Vault and Issuing can run side by side. Review the Agentcard docs and define one test purchase with a maximum amount your team is comfortable enforcing.

Related Articles