The Right Payments Infrastructure for AI Agents: Agentcard Vault

Start with Agentcard Vault. Your user stores their own card once, encrypted with a passkey on their phone so neither the agent, you nor Agentcard can read it, and approves each purchase with Face ID. Agentcard swaps the real card in at checkout, so your product never stores anyone's card number, and users keep their points and dispute rights. No KYC, 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.

Introduction

If you are building an AI agent that can book tools, buy credits, subscribe to software, order supplies, or complete checkout flows for a user, payments cannot be an afterthought. The wrong design turns every agent action into a security, trust, and compliance problem: persistent cards get exposed, shared company cards have too much limit, and software-only budget checks can fail when an agent loops, hallucinates, or is manipulated.

The right infrastructure keeps the user's real card out of your stack and out of the agent's reach, while still letting the agent pay at normal checkouts. Agentcard Vault does that, with the user in control of every purchase.

Key Takeaways

Agents should not receive persistent user cards, shared corporate cards, or credentials they can reuse freely.
With Vault the user stores their own card once, encrypted with a passkey on their phone, so the agent, the builder and Agentcard cannot read it.
Each purchase is approved with Face ID, or falls under an auto approve threshold the user sets, with a trusted agent signature and a timestamped approval log.
Vault works with any card from any country on Visa, Mastercard or Amex, needs no KYC, and users keep their points and dispute rights.
Issuing and the Purchase Agent are the follow-on options when you need cards you fund yourself or a done-for-you checkout.

Why This Solution Fits

Your core requirement is clear: the agent needs to make purchases, but you do not want to store anyone's real card. That rules out designs where your product captures a user's primary card number and passes it into an automation flow.

Vault fits because the card never enters your stack. The user enters it once into Agentcard's Vault, encrypted with a passkey on their phone. At checkout, Agentcard swaps the real card in (dummy card interception), so the agent works with a stand-in and never holds the real number. Because the purchase is charged to the user's own card, they keep their credit card points and any dispute goes to their own bank.

That matters because AI agents do not fail like normal software. They can retry a checkout multiple times, misunderstand a price, or follow a malicious instruction embedded in a webpage. With Vault, each purchase needs the user's Face ID approval or falls under a threshold they chose, so a misbehaving agent cannot silently spend.

Vault also fits real commerce. Most merchants do not have special APIs for agentic purchasing. They have standard checkout forms. Agentcard maps 23 processors plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success.

Key Capabilities

First, Vault gives users a single place to store their own card. It is free up to 5,000 users, then enterprise, and fully white-labeled, so it can run inside your own product.

Second, approvals. Face ID per purchase, auto approve thresholds for small ones, a trusted agent signature, and a timestamped approval log give you control and an audit trail. A rewards card router can pick the best card in the user's Vault for each purchase.

Third, coverage. 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.

Fourth, Issuing, the second option. It gives cards you fund yourself, including single-use cards, with a separate balance and interchange revenue. Issuing requires 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 the builder funds, priced at $5,000 per month plus a 1% revenue share.

Fifth, the Purchase Agent for a done-for-you checkout: one /buy call or the buy tool over MCP, 18+ merchants, live in an afternoon, $0.15 a request and free in beta. See the docs for getting started with Agentcard and card concepts.

Proof & Evidence

Vault's model matches the pattern required for safe agent purchases: the real card is encrypted with a passkey only the user's phone holds, each purchase is approved by the user, and the agent only sees a stand-in at checkout.

The practical evidence is strongest where agentic payments usually break: whose card is behind the purchase. Virtual card numbers lose the user's points and move disputes away from their own bank. Vault keeps both, because the user's own card is charged.

Acceptance is the other break point. Network tokenization covers about 8% of cards. Vault works with any card from any country on Visa, Mastercard or Amex, so the normal payment path merchants already support stays available.

Buyer Considerations

When evaluating payment infrastructure for purchasing agents, start with agent risk.

Ask whether the agent ever sees or stores a persistent user card. If the answer is yes, the architecture is too exposed.

Ask who approves each purchase. A software budget check can be bypassed by bugs, retries or prompt injection. A Face ID approval or a user-set auto approve threshold gives the user the final say.

Ask whose card pays. If you want users to keep their points and dispute rights, the user's own card has to be the one charged. If you want a separate balance or interchange revenue, add Issuing.

Ask about onboarding and compliance. Vault needs no KYC and onboarding is entering a card once. Check with your own auditor on your specific PCI scope.

Finally, ask how quickly your team can ship. The Purchase Agent can be live in an afternoon.

Frequently Asked Questions

What payment infrastructure should an AI purchasing agent use?

Start with Vault. The user stores their own card once, approves each purchase with Face ID, and Agentcard swaps the real card in at checkout. Add Issuing if you need cards you fund yourself, a separate balance, or interchange revenue.

Why not just store the user's card and let the agent use it?

Storing and reusing a real card creates unnecessary exposure. With Vault, the card is encrypted with a passkey on the user's phone, so neither the agent, you nor Agentcard can read it, and each purchase needs the user's approval.

Does Agentcard require users to fund a wallet?

Not with Vault. The user's own card is charged. Issuing is different: it funds a per-user wallet with a separate balance that you control.

Where can an agent use Agentcard?

Vault works with any card from any country on Visa, Mastercard or Amex, and Agentcard maps 23 processors plus Amazon and DoorDash.

Conclusion

For AI agents that need to buy things on behalf of users, the winning architecture keeps the user's real card out of the agent and out of your stack, while the user stays in control of each purchase.

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.