What Is Stripe's Link Wallet for Agents and Issuing for Agents?

What Is Stripe's Link Wallet for Agents?

Stripe's Link wallet for agents is a consumer product launched April 29, 2026 that lets people authorize AI agents to make purchases through their Link wallet via a standard OAuth flow. After consumer approval in Link's web, iOS, or Android app, Link returns a one-time-use card or Shared Payment Token to the agent. Stripe Blog

• Consumer-controlled access: Agents request access through a standard OAuth flow, and the consumer can revoke access or manage connected agents directly from Link.
• Per-request approval today: Every spend request currently requires explicit consumer approval in Link before the credential is shared with the agent, with planned support for spending limits and unattended agent action thresholds.
• Two credential types: Agents can receive either a one-time-use virtual card or a Shared Payment Token, with stablecoins and additional payment methods announced as coming soon.
• 200 million+ consumer reach: Link's wallet for agents removes the need for developers to build wallet infrastructure from scratch and gives them access to Link's customer base of more than 200 million consumers.

For developers building consumer-facing agents like personal assistants or shopping agents, Link removes wallet infrastructure as a build requirement and provides a consumer-recognizable approval surface that already exists on hundreds of millions of devices. Dan Hill, Stripe's Link Consumer PM, frames the launch as closing the gap between capable agents and the payment options consumers use today.

What Is Stripe Issuing for Agents?

Stripe Issuing for agents is the developer API that powers Link's wallet for agents and is also available directly to any business. Launched April 29, 2026, it provides single-use virtual cards, fund storage, spending controls, real-time authorization decisioning via webhooks, and advanced fraud signals through the same primitives Stripe uses internally for Link. Stripe Issuing for Agents Docs

Capability	What Stripe Provides
Single-use cards	Virtual cards scoped to a single task or session, automatically invalidated after use
Real-time authorizations	Approve or decline every transaction via webhook, with a 2 second default response window before Stripe falls back to the card's default rules
Spend controls	Limits on amount, frequency, and merchant category, set at the card or cardholder level and updatable at any time
Transaction visibility	Track every transaction including captures, refunds, partial captures, over-captures, and force captures
Advanced fraud signals	ML-generated risk scores on every authorization, including fraud risk, merchant dispute risk, and card testing detections

Two access paths are available at launch. Cards for your own business can be applied for directly in the Stripe Dashboard, giving each agent its own virtual card with per-agent spend limits. Cards for your platform requires contacting Stripe and is intended for fintech, SaaS, and marketplace platforms that want to issue cards on behalf of their own users. Stripe Issuing for Agents Docs

How the Spend Request Flow Works

The end-to-end flow uses OAuth for agent authorization, an explicit consumer approval step in Link, and a scoped credential return. The flow is the same whether the agent ultimately uses a one-time-use card or a Shared Payment Token. Stripe Blog

• Step 1, OAuth grant: The consumer grants the agent access to their Link wallet via a standard OAuth flow.
• Step 2, spend request: The agent creates a spend request, providing transaction context including merchant name, merchant URL, amount, currency, and a human-readable purpose for the purchase.
• Step 3, consumer approval: The consumer receives a notification and reviews the spend request in Link's web, iOS, or Android app.
• Step 4, credential return: After approval, Link returns a one-time-use card or SPT to the agent, scoped with controls like amount, currency, and merchant.
• Step 5, settlement and audit: The agent completes the purchase using the scoped credential, and the consumer can track agent spending and manage connected agents directly in Link.

Stripe published a sample CLI invocation showing how an agent constructs a spend request through the Link wallet API, including the merchant context that the consumer sees during approval:

link-cli spend-request create \
  payment-method-id csmrpd_12345 \
  merchant-name "Powdur" \
  merchant-url "https://powdur.com" \
  amount 3500 \
  context "Purchasing the Powdur Glow Renewal Vitamin C Serum as a gift for $35." \
  request-approval

