Stripe Link Agent Wallet and Machine Payments Protocol Explained
Prefer to watch? Watch on YouTube · Subscribe for new builds · Read the transcript
In this video I break down the agent commerce pieces Stripe announced at Sessions 2026: Link Agent Wallet, the Machine Payments Protocol, and Stripe Projects. If you build AI agents, or you run a product that agents might pay for one day, this covers what shipped, why it matters, and what you can build with it. I recorded this in April 2026. Tools like this change fast, so check Stripe's current docs before you build anything.
What I cover in this video
- 0:00: Why agent commerce was stuck at the pay button
- 2:17: Stripe's 288 launches and the three pieces that matter for agents
- 4:35: How Link Agent Wallet uses one-time-use cards
- 5:21: The Machine Payments Protocol, co-authored with Tempo
- 7:40: Stablecoins, fiat, and shared payment tokens
- 8:25: Stripe Projects goes generally available
- 9:11: What you can build with this
- 13:00: Why this beats crypto-only solutions
Why agents couldn't pay for things
Over the last year, most of the talk about AI agents has been about what they can read and what they can do: tool use, browser use, computer use, MCP servers. The part nobody had solved cleanly was what agents can buy. An agent can find a flight, summarize a booking page, and fill out a form, but once it hits the pay button you're stuck. There were workarounds, but they were a pain to build, and you don't want to hand your agent your real card details and hope it behaves.
Merchants had a problem too. They had no clean way to tell whether a human or an agent was paying them. That's the gap Stripe went after. Out of the 288 launches at Stripe Sessions 2026, I focus on three: Link Agent Wallet, the Machine Payments Protocol, and Stripe Projects.
Link Agent Wallet: one-time cards for each task
If you've checked out on Shopify, DoorDash, or another big Stripe-powered site, you've probably seen Link. It's Stripe's consumer wallet: you save your card once and tap to pay after that. It has over 250 million users worldwide. Stripe has now extended Link so you can let AI agents spend on your behalf.
The design is the part I like most. Here's the flow:
- You authorize your agent.
- The agent decides it needs to buy something.
- Stripe issues a one-time-use card for that specific task.
- You get a notification and approve the payment.
- The agent completes the purchase, and that card can't be used again.
The agent never sees your real card details, your funding source, or your bank info. All it touches is a tokenized card that works for one transaction. So if your agent goes off the rails, gets prompt injected, or makes a bad call, the damage is limited to one task and one approval. That's the pattern people have been asking for, and it now runs on the largest consumer wallet on the internet.
Machine Payments Protocol (MPP)
I think MPP matters more in the long run, and it's the piece builders will feel most. Stripe co-authored it with a company called Tempo. It's an open spec, not a closed Stripe-only product. It defines how agents and services coordinate payments programmatically. Think of it the way HTTP or OAuth is a spec.
What it supports:
- Microtransactions
- Recurring payments
- Payment per API call, per task, or per outcome
Businesses can accept MPP in a few lines of code through the Payment Intents API, which most Stripe shops already have set up. You don't need to rebuild your billing stack. Add MPP support, and agents can pay you the same way humans do, just programmatically.
Stablecoins, cards, and shared payment tokens
MPP doesn't pick a side on the payment rail. It supports stablecoins like USDC, and it also supports regular fiat cards and buy now, pay later. It does this through shared payment tokens (SPTs), which hide the underlying funding source. The agent doesn't need to know whether it's using a Visa card, a stablecoin, or a BNPL plan. It sends the payment intent and the protocol handles the rest. Most earlier attempts at agent commerce were crypto-only, and most merchants don't accept stablecoins. They accept cards. That's why I think MPP has a real chance of becoming the standard.
Stripe Projects and what you can build
Stripe Projects is more about developer experience. It lets you set up Stripe services from the CLI instead of clicking through the dashboard to create accounts, set up products, or configure webhooks. Since you can script it, agents can run it too. An agent could spin up its own Stripe environment and configure payment routes without a human touching the dashboard. Stripe Projects is now generally available, so there's no waitlist anymore.
Here are the use cases I walk through:
- Travel agent: "Book me a flight to Austin next weekend under 400 bucks." The agent finds the flight, triggers the payment intent, you approve it, and the confirmation shows up in your inbox. It runs on its own, but you still sign off when money moves.
- Self-refilling API credits: When an agent's OpenAI, Anthropic, or search API balance runs low, it triggers a small payment and tops up. No more waking up to a dead workflow.
- Subscription manager: An agent can subscribe for you and, more importantly, unsubscribe. It can audit your spending, renegotiate, and move you off plans you don't use, kind of like a personal CFO.
- Agent-friendly services: If you run an API or SaaS, ask how to make your service the easiest one for an agent to pay. The companies that adopted Stripe early because it was developer-friendly ended up dominating e-commerce. I think the same will happen with MPP and agent commerce.
Why this beats crypto-only agent payments
Crypto agent payments already exist. You can pay in stablecoins and run payments on-chain. The problem is that almost no real merchants accept them. Your agent might pay another agent on-chain, but as soon as it tries to buy from a real business, you need fiat rails again. MPP supports both, so you get crypto's programmatic payments and the reach of traditional payments in one protocol.
Trust is the other piece. People know the Link button and already have a card saved. Compare that to asking someone to install a wallet, fund it with stablecoins, and connect it to your agent. When your agent pays with Link, your users don't have to learn anything new. They approve a payment like they always have. The only difference is that the agent started it.
My suggestion: give this video and the MPP docs to your agent, whether that's Claude Code or OpenClaw, and ask how to apply it to what you're building. The spec is open, the API examples are clear, and I think you can get a working integration done in an afternoon.
Key takeaways
- Link Agent Wallet gives your agent a one-time-use card for each task you approve, so your real card details never reach the agent.
- The Machine Payments Protocol is an open spec, co-authored by Stripe and Tempo, that covers microtransactions, recurring payments, and pay-per-call or pay-per-outcome pricing.
- Shared payment tokens let MPP work with cards, BNPL, and stablecoins without the agent needing to know which one it's using.
- Stripe Projects is generally available and lets you, or your agent, set up Stripe from the CLI.
- If you run a SaaS or API, start thinking now about what paying you looks like for an agent.
FAQ
What is Stripe Link Agent Wallet?
It extends Stripe's Link wallet so you can authorize an AI agent to spend for you. For each purchase, Stripe issues a one-time-use card. You approve the payment, and the card can't be used again, so the agent never sees your real card details.
What is the Machine Payments Protocol (MPP)?
MPP is an open spec co-authored by Stripe and Tempo for how agents and services coordinate payments programmatically. It supports microtransactions, recurring payments, and payment per API call, task, or outcome. Businesses can accept it in a few lines of code through the Payment Intents API.
Does MPP only work with crypto?
No. MPP supports stablecoins like USDC, and it also supports regular cards and buy now, pay later. Shared payment tokens handle the underlying funding source, so the agent doesn't need to know which one it's using.
What is Stripe Projects?
Stripe Projects lets you set up Stripe services from the CLI instead of the dashboard, which means an agent can do it too. In April 2026 it became generally available, with no waitlist.
Chapters
Transcript
Read the full transcript
0:00Your AI agents can now use Stripe to pay for things. This came out just hours ago from the Stripe convention, and in this video, I'm going to be explaining how this changes how AI agents operate. So, Stripe sessions went down just a few hours ago, and if you build any type of agent, this is one of the things you cannot afford to skip past. Stripe basically shipped agent commerce infrastructure. You know, they gave your AI agents a wallet now. So, they gave them an opportunity to make open payments through a protocol, and they made it so any business can accept agent payments in just a few lines of code. So, basically, the whole missing piece for autonomous agents that can actually
0:45go out and buy things on your behalf, that piece just landed today. And I want to walk you through what they shipped, why it matters, and what you can actually build with this starting today. So, let me set the stage real quick and back up as to what this even means if you're building with AI. You know, if you've been following the agent infrastructure for the last year, you know almost every conversation has been about what agents can read and what agents can do. Tool use, browser use, computer use, MCP servers, all of that, right? But the thing that nobody was really solving in a clean way, anyways, was what agents can actually buy. This is the start of the AI agent economy. You know, your agent can find a flight,
1:31it can summarize a booking page, it can fill out a form, but the moment it gets to a pay button, you have a problem. Yes, there are some workarounds, but they're a pain to build out. You know, you do not want to hand your agent a real credit card, do you? I mean, if you want, but you do not want to give them your full card. You want want to give them your card details. I certainly don't. And you don't want to just hope that they're responsible with it, you know? And on the merchant side, anyways, businesses had to have a clean way to even know what they were being paid by an agent and versus a human. So, they need to know the difference. So, agent commerce has been kind of stuck in this weird awkward middle ground where nobody
2:17even knew it was coming. Nobody had really any idea that this was being shipped until today. Stripe shipped 288 launches at Session 2026. So, that is the headline number, 288. But the part I care about and the part you should really care about if you're building anything with AI agents or anything in the AI agent space is that agent commerce is about to go crazy. There are basically three pieces to this. The first one is called the Link Agent Wallet, and the second one is called Machine Payments Protocol, which they are co-authoring with a company called Tempo. And the third is Stripe Projects. So, this lets you provision Stripe services right from your terminal. Let me walk you through each one because all
3:03three of these actually matter, but the first are two the first two are a huge deal in the whole AI agent space. So, Link Agent, real quick, before we keep going, if you're watching this and you want to actually build with some of these tools, not just watch videos about them, then you're going to want to check out our community down below, Shipping School. We have a full Claude code course, a full open Claude course, and four live bootcamps every single week where we actually help you get set up from scratch. Like actually set this thing up, not just watch a tutorial and figure it out by yourself. And we also provide one-on-one coaching, so you could book a call with me, we could share screens, and I can help you get Claude code or open Claude running on your machine. That's it, no fluff. I built this community because watching
3:49YouTube's only gets you so far. We launched it just 3 days ago, and we have over 55 members. You need people around you who are actually building, people who hold you accountable, and coaches who can help you when you get stuck. I'll put the link in the description down below. Get in now before the price goes up. If you have ever checked out on Shopify or DoorDash or any of the bigger Stripe-powered sites, you have probably seen Link. It's Stripe's consumer wallet. Instead of typing in your credit card every time, you put in your card once, and you just tap the button to pay. The wallet now has over 250 million users globally, which is a crazy number when you actually sit with it. You know, that is the most of the active online buyers in the United States and a huge chunk of the rest of the world. And what
4:35they did today is they extended Link to authorize AI agents to spend on your behalf. So, now your agent can pay using Link, but the way they built it is the part that I want to highlight because it is actually the really thoughtful way they built it. The way it works, you authorize your agent, the agent decides it needs to make a purchase, Stripe issues a one-time use card for that specific task, you get a notification, you approve the payment, the agent then completes the purchase, and that card cannot be used again. Pretty safe. Your real card details, the underlying funding source, your actual bank info, that never gets exposed to the agent. The agent is just touching a tokenized one-shot card that only works for that
5:21one transaction. So, even if your agent goes off the rails, even if it gets prompt injected, even if it makes a bad decision, the blast radius for the one task and one approval, you know, it's much safer. So, that is the exact design and the pattern people have been asking for. It is what you would have built yourself if you were trying to make this safe. And Stripe just shipped it for you to the largest consumer wallet on the internet. So, I'm going to talk about the Machine Payments Protocol because this is the piece that I think is actually bigger for the long-term aspect of all this. The Link Wallet thing is pretty huge for consumer use cases, but the MPP is the piece that builders are actually going to really feel. So, Stripe co-authored this with Tempo, and
6:07what is an open spec is not a closed Stripe-only product. It is a spec for how agents and services should coordinate payments from a programmatic. So, if you think of it like the way an HTTP is a spec or the one way an OAuth is a spec, right? Or MPP, like MPP is trying to be that for basically a machine, to be able to take machine payments. So, similar to HTTP, similar to OAuth, it supports microtransactions, which is great, which is a thing that crypto people have been promising for 10 years and never really delivered in any type of usable form, but it supports recurring payments as well. It supports payment per API call, payment per task, payment per outcome, and the businesses on the receiving end can accept MPP in
6:53few lines of code right through their payment intense API, which most Stripe shops already have wired up. So, an API service, a content site, anything that wants to charge for value, you do not need to rebuild your building stack. So, if you add MPP support and now agents can pay you the same way humans do, they just do it programmatically. So, if you're building a web web page or a landing page or any type of product on the internet, you might want to start integrating this right now because now agents can now buy things, and that is insane. So, the other thing that is really clever about the MPP story is that they did not pick a side on the payment rail. The protocol supports stablecoins. So, if you want to pay with USDC or whatever, you can. It also
7:40supports regular fiat cards, buy now, pay later, the whole stack. And they do this through something called shared payment tokens or SPTs. Basically, abstract the underlying funding so the agent does not need to know if it's using a Visa card or a stablecoin or a BNPL plan. It just tells the protocol, here's the payment intend, and the rail configures all of it itself. So, this matters a lot because most every agent that is in commerce, the attempt before was basically crypto only, and you know, I'm not anti-crypto, but if you're trying to build agents that buy real things from real merchants, the merchants do not all accept stablecoins. They accept cards. So, a payment protocol that only
8:25works with one rail was never going to win in a real economy. MPP works with everything, which is why I think it has a real shot at becoming the actual standard. The third piece is Stripe Projects. This is more of a developer experience thing, but it is worth mentioning because it shows where Stripe is heading. Stripe Projects lets you provision Stripe services programmatically from the CLI. So, instead of clicking through the dashboard to create a new account or set up products or configure webhooks, all of that, you can now just script it, which means agents can do it, too. Which means an agent can spin up its own Stripe environment, configure its own payment routes, and start moving money all without a human touching the dashboard. Stripe Projects is now
9:11generally available to everyone, which is a huge shift from being on a waitlist. So, now let's talk about what you can actually build with this because this is where it gets more fun. We're all builders on the channel. We want to know, how can we integrate and use this? So, the first obvious one is the travel agent. You could tell your agent, book me a flight, let's say to Austin next weekend under 400 bucks, and it actually goes and books the flight. Right now, if you tried to build that with Claude or any other agent, you hit a wall at the checkout. With Link Agent Wallet, that wall comes down. The agent finds the flight, it triggers the payment intend, you get a notification, you approve it, it pays it, and then you have a confirmation in your inbox. End-to-end autonomous, but with a human checkpoint
9:58at the actual money moment. That is the right decision, and I love that flow. Another one that I'm genuinely excited about is the agent that buys its own API credits. So, anybody who has run an agent in production knows the pain of waking up to a dead workflow because some upstream service ran out of credits. With MPP, your agent can just refill its own OpenAI credits or its own Anthropic credits, its own search API, or whatever. When the balance gets low, it just tops up. It checks the balance, it triggers a small payment, and then it tops up your API credits. That is hours of babysitting that just disappeared. So, there is the subscription manager use case as well. So, think about how much monthly spend goes into little $10
10:44subscriptions you forget about. I go through my whole list every month, and I find stuff that I'm so glad I looked for it that I would have been paying months in advance, just wasting money. Basically, an agent that uses MPP can now subscribe to things on your behalf, but more importantly, it can unsubscribe. It can audit your spend, it can renegotiate as well, it can move you off plans you're not using. Your agent becomes basically a personable CFO, which is pretty cool when you think about this whole thing. I mean, people That's why everything is a subscription now. They know that the consumer's going to forget that they have that subscription, and they can just keep billing that person. That's why everything is a subscription model. I mean, think about how much more managed these agents can be now, and how much more money you could save just from a
11:30personal level. If you're struggling to keep up with content, what I'm about to save you about 40 days worth of work. I built [music] something called Content Machine. It's 10 AI agents that run on the Open Claw orchestration, and they handle everything. Scripts, [music] thumbnails, X posts, blogs, outreach, clips, newsletters, [music] all of it. So, I went from 1,000 subscribers to 4,000 subscribers on YouTube in 7 days using this exact system. Every single morning, I wake [music] up, and the content's already done. I spend maybe 15, 20 minutes reviewing and approving them, and I move on with my day. It works for any niche, fitness, finance, real estate, marketing, whatever you're building, and it is 100% completely
12:15customizable to your use case. So, you get the mission control dashboard, all of the cron jobs, everything I've built over the last 40 days helping me gain more and more people to subscribe and join the community. So, you plug in your own thing, and it molds it to you, it learns how you talk, and it [music] writes so it doesn't sound like AI slop. $97 one time, it's not a subscription, I'll put the link down below, and you'll thank me later. So, for builders specifically, I think the biggest near-term opportunity is agent-friendly services. Like, if you run any kind of API or SaaS, right, you should be looking at MPP and asking, "How do I make my service the easiest for one agent to pay?" Because agents are coming, the volume is going to be real,
13:00and the services that are built MPP native from day one are going to capture a huge chunk of that flow. That is the same playbook as early days of Stripe itself. The companies that adopted Stripe early because it was developer-friendly ended up dominating e-commerce. The companies that adopt MPP early because it is agent-friendly are going to dominate the agent commerce. Now, I want to talk about why this beats the crypto-only solutions for just a second because I know someone's going to bring it up in the comments. Crypto agent payments have been a thing for a while already. You can pay an agent in stablecoins. You can run on-chain payments. All of that really does exist now, but the problem has always been that almost no real merchants accept it.
13:45Your agent might be able to pay another agent on-chain, but the moment it tries to buy a real product or a service from a real business, you are back to needing fiat rails. Stripe just collapsed that entire gap. They support stablecoins for the people who want that, and they also support cards and else. So, you get the agent-native programmatically of crypto, right, in the real world reach of traditional payments in one protocol. So, that is a really hard combination to beat. The other thing that's worth saying is the trust layer. Stripe is a trusted brand. If you put a link button on your checkout, your customers know what it is. They have used it before. They have a card on file. There is no friction. Compare that
14:30to asking somebody to install a wallet, fund it with stablecoins, and connect it to your agent. Who's going to do that? The conversion difference is massive. So, when you ship an agent that pays with link, your users do not have to learn anything new. They just approve a payment the same way they've always had, except now their agent is the one that's initiating. So, what should you do this information like now, like today? First of all, take the link to this video and give it to your agent and say, "How can we apply what this guy is talking about?" The next thing is if you're building any kind of agent that touches commerce, go read the MPP docs. I'll put them in the link down below. The link, you got to check it out. Bookmark it. Give the link to your agent as well. The spec is open, the API examples are clear, and you can have a working
15:17integration in an afternoon. The second thing is if you run a SaaS or any kind of paid service, start thinking about how an agent would pay you and what the experience should feel like. Because in 12 months, a meaningful slice of your traffic is going to be agents. Third, if you are in the community shipping school, this is exactly the kind of thing we're going to be breaking down in the community over the next few months because there are going to be a lot of side projects that pop out of this announcement, and the early movers are going to win. So, Stripe basically just gave agents a wallet, they gave us a protocol, and they made it easy for businesses to accept agent money. They did this with 250 million existing link users in one day, which is a distribution head start nobody else has.
16:02And they did it with a spec that does not lock you into any one payment rail. That is a huge deal. I don't think people even know what's coming. I think looking back 12 months from now, today is going to be the day where we point to where agent commerce actually became real. Essentially, if you were to just sum all this up, a new economy is starting, and it doesn't involve humans. It involves billions of AI agents that are transacting. And just ask to you, do you want a piece of the pie? Give this link to the agent, give this video to the your agent, and say, "Let's implement this today." Especially if you already have a product. You know, I want to hear from you. Drop a comment if you're already building something that needs agent payments. I want to hear what you're working on. If this is the first agent commerce video you've seen on the channel, hit the subscribe button
16:48because we're going to be covering this stuff heavily as it develops. And if you need to be in a community that ships stuff every day, click the link down below, join us in shipping school. We do nine live calls a week covering these exact topics from Hermes, Open Claw, Claude code, building landing pages, building back ends, installing local LLMs as well. Um, we also have unlimited one-on-one calls. So, if you want to join the group, but you don't like the group setting, we have unlimited one-on-one calls. So, you could book a million calls if you'd like, and we'll help you take the next step in your AI journey. So, amazing time to be alive, right? It is just such a crazy time to be alive if you're building with AI. So, hit subscribe, we'll see you in the next one. Have a blessed day. Bye.
Ready to start building with AI?
Join the Shipping Skool community free. Paid members get live bootcamp calls every week and weekly-updated courses.
Join Shipping SkoolKeep reading
Context Overflow Explained: Shared Memory for AI Agents
Context Overflow is a Q&A knowledge-sharing layer for AI agents. Agents search past solutions before starting a task, ask questions when they get stuck, and share what they figure out, so the next session doesn't start from scratch. I also cover OpenClaw's memory wiki and active memory, plus GBrain.
NemoClaw Explained: Nvidia's Secure Runtime for OpenClaw Agents
NemoClaw is Nvidia's version of OpenClaw with security built in. It adds Nemotron models and OpenShell, a secure runtime with YAML sandboxing policies, a privacy router that strips PII, and least privilege access. It was in alpha in March 2026, and your OpenClaw skills and cron jobs carry over.
Harness² Explained: Google's Self-Improving AI Agent Harness
Harness² from Google Cloud AI Research and Northwestern improves AI agents by rewriting the prompts, memory, skills, tools and plugins around a model. The weights stay the same. In the researchers' tests, GLM-5 gained 11.5 points on an office and coding benchmark, and you can run a manual version of the same loop in Claude Code.
