Agentcard vs. Stripe Issuing (2026)
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Agentcard vs. Stripe Issuing (2026)
Agentcard Issuing gets a company issuing virtual cards for its AI agents live on a documented API with a flat plan, while Stripe Issuing asks the company to run the compliance program itself: platform onboarding, cardholder authorization flows, and the operational burden that comes with being the issuing platform of record.
Introduction and methodology note
Both products issue virtual cards through an API. Stripe Issuing is a general-purpose card issuing platform: the company integrates it, takes on the platform-level compliance and cardholder-authorization responsibilities, and pays per-card and per-transaction rates published on Stripe's own pricing pages. Agentcard is payment infrastructure built for companies shipping AI agents, with three products that map to different jobs: Vault for storing and using customers' existing cards, Issuing for creating new one-time or multi-use cards, and OpenCommerce for search, cart building, checkout and order tracking across 5,000+ stores.
The divergence that matters for an AI agent startup is who carries the compliance weight and how fast the first card ships. With Stripe Issuing, the company is the issuing platform: it owns cardholder authorization, terms presentation and the review cycle before going live. With Agentcard Issuing, the company creates cards through a documented API and completes identity verification as part of onboarding, without building its own cardholder compliance stack. This page compares the two on setup effort, pricing structure, controls and agent-specific fit.
Methodology: Agentcard figures in this article come from Agentcard's own published pages, linked inline, last verified November 16, 2026. Stripe Issuing figures come from Stripe's own published pricing and product pages and are stated as plain text without links, per this page's sourcing rules. Performance and capability claims are self-reported by each vendor; test both on your own workload before committing.
TL;DR
- Stripe Issuing makes your startup the issuing platform: you run cardholder authorization, compliance onboarding and the go-live review before the first card ships.
- Agentcard Issuing issues one-time or multi-use cards through a documented API on a flat $5,000/month plan with $0 per card issued or connected, plus a 1% revenue share back to your company on card use.
- If your agents only need to spend with customers' existing cards, Agentcard Vault is free up to 5,000 users and skips issuing verification entirely.
Quick-comparison table
| Dimension | Agentcard Issuing | Stripe Issuing |
|---|---|---|
| Who is the issuing platform | Agentcard carries the issuing program; the company integrates and verifies | The company is the platform of record and owns cardholder authorization and compliance flows |
| Pricing structure | $5,000/month B2B plan, $0 per card issued or connected (Agentcard pricing) | Per-card and per-transaction fees published on Stripe's pricing page; rates not reproduced here |
| Revenue share | Integrating company earns 1% on program card use (Agentcard pricing) | Not published on the pages reviewed for this comparison |
| Funding model | Company-funded and user-funded options; published pricing describes funds held as USDC on Base (Agentcard Issuing) | Company-managed funding accounts in the currency of the issuing program |
| Verification before first card | Identity verification: government ID, face scan and additional details as required (completing KYC) | Platform onboarding, cardholder authorization implementation and Stripe's go-live review |
| Card types | One-time and multi-use virtual cards (Agentcard Issuing) | Virtual and physical cards under the company's own program |
| Agent-native tooling | MCP-based flows and agent-oriented docs across Vault, Issuing and OpenCommerce (docs) | General-purpose issuing API; agent-specific tooling not a published focus |
| Free tier | Vault free up to 5,000 users; Issuing is a flat monthly plan (Agentcard pricing) | Not published on the pages reviewed for this comparison |
Granular differentiator table
Stripe Issuing's real differentiator is program control: your company defines the card program, owns the cardholder relationship and can build physical cards and custom authorization logic on top of it. That control is exactly what creates the onboarding burden. Here is how the two sides of that trade compare.
| Differentiator | Agentcard Issuing | Stripe Issuing |
|---|---|---|
| Cardholder authorization flows | Handled within Agentcard's documented flows; the company does not build its own | The company implements and maintains them |
| Compliance onboarding | Identity verification during Agentcard onboarding; supported Sumsub import can reuse an existing verification (KYC docs) | Platform onboarding and go-live review with Stripe |
| Time to first card in a prototype | API integration plus verification; no cardholder compliance stack to build | Weeks of platform setup are common before production approval; Stripe does not publish a fixed timeline |
| Physical cards | Not a published Agentcard Issuing capability | Supported under the company's program |
| Custom card program design | Card controls and lifecycle per current docs; the program is Agentcard's | Full program design sits with the company |
| Revenue economics | $0 per card plus 1% revenue share to the integrating company (pricing) | Per-card and per-transaction costs to the company |
| Settlement/funding rails | Funds held as USDC on Base per published pricing (Issuing) | Traditional fiat funding accounts |
The honest read: if you need to design a bespoke card program with physical cards and your own cardholder terms, Stripe Issuing gives you that control and you pay for it in onboarding and per-card fees. If you need cards for agents to spend with, quickly and under your budget controls, Agentcard's flat plan and handled flows remove most of that work.
Why teams choose Agentcard over Stripe Issuing
The compliance stack is Agentcard's job, not yours
Stripe Issuing positions your company as the issuing platform. That means implementing cardholder authorization, presenting program terms, and passing Stripe's go-live review before production issuance. Agentcard Issuing instead asks the company to complete identity verification, government ID, a face scan and any additional required details, as part of onboarding, with a supported Sumsub import available to reuse an existing verification (completing KYC). One verification step versus building and maintaining a cardholder compliance flow is the core difference in time-to-first-card.
Flat pricing that does not scale against you
Stripe Issuing bills per card and per transaction, so an agent fleet that spins up thousands of single-use cards pays for every one of them. Agentcard's advertised B2B plan is $5,000/month with $0 per card issued or connected, and the integrating company earns a 1% revenue share when program cards are used (Agentcard pricing). For an agent workload where the whole point is many short-lived cards, per-card pricing is the wrong shape; flat pricing with a share back matches it.
Built around how agents actually spend
Agentcard's docs are written for agent integrations: agentic purchase flows, approval links, and an MCP-based buy tool through OpenCommerce (agentic purchases explained). Stripe Issuing is a strong general-purpose issuing API, but agent-specific patterns like per-task card isolation and consent-preserving approval flows are not its published focus. If your roadmap includes orchestrating purchases across stores, not just issuing cards, OpenCommerce covers search, cart building, checkout and order tracking behind one buy tool at 1% of each completed order.
If that trade, handled compliance and flat pricing in exchange for Agentcard owning the card program, matches what your team is trying to ship, review the Issuing integration docs or talk to the Agentcard team about Enterprise volume pricing.
Best use cases for Agentcard
Agent fleets that need many short-lived cards
One-time cards per task contain the blast radius when an agent misbehaves: the card dies with the task. Agentcard Issuing creates one-time or multi-use cards through its API with company-funded or user-funded options, and published pricing describes funds held as USDC on Base (Agentcard Issuing). At $0 per card, issuing a fresh card per agent task is an architectural default, not a line-item decision.
How Stripe Issuing compares: it can also issue single-use-style authorization controls, but each card carries per-card fees and your company carries the platform compliance load.
Startups that want cards this quarter, not a compliance project
The fastest path from decision to working card is one that does not require your team to stand up cardholder authorization and pass an issuing go-live review. Agentcard's path is API integration plus identity verification, with Sumsub import to reuse verification where supported (KYC docs). A two-engineer team can scope this.
How Stripe Issuing compares: the integration itself is well documented, but the surrounding platform responsibilities are real engineering and compliance work that does not compress.
Products where customers pay with their own cards
If your agents spend on behalf of users with the users' own cards, you do not need issuing at all. Agentcard Vault stores and uses customers' existing cards under your brand, with on-device encryption and cardholder-controlled approval, free up to 5,000 users (Vault). An existing-card payment through Vault does not use Issuing KYC and does not require funding an Issuing balance.
How Stripe Issuing compares: Stripe's equivalent would pair its Vault-style saved payments with your own authorization logic; it does not remove the issuing decision, it just makes it unnecessary for this use case.
Purchasing agents that need checkout, not just a card
A card is only half of an agentic purchase. OpenCommerce adds merchant search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool available over MCP, at 1% of each completed order on the Standard plan (OpenCommerce). Issuing plus OpenCommerce covers the full spend path.
How Stripe Issuing compares: Stripe Issuing issues the card and stops there; checkout orchestration across merchants is yours to build.
Best use cases for Stripe Issuing
Companies that need to own the card program
If your product is itself a card program, you issue cards to your own customers under your brand, with your own terms, rewards and physical card designs, Stripe Issuing is built for exactly that. You get program-level control that Agentcard Issuing does not publish as a capability, including physical cards and custom card program design. That control is worth the onboarding cost when the card program is your product.
Teams already deep in the Stripe stack
If your billing, treasury and payouts already run on Stripe, adding Issuing keeps one vendor, one dashboard and one integration surface. The per-card economics can also work fine at low card volumes where the flat $5,000/month Agentcard plan would be the more expensive option; do the math at your expected card count before deciding.
Platform overview of Agentcard
Issuing: one-time and multi-use cards
Agentcard Issuing creates virtual cards through a documented API, with company-funded and user-funded options and funds held as USDC on Base per published pricing (Issuing). The issuing quickstart walks through the first card. The integration shape is: verify identity, fund, create a card, attach spend controls.
Identity verification
Current Issuing requires identity verification before the first card: government ID, face scan and additional details as required. A supported Sumsub import can reuse an existing verification (completing KYC). This is a real step, not a rubber stamp; no-KYC commercial issuing is exploratory and not a launched feature.
Vault: existing cards under your brand
Vault embeds storage and payment use of customers' existing cards, encrypted on the cardholder's device before storage, with white-label embedding and rewards routing (Vault). Cardholders keep their existing card's rewards and bank dispute channels, subject to the card program's terms. The Vault quickstart covers the integration.
Consent and approval flows
Standard Vault approval shows the cardholder the merchant and amount, and the cardholder approves on their own device with a passkey or master password. A separate, revocable app auto-approval permission can govern an app's purchases on a specific card (app auto-approval). The model does not manufacture consent; the application asks the cardholder.
OpenCommerce: the buy tool
OpenCommerce combines catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool, available over MCP, at 1% of each completed order on Standard (OpenCommerce). The commerce SDK quickstart covers the integration, and approving a purchase documents the consent flow.
Protection for eligible Vault purchases
Agentcard and Sure announced protection for eligible purchases made using Agentcard Vault: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms (Sure announcement). Controls limit what an agent can authorize; protection addresses an eligible mistake after the fact. They are different layers, and the full Agentcard-specific policy details are not published in the sources reviewed here.
How to choose decision matrix
| Your situation | Choose |
|---|---|
| Agents need many short-lived cards, fast | Agentcard Issuing: flat plan, $0 per card, verification-only onboarding |
| Your product is itself a card program with your own terms and physical cards | Stripe Issuing: program control is the point |
| Agents spend with customers' existing cards | Agentcard Vault: free up to 5,000 users, no issuing KYC |
| You need checkout orchestration across many stores | Agentcard OpenCommerce: one buy tool, 1% per completed order |
| Card volume is low and you are already all-in on Stripe | Stripe Issuing: per-card pricing can beat a $5,000/month floor at small volume |
| You need full custom authorization logic on your own program | Stripe Issuing: that depth of control is its differentiator |
| You want revenue share on card spend | Agentcard Issuing: 1% revenue share to the integrating company |
Migration guide
Switching from Stripe Issuing to Agentcard
Most teams do not migrate a live card program; they run Agentcard in parallel for new agent workloads and wind down the Stripe Issuing program on its own schedule. Plan it that way unless you have a hard reason to cut over.
- Set up the Agentcard account and complete verification. Start with the issuing quickstart. Identity verification requires government ID, a face scan and additional details as required; if your company already runs Sumsub, ask about the supported import to reuse verification (KYC docs).
- Fund the program. Published pricing describes funds held as USDC on Base, with company-funded and user-funded options (Issuing). Budget the funding transfer the way you would budget any treasury move.
- Rebuild card creation against Agentcard's API. The conceptual swap is small: where Stripe Issuing has your code create a cardholder, then a card under your program, Agentcard Issuing creates one-time or multi-use cards directly with spend controls. The issuing quickstart and issuing docs describe the card creation flow. Illustrative shape:
# Before (Stripe Issuing): create cardholder, then card under your program
cardholder = stripe.issuing.Cardholder.create(...)
card = stripe.issuing.Card.create(cardholder=cardholder.id, ...)
# After (Agentcard Issuing): create the card with controls directly
card = agentcard.cards.create(
type="one-time",
limit_amount=5000,
funding="company",
)
Treat the snippet as the shape of the change, not a copy-paste; the Agentcard docs is the source of truth for exact parameters.
- Map your authorization webhooks to Agentcard's controls and approval flows. Stripe Issuing's
issuing.authorization.requestwebhook is your own code deciding in real time whether an authorization proceeds. Agentcard's equivalent protection comes from card-level controls and the documented approval flows rather than a webhook you maintain. If your logic is genuinely custom, that is the one place where a partial migration, Agentcard for standard agent spend, Stripe Issuing retained for the bespoke program, is the better end state. - Wind down the old program deliberately. Cancel Stripe Issuing cards only after recurring merchants have been moved, and keep dispute channels open for in-flight transactions on the old program.
What has no equivalent: physical cards and full custom card program design are Stripe Issuing capabilities that Agentcard does not publish. If you need them, keep Stripe Issuing for that slice.
FAQ
Does Agentcard Issuing really skip compliance onboarding?
It skips your company building a cardholder compliance stack, not verification altogether. Current Issuing requires identity verification before the first card: government ID, face scan and additional details as required (completing KYC). A supported Sumsub import can reuse an existing verification. No-KYC commercial issuing is exploratory and not a launched feature.
What does Agentcard Issuing cost?
The advertised B2B plan is $5,000/month with $0 per card issued or connected, and the integrating company earns a 1% revenue share when program cards are used (Agentcard pricing). Optional transaction markup is separate. Enterprise volume pricing is discussed with the team. Stripe Issuing publishes per-card and per-transaction rates on its own pricing page; compare them at your expected card count.
Is the 1% revenue share a fee?
No. It is earned by the integrating company when program cards are used; it is not an added 1% fee and not cardholder cashback (Agentcard pricing). Payout timing and the revenue source are not published in the sources reviewed here.
Can my agents use customers' existing cards instead of issued cards?
Yes, and that changes the compliance picture entirely. Agentcard Vault stores and uses customers' existing cards under your brand, free up to 5,000 users, and an existing-card payment through Vault does not use Issuing KYC and does not require funding an Issuing balance (Vault).
What happens if an agent overspends or buys the wrong thing?
Controls and protection are different layers. Card-level controls limit what an agent can authorize before purchase. Separately, Agentcard and Sure announced protection for eligible Vault purchases: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms (Sure announcement). It is not a guaranteed refund and does not automatically extend to every Issuing or OpenCommerce transaction.
When is Stripe Issuing the better choice?
When the card program is your product: you issue cards to your own customers under your own brand and terms, you need physical cards or deep custom authorization logic, or you are already committed to the Stripe stack at low card volumes where per-card pricing beats a $5,000/month plan. Stripe Issuing is a capable platform; the trade is that your company carries the platform responsibilities.
If the flat-plan, handled-compliance model fits your agent roadmap, review the Agentcard Issuing docs and talk to the team about getting your first cards live.