The merchant context field is what the consumer sees in their Link approval notification. It is the agent's opportunity to communicate intent, item details, and rationale to the human authorizing the purchase. Stripe explicitly notes that today each request requires the person's review before the credential is shared, and that future iterations will let people set spending limits and choose when agents can act without additional approval.

What Are Shared Payment Tokens (SPTs)?

Shared Payment Tokens (SPTs) are Stripe's machine-native payment credential for agent-to-merchant transactions, originally launched in 2025 and significantly expanded at Stripe Sessions 2026 with support for additional payment methods including network tokens (Mastercard Agent Pay, Visa Intelligent Commerce) and BNPL providers like Affirm and Klarna. Stripe Blog

• Machine-native design: SPTs are intended for direct agent-to-merchant flows, not card swipe or e-commerce checkout, and are part of Stripe's broader push into machine payments protocols.
• Backed by existing wallet credentials: Today SPTs draw on the cards and bank accounts already in a consumer's Link wallet, with stablecoins and additional payment methods announced as coming soon.
• Scoped at issuance: Each SPT carries scope controls including amount, currency, and merchant, applied before the token reaches the agent.
• Stripe ecosystem alignment: SPTs are the credential type used in the Machine Payments Protocol that Stripe and Tempo launched on March 18, 2026 alongside Tempo's mainnet, and were extended at Sessions 2026 to support network tokens and BNPL. Stripe Blog

SPTs are positioned as the foundation for Stripe's broader machine payments roadmap, alongside the Machine Payments Protocol (MPP) Stripe and Tempo launched on March 18, 2026 and Stripe's endorsement of Google's Universal Commerce Protocol for AI Mode and the Gemini app. As more merchants adopt machine payments, SPTs are designed to displace card credentials in agent flows.

One-Time-Use Cards versus Shared Payment Tokens

Both credential types are issued through the same Link wallet for agents flow and the same Issuing for agents primitives, but they are designed for different transaction contexts. The choice depends on how the agent intends to transact and what the merchant supports.

Attribute	One-Time-Use Card	Shared Payment Token (SPT)
Settlement rail	Card networks (Visa, Mastercard, etc.)	Machine payments flows (MPP and others)
Merchant compatibility	Any merchant accepting the underlying card brand	Merchants integrated with machine payments protocols
Scope controls at issuance	Amount, currency, merchant, lifecycle (cancel after one charge)	Amount, currency, merchant
Underlying funding	Funds in the connected wallet	Cards and bank accounts in Link today; stablecoins coming
Best fit	Agents transacting with merchants that have not yet adopted machine payments	Agents transacting with machine-payment-enabled merchants and protocol-native flows

The practical implication for developers is that Link's wallet for agents abstracts this choice. The agent does not need to know in advance whether to request a card or an SPT, because Link can return whichever credential type fits the merchant context for the spend request. Over time, as more merchants adopt machine payments protocols, SPTs are positioned to become the dominant credential for agent-mediated transactions.

Use Cases for Issuing for Agents

Stripe's launch post lists four explicit use cases for Issuing for agents, each targeting a different category of business that wants to embed agent-issued cards into its product. Stripe Blog

• Developers automating their own business spend: Use agents to create programmatic workflows and recurring purchases, replacing manual procurement or expense reimbursement steps with autonomous agent execution.
• Fintechs embedding agent-issued cards: Embed agent cards directly into expense management or treasury products to control and reconcile spend in real time, with the agent handling categorization, approvals, and posting.
• Vertical SaaS platforms issuing cards to SMB customers: Issue agent cards to small business customers under the platform's own brand, letting agents automate spend categories like supplier payments, advertising, or subscriptions.
• Marketplaces issuing cards to sellers: Issue cards to marketplace sellers so their agents can automate supplier payments, logistics, and fulfillment purchases without seller intervention.

