Choose a Payment Flow That Keeps AI Purchases Awaiting Your Approval

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.

The right option is a payment flow where a human approves each purchase before the agent can complete it, not a reusable card number handed to an agent. Agentcard Vault is built for this decision: the user stores their own card once, encrypted with a passkey on their phone, and approves each purchase with Face ID. Agentcard swaps the real card in at checkout, so the agent completes the permitted checkout without ever seeing the card.

Introduction

An AI agent that can find an item, compare options and fill a checkout page still needs financial authority to place the order. Giving it unrestricted access to a personal or company card solves the last step, but creates a much larger problem. The agent has a credential that can be reused beyond the task, and the person responsible for the budget may not see the decision at the right moment.

The better question is not whether an agent should be able to pay. It is where a human decision happens in the payment flow. A strong approval model makes the merchant, amount and purpose clear before the purchase goes through, and does not turn permission for one purchase into permission for every future purchase.

Agentcard Vault puts that decision in the user's hands. Read the card concepts documentation for how cards work in Agentcard.

Key Takeaways

Choose a payment option with a human authorization step before the agent can complete a purchase. A notification after a charge is useful, but it is not pre-purchase control.
With Vault, each purchase is approved with Face ID, and every approval is recorded in a timestamped log with a trusted agent signature.
Auto approve thresholds let the user wave through small, routine purchases while larger ones always wait for approval.
Users keep their credit card points and disputes go to their own bank, and Vault needs no KYC.
If you need cards you fund yourself, add Issuing, which offers single-use cards.

Decision criteria

Does approval happen before the agent can pay?

This is the essential criterion. Some workflows alert an owner only after a transaction attempt or completed charge. Those alerts support monitoring, but they do not give the owner a chance to prevent the purchase. Look for a flow in which the person with budget authority approves the purchase before it completes.

With Vault, the control point is the purchase itself. The user approves with Face ID, and only then does Agentcard swap the real card in at checkout (dummy card interception).

Is the amount understandable?

An approval request should answer a simple question: what is the agent about to spend on this task? Reviewing a specific purchase is easier than reviewing an open-ended payment method. Auto approve thresholds let you decide in advance which small amounts do not need a prompt.

Is the payment credential isolated from the agent?

A payment mechanism can look approved on paper while leaving a usable card accessible to an agent. If the credential is exposed in browser state, prompts, logs or a compromised agent environment, its potential use should be as narrow as possible. With Vault, the card is encrypted with a passkey on the user's phone, so neither the agent, the builder nor Agentcard can read it.

Can the agent complete ordinary online checkout?

Approval should not force a human to re-enter payment details after every decision. Once the user approves, the agent should be able to complete the payment at a standard web checkout. Vault works with any card from any country on Visa, Mastercard or Amex. 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. Agentcard maps 23 processors plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success, and Agentcard Pay supports checkout for MCP-compatible agents.

How to choose

If you want to approve every distinct agent purchase, choose Vault. The user reviews the item, merchant and amount, approves with Face ID, and the agent finishes the checkout. A rewards card router can pick the best card for each purchase, so approval does not cost the user their points.

If an agent handles recurring operational work, approve routine purchases with thresholds. Set auto approve thresholds for small recurring purchases, and keep Face ID for anything larger. Revisit those boundaries as order sizes or agent responsibilities change.

If you are building an agent product for other users, use the white-labeled Vault inside it. Vault is free up to 5,000 users, then enterprise, and runs inside your own product. Start with the integration guide, and see how it works inside Kernel, Browserbase, Browser Use, Anchor or your own browser, and over iMessage through Linq and Blooio.

If you only receive transaction notifications after an agent acts, do not treat that as approval. Post-purchase visibility can help with reconciliation, but it cannot undo a completed purchase. Move the decision earlier.

If you want cards you fund yourself, add Issuing. Issuing provides single-use or multi-use virtual Visa cards you fund, a separate balance, interchange revenue and a funded per-user wallet, at $5,000/mo plus 1% revenue share. It requires KYC before the first card and funds the per-user wallet in USDC on Base. It runs side by side with Vault.

Frequently Asked Questions

What payment option actually asks for approval before an AI agent buys something?

Agentcard Vault. The user approves each purchase with Face ID before the real card is swapped in at checkout, unless it falls under an auto approve threshold the user set.

Is a spending limit enough to count as approval?

Not by itself. A limit constrains the maximum amount, but a pre-purchase approval flow requires the owner to authorize the purchase before the agent can complete it.

What happens if the purchase total is higher than expected?

Treat that as a new decision. The agent comes back with the updated total, and the user approves or declines it.

Can this work at normal online merchants?

Yes. Vault works with any card from any country on Visa, Mastercard or Amex, and the checkout works like any normal card payment.

Conclusion

For AI purchasing, choose the payment option that makes human approval the gate, not an after-the-fact alert. To put an approval-first agent payment flow in place, review the Agentcard integration guide.