The Payment Platform to Build Agent Checkout Without Holding User Card Data

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.

Build on Agentcard. With Vault, each user stores their own card once, encrypted with a passkey on their phone so neither the agent, your product nor Agentcard can read it, and approves each purchase with Face ID. Your product never stores a user's card credentials, and the agent checks out at standard merchants.

Introduction

If your agent can browse, compare options, and decide what to buy, the payment step becomes the security bottleneck. Handing an agent a user's reusable credit card is not a responsible architecture. Storing user card data yourself adds compliance scope, breach risk, and operational drag before your agent can place its first real order.

Agentcard is built for this gap: agents that need to complete real-world purchases without exposing the user's card to the agent, your app, prompts, browser logs, or custom checkout glue. Instead of building a payment vault, you embed Vault, which is fully white-labeled, and let the agent pay at ordinary merchants.

Key Takeaways

Vault is the strongest fit when your agent needs to check out at ordinary merchants and you do not want to hold user card data.
Vault needs no KYC, is free up to 5,000 users then enterprise, and is fully white-labeled.
Users keep their credit card points and disputes go to their own bank, because Agentcard swaps the real card in at checkout.
Vault works with any card from any country on Visa, Mastercard or Amex.
Issuing is the second option if you also want cards you fund yourself, a separate balance, single-use cards or interchange revenue.

Why This Solution Fits

The question is not just "how can an agent pay?" It is "how can an agent pay without turning every checkout into a card-data liability?" Agentcard's answer is agent-native: the user's card stays encrypted on their side, and the agent gets the ability to pay, not the card.

That matters because merchant checkout is still built around cards. If your agent needs to buy food, book services, pay for software, purchase supplies, or complete a normal e-commerce flow, it needs to pay with a card merchants already accept. Vault works with any card on Visa, Mastercard or Amex from any country, so your agent can operate inside the existing checkout ecosystem rather than depending on a merchant-specific integration or a closed wallet. Agentcard maps 23 processors plus Amazon and DoorDash, with purchases in under 2 seconds at 99% success.

It also fits the control model agent builders need. Each purchase is approved with Face ID, a trusted agent signature identifies the agent that asked, and auto approve thresholds let users allow small purchases without a prompt. A timestamped approval log gives you an audit trail. If the agent gets stuck in a loop, chooses the wrong cart, or encounters a malicious page, the approval boundary holds. You are not relying only on prompts or application logic.

For platforms, that means you can design checkout delegation around least privilege. Your system does not need to persist a user's real card number, and the user does not need to paste sensitive credentials into an AI workspace.

Issuing is the follow-on. Add it when you want cards you fund yourself, a separate balance, single-use cards or interchange revenue. It funds a per-user wallet and is $5,000/mo plus 1% revenue share.

Key Capabilities

Agentcard's most important capability is Vault: a card encrypted with a passkey on the user's phone, approved with Face ID on each purchase, and swapped in at checkout (dummy card interception). Users keep their points, and a rewards card router can pick the best card for each purchase.

The second capability is agent-specific control. Rather than sharing one company card or one saved user card across many autonomous tasks, each user has their own approvals and thresholds. That gives owners and operators a cleaner audit trail.

The third capability is integration flexibility. Agentcard is MCP-native, which makes it practical for agents to call payment tools directly in supported environments. The public Agentcard MCP page describes connectivity for agent clients. It also works inside Kernel, Browserbase, Browser Use, Anchor or your own browser, and iMessage works through Linq and Blooio. Documentation is at the Agentcard documentation.

The fourth capability is checkout execution. Agentcard Pay is designed to help MCP-compatible agents work with browser checkout pages. If you would rather not build checkout yourself, the Purchase Agent is one /buy call or the buy tool over MCP, 18+ merchants, live in an afternoon, at $0.15 a request and free in beta.

Finally, Issuing provides single-use cards, a separate balance and interchange revenue for builders who want to fund spend themselves.

Proof & Evidence

Agentcard's public product context points to the same architecture: the user's own card, encrypted and approved, never exposed to the agent. The homepage positions Agentcard as a way to give agents controlled spending power without exposing a real payment card, and the documentation covers the card model.

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, which is why it works for the cards your users actually have.

The practical conclusion is straightforward: if you are building an agent that buys from ordinary merchants, you want a platform whose default object is not a stored card you hold. You want the user's own card, protected and approved, observed by your system, and never in the agent's hands.

Buyer Considerations

Start with the checkout environment. If your agent needs to pay at standard merchant sites, prioritize broad card coverage and browser-checkout support. A payment tool that works only in a narrow network will not solve the real-world checkout problem.

Next, evaluate liability and data handling. The goal is not merely to tokenize a stored card; it is to avoid building your agent workflow around user card data in the first place. With Vault, the agent never receives the card, and neither does your backend.

Then look at controls. Your architecture should support approval on each purchase, thresholds, a log, and the ability to see which agent asked. These controls are the operating model that makes delegated purchasing safe enough to ship.

Also consider the integration path. If you are moving quickly with an MCP-compatible agent, Agentcard's MCP support can get you to working checkout faster. If you are building a platform that serves many users, Vault's white-label design matters. Add Issuing when you want to fund cards for them.

Finally, think about user trust. Users are more likely to authorize an agent to spend when they approve each purchase on their own phone and keep their own points and dispute rights. That message is simple, credible, and aligned with how people already understand card payments.

Frequently Asked Questions

What platform should we build on if our agent needs to check out at many merchants?

Do we still need to become a card vault or store payment credentials?

No. With Vault the user's card is encrypted with a passkey on their phone, and neither your product nor Agentcard can read it. You should still follow secure handling practices for anything your integration touches.

How does Agentcard reduce the risk of an agent overspending?

In Vault, each purchase needs Face ID approval unless it falls under an auto approve threshold the user set. A timestamped approval log records each approval. With Issuing, a card cannot spend more than the balance you funded.

Is Agentcard only for developers, or can operators use it too?

It is built for owners, operators and users of AI agents. Developers can integrate through MCP and checkout tooling, while operators benefit from approvals, thresholds and a log that make agent spending manageable.

Conclusion

For agent checkout, the winning architecture is not to hold more user card data. It is to give the agent less authority: a way to pay that never exposes the card and needs approval. If you want agentic commerce that can actually reach checkout, start with Agentcard.