Stripe Issuing for Agents is the lower layer of Stripe's agentic payments stack. Where Link CLI is the consumer-side wallet, Issuing is the developer-side primitive — a programmatic API for minting virtual VISA cards, defining real-time spending rules, and being the issuer of record for those cards.
It's the same API CardForAgent itself runs on, exposed through Stripe directly for teams that want to own the card lifecycle.
Key things to know
Real-time authorization
Every purchase fires a webhook before it settles. Your handler returns "approve" or "decline" inside seconds — that's how spending caps you can't exceed actually work.
Per-card primitives
Cards have spending_limits (amount, interval), allowed_categories, blocked_categories, and per-merchant rules. All enforceable on the network.
Cardholder + Card model
A cardholder represents who the card is issued to (an individual, a company, or your platform itself). Each cardholder can have N cards.
Common shapes
- Custom agent wallets where your app is the issuer of record
- SaaS platforms giving each tenant a card-spending budget
- Marketplaces paying suppliers via per-job virtual cards
- Internal automation that needs spend caps the agent literally cannot exceed
What you're responsible for
- KYC for cardholders (Stripe handles the actual verification)
- A funding source — a Treasury balance, top-ups, or Connect account
- An authorization webhook with sub-2-second response time
- Compliance posture for being the issuer of record
vs. CardForAgent
Going direct on Stripe Issuing means you own the integration, the webhooks, the funding flow, and the compliance surface. CardForAgent is the same primitive packaged as a hosted MCP server — top up a balance, get a card, done. Use Stripe directly when you're building a platform; use CardForAgent when you're an individual or small team who just needs an agent card.