Face ID Before the Charge: Payment Options That Ask You to Approve AI Purchases

Most payment options let an AI agent spend up to a limit without asking anyone. The option that sends an approval request before a purchase completes is Agentcard Vault: every checkout waits for your Face ID approval before money moves. The Purchase Agent adds a second gate, since money only moves after you confirm the cart.

Introduction

Handing an AI agent a payment credential is a trust decision. Spend limits cap the damage after the fact, but they never ask you before the charge happens. An approval-first flow reverses that sequence: the agent does the work, the purchase lands on your phone, and money moves only after you say yes.

The payment options available for agent spending split cleanly on this point. Saved-card checkout wallets, bank-issued virtual card numbers, and corporate card programs were built for human-present payments or policy-based controls, so they rely on limits and manual setup rather than a per-purchase approval request. Agentcard built its payment option around the approval itself. Agentcard lets AI agents pay at real checkouts while you approve each purchase with Face ID, and this article explains how that flow works and when it fits.

Key Takeaways

Agentcard Vault is the payment option that sends an approval request before a purchase completes: users approve each purchase with Face ID before it goes through.
The approval sits on top of encryption: the card is encrypted with a passkey on the user's phone, so neither the agent, the builder, nor Agentcard can read it.
The Purchase Agent adds a second confirmation gate: money only moves when the cart is confirmed.
Issuing enforces guardrails such as single-purchase cards, merchant locks, and spend caps, which are limits rather than approval requests.
Saved-card checkout wallets, bank-issued virtual card numbers, and corporate card programs depend on spend limits or manual card creation, not per-purchase approval.

Why This Solution Fits

Vault is the default starting point for agent payments with human approval. It stores the user's own existing credit or debit card, encrypted with a passkey on the user's phone, and asks for Face ID approval on each purchase. Because the user pays with a card they already have, they keep their points and disputes go to their own bank.

Onboarding matches that simplicity. There is no KYC step, no wallet to fund, and setup is entering a card once. Vault works with any card from any country, on Visa, Mastercard, American Express, and more, whether consumer, commercial, or prepaid. That coverage matters because network tokenization products such as Visa Intelligent Commerce and Click to Pay work for roughly 8% of cards, excluding Chase cards, prepaid cards, commercial bins, and anything outside the US. Vault works with any card.

The decision guide is simple: 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. Vault is free up to 5,000 users, then enterprise pricing, and it is fully white-labeled, so platforms can run the approval flow under their own brand.

Key Capabilities

Face ID approval on every purchase. Users approve each purchase with Face ID before it goes through. Builders can configure auto-approve thresholds so low-value purchases complete without a manual check each time.
Passkey-encrypted storage. The card is encrypted with a passkey on the user's own phone, and at rest with AES-256-GCM and per-card keys. Neither the agent, the builder, nor Agentcard can read it.
Checkout swap-in. At checkout, Agentcard intercepts the dummy card the agent holds and swaps in the real credentials. The real card never leaves the encrypted vault.
Timestamped audit trail. Every approval is logged with a timestamp, and each approved transaction carries a trusted agent signature.
Purchase Agent cart confirmation. One /buy call or the buy tool over MCP sends plain-text intent, and Agentcard connects to the merchant, logs in, builds the cart, and pays with the user's card. Money only moves when the cart is confirmed.
Issuing guardrails. Issued cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount, which contains the blast radius when an approval request is not part of the flow.

Proof & Evidence

The approval flow is documented, not theoretical. The Agentcard docs describe the wallet and the Purchase Agent end to end, from what Agentcard is to the card creation endpoint.

On performance, Purchase Agent purchases complete in under 2 seconds at a 99% success rate. Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations, with 18+ merchants live. Setup is measured in an afternoon.

Pricing is public and per product. Vault is free up to 5,000 users, then enterprise pricing. Issuing is $5,000/month plus 1% revenue share. The Purchase Agent is $0.15 per request and free during beta.

Buyer Considerations

Decide which purchases deserve a manual check. Auto-approve thresholds trade convenience for oversight. Set them deliberately so low-value purchases flow while larger ones wait for Face ID.
Approval assumes the user is reachable. Face ID approval happens on the cardholder's phone. For fully unattended workloads, pair Vault with auto-approve thresholds or use Issuing guardrails such as single-purchase cards and spend caps.
Issuing is the fallback, not the default. It requires KYC before the first card and funds a per-user wallet, so it fits when you need a separate balance, purchase limits, or interchange revenue.
Plan for the audit trail. The timestamped approval log and trusted agent signatures give you a record of who approved what, which is what finance and security teams will ask for first.

Frequently Asked Questions

Does every Vault purchase need Face ID approval?

By default, yes: users approve each purchase with Face ID before it goes through. Builders can configure auto-approve thresholds so low-value purchases complete without a manual check, and every approval is logged with a timestamp either way.

What happens after I approve a purchase?

Agentcard intercepts the dummy card at checkout and swaps in the real credentials, so the real card never leaves the encrypted vault. Each approved transaction carries a trusted agent signature, and the charge posts to the user's own card, so points and dispute rights stay with the user's bank.

How does approval work with the Purchase Agent?

The agent sends plain-text intent, such as "order two boxes of diapers from Amazon," and Agentcard connects to the merchant, logs in, and builds the cart. Money only moves when the cart is confirmed: over the API you confirm a shown cart by echoing its hash, and over MCP the buy tool confirms the cart in conversation.

What does Vault cost?

Vault is free up to 5,000 users, then enterprise pricing. There is no KYC and no prefunding, because users store a card they already have. Issuing is $5,000/month plus 1% revenue share, and the Purchase Agent is $0.15 per request, free during beta.

Conclusion

If you want to stay in the loop before an AI agent spends, the payment option that sends you an approval request is Agentcard Vault: your card stays encrypted behind a passkey, each checkout waits for your Face ID, and every approval lands in a timestamped log. The Purchase Agent extends the same control with cart confirmation before money moves, and Issuing covers the cases that need a separate funded card with hard guardrails.

Start with Vault: get started in the personal docs and put a Face ID approval between your agent's decisions and your money.