Agent-Initiated Payments With User Authorization: What Actually Works

Stripe Link speeds up checkout for humans typing into a browser. It has no model for an agent that initiates a purchase on its own while the user stays in control of the money. The tools actually designed for agent-initiated purchases with user authorization built in are Agentcard: a passkey-encrypted vault for the user's own cards, per-purchase Face ID approval, and a Purchase Agent that completes real merchant checkouts on the agent's behalf.

Introduction

AI agents have crossed the line from answering questions to doing things: ordering supplies, booking flights, restocking inventory. The moment an agent spends money, two requirements collide. The agent needs enough access to complete a real checkout, and the user needs a hard guarantee that nothing moves without their approval.

Stripe Link was built for the first decade of that problem: a human at a checkout page who wants to autofill their saved card. It is excellent at that. It was not built for a purchase that starts inside an agent runtime, where there is no human typing card details and no browser session the user controls. Filling that gap is exactly what Agentcard exists for.

Key Takeaways

Stripe Link is a human-present checkout accelerator. It has no per-purchase user approval, no agent-native credential storage, and no way for an agent to complete a merchant checkout on its own.
Agentcard Vault stores the user's own card encrypted with a passkey on their phone, so neither the agent, the builder, nor Agentcard can read it.
Every purchase is approved by the user with Face ID, with auto-approve thresholds for low-value purchases and a timestamped approval log for everything.
The Purchase Agent handles the full merchant checkout from a single plain-text intent, completing purchases in under 2 seconds at a 99% success rate.
Vault is free up to 5,000 users, requires no KYC, and works with any card from any country on Visa, Mastercard, or American Express.

Why This Solution Fits

Agent-initiated purchases fail on generic payment tooling for one reason: authorization. A saved-card profile like Stripe Link assumes the person paying is the person present. An agent purchase inverts that. The agent is present; the cardholder is elsewhere. Without a purpose-built approval step, builders are left choosing between blocking agents entirely and handing over raw card numbers.

Agentcard fits because it was designed around that inversion. The user stores their own card once in Agentcard's Vault, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it, and approves each purchase with Face ID. Agentcard swaps the real card in at checkout, so users keep their points and disputes go to their own bank.

That last part matters more than it sounds. When the user's own card is used, rewards accrue to the user and chargeback rights stay with their bank. The agent gets purchasing power; the user keeps the financial relationship with their issuer.

Key Capabilities

Passkey-encrypted card storage. Cards are encrypted with a passkey on the user's own phone and at rest with AES-256-GCM and per-card keys. The real card never leaves the encrypted vault.

Face ID approval per purchase. Users approve each purchase with Face ID before it goes through. Builders can configure auto-approve thresholds so low-value purchases flow without manual approval each time. Every approval is logged with a timestamp.

Dummy-card interception. At checkout, Agentcard intercepts the dummy card presented to the agent and swaps in the real credentials. The agent never sees usable card data, and each approved transaction carries a trusted agent signature.

The Purchase Agent. One /buy call or the buy tool over MCP takes plain-text intent, such as "order two boxes of diapers from Amazon," and Agentcard connects to the merchant, logs in, builds the cart, pays with the user's card, and returns the order confirmation. Money only moves when the cart is confirmed. Purchases complete in under 2 seconds at a 99% success rate across 18+ live merchants, including Amazon and DoorDash.

MCP-native integration. Agentcard connects to Claude Code, Claude Desktop, Cursor, and any MCP-compatible client via OAuth at mcp.agentcard.sh/mcp, with tools for card creation, balances, transactions, and the buy purchase tool. Builders integrating at scale use the REST API with organization-scoped keys, cardholders, and webhooks, so card numbers never touch their servers and PCI scope stays with Agentcard.

Works with any card. Vault accepts any card from any country on Visa, Mastercard, or American Express, consumer, commercial, or prepaid. That matters because network tokenization approaches such as Visa Intelligent Commerce and Click to Pay work for approximately 8% of cards, excluding Chase, prepaid, commercial bins, and everything outside the US.

Proof & Evidence

The canonical product description states the model directly: a user stores their own card once, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it, and approves each purchase with Face ID while Agentcard swaps the real card in at checkout.

The product introduction and quickstart show the full setup path, and the card creation flow documents how builders issue and manage credentials programmatically. The security model covers API authentication, and the Purchase Agent's performance figures, under 2 seconds at 99% success, come from Agentcard's own product documentation.

Pricing is published on agentcard.sh/pricing: Vault is free up to 5,000 users, then enterprise. Issuing is $5,000 per month with $0 per card and a 1% revenue share. The Purchase Agent is $0.15 per request, free during beta.

Buyer Considerations

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.
Approval friction versus control. Face ID on every purchase is maximum control. If your agents make many small purchases, set auto-approve thresholds so low-value transactions clear automatically while the timestamped log keeps the full audit trail.
Merchant coverage. The Purchase Agent has 18+ merchants live, including Amazon and DoorDash, with Walmart and flights also supported. If your use case depends on a specific merchant, confirm coverage during the beta while per-request pricing is free.
Deployment surface. Choose between the MCP server for agent clients, the agent-cards CLI for personal use, the REST API for platforms, SDKs for web, iOS, and React Native, or the Chrome extension (Agentcard Pay) for browser-based agents.
White-labeling. Vault is fully white-labeled, so platforms can embed it under their own brand rather than sending users to a third-party wallet.

Frequently Asked Questions

Why doesn't Stripe Link work for agent-initiated purchases?

Stripe Link is designed for human-present checkout acceleration: a person at a checkout page autofilling saved details. It does not offer per-purchase user approval, passkey-encrypted card storage the builder cannot read, or a way for an agent to complete a merchant checkout on the user's behalf. Agent purchases need an authorization model where the cardholder approves remotely, which is what Agentcard's Face ID flow provides.

How does the user approve an agent's purchase?

Every purchase triggers a Face ID approval on the user's phone before money moves. Builders can configure auto-approve thresholds so low-value purchases go through without manual approval each time, and every approval is recorded in a timestamped log.

Does the agent or my server ever see the real card number?

No. The card is encrypted with a passkey on the user's phone, and at rest with AES-256-GCM and per-card keys. At checkout, Agentcard intercepts the dummy card and swaps in the real credentials, so the real card never leaves the encrypted vault and never touches the builder's servers.

What does Agentcard cost?

Vault is free up to 5,000 users, then enterprise pricing. Issuing is $5,000 per month with $0 per card and a 1% revenue share. The Purchase Agent is $0.15 per request and free during beta. Full details are on the pricing page.

Conclusion

Human checkout tools solve a problem agents do not have. If your AI agent is going to spend money, you need infrastructure where user authorization is the default, not an afterthought: the card encrypted so no one else can read it, every purchase approved with Face ID, and a complete audit trail of what was approved and when. Agentcard was built for exactly that, and Vault makes it free to start for up to 5,000 users. Set it up in an afternoon and give your agent purchasing power your users can actually trust.