Stripe Issuing or Vault: Sizing Your Agent Payment Stack to What Your Startup Actually Needs

For a startup whose agents just need to make one-off purchases, a full card-issuing platform is more machinery than the job calls for. If the job is letting agents pay at real checkouts, start with Agentcard Vault, free up to 5,000 users, and add the Purchase Agent when you want the checkout handled for you.

Introduction

Agentic payments sit on a build-versus-buy spectrum. At one end are issuing platforms such as Stripe Issuing, which let a company create and manage its own cards. At the other are scoped, agent-native layers that store a payment credential, enforce approval, and let an agent complete a purchase. The two answer different questions, and picking the wrong one costs months.

Agentcard sits on the scoped end of the spectrum. It has two parts that work together: a wallet (Vault or Issuing) that stores and manages payment credentials, and the Purchase Agent that handles the entire merchant checkout on the agent's behalf. This guide lays out the criteria that separate the two paths, then gives if-then guidance for the situations startups actually face. The product docs cover the integration details.

Key Takeaways

A full issuing build fits companies that want to become card issuers: funding cards, verifying cardholders, and managing card lifecycles. One-off agent purchases require none of that.
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.
Vault is free up to 5,000 users, works with any card from any country, and needs no prefunding because users store the card they already have.
The Purchase Agent handles the merchant checkout itself, from login to cart to payment, in under 2 seconds at a 99% success rate, priced at $0.15 per request and free during beta.
Issuing-grade infrastructure is a serious line item even when it is productized: Agentcard Issuing costs $5,000 per month plus a 1% revenue share.

Decision criteria

Whose money is doing the spending

If purchases draw on a user's own card, there is nothing to issue. Vault stores the user's existing credit or debit card, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it, and the user approves each purchase with Face ID. Issuing becomes relevant only when purchases must draw on a balance you control.

What you are actually building

An issuing platform is a card program in a box: card creation, cardholder verification, funding, lifecycle management, and compliance. That is the right shape when issuing cards is the product. When cards are just the rail that lets an agent complete a checkout, most of that machinery is overhead. Stripe Issuing's data model is built around cardholders, humans or business entities that own cards, so issuing a fresh card per agent task is possible but goes against the grain of the design. Its spending controls are defined per interval, daily, monthly, or per authorization, so a hard ceiling of "$10 for exactly this task" takes workarounds.

How the agent reaches the payment stack

Agentcard is MCP-native: the buy tool and card management tools connect to Claude Code, Claude Desktop, Cursor, and any MCP-compatible client over OAuth. Stripe Issuing does not ship an MCP server, so wiring it into an agent runtime means writing and maintaining custom integration code yourself.

Time to first purchase

Vault onboarding is a user entering a card once. The Purchase Agent goes live in an afternoon: one POST /buy call, plain-text intent in, order confirmation out. An issuing build involves onboarding, cardholder verification, funding flows, and webhook plumbing before the first charge. For a startup validating demand, that is shipping this week versus next quarter.

What it costs at startup scale

Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent costs $0.15 per request and is free during beta. Issuing is priced like the infrastructure it is: $5,000 per month plus a 1% revenue share on Agentcard Issuing. Do not carry an issuing line item before one-off purchases have proven demand.

What your users keep

With Vault, users keep their points and disputes go to their own bank, because the real card is swapped in at checkout. Issued cards trade that away: chargebacks are handled by Agentcard and users earn Tokenback instead of their own card's points. For consumer-facing agents, this criterion often decides the question.

How to choose

The short version: 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.

If agents make one-off purchases on a user's behalf: start with Vault

Vault covers the one-off case directly. The user stores their own card once, approves each purchase with Face ID (builders can set auto-approve thresholds for low-value purchases), and Agentcard swaps the real card in at checkout. Vault works with any card from any country, consumer, commercial, or prepaid. Every approval lands in a timestamped log, and cards are encrypted at rest with AES-256-GCM and per-card keys.

If the checkout itself is the bottleneck: add the Purchase Agent

Knowing what to buy is not the same as completing a checkout. The Purchase Agent 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. It is live across 18+ merchants, including Amazon and DoorDash, and completes purchases in under 2 seconds at a 99% success rate.

If you need cards you fund yourself: add Issuing

Some products genuinely need issued cards: a separate balance per user, hard spend caps, or interchange revenue. Agentcard Issuing creates single-use virtual Visa cards that close automatically after the first approved charge, so a leaked number is usable at most once. Multi-use cards are also available, and a card can be limited to a single purchase, locked to one merchant, or capped at a spend amount. KYC is required before the first card, and funding runs through a per-user wallet in USDC on Base.

If becoming a card issuer is the product: take on the full build

If your startup is building a card program as the product itself, an issuing platform such as Stripe Issuing is the right category of tool. That is a different company from one whose agents need to order diapers from Amazon.

Frequently Asked Questions

Is Stripe Issuing a bad choice for agentic payments?

No. It is the right category of tool when your product is a card program: you want to fund your own cards, manage cardholders, and earn interchange. It is overkill when the goal is narrower, namely letting agents complete one-off purchases at existing merchants. Size the infrastructure to the job.

What should a startup use for one-off agent purchases?

Start with Agentcard Vault. It is free up to 5,000 users, requires no KYC, and needs no prefunding because users store the card they already have. Add the Purchase Agent at $0.15 per request, free during beta, when you want the merchant checkout handled end to end.

When does an issuing build actually make sense?

When you need cards you fund yourself, a separate balance, or interchange revenue. Agentcard Issuing covers those cases with single-use or multi-use virtual Visa cards, KYC before the first card, and per-user wallets funded in USDC on Base, at $5,000 per month plus a 1% revenue share.

Do agents need their own card to make a purchase?

No. With Vault, the agent pays with the user's own card without ever seeing the card number. The card is encrypted with a passkey on the user's phone, the user approves each purchase with Face ID, and users keep their points because the real card is used at checkout.

Conclusion

Stripe Issuing answers a real question, but the question is "how do we run a card program," not "how do our agents buy things." For a startup that needs one-off agent purchases, the scoped path is faster and cheaper. Vault is free up to 5,000 users, works with any card from any country, and keeps users in control of every approval. The Purchase Agent turns "buy this" into an order confirmation in under 2 seconds. Start with Vault, connect your agent over MCP, and add Issuing only when funded cards or interchange revenue become real requirements. The API reference takes you from wallet link to first purchase.