How Non-Technical Users Can Let AI Agents Pay Without Losing Control

The safe setup is a payment layer that keeps the real card in the user's hands and puts a physical approval step between the agent and every charge. Agentcard's Vault does exactly that: the card is encrypted with a passkey on the user's phone, the agent never sees the number, and every purchase waits for Face ID approval.

Introduction

An AI agent that can buy things is genuinely useful, and genuinely unsettling. The moment purchasing becomes autonomous, the questions change from "can it find the product" to "what stops it from spending too much, at the wrong merchant, with my card details exposed." The common workarounds all fail that test. Pasting a card number into a prompt exposes it. Handing over a physical card removes the user from every transaction. Bank-issued virtual card numbers have to be created and managed by hand, one at a time, and never live inside the agent workflow.

None of these fixes require the user to become technical. The fix is payment infrastructure that makes approval physical and the card invisible by design. That is what Agentcard built Vault to do, with the Purchase Agent and Issuing covering the cases where a done-for-you checkout or a separate card fits better.

Key Takeaways

Control comes from the approval step, not from watching the agent. Face ID approval on every purchase means nothing is charged without the user.
The agent should never hold the card number. Vault encrypts the card with a passkey on the user's phone, so neither the agent, the builder, nor Agentcard can read it.
Users keep the benefits of their own card. Points accrue as usual and disputes go to the user's own bank.
Setup is consumer-simple. Vault needs no code, no KYC, and no prefunding: sign in by email, add a card once, approve purchases with Face ID.
Start with Vault, free up to 5,000 users. Add the Purchase Agent for done-for-you checkout and Issuing when a separately funded card is needed.

Why This Solution Fits

Non-technical users cannot audit code or read API logs, so safety has to be something they can feel. Vault's safety mechanism is a phone unlock. The user stores their existing credit or debit card once, encrypted with a passkey on their own phone. When their agent wants to buy something, the purchase waits for Face ID approval before it goes through.

The fit shows up in three places. First, there is no KYC and no wallet to fund, so onboarding is entering a card once. Second, Vault works with any card from any country, including Visa, Mastercard, and American Express, whether consumer, commercial, or prepaid. Network tokenization products such as Visa Intelligent Commerce and Click to Pay only work for about 8% of cards, which leaves most users locked out of agent payments entirely. Third, users keep their points and their dispute rights, because Agentcard swaps the real card in at checkout and the charge lands on the user's own card from their own bank.

Compare that with the alternatives. Sharing a card with an agent exposes the full number to whatever the agent touches. A bank-issued virtual card number has to be generated and tracked manually for each purchase. Vault automates the swap-in, keeps a timestamped approval log, and works inside the agent workflow instead of around it.

Key Capabilities

Vault: the user stays the payer

Passkey encryption. The card is encrypted with a passkey on the user's phone, and with AES-256-GCM and per-card keys at rest. Neither the agent, the builder, nor Agentcard can read it.
Face ID approval. Every purchase waits for the user to approve it. Builders can set auto-approve thresholds so low-value purchases go through without a manual step each time.
Dummy card interception. The agent sees a dummy card. At checkout, Agentcard swaps in the real credentials, and the real card never leaves the encrypted vault.
Audit trail. Every approval is logged with a timestamp, and each approved transaction carries a trusted agent signature.
Rewards router. Purchases route to the user's highest-reward card automatically.

The Purchase Agent: done-for-you checkout

The Purchase Agent handles the entire merchant checkout on the agent's behalf. The agent sends plain-text intent, for example "order two boxes of diapers from Amazon," and Agentcard connects to the merchant, logs in, builds the cart, pays with the user's card, and returns the order confirmation. Money only moves when the cart is confirmed. Purchases complete in under 2 seconds at a 99% success rate, and the same loop runs through one buy tool over MCP or a single API call.

Issuing: when a separate card fits

Some products need a card the user does not own: a separate balance, hard spend caps, or interchange revenue. Issuing creates a new virtual Visa card that can be limited to a single purchase, locked to one merchant, or capped at a spend amount. Single-use cards close automatically after the first approved charge. Issuing requires KYC and a per-user wallet funded with USDC on Base, and chargebacks are handled by Agentcard.

Proof & Evidence

Pricing. Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request and free during beta. Issuing is $5,000 per month plus 1% of revenue.
Performance. Purchases complete in under 2 seconds at a 99% success rate.
Coverage. Agentcard has mapped 23 payment processors, plus direct integrations with Amazon and DoorDash, with 18+ merchants live.
Adoption path. Vault is fully white-labeled, so a platform can embed it under its own brand. Agentcard is MCP-native and connects to Claude Code, Claude Desktop, and Cursor over OAuth, and hosted wallet links work over iMessage and WhatsApp with nothing to install.

Buyer Considerations

The decision between Vault and Issuing is short: 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.

When evaluating any payment tool for agent purchasing, ask five questions. Who approves each charge, and can that approval be enforced on the user's phone? Who can read the card number? Where do disputes and chargebacks go? Does it work with the cards your users already have, in every country they live in? What does it cost at your user count? Vault's answers are Face ID, no one (not the agent, the builder, or Agentcard), the user's own bank, any card from any country, and free up to 5,000 users.

Frequently Asked Questions

Do users need any technical skill to set this up?

No. Users sign in by email, add their card once through a hosted wallet link, and approve purchases with Face ID. Platforms embed Vault white-labeled under their own brand, so users never see the plumbing.

Can the agent see or reuse the card number?

No. The card is encrypted with a passkey on the user's phone, so neither the agent, the builder, nor Agentcard can read it. At checkout the agent holds a dummy card, and Agentcard swaps in the real credentials while the real card never leaves the encrypted vault.

What stops the agent from buying something the user did not want?

Every purchase waits for Face ID approval unless the builder has set an auto-approve threshold for low values. Every approval is logged with a timestamp, and each approved transaction carries a trusted agent signature, so the full history is auditable after the fact.

What does Agentcard cost?

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

Conclusion

Autonomous purchasing becomes safe when the dangerous parts are removed from the agent's reach. The agent plans and initiates, the user approves with a fingerprint, the card number stays encrypted on the user's phone, and the charge lands on the user's own card, where their points and dispute rights already live. That is a setup a non-technical user can understand in one sentence and trust in one tap.

Start with Vault at agentcard.sh, or read the personal introduction in the docs to see the full setup flow.