
product @stripe agentic commerce, leading machine payments. also, @justinkan's youtube/tiktok
Joined December 2017
- Tweets4.4K
- Following997
- Followers9.9K
- Likes8.5K
Jen retweeted
Stripe spent 15 years perfecting checkout for humans. Now the team is rebuilding it for AI.
Jennifer Lee ( @BackseatVC ) is a Product Manager @stripe. Her team builds the tools that let AI agents buy things for you.
The problem is trust. Most people don’t want to hand an AI their card number.
So Stripe never gives it one. The agent gets a single-use code that works at one store, for one purchase. Your card number stays hidden.
Companies are already building on it. @thelinqapp recently launched Agent Pay, which lets AI agents pay for things right inside messages.
Most people assume checkout disappears once AI does the shopping. Jen thinks the opposite.
On November 3 at Hello, World!, she’s giving a talk called “Long Live Checkout,” about why checkout is about to matter more, not less.
Link to apply in the comments.
Jen retweeted
1/ Coding agents, like Claude Code and Codex, can now build working machine payment integrations on Stripe in one shot.
With Stripe's Machine Payments SDK, developers can build APIs and services that AI agents pay for with stablecoins, one request at a time.
Jen retweeted
What are tasks, or data to query, do you want for Muse, Grok Bot, Instinct, etc, where you’d be excited to _passively_ pay a penny, 10c, $1, for the task/data to be high quality and low latency?
For me, I’d pay to have perfect places data. I still get recommended closed places.
Jen retweeted
Inside @Stripe's MPP IRL: machine payments, stablecoins, and the future of agent commerce.
Agents are starting to pay for things on their own: API calls, services, each other. Nobody's agreed on how that should work. This panel was three takes on it.
@BackseatVC (Stripe) leads product for Machine Payments — the open standard for how agents pay for things.
@dwr (@tempo) is building stablecoin payment rails, and thinks that's what agent commerce runs on, not cards.
@blauyourmind (Royal) magician turned @a16z Crypto partner turned CTO is exploring programmable money for creators, and why the demand side is barely here yet.
We got into:
• Why HTTP 402, a status code from the early web, is suddenly the backbone of agent payments
• Why Dan thinks a credit card is a private key and why stablecoins are safer for agents
• Where stablecoins actually win first
• Whether you should build for agent payments now or wait
• Why the demand side is "virtually nonexistent" and what that means if you're building
𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒
(00:00) Event Kickoff
JEN LEE — Product Lead, Stripe
(00:44) What the Machine Payments Protocol Is
(01:28) How MPP Works — the HTTP 402 Payment Challenge
(03:25) Adoption So Far: ~30,000 Transactions
(04:04) Building Trust — Shared Tokens & the Link Agent Wallet
(05:56) What the Creator Economy Looks Like When the Audience Is Agents
(07:15) What She Was Certain About at 22 That's Now Wrong
DAN ROMERO — GTM, Tempo
(08:34) Meet Dan
(08:49) Why Stablecoins, and the Genius Act Tailwind
(09:48) "A Credit Card Is Basically a Private Key"
(11:19) Should Every Company Be Thinking About MPP?
(13:03) What to Be Wary Of
(15:15) Where Stablecoins Win — Payouts, Remittances, DoorDash
MICHAEL BLAU — CTO, Royal
(16:36) Meet Michael
(17:13) From Magician to a16z Crypto to CTO
(17:57) Team Over Idea — His a16z Takeaway
(18:26) "The Demand Side Is Virtually Nonexistent"
(19:03) Closing
Jen retweeted
1/ Stripe has signed an agreement to acquire OpenRouter.
OpenRouter will continue to operate as it is: same name, same product, same roadmap, same mission. But now, we will do it faster, and with Stripe's unparalleled excellence and reach.
OpenRouter is joining Stripe: stripe.com/newsroom/news/str….
As anyone who uses it knows, @OpenRouter is a truly delightful developer tool. It is by far the best way to use new models and manage multiple inference providers.
OpenRouter is also playing an increasingly important role: in the future, every business will have to manage both revenue flows and token flows. OpenRouter is the world's leading token marketplace, helping businesses effectively allocate the new currency of intelligence capital. We think that there's a lot to build together.
Jen retweeted
pretty convinced most businesses will want to offer a subset of their service in a pay-per-use style for agents, with path for agent to upgrade to account for better pricing, subscriptions, etc
@stripe can help with accepting agent payments and identity => [email protected]
Jen retweeted
full house at @stripe hq today for our invite only MPP event with @BackseatVC and @brendan_j_ryan running us through demos!
Jen retweeted
filming the next mts exclusive at @stripe hq
the legendary makerspace where the patrick x dwarkesh ep was made
there’ll be a few. can’t wait for these to release
Jen retweeted
Approaching 30k @mpp transactions per day. Machine-to-machine payments are starting to become a thing.
mppscan.com/?d=0
Jen retweeted
I've been enjoying Victoria Whitworth's new work, The Book of Kells: Unlocking the Enigma.
I've actually never seen the Book of Kells in person, somewhat to my embarrassment. I've been doing some reading about the origins of Christianity this year, however, and I figured I should know something about the most famous Irish manuscript. (Perhaps the most famous manuscript, full stop.)
Reading the book, I was struck by how much the contents have suffered over the past ~1200 years (enduring everything from water damage to reckless malfeasance in attempted nineteenth century restoration), and I wondered whether AI could help give a sense for how the work might originally have appeared.
I downloaded the Internet Archive's PDF and asked my friendly neighborhood agent to use gpt-image-2 to render each page the way it imagines it might have originally appeared. Remarkably, this all worked with a single prompt, with the agent spinning up 48 workers, since each page took a minute or two. (I'm sure that someone wiser than me could prompt the model better, ensuring somewhat more historical accuracy in color restoration and so forth. There is no gold leaf in the Book of Kells!) This part of the project went from conception to completion before I'd finished my morning coffee.
I then wanted some easy way to view the results online, so I asked Stripe Projects (projects.dev) to host the result on Vercel. That also worked in basically a single prompt: bookofkells.vercel.app.
I also figured that people might want an easy way to download the full PDF of updated images, but it's a large (~200MB) file, so I decided that I should charge $0.10 to cover bandwidth costs using @MPP. I asked my agent to set this up, and it basically worked smoothly, though I had to tell it what MPP is (I guess it's not yet in the pretrain) and also manually set up the Cloudflare account that actually hosts the PDF and configure the API key. (Vercel seemingly has a 100MB limit.) The purchases now show up in my Stripe account alongside all other activity.
The site now has a ready-made agent prompt for anyone who wants to download the whole thing. I'm guessing that we'll see a lot more UIs like this in the future.
I remain pretty intrigued by the intersection of agents, micropayments, and stablecoins. I don't know much about managing crypto wallets from the CLI, but now AI can do that for me, while Stripe seamlessly handles turning it all back into fiat.
So what is the moral of the story?
• Whitworth's book is very good, and you should buy it.
• The Internet Archive continues to be wonderful and a civilizational treasure.
• While there are rough edges, setting up third-party services via the CLI now basically works. I'm pretty sure I wouldn't have bothered with any of this if I couldn't have outsourced almost all of the work to AI.
• The image models have gotten very good.
• There will probably continue to be all kinds of interesting applications of AI to history. (The Vesuvius Challenge of course being a shining pioneer.)
• These days, I often find myself building single-use sites for things I'm learning or for books I'm reading. I think this is a cool new category of software.
Jen retweeted
Machine payments are starting to work: very small N, but we're seeing consistent, "real" daily use across a number of Stripe businesses.
A number are also powered by @tempo, which is working well in production.
Our machine payments support is currently in private preview because we want to go deep with partners to understand their use-cases as we refine our APIs: docs.stripe.com/payments/mac….
Register on that page if interested. We'll get back very quickly.
Jen retweeted
no, this is a category error
it’s fun to dunk on incumbents, but this misses the point (or is just intentional CT rage bait)
Stripe is selling payment acceptance, not blockchain transfers
comparing 1.5% to gas fees misunderstands where value is created, here’s why:
Stripe isn’t charging 1.5% to move USDC
they’re charging 1.5% to wrap stablecoins into a full payments stack:
• checkout integration
• multi-chain routing,
• refunds
• fiat settlement
• fraud checks
• subscription logic
• compliance
• support
• analytics
...all inside the same place merchants already accept everything else (cards, Link, PayPal, etc.)
to beat Stripe on price, a competitor would have to beat Stripe on scope
not just “receive a USDC payment,” but replicate the entire checkout surface and the full payments suite around it
that’s a tall order, and no one is there today
and merchants aren’t going to build it themselves:
• crypto acceptance isn’t their business
• developer time is scarce
• stablecoin volume is tiny
• it’s incremental revenue
• and it’s cheaper than the 2.9% they already pay
no one wants two parallel payment systems for a marginal method
Stripe’s value isn’t the rail, it’s the checkout suite that orchestrates all the rails
stablecoins are just another funding path, and funding paths are commoditized
so yes, while blockchain transfers are near-free, payment acceptance is not
are they making a bunch of margin? probably
but that’s what pricing power looks like when you own the checkout surface
if 1.5% is “ridiculous,” go build the alternative and displace them
I’ll wait
Jen retweeted
save your wallet as a payment method in Stripe and authorize recurring charges. subscription payments are quite important - now possible with stablecoins via Stripe + Bridge
You can now accept stablecoins for recurring payments with @Stripe.
🔄 Let customers use their crypto wallets to pay for subscriptions
👩💻 Manage fiat and stablecoin subscriptions together from your dashboard
🌏 Reach global customers at lower costs
Here’s how it works:
Jen retweeted
We're delighted to welcome @privy_io to @stripe.
Money has to reside somewhere, and Privy builds the world's best programmable vaults. Alongside our other stablecoin work, we're looking forward to enabling a new generation of global, internet-native financial services.






























