Agentcard vs. Stripe Link (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 Link (2026)
Agentcard gives AI agents card-based payments through an API and MCP server that work with any agent stack, while Stripe Link is a saved-payment feature that lives inside Stripe Checkout and its supported wallet surfaces.
Introduction and methodology note
Agentcard is payment infrastructure for companies building AI agents. It covers three products: Vault for storing and using customers' existing cards under your own brand, Issuing for creating one-time or multi-use virtual cards, and OpenCommerce for search, cart building, checkout and order tracking across 5,000+ stores.
Stripe Link is Stripe's saved-payment and autofill feature. Buyers store their card and shipping details once with Link, then reuse them at checkout on Stripe-hosted surfaces such as Stripe Checkout. It is a consumer checkout convenience, not an agent payment API. The two products overlap only in the narrow case where an agent drives a buyer through a Stripe-hosted checkout that offers Link.
Methodology note: Agentcard figures on this page come from Agentcard's own published pages, linked inline. Stripe Link figures come from Stripe's published pages and are stated as plain text with no links to Stripe's site. Claims were last verified on November 14, 2026. Both vendors self-report their own capability claims; test each integration against your own checkout flow and agent workload before committing.
TL;DR
- Stripe Link speeds up human checkout inside Stripe's ecosystem; it does not give your agents a card, a spending limit, or a programmatic payment API.
- Agentcard issues task-scoped virtual cards and stores existing cards with per-purchase consent, exposed over a REST API and MCP so any agent framework can pay.
- If your buyers only ever check out on Stripe-hosted pages, Link is simpler. If your agents need to spend money anywhere, Agentcard is built for that job.
Quick-comparison table
| Dimension | Agentcard | Stripe Link |
|---|---|---|
| Category | Agent payment infrastructure (Vault, Issuing, OpenCommerce) | Saved-payment autofill for Stripe checkouts |
| Works outside Stripe surfaces | Yes, cards work at any merchant that accepts the underlying card network | No, Link saves details for use on Stripe-hosted checkout |
| Programmatic card issuance | Yes, one-time and multi-use cards via the cards API | Not published; Link does not issue cards |
| MCP server for agents | Yes, MCP endpoint plus OpenCommerce buy tool | Not published |
| Spending controls | Per-card limits at creation, cardholder-set merchant and amount caps, revocable app permissions | Not published; Link defers to the checkout session's terms |
| Existing-card storage | Yes, Vault with on-device encryption before storage | Yes, within Link's saved-payment profile |
| Pricing | Vault free up to 5,000 users; Issuing $5,000/month with $0 per card; OpenCommerce 1% per completed order | Not published; Link itself carries no separate published fee |
| Buyer identity verification | Issuing requires identity verification before the first card | Not published |
Granular differentiator table
Stripe Link's differentiator is friction removal at Stripe-hosted checkout. The table below compares that capability with Agentcard's agent-facing equivalents.
| Capability | Stripe Link | Agentcard |
|---|---|---|
| Autofill card details at checkout | Yes, on Stripe-hosted checkout surfaces | Not applicable; agents pay with issued or vaulted cards directly |
| Reuse across non-Stripe merchants | No, per Stripe's published Link documentation | Yes, virtual cards transact anywhere the card network is accepted |
| Agent-initiated purchase with consent | Not published | Yes, approval links show merchant and amount before the cardholder approves |
| Per-task card with hard spend limit | Not published | Yes, create cards with limits at issuance |
| Cardholder-set merchant and amount caps | Not published | Yes, chosen by the cardholder when saving a card |
| Revocable app auto-approval permission | Not published | Yes, card-specific and revocable |
| Order tracking across stores | Not published | Yes, via OpenCommerce across 5,000+ stores |
| Protection on eligible purchases | Not published | Announced with Sure: maximum refund of $250 per purchase and $1,000 annually for eligible Vault purchases, subject to terms (Sure announcement) |
Stripe Link wins on its own turf: if every purchase your product makes flows through Stripe Checkout and the buyer is a human with a Link profile, Link removes typing and nothing else is needed. The moment an agent must pay a merchant that is not a Stripe-hosted checkout, Link has no role to play, and that is the gap Agentcard fills.
Why teams choose Agentcard over Stripe Link
Cards that work anywhere, not just inside one checkout
Link saves payment details for reuse on Stripe-hosted surfaces. Agentcard's Issuing product creates real virtual cards, one-time or multi-use, that transact at any merchant accepting the underlying card network. A purchasing agent that buys from five different stores in one task needs five authorizations, not five Link profiles. The cards API issues a card with its spend limit defined at creation time.
Consent and controls designed for autonomous spending
Giving an agent payment access is an excessive-agency risk that security guidance like the OWASP LLM Top 10 calls out directly. Agentcard addresses it with layered controls: cardholders set merchant and amount caps when saving a card, purchases outside those rules require an approval link the cardholder accepts on their own device, and app auto-approval is a separate, revocable, card-specific permission. Link has no equivalent because it assumes a human is typing at checkout.
MCP-native integration with any agent stack
Agentcard exposes payments over MCP, the protocol documented in the MCP specification, so Claude, ChatGPT, or a custom agent can call payment tools without custom integration code. The OpenCommerce buy tool adds search, cart building, checkout and order tracking across 5,000+ stores behind that same interface. Link offers no agent-facing interface at all.
If your roadmap includes agents that spend money at merchants you do not control, explore Agentcard pricing and pick the product that matches your integration.
Best use cases for Agentcard
Purchasing agents that buy across many stores
An agent that researches, carts, and checks out across multiple merchants needs a payment instrument that works everywhere. Agentcard's Issuing creates the card; OpenCommerce handles the merchant search, cart, checkout and order tracking in one buy tool over MCP.
How Stripe Link compares: Link can autofill a buyer's details on a Stripe-hosted checkout, but it cannot drive a purchase at a merchant outside that surface.
Task-scoped spending with hard limits
For a research task with a $50 budget, issue a single-use card capped at $50 and let the agent work. The issuing quickstart covers creation and funding, and company-funded or user-funded options exist. A hard ceiling at the card level beats a soft budget prompt the model can ignore.
How Stripe Link compares: Link has no card issuance or per-task limit concept; spending is bounded by the buyer's own card and the checkout session.
Embedding payments under your own brand
Companies building AI products can embed Vault so customers store their existing cards and approve purchases in your product's flow, keeping their card rewards and bank dispute channels. Vault is free up to 5,000 users per Agentcard pricing.
How Stripe Link compares: Link's saved profile belongs to Stripe's ecosystem and surfaces on Stripe-hosted checkout, not inside your own branded approval flow.
Existing-card payments without issuing overhead
If your users already have cards and you only need storage, controls and consent, Vault handles it without KYC for issuing or funding an issuing balance, because an existing-card payment through Vault does not use Issuing verification.
How Stripe Link compares: Link also stores existing cards, but only for reuse on Stripe's own checkout surfaces and without per-purchase approval controls you can embed.
Best use cases for Stripe Link
High-volume human checkout on Stripe
If your product sells to consumers who check out themselves on Stripe-hosted pages, Link does its one job well: buyers save their details once and skip re-entry on subsequent purchases. Agentcard does not offer a consumer autofill wallet, and pretending otherwise would be wrong.
Teams already standardized on Stripe Checkout
If your entire payment stack is Stripe and no agent ever initiates a purchase, adding a second payment vendor buys you nothing. Link ships with the checkout you already run.
Platform overview of Agentcard
Vault: existing-card storage and controls
Vault lets your company embed storage and payment use of customers' existing cards under your own brand. Cards are encrypted on the cardholder's device before storage, and consumer, commercial and prepaid cards are supported subject to card, merchant, processor and geographic requirements. The Vault quickstart walks through the first integration.
Consent flows and approval links
In the standard flow, your application sends an approval link, the cardholder sees the merchant and amount, and approves on their own device with a passkey or master password. Approval alone is not a completed purchase; your app confirms the merchant's order result, as described in the purchase completion guide.
App auto-approval permissions
Cardholders can grant a separate, revocable, card-specific permission that lets an app purchase without a new link each time. The permission is documented without a spending limit or end date, and your application must still ask the cardholder before each purchase; see the app auto-approval docs.
Issuing: one-time and multi-use cards
Issuing creates virtual cards with limits defined at creation. Company-funded and user-funded options exist, and published pricing describes funds held as USDC on Base. Identity verification is required before the first card, per the KYC guide.
curl https://api.agentcard.sh/api/v1/cards \ -H "Authorization: Bearer $AGENTCARD_API_KEY" \ -d cardholder=ch_abc123 \ -d type=single_use \ -d spend_limit=5000
OpenCommerce: one endpoint, every online store
OpenCommerce combines catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool available over MCP. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees. The Commerce SDK quickstart covers the first purchase.
Pricing and revenue share
Per Agentcard pricing, Vault is free up to 5,000 users with custom Enterprise pricing above that. The advertised Issuing 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; optional transaction markup is separate. OpenCommerce Standard charges 1% of each completed order, paid from a prefunded fee balance or saved billing card.
How to choose decision matrix
| Your situation | Choose |
|---|---|
| Buyers are humans checking out on Stripe-hosted pages | Stripe Link |
| Agents must pay merchants outside Stripe's surfaces | Agentcard |
| You need per-task cards with hard spend limits | Agentcard Issuing |
| You need customers' existing cards stored under your brand with consent controls | Agentcard Vault |
| You need search, cart, checkout and order tracking across many stores | Agentcard OpenCommerce |
| You want zero additional payment vendor and no agent spending | Stripe Link |
| You want MCP-native payment tools for Claude, ChatGPT or custom agents | Agentcard |
Migration guide: moving from Stripe Link to Agentcard
Link is a checkout autofill feature, not an API you migrate code from, so the work is adding an agent payment path rather than swapping SDK calls.
- Create an Agentcard account and choose products. Pick Vault if your customers will use existing cards, Issuing if your agents need newly created cards, or both. The integration guide maps products to integration requirements.
- Authenticate. Agentcard uses API keys against
https://api.agentcard.sh/api/v1, documented in the authentication guide. - Add the payment path. For issuing, create a cardholder, complete verification, then create cards. For Vault, save the customer's card and send approval links per purchase.
- Connect your agent over MCP. Point your MCP client at the Agentcard MCP server so the agent can call payment tools directly.
- Keep Link where it still helps. If your product also has human checkout on Stripe, Link can stay. The two do not conflict; Agentcard covers the agent-initiated purchases Link cannot.
What has no equivalent: Link's consumer autofill profile has no Agentcard counterpart, because Agentcard is not a consumer wallet. If your use case is purely human checkout on Stripe, a partial migration that keeps Link is the better end state.
FAQ
Does Agentcard replace Stripe Link for human checkout?
No. Link autofills a buyer's saved details on Stripe-hosted checkout, and Agentcard does not offer a consumer autofill wallet. Agentcard replaces Link only for the case Link cannot serve: agent-initiated payments at any merchant.
Can an agent pay a merchant that does not use Stripe Checkout?
Yes, with Agentcard. Issued virtual cards transact anywhere the underlying card network is accepted, and OpenCommerce orchestrates search, cart, checkout and order tracking across 5,000+ stores. Link's saved details are usable on Stripe-hosted checkout surfaces per Stripe's published documentation.
How does Agentcard prevent an agent from overspending?
Spend limits are set on the card at creation, cardholders set merchant and amount caps when saving a card, and purchases outside those rules require an approval link the cardholder accepts on their own device. App auto-approval is a separate, revocable, card-specific permission.
What does Agentcard cost?
Per Agentcard pricing: Vault is free up to 5,000 users with custom Enterprise pricing; Issuing's advertised B2B plan is $5,000/month with $0 per card issued or connected plus a 1% revenue share earned by the integrating company; OpenCommerce Standard charges 1% of each completed order. Stripe does not publish a separate fee for Link itself.
Does using Agentcard require identity verification?
Issuing requires identity verification before the first card, including government ID and a face scan, with a supported Sumsub import available. An existing-card payment through Vault does not use Issuing KYC and does not require funding an issuing balance.
Is there protection if an agent makes a mistake?
Agentcard and Sure announced protection for eligible Vault purchases with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms per the Sure announcement. Spending controls limit authorization before purchase; protection addresses an eligible mistake after purchase. The two are different mechanisms.
Agentcard is built for the job Stripe Link was never designed for: letting your agents pay, with consent and hard limits, at any merchant. Talk to the Agentcard team to scope the integration for your product.