The docs site adds operational patterns that apply across these use cases. Real-time authorization webhooks let businesses approve or decline every transaction based on signals like business name match, amount confirmation, velocity, and fraud risk score. Stripe documents a 2 second default response window for the webhook, after which the card's default rules take over. Settlement typically completes within 1 to 2 days of the original authorization. Stripe Issuing for Agents Docs

Where Stripe Sits Relative to Other Agentic Commerce Protocols

Stripe's Link wallet for agents and Issuing for agents sit a layer above the network-side agentic commerce frameworks announced by Amex, Visa, and Mastercard, while integrating with the open protocols Stripe co-developed (Agentic Commerce Protocol with OpenAI, Machine Payments Protocol with Tempo) and the protocols Stripe endorses (Google's Universal Commerce Protocol).

• Network frameworks (Amex ACE, Visa ICC, Mastercard Verifiable Intent): These define how a specific card network authenticates agents, verifies purchase intent, and issues payment credentials within its own network. See the Amex ACE Developer Kit analysis, the Visa Intelligent Commerce Connect analysis, and the Mastercard Verifiable Intent analysis for full breakdowns.
• Stripe Link wallet and Issuing for agents: Sits a layer above the networks, working across cards, bank accounts, and SPTs. Stripe is also a payments partner on Amex ACE alongside Adyen, Fiserv, Forter, Global Payments, and PayPal, meaning Amex card credentials issued through ACE can flow through Stripe Issuing for agents in production.
• Agentic Commerce Protocol (ACP): Open standard Stripe co-developed with OpenAI (with Meta as a contributor) for agent-to-merchant transactions, currently powering Instant Checkout in ChatGPT and the Meta integration in the Agentic Commerce Suite. See the UCP versus ACP comparison. Stripe Newsroom
• Universal Commerce Protocol (UCP): Google's open standard for agent checkout, co-developed with Shopify, Etsy, Wayfair, Target, and Walmart. Stripe is an endorser and joined the UCP Tech Council on April 24, 2026, but did not co-develop the protocol. See the UCP implementation guide.
• Machine Payments Protocol (MPP): The Stripe-and-Tempo open standard for agent-native microtransactions and recurring payments, with SPTs as the credential type. Launched March 18, 2026 alongside Tempo's mainnet, not at Sessions 2026 (though featured heavily there). Stripe Blog

The strategic position is clear. Network frameworks like ACE and ICC are about who is allowed to issue a credential and on what trust basis. UCP and MPP are about how agents and merchants exchange a transaction. Link wallet for agents and Issuing for agents are about where the credential lives, who controls it, and how it is scoped at the moment of use. The three layers are complementary rather than competitive, which is why Stripe is simultaneously building its own agent issuing stack and partnering across every major network framework.

Where This Sits in the Sessions 2026 Picture

Stripe Sessions 2026 took place on April 29, 2026 in San Francisco. According to Will Gaybrick, the company shared 288 new products and features with more than 9,000 business leaders and builders at the conference, organized around three strategic pillars: making Stripe more programmable, protecting and propelling business via the Stripe network, and building economic infrastructure for AI. Everything We Announced at Sessions 2026

Patrick Collison, Stripe's CEO and cofounder, framed the AI thesis directly in the Sessions keynote. AI is the biggest platform shift for the economy since the internet, and in the not-too-distant future agents will account for most transactions online. Will Gaybrick added the operating mantra for Stripe's agent-facing roadmap: if AI can solve Nobel level physics problems but cannot buy a domain, something has gone wrong, and the goal is to empower agents. Stripe Newsroom

