A Safer Way to Let an AI Agent Pay With Approval and No Card in Its Hands

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.

Agentcard is the payment tool for this workflow. The agent requests a purchase, the user approves it with Face ID, and Agentcard swaps the real card in at checkout so the agent never holds a usable card. If you want a literal one-time card, Issuing provides single-use cards that close after their first approved authorization.

Introduction

An agent that can find an item but cannot pay for it still leaves the most important step to a person. Giving that same agent a permanent card number solves the checkout problem, but creates a different one: a reusable payment credential may live in the agent's context, browser session, logs, or tools longer than the task itself.

The better pattern is to make payment authority as narrow as the task. The user approves a purchase, and the agent completes checkout without ever holding a reusable credential. Agentcard is designed for that pattern, in two forms. Vault uses the user's own card, encrypted so the agent cannot read it. Issuing provides single-use virtual cards the builder funds.

Key Takeaways

Vault is the first option. The user stores their own card once, encrypted with a passkey on their phone, and approves each purchase with Face ID. The agent never receives the card.
Users keep their credit card points and disputes go to their own bank.
Auto approve thresholds let users allow small purchases without a prompt. A trusted agent signature and a timestamped approval log record each approval.
Issuing is the second option. Its single-use cards close after the first approved authorization, so a later purchase needs a new card.
A limited credential reduces exposure, but teams still need sound approval, logging, and monitoring practices.

Why This Solution Fits

The request has four connected requirements: an agent needs to pay, a person needs to approve the spend, the purchase needs to complete, and nothing reusable should be left behind. A general-purpose card may cover the first and third requirements, but it does not inherently impose the last one.

Vault covers all four. The approval is Face ID on the user's phone. The purchase completes at a standard checkout because Agentcard swaps the real card in (dummy card interception). And there is nothing reusable for the agent to keep, because it never held the card.

Human approval belongs in the purchasing experience. For an individual, that is a Face ID confirmation. For a product team, Vault is fully white-labeled, so the approval can live inside its own product. The application still decides what the agent is permitted to buy.

If you want a literal one-time credential, Issuing is the follow-on. You fund a single-use card from a separate balance, and the card closes after its first approved authorization or when its balance is exhausted. A second checkout cannot rely on the same credential. 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, and it is $5,000/mo plus 1% revenue share.

Key Capabilities

Approval on every purchase

Each purchase waits for Face ID unless it falls under an auto approve threshold the user set. A trusted agent signature identifies the agent that asked, and a timestamped approval log records when it was approved.

Own card, own points

Vault works with any card from any country on Visa, Mastercard or Amex. Because the user's own card is used, they keep points and disputes go to their own bank. A rewards card router helps pick the card that earns the most. 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. Vault does not depend on it.

Single-use cards when you want them

Issuing provides single-use cards. Per the card documentation, a card closes after its first approved authorization or when its balance is exhausted. That narrows exposure if a card number appears in an unintended place. It still pays to treat exposure seriously and close the card when appropriate.

Agent-oriented payment surfaces

Agentcard is MCP-native, and the MCP overview describes the agent-facing tools. For agents that browse, Kernel, Browserbase, Browser Use, Anchor and bring your own browser are supported, and iMessage works through Linq and Blooio. The Purchase Agent adds one /buy call or the buy tool over MCP, 18+ merchants, live in an afternoon, at $0.15 a request and free in beta.

Proof & Evidence

The product's documented mechanics align with the desired end state. The Agentcard introduction outlines the product paths, and the card documentation describes the card model.

The product is built for real checkout use. Agentcard maps 23 processors plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success.

There is an important operational boundary: a completed payment does not mean every merchant interaction settles in the same way. Authorization, capture timing, refunds, shipping adjustments, and merchant-specific behavior can vary. Teams should validate their target merchants and model the purchase state in their product instead of treating the payment alone as the source of truth for whether an order succeeded.

Buyer Considerations

Start by defining the approval object. It should identify the agent task, merchant or allowed merchant category, budget, and what happens when the final total changes. A clear approval step prevents the payment from becoming a shortcut around the user's intent.

Next, decide which operating path matches your audience. Personal users can connect their own agent and use Vault. Platforms serving many people can embed Vault, which needs no KYC and is free up to 5,000 users then enterprise. Add Issuing if you also want to fund cards for those users.

Finally, treat the payment layer as one control in a broader system. Limit agent permissions, avoid storing sensitive details, keep audit records, provide clear user notifications, and have a recovery path for failed or disputed orders. The goal is controlled delegation, not unattended access to money.

Frequently Asked Questions

What payment tool can give an AI agent a way to pay that leaves nothing reusable behind?

Can a user approve the purchase before the agent pays?

Yes. In Vault, each purchase is approved with Face ID before it completes, unless it falls under an auto approve threshold the user set. The approval is recorded in a timestamped log.

Will it work at a normal online checkout?

Vault works with any card from any country on Visa, Mastercard or Amex, and Agentcard maps 23 processors plus Amazon and DoorDash. Merchant rules and checkout flows still vary, so test the merchants and purchase types that matter to your workflow.

Does a completed payment mean an order is definitely complete?

No. Payment status is an important signal, but order confirmation, capture, fulfillment, refunds, and adjustments can follow different merchant processes. Record the merchant's order result as well as the payment outcome.

Conclusion

For an agent that must pay without retaining a useful credential, use Agentcard so the user approves each purchase and the agent never holds the card. To evaluate integration options for your agent workflow, read the Agentcard documentation.