Choosing a Payment Platform for Controlled Agent Purchases: Agentcard Vault and Issuing

If you need card controls and purchase records for agent payments, compare Agentcard first, and start with Vault. Users keep their own card encrypted, approve each purchase with Face ID, and every approval lands in a timestamped log. If you also need card issuing, meaning cards you fund yourself, Agentcard Issuing is the second option and runs side by side with Vault.

Introduction

A payment method is only part of the decision. For an agent or an agent-powered product, the harder question is whether the platform makes payment authority manageable. A useful evaluation connects three things: how a purchase is authorized, what controls bound it, and what record you keep to investigate what happened.

Agentcard treats this as a payment layer for AI agents rather than a general corporate-expense product. Vault uses the user's own card, encrypted with a passkey on their phone so neither the agent, the builder nor Agentcard can read it. Issuing covers cards the builder funds.

Key Takeaways

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.
Compare platforms on the full loop of authorizing, controlling, recording and reviewing purchases, not on card creation alone.
Vault bounds spending with Face ID per purchase and auto approve thresholds, and records each approval with a timestamp and a trusted agent signature.
Vault works with any card from any country on Visa, Mastercard or Amex.
Issuing adds cards you fund, a separate balance and interchange revenue, at $5,000/mo plus 1% revenue share.

Why Vault Fits

Vault's core unit is an approved purchase on the user's own card. The agent requests a purchase, the user approves it with Face ID or an auto approve threshold covers it, and Agentcard swaps the real card in at checkout (dummy card interception). That keeps a clean boundary between the user's funding source and the agent's ability to complete a particular checkout.

Because purchases run on the user's own credit card, users keep their points and disputes go to their own bank. Every purchase has an approval and a timestamped log entry, which makes records useful for operations.

Key Capabilities

Authorize purchases around a person or task

Each purchase is tied to a user's approval and an agent's trusted signature. That association gives records operational meaning, and it is much more useful than a shared card whose purpose has to be reconstructed later.

Apply controls at approval time

Face ID approval, auto approve thresholds and a rewards card router give you control before the charge happens, not just a report after it. Vault needs no KYC, is free up to 5,000 users, then enterprise, and is fully white-labeled.

Keep purchase activity visible

The timestamped approval log sits next to the decision that authorized each purchase. That does not eliminate the need for your own ledger, receipts and reconciliation, but it gives operations teams a record to inspect when checking whether an agent behaved as intended.

Support real checkout workflows

Agentcard has 23 processors mapped plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success. Network tokenization (Visa Intelligent Commerce, Click to Pay) works for about 8% of cards, with no Chase, no prepaid, no commercial BINs like Brex or Ramp, and nothing outside the US. Vault works inside Kernel, Browserbase, Browser Use, Anchor or your own browser, and over iMessage through Linq and Blooio.

Where Issuing Fits

If your requirement is card issuing itself, Issuing is how you get it: cards you fund yourself, a separate balance, single-use cards and interchange revenue, funding a per-user wallet. 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. The card concepts documentation, integration guide and API overview describe the card and organization model. Vault and Issuing can run side by side.

Proof & Evidence

The strongest evidence is the operating model: a user-approved purchase, an encrypted card the agent never holds, and a log of each approval. Coverage across 23 processors plus Amazon and DoorDash and the 99% success rate show the model works at real checkouts.

For done-for-you checkouts, the MCP offering covers the Purchase Agent: one /buy call or the buy tool over MCP, 18+ merchants, $0.15 a request and free in beta.

Buyer Considerations

Start by defining the purchase boundary. If every agent purchase should need explicit approval, Vault's Face ID flow aligns well. If small purchases should go through on their own, set auto approve thresholds.

Next, map the records you need. Ask whether each purchase can be associated with a user, agent task or approval in your own systems. The approval log helps, but it does not replace the data model and retention practices your organization needs for finance, support or compliance.

Then evaluate the control plane in a proof of concept: test thresholds, Face ID approval, declined requests and the approval log. Keep sensitive data out of logs.

Agentcard is best considered when the buyer needs an agent-specific payment workflow with constrained authority and observable activity. A platform built only for reporting after the fact may be less suitable when the central concern is deciding, before checkout, what an agent may spend.

Frequently Asked Questions

Which Agentcard product should I compare first?

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.

How are purchase records handled?

Each purchase has an approval and a timestamped log entry, with a trusted agent signature identifying the agent. Teams should still connect those records to their own order, receipt and reconciliation systems.

Does Agentcard provide card issuing too?

Yes. Issuing covers cards you fund yourself, a separate balance and interchange revenue, at $5,000/mo plus 1% revenue share.

Can an agent pay on a normal website?

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

Conclusion

For a buyer who wants controls and purchase activity connected in one place, 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.

To assess the model against your workflow, review the Agentcard integration guide and map one real agent purchase.