AI agents have been browsing, drafting, and recommending for over a year, but the moment they tried to buy something they hit a wall: no payment method, no checkout flow, no way to prove authorization. Stripe just knocked that wall down. At its Sessions 2026 keynote, the company launched Link’s wallet for agents, built on a new product called Stripe Issuing for agents. The pitch is simple — give your agent programmatic access to Link, and it can transact on your behalf without ever touching your raw card or bank credentials. For product teams that have been waiting to ship agentic checkout, the missing primitive just arrived.
How Link’s Wallet for Agents Actually Moves Money
The mechanics are tighter than most agent demos this year. According to Stripe, a consumer grants an agent access to their Link wallet through a standard OAuth flow. From there, the agent creates a spend request and receives either a one-time-use card or a Shared Payment Token (SPT), backed by the cards and bank accounts already in the user’s Link wallet. Each credential can be scoped with controls like amount, currency, and merchant, and Stripe says support for agentic tokens, stablecoins, and other payment types is coming soon.
Agents have lived in a no-man’s-land between “can browse” and “can pay,” and the bridge most builders rolled themselves was insecure. Handing an agent a raw PAN is a non-starter for any team that has read a PCI checklist. A scoped, single-use credential issued at the moment of purchase is the cleanest way to keep the human in control while letting the agent finish the job.
Imagine you’re building a shopping assistant that recommends apparel — Stripe’s own example. The consumer connects their Link wallet, the agent assembles a cart, and Link fires a notification to the user’s iOS or Android app for approval. Only after the person taps approve does the SPT or virtual card flow back to the agent to complete the transaction. The author’s prediction: within twelve months, “connect your Link wallet” will be a standard onboarding step in consumer agent products, the same way “sign in with Google” became table stakes a decade ago.
Why Shared Payment Tokens Are the Real Story
The headline is the wallet, but the more interesting building block is the Shared Payment Token. Per Stripe’s documentation, an SPT is a payment credential designed for agent-to-merchant flows where the agent isn’t a human checkout session and isn’t a card-present transaction either. It is a third category, and that category previously didn’t exist in any meaningful form for general-purpose merchants.
This matters because the alternative — issuing a virtual card per transaction — works, but it inherits all the friction of card rails: interchange, decline rates, 3DS step-ups, chargebacks. An SPT lets Stripe and willing merchants negotiate a cleaner machine-native path. Combined with Link’s stated reach of more than 200 million consumers, the network effect compounds fast. Agents that integrate get instant distribution; merchants that accept SPTs get cleaner authorization data than they’d ever get from a screen-scraping bot.
If you’re a fintech or SaaS team weighing whether to wait on the broader machine payments protocol standards or ship now, this announcement collapses the dilemma. You can ship today on Link’s rails and adopt other protocols as they mature. The author’s take: SPTs will eat a meaningful slice of card-not-present volume in agent flows by the end of 2027, and any merchant still relying on agents to type fake cardholder names into a checkout form will be looking at a noticeably higher fraud rate than competitors who accept the new token.
Stripe Issuing for Agents Is the Real Platform Play
Link’s wallet is the consumer-facing skin. Underneath, Stripe Issuing for agents exposes the full Issuing API to developers who want to build their own agentic wallets and cards. Stripe lists four use cases explicitly: developers automating their own business spend, fintech providers embedding agent-issued cards for expense management, vertical SaaS platforms issuing agent cards to SMB customers under their own brand, and marketplaces issuing cards to sellers so agents can automate supplier and fulfillment payments.
Competing payment providers should be nervous. Stripe is offering the primitives so other companies build their own competing wallets on top of Stripe rails. Single-use virtual cards, fund storage, spending controls, transaction monitoring, and fraud tools are all exposed. For a vertical SaaS team — say, a procurement platform for restaurants — this means you can issue branded agent cards to your customers without standing up an issuing program from scratch. That kind of embedded financial workflow used to take a year and a sponsor bank conversation. Now it’s an API integration.
If you’re a marketplace founder, picture this: your seller’s agent automatically reorders inventory from a supplier, books freight, and pays the warehouse — all on a card you issued, scoped per supplier, with real-time authorization controls. That’s the product Stripe wants you to build on its rails. The author’s prediction: at least one major vertical SaaS platform will announce an agent-card product on Stripe Issuing within six months, and the announcement will be framed as a margin story, not a payments story.
What Product Teams Should Do This Quarter
For any team integrating checkout, the question is whether to wait or move. Waiting is tempting because the standards aren’t fully settled — stablecoin support and broader agentic token compatibility are still on Stripe’s roadmap, not in production. But the cost of waiting is that competitors who ship agent checkout first will accumulate the behavioral data that makes their fraud models, approval flows, and spending-limit defaults better than yours.
The pragmatic play is to scope a small surface area now. Pick one use case — refunds, reorders, subscription top-ups — and run it through Link’s wallet for agents or a custom Issuing integration. Treat it as a learning project, not a flagship launch. Teams that need to wire this into existing billing systems and customer dashboards will find the heavy lift is less in the issuing call itself and more in the API plumbing and reconciliation work around it.
FAQ
Q: What is a Shared Payment Token (SPT)? A: According to Stripe’s documentation, an SPT is a payment credential designed for agentic commerce. The agent presents the token to a merchant to complete a purchase, but never sees the underlying card or bank account. Controls like amount, currency, and merchant can be scoped onto each token before it is issued.
Q: Does the agent get my actual card number? A: No. Stripe explicitly states the agent never gets access to raw payment credentials. The agent receives either a one-time-use card or an SPT, both of which are derived from the cards and bank accounts in your Link wallet but cannot be reused beyond the approved transaction.
Q: Can agents spend without my approval? A: Not today. Stripe says each spend request currently requires the person’s review before the credential is shared with the agent. The company has indicated it plans to expand controls so users can set spending limits and choose when agents can act without additional approval, but that is a future capability.
Key Takeaways
- Teams building consumer agents should evaluate Link’s wallet before rolling their own credential vault — the security and distribution math now favors integration over building from scratch.
- Shared Payment Tokens are the primitive worth tracking; merchants that accept them early will have cleaner authorization data than competitors stuck on screen-scraped checkout.
- Vertical SaaS and marketplace founders now have a credible path to issue branded agent cards without standing up an issuing program, which compresses go-to-market timelines for embedded finance products.
- Expect the first wave of agent-card announcements from non-Stripe brands within roughly six months, framed as margin and retention plays rather than payments plays.
- Waiting for the full machine payments protocol ecosystem to mature is no longer free — competitors shipping on Link rails today will accumulate the behavioral and fraud data that compounds into a real moat.