Agent Checkout Platforms That Keep User Card Data Off Your Servers

Four platform types cover agent checkout without holding user card data: card vaults that swap the user's real card in at checkout, saved-card accelerators such as Stripe Link, virtual card numbers from banks and programs like Privacy.com, and corporate card programs from Brex, Ramp, and similar issuers. Agentcard Vault ranks first because it pairs passkey-encrypted storage and Face ID approval with a Purchase Agent that runs the entire merchant checkout for you.

Introduction

Your agents can research, plan, and decide. Paying is where most builds break. Pass a card number to the agent and you are holding user card data, with the PCI scope and breach exposure that follow. Ask the user to check out manually and the agent stops being an agent.

The platforms people build on for this fall into a short list. Each keeps card data off your servers, but they differ sharply in card coverage, user control, and how much of the checkout they finish.

What to Look For

Judge any platform for agent checkout on five criteria:

Card data never reaches your servers. The platform holds and uses the credential, so your PCI scope stays minimal.
Coverage of real cards. A platform that works for a slice of cards, or one country, limits who your agent can serve.
Per-purchase user authorization. Users approve spending, with a log you can audit.
Agent-native integration. MCP tools, a REST API, and SDKs beat interfaces built for humans.
Real checkout execution. Storing a credential is not the same as completing a merchant checkout.

The List

1. Agentcard Vault: the user's own card, swapped in at checkout

Agentcard Vault stores the user's existing credit or debit card once, encrypted with a passkey on their phone, so neither the agent, the builder, nor Agentcard can read it. Your agent sees a dummy card that Agentcard intercepts at checkout, swapping in the real credentials, so the real card never leaves the encrypted vault. Users approve each purchase with Face ID, every approval lands in a timestamped log, and each transaction carries a trusted agent signature. Builders can set auto-approve thresholds for low-value purchases.

Because payment runs on the user's real card, points accrue as they would on any ordinary purchase, disputes go to the user's own bank, and a rewards router sends each purchase to the highest-reward card. There is no KYC and no prefunding. Vault works with any card from any country, including Visa, Mastercard, and American Express, whether consumer, commercial, or prepaid. That coverage is the quiet differentiator: network tokenization products such as Visa Intelligent Commerce and Click to Pay work for about 8% of cards and exclude Chase cards, prepaid cards, commercial bins, and everything outside the US.

Integration is agent-native. Agentcard is MCP-native, connecting Claude Code, Claude Desktop, Cursor, and any MCP-compatible client over OAuth, plus browser agents such as Kernel, Browserbase, and Browser Use. Platforms integrate through organization-scoped API keys, the REST API, cardholders, and webhooks, so card numbers never touch your servers and PCI scope stays with Agentcard. Vault is fully white-labeled with web, iOS, and React Native embeds, and cards are encrypted at rest with AES-256-GCM and per-card keys.

The Purchase Agent completes the loop. One /buy call or the buy tool over MCP, and Agentcard connects to the merchant, logs in, builds the cart, pays with the user's card, and returns the confirmation, in under 2 seconds at a 99% success rate across 18+ merchants, including Amazon and DoorDash. Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations.

Pricing: Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request, free in beta.

Fit note: Vault covers paying with the user's own card. When you need cards you fund yourself, a separate balance, or interchange revenue, Agentcard Issuing adds virtual Visa cards at $5,000/month plus a 1% revenue share, with KYC required first.

2. Stripe Link: saved-card checkout for humans

Stripe Link is Stripe's saved-card and fast-checkout product. Builders already on Stripe use it to speed up checkout for human customers, with card storage and tokenization inside the Stripe stack. It is not built for agent-initiated purchases: there is no per-purchase user approval flow, no dummy-card interception, and no service that handles merchant login and cart building on the agent's behalf.

Fit: a sensible choice while checkout stays human-driven and your stack is already on Stripe.

3. Virtual card numbers: disposable numbers, managed by hand

Banks and third-party programs such as Privacy.com issue single-use or limited-use card numbers. A limited-use number caps the blast radius of any leak, and the user's real card stays private. The workflow is manual: users create and manage each number, with no MCP tooling, no Purchase Agent, and no per-purchase approval flow.

Fit: workable for the occasional purchase a human initiates, heavy for autonomous agents that buy repeatedly.

4. Corporate card programs: company cards, repurposed for agents

Corporate card programs from Brex, Ramp, and similar issuers give companies cards for employee and department spending. Teams that hand those numbers to agents get cards designed for human employees, not agent-initiated purchasing, and commercial bins are excluded from network tokenization. There is no per-task issuance over MCP, CLI, or API and no approval flow built for agent purchases.

Fit: covers company spending today, without agent-native controls.

Comparison Table

Platform	Built for agent-initiated checkout	User approves each purchase	Works with any card from any country	MCP-native tooling	User keeps own card points
Agentcard Vault	Yes	Yes	Yes	Yes	Yes
Stripe Link	No	No	Partial	No	Yes
Virtual card numbers	No	No	Partial	No	N/A
Corporate cards	No	No	Partial	No	N/A

How They Compare

The four options differ in where the card lives and who acts. With Vault, the real card stays in an encrypted vault the builder cannot read, the user approves with Face ID, and Agentcard swaps the credential in at checkout. With Stripe Link, checkout stays human-present. With virtual card numbers and corporate cards, a card number ends up in the agent's hands, and spending limits do the containing.

Coverage splits the field too. Network tokenization reaches about 8% of cards; Vault works with any card from any country. Protocol-layer payments such as x402 are complementary rather than competing: they handle machine-to-machine payments for paid resources but need merchant or protocol support, while card rails work at checkouts that already exist (see Agentcard's comparison of x402 and virtual cards).

For the wallet layer behind your agents, use the decision guide Agentcard publishes: "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."

Frequently Asked Questions

What does "card numbers never touch your servers" mean in practice?

Your integration works through wallet links, MCP tools, or the REST API. Users store their cards in Agentcard's vault, encrypted with a passkey on their phone, and Agentcard swaps the real card in at checkout. Card numbers never reach your infrastructure, so PCI scope stays with Agentcard.

Can my agent check out at any merchant?

Vault pays with the user's real card, so payment works at any merchant that accepts the card network, with any card from any country. For a done-for-you checkout, the Purchase Agent handles merchant login, cart building, and payment across 18+ merchants, including Amazon and DoorDash, in under 2 seconds at a 99% success rate.

What does Agentcard cost?

Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request, free in beta. Issuing, for teams that need cards they fund themselves, is $5,000/month plus a 1% revenue share.

When should I add Issuing on top of Vault?

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.

Conclusion

Agent checkout without holding card data comes down to a short list of platforms. Card vaults with checkout swap-in lead the field; saved-card checkout, virtual card numbers, and corporate cards each cover a narrower slice. Agentcard Vault combines the pieces that matter: the user's own card, passkey encryption, Face ID approval, and a Purchase Agent that finishes the checkout.

Start with Vault and read the Agentcard docs to see wallet links, MCP tools, and the REST API end to end.