• Agentic Commerce Suite expansion: Now supports Google AI Mode and the Gemini app via the Universal Commerce Protocol, plus a Meta partnership for native checkout inside Facebook ads.
• Existing Agentic Commerce Suite users: Kate Spade, Best Buy, and Coach were named in the Sessions newsroom post, with new and coming partners including Quince, Fanatics, JD Sports, Wix, BigCommerce, and WooCommerce.
• Machine Payments Protocol (MPP): Featured at Sessions 2026 but originally launched on March 18, 2026 alongside Tempo's mainnet. Co-authored by Stripe and Tempo, MPP supports agent microtransactions and recurring payments using SPTs as the credential type.
• Link agent wallet metrics: Stripe cited 250 million Link users globally in the newsroom post and more than 200 million consumers in the Link wallet for agents launch post.
• Radar upgrades for agent fraud: The biggest-ever upgrades to Radar were announced at Sessions, including detections for token theft, sign-up fraud, and free trial abuse, addressing fraud surfaces unique to agent-mediated transactions.

The Link wallet for agents and Issuing for agents launches are deliberately positioned as the consumer-facing and developer-facing entry points into Stripe's broader agent strategy. The Agentic Commerce Suite expansion gives merchants the ability to be sold from inside AI surfaces. UCP defines how the cart moves between agent and merchant. MPP and SPTs define how the value moves on-chain or through machine-native rails. Link wallet for agents and Issuing for agents are the credential and trust layer that consumers and businesses interact with directly.

Availability and What Is Coming Next

Both Link's wallet for agents and Stripe Issuing for agents are available at launch. Link's wallet for agents is generally available with a getting started page at link.com/agents, and Issuing for agents has full developer documentation at docs.stripe.com/issuing/agents. Cards for your own business can be applied for in the Stripe Dashboard, and Cards for your platform requires contacting Stripe. Stripe Issuing for Agents Docs

Stripe explicitly called out several capabilities as coming soon, all of which expand the surface area for agent-mediated commerce on Link.

• Stablecoin support in Link wallet: Stripe says stablecoins and additional payment methods are coming soon as backing for SPTs and as direct payment options for agents.
• Spending limits and unattended action thresholds: Stripe is planning to expand spending controls so consumers can set limits and choose when agents are allowed to act without additional approval.
• Broader payment method coverage: The launch post says Link will continue to handle the abstraction across payment options the agent might need.
• Sessions 2026 roadmap items: The Sessions recap announced a public roadmap with hundreds of detailed entries through Q1 2027 across Payments, Revenue, Money Management, and beyond, including Agent Guardrails (agent identity assignment, scope rule enforcement, approval flows), Issuing for agents single-use virtual cards extensions, and Stripe Console for plain-language business queries inside the Dashboard.

For developers building consumer-facing agents today, the immediate path is Link's wallet for agents. For platforms and businesses building their own agent wallet products, the path is Stripe Issuing for agents directly. Both paths share the same underlying infrastructure, which means an integration choice today does not lock a developer out of the other path tomorrow.

What This Means for the Agentic Commerce Stack

Stripe's Link wallet for agents and Issuing for agents fill the wallet and credential gap that network-side frameworks like Amex ACE and Visa Intelligent Commerce Connect could not fill alone. They give consumers a recognizable approval surface and give developers one integration path to reach 200 million Link consumers across cards, bank accounts, and SPTs.

• Network integration is necessary but no longer sufficient: Brands need to be reachable through the Stripe wallet and issuing layer that increasingly mediates agent-to-merchant flows, not just integrated with Amex ACE, Visa ICC, or Mastercard Verifiable Intent.
• Merchant readiness for SPTs and MPP is a different integration: Accepting Shared Payment Tokens and Machine Payments Protocol flows is a separate engineering investment from card-not-present commerce, and the merchants that adopt those rails first will be the ones agents transact with first.
• Consumer-facing agents have a default wallet now: Personal assistants, shopping agents, and finance agents no longer need to build wallet infrastructure from scratch and can integrate with Link to reach 200 million consumers immediately.

This shifts the build-versus-buy question for consumer-facing agents. Building a wallet from scratch was the default; integrating with Link is now the default. The A.G.E.N.T.I.C. Framework maps the full lifecycle across seven phases, from AI visibility audit through agent-completed transactions, including the wallet and credential layer Stripe just shipped.