﻿WEBVTT

1
00:00:10.160 --> 00:00:14.800
<v 0>All right. Welcome everyone to the platform roadmap breakout,</v>

2
00:00:14.860 --> 00:00:18.760
where we'll go deeper into the most impactful product launches for platforms.

3
00:00:19.200 --> 00:00:22.700
Come on in, grab a seat, everyone. How's everyone's Sessions going so far?

4
00:00:23.080 --> 00:00:27.840
How was the morning? Come on, how was the morning? All right.

5
00:00:30.740 --> 00:00:35.360
So everyone in this room knows that AI has introduced a really important

6
00:00:35.380 --> 00:00:36.213
question.

7
00:00:36.380 --> 00:00:39.900
How resilient is your business model in the face of this generational technology

8
00:00:40.020 --> 00:00:42.220
shift? I'm Christian DiCarlo.

9
00:00:42.480 --> 00:00:45.940
I spent the last 10 years at Stripe working exclusively with platforms like

10
00:00:45.960 --> 00:00:50.300
yours to help answer questions like this. Over the past decade,

11
00:00:50.360 --> 00:00:54.620
we've seen fintech transform from an interesting experiment to a bolt-on set of

12
00:00:54.640 --> 00:00:58.900
features to now being one of the most impactful ways that you can drive

13
00:00:58.940 --> 00:01:02.360
defensibility and build a moat around your business. Today,

14
00:01:02.480 --> 00:01:06.600
over 16,000 software platforms on Stripe offer financial products to their

15
00:01:06.620 --> 00:01:07.453
customers.

16
00:01:07.860 --> 00:01:11.740
And this spans hundreds of industries-whether that's Granum for arborists,

17
00:01:12.660 --> 00:01:14.040
Piano in the media space,

18
00:01:15.000 --> 00:01:19.280
or Procede Software in heavy-duty trucking.
Platforms on Stripe serve nearly

19
00:01:19.480 --> 00:01:20.500
every sector of the economy,

20
00:01:21.360 --> 00:01:23.640
and nearly a thousand of them are here today at Sessions,

21
00:01:24.340 --> 00:01:28.160
including the likes of Cloudbeds and hospitality, GlossGenius in beauty,

22
00:01:28.840 --> 00:01:30.640
and Lightspeed in retail, just to name a few.

23
00:01:32.300 --> 00:01:35.120
We're really honored to have several of our platforms joining us onstage

24
00:01:35.360 --> 00:01:36.193
throughout the talks.

25
00:01:36.620 --> 00:01:40.000
They'll be helping us tackle really some of the most important questions you're

26
00:01:40.020 --> 00:01:41.400
all asking, such as:

27
00:01:41.960 --> 00:01:44.900
how is AI helping me open up new sales channels for my customers?

28
00:01:45.500 --> 00:01:46.520
How can I be improving my

29
00:01:48.960 --> 00:01:51.600
payments attach rate and expanding my take rate? Or,

30
00:01:51.920 --> 00:01:54.020
which products should we prioritize next on our roadmap?

31
00:01:55.240 --> 00:01:58.180
So make sure you check out these talks throughout today and tomorrow.

32
00:02:00.480 --> 00:02:03.640
We know that durable and fast-growing revenue is top of mind for everyone in

33
00:02:03.660 --> 00:02:06.120
this room. And many of you want to know:

34
00:02:06.220 --> 00:02:09.680
what traits are we seeing across the breakout platforms on Stripe?

35
00:02:10.560 --> 00:02:11.400
So let's dive in.

36
00:02:13.020 --> 00:02:17.720
The first trait we're seeing is that breakout platforms are deeply entrenched in

37
00:02:17.820 --> 00:02:21.480
how their users run their business. Take, for example, Moxie.

38
00:02:22.280 --> 00:02:23.400
It's not just employee payroll.

39
00:02:23.960 --> 00:02:26.800
It's how med spas stay compliant and protect their license.

40
00:02:28.620 --> 00:02:31.340
Or take Venue Link. It's not just appointment scheduling.

41
00:02:31.520 --> 00:02:34.240
It's how tattoo artists sell and manage their artwork.

42
00:02:35.980 --> 00:02:40.100
The second trait we see is that leaders are putting AI to work across their

43
00:02:40.140 --> 00:02:42.040
vertical. For example,

44
00:02:42.160 --> 00:02:44.660
SimplePractice isn't just how you run your telehealth appointments.

45
00:02:45.940 --> 00:02:49.600
It's your therapist's AI notetaker to keep track of everything that's covered.

46
00:02:50.420 --> 00:02:52.080
Or Clio-it's not just case management.

47
00:02:52.480 --> 00:02:55.020
It's your legal AI engine for case execution.

48
00:02:56.760 --> 00:03:01.200
And the third trait we see, and frankly, I think is why we're all here at the

49
00:03:02.880 --> 00:03:03.713
product breakout,

50
00:03:04.140 --> 00:03:08.260
is that breakout platforms have become the complete financial operating system

51
00:03:08.680 --> 00:03:13.520
for their users.
Leaders like Shopify now power every financial workflow.

52
00:03:14.840 --> 00:03:16.320
They've gone from how their users earn money,

53
00:03:17.220 --> 00:03:20.300
to how they store and manage funds, to how they access funds,

54
00:03:20.700 --> 00:03:21.880
and how they move and spend money.

55
00:03:22.500 --> 00:03:26.740
And so this is a retention and revenue flywheel that keeps spinning as you solve

56
00:03:27.560 --> 00:03:32.420
more high ROI problems for your customers.
And here's the proof.

57
00:03:33.100 --> 00:03:37.940
Platforms on Stripe who have a multiproduct embedded payments and finance

58
00:03:37.960 --> 00:03:42.340
strategy see 50% higher revenue growth than those with just payments alone.

59
00:03:43.500 --> 00:03:48.280
And they experience a 40% increase in customer lifetime value. That's massive,

60
00:03:49.080 --> 00:03:51.920
and that is how you build the moat.
So,

61
00:03:52.400 --> 00:03:55.720
which brings us to why you're here today.
So we have thousands of engineers at

62
00:03:55.760 --> 00:03:57.620
Stripe building solutions for platforms,

63
00:03:58.480 --> 00:04:00.880
and that's more R&amp;D than any other company in our space,

64
00:04:01.420 --> 00:04:03.360
and your feedback shapes every line of code.

65
00:04:04.420 --> 00:04:08.120
And you've told us you want three things.
First, you want speed,

66
00:04:08.560 --> 00:04:11.720
so you can build and launch new products faster. Second,

67
00:04:12.020 --> 00:04:15.600
you want monetization to open up new revenue streams and expand your take rate.

68
00:04:16.360 --> 00:04:17.180
And third,

69
00:04:17.180 --> 00:04:20.680
you want scale to be able to grow your volumes confidently while mitigating

70
00:04:20.720 --> 00:04:22.800
risk. Over the next 25 minutes,

71
00:04:23.180 --> 00:04:26.400
we're going to go deep on each of these areas and we're going to illustrate how

72
00:04:26.460 --> 00:04:28.740
Stripe can help you build your remote and expand your lead.

73
00:04:29.320 --> 00:04:32.520
So now I'll pass it over to our product leaders for the roadmap. Over to you,

74
00:04:32.580 --> 00:04:33.413
Jason.

75
00:04:33.780 --> 00:04:37.040
<v 1>Thank you, Christian. Platforms keep asking us,</v>

76
00:04:37.600 --> 00:04:41.620
"How can we move faster?" Roadmaps are stacked,

77
00:04:42.060 --> 00:04:46.820
delays mean losing ground and development expectations have

78
00:04:46.980 --> 00:04:48.960
never been higher. Well,

79
00:04:49.160 --> 00:04:53.740
our goal is to help reduce your lift to just a few lines of code or

80
00:04:54.200 --> 00:04:58.820
even a few clicks. Today, I'm going to show you how across three areas:

81
00:04:59.620 --> 00:05:02.280
agentic development, embedded components,

82
00:05:02.800 --> 00:05:07.240
and turnkey embedded finance. Let's get into it.

83
00:05:07.740 --> 00:05:11.000
And we've got to start with agentic development.

84
00:05:12.220 --> 00:05:13.053
Last year,

85
00:05:13.300 --> 00:05:18.260
we saw 10 times more LLM traffic to Stripe docs than

86
00:05:18.280 --> 00:05:23.240
the year before. So we optimized everything, all for agents.

87
00:05:23.720 --> 00:05:26.200
Our docs, APIs, SDKs.

88
00:05:26.720 --> 00:05:29.980
Your LLM can now understand Stripe right out of the box.

89
00:05:31.160 --> 00:05:33.300
And you can now build, test,

90
00:05:33.500 --> 00:05:37.920
and go live with Stripe products directly from your favorite vibe coding tools.

91
00:05:39.160 --> 00:05:41.640
Take Biz Lab, who builds software for teachers.

92
00:05:42.520 --> 00:05:47.220
Their founder used Base44 to set up Connect for payments processing on their

93
00:05:47.260 --> 00:05:51.700
platform in only three hours of work. That's hours,

94
00:05:51.840 --> 00:05:55.860
not days. That's the new bar. And honestly,

95
00:05:56.020 --> 00:05:59.620
BizLab will probably offer a full financial suite to their users by the end of

96
00:05:59.640 --> 00:06:02.120
the week.
Now, of course,

97
00:06:02.360 --> 00:06:06.980
selling multiple products to the same users requires extensible infrastructure.

98
00:06:08.120 --> 00:06:08.953
And historically,

99
00:06:09.540 --> 00:06:12.360
integrating on Stripe involved multiple accounts for your users:

100
00:06:13.100 --> 00:06:14.160
one for their subscription,

101
00:06:14.440 --> 00:06:19.380
another one for their payments and custom logic to link it all together. Well,

102
00:06:19.680 --> 00:06:24.520
you've told us that this slows you down and it adds complexity for AI agents

103
00:06:24.680 --> 00:06:27.320
and it makes launching new products harder than it needs to be.

104
00:06:28.720 --> 00:06:33.680
So we've completely redesigned the account architecture that powers

105
00:06:33.720 --> 00:06:38.460
the Stripe network. One account now does everything for your user.

106
00:06:39.120 --> 00:06:42.440
Paying subscriptions, accepting payments, making payouts,

107
00:06:42.540 --> 00:06:43.740
opening a financial account.

108
00:06:44.500 --> 00:06:48.320
This means that you can execute on a multiproduct strategy much faster.

109
00:06:48.880 --> 00:06:51.820
It enables agents to execute with minimal intervention,

110
00:06:52.320 --> 00:06:56.380
and it means that you maintain less code as you scale.
Okay,

111
00:06:56.680 --> 00:07:01.360
that's agentic development. Next, let's talk about embedded components.

112
00:07:02.240 --> 00:07:06.300
There are so many different financial UI workflows that you have to build to

113
00:07:06.340 --> 00:07:09.920
have an excellent product. Onboarding flows, payment forms,

114
00:07:10.000 --> 00:07:13.920
payout dashboards-and every platform rebuilds the same things.

115
00:07:14.620 --> 00:07:15.920
So we built them for you.

116
00:07:17.420 --> 00:07:21.940
We're now up to 40 prebuilt components. Honestly,

117
00:07:22.040 --> 00:07:24.220
it's starting to get hard to fit them all on a slide.

118
00:07:24.280 --> 00:07:25.360
We had to reduce the font size.

119
00:07:26.160 --> 00:07:29.860
These are full experiences that you can customize and drop into your code.

120
00:07:31.240 --> 00:07:35.640
Now, you might be thinking: can't I just vibe code this? Well,

121
00:07:36.760 --> 00:07:39.440
sure you can-until compliance rules change,

122
00:07:39.520 --> 00:07:42.340
and you got to start collecting new information from your users,

123
00:07:42.520 --> 00:07:45.160
or you want to launch a new feature like Smart Disputes.

124
00:07:45.800 --> 00:07:50.080
With embedded components, we handle all of that for you. Compliance updates,

125
00:07:50.200 --> 00:07:53.560
security, new features, optimizations from the Stripe network.

126
00:07:53.920 --> 00:07:57.120
They're all automatically built into the components that you embed.

127
00:07:58.000 --> 00:08:02.760
You ship once and they just keep working.
Let's take account onboarding.

128
00:08:03.720 --> 00:08:08.080
The Stripe network has now seen one in six businesses globally,

129
00:08:09.000 --> 00:08:11.560
and we're putting that immense data to work for you.

130
00:08:14.120 --> 00:08:16.480
If we already know the business signing up to your platform,

131
00:08:16.880 --> 00:08:19.160
we'll fast-track their onboarding to just one click.

132
00:08:19.480 --> 00:08:24.280
And we call this "networked onboarding." The industry average for onboarding

133
00:08:24.360 --> 00:08:27.200
businesses to accept payments is three days.

134
00:08:27.960 --> 00:08:32.480
The Stripe average with networked onboarding is about five and a half minutes.

135
00:08:33.760 --> 00:08:38.080
This gives platforms like FreshBooks or MYOB that are using networked onboarding

136
00:08:38.160 --> 00:08:39.320
through embedded components,

137
00:08:39.440 --> 00:08:42.160
a real advantage when it comes to driving payments adoption.

138
00:08:43.960 --> 00:08:47.400
Another component that we've optimized for conversion is Capital.

139
00:08:48.200 --> 00:08:50.040
Your users need financing to grow,

140
00:08:50.400 --> 00:08:54.600
but many find it difficult and a stressful process that involves months of back

141
00:08:54.640 --> 00:08:56.680
and forth with the bank. Well,

142
00:08:56.960 --> 00:08:59.600
Stripe Capital helps you be a part of their solution.

143
00:09:00.360 --> 00:09:04.360
You can now offer access to financing directly in your platform to help users

144
00:09:04.360 --> 00:09:05.193
grow their business,

145
00:09:05.320 --> 00:09:08.520
and this is one of the strongest drivers of stickiness that we've seen.

146
00:09:09.720 --> 00:09:13.160
Platforms in the Stripe partner program like Tekmetric, Jobber,

147
00:09:13.240 --> 00:09:18.240
and GlossGenius see an average 66% increase in net revenue

148
00:09:18.440 --> 00:09:23.280
when offering Capital and 146% increase in product adoption

149
00:09:23.440 --> 00:09:26.680
when implementing best practices. And today,

150
00:09:26.800 --> 00:09:28.600
we're launching lines of credit.

151
00:09:29.840 --> 00:09:34.520
Your users draw what they need up to an improved limit and they only pay fees on

152
00:09:34.640 --> 00:09:35.473
what they use.

153
00:09:36.040 --> 00:09:39.680
We've built this new form of capital directly into our existing components,

154
00:09:39.960 --> 00:09:44.440
so you can start offering a more flexible financing program without even lifting

155
00:09:44.560 --> 00:09:49.280
a finger. But we're not just improving our existing components.

156
00:09:49.520 --> 00:09:51.840
We're also building new ones to help you move faster.

157
00:09:52.320 --> 00:09:55.320
Let me give you a few examples. Starting with terminal,

158
00:09:55.520 --> 00:09:59.560
you can now use embedded components to help your users easily purchase, track,

159
00:09:59.760 --> 00:10:04.440
and manage devices or in-person payments. Stripe handles ordering,

160
00:10:04.500 --> 00:10:06.140
warehousing, delivering, and monitoring,

161
00:10:06.500 --> 00:10:10.860
and all you got to do is embed the component.
Another is Instant Payouts,

162
00:10:11.200 --> 00:10:15.060
which lets you offer accelerated access to earnings. And you guessed it:

163
00:10:15.380 --> 00:10:16.560
there's now a component for that too.

164
00:10:16.840 --> 00:10:21.380
So your users can just click one button and get paid out instantly.
Now,

165
00:10:21.440 --> 00:10:24.680
of course, all these new funds flows, they make reconciliation harder.

166
00:10:25.380 --> 00:10:29.660
So we built a component for balance reporting and another one for payout

167
00:10:29.680 --> 00:10:33.900
reconciliation reporting, so your users can easily track their money movement.

168
00:10:35.500 --> 00:10:37.680
And it's not just web experiences.

169
00:10:38.000 --> 00:10:41.400
We've also made new components available in your React Native mobile

170
00:10:41.440 --> 00:10:45.100
applications. You can just customize them, brand them,

171
00:10:45.540 --> 00:10:49.820
and drop them into your code.
Okay, so I've covered Capital, Terminal,

172
00:10:50.120 --> 00:10:50.953
and Instant Payouts,

173
00:10:51.380 --> 00:10:55.500
but there are two other massive revenue opportunities for platforms that we

174
00:10:55.580 --> 00:10:58.180
touched on in the keynote: Treasury and Issuing.

175
00:10:59.920 --> 00:11:03.060
One of the breakout platforms on Stripe is PlayMetrics.

176
00:11:03.480 --> 00:11:07.660
They launched Treasury and Issuing to help youth sport club leaders store funds

177
00:11:08.340 --> 00:11:13.160
and manage expenses.
PlayMetrics quickly tripled their processing volumes

178
00:11:13.480 --> 00:11:16.920
and increased average revenue per account by 15%.

179
00:11:18.440 --> 00:11:22.120
These expansion products are some of the most effective ways to build a real

180
00:11:22.120 --> 00:11:23.360
moat around your platform.

181
00:11:24.880 --> 00:11:29.080
Your users no longer lose money and time cobbling together point solutions to

182
00:11:29.260 --> 00:11:33.400
store, manage and move funds, and your platform gets to capture the value.

183
00:11:34.480 --> 00:11:35.360
But historically,

184
00:11:35.560 --> 00:11:39.740
becoming the financial home for your users was operationally brutal.

185
00:11:40.400 --> 00:11:43.560
It involved banking partners, compliance, fraud management, and more.

186
00:11:44.260 --> 00:11:48.900
And most platforms that I talk to just don't have the resources. Well,

187
00:11:49.020 --> 00:11:49.680
in the keynote,

188
00:11:49.680 --> 00:11:53.520
we announced that we're abstracting all of that away to help you move a lot

189
00:11:53.920 --> 00:11:54.753
faster.

190
00:11:55.380 --> 00:12:00.020
But I want to actually show you just how low the lift is with our new turnkey

191
00:12:00.220 --> 00:12:02.900
embedded finance solution. Let's take a look.

192
00:12:06.380 --> 00:12:10.060
Okay. So here we are in the Stripe Dashboard in the embedded Treasury tab,

193
00:12:10.660 --> 00:12:11.880
and we can click to get started.

194
00:12:13.080 --> 00:12:15.820
And we've preconfigured everything for you that you need,

195
00:12:16.340 --> 00:12:20.900
including the features for your users-like allowing them to pay bills or issue

196
00:12:20.940 --> 00:12:25.040
cards, fees, as well as cash rewards,

197
00:12:25.380 --> 00:12:28.460
so you can incentivize users to store money on your platform.

198
00:12:30.200 --> 00:12:32.180
When it comes to risk, we'll handle risk for you,

199
00:12:32.840 --> 00:12:34.800
but if you manage risk for payments,

200
00:12:34.940 --> 00:12:38.600
we'll make it easy for you to extend that coverage to your financial accounts

201
00:12:38.920 --> 00:12:41.000
with preconfigured rules with Stripe Radar.

202
00:12:43.120 --> 00:12:44.540
The integration is super easy.

203
00:12:44.780 --> 00:12:47.880
We've built a bunch of embedded components just for Treasury and Issuing,

204
00:12:48.240 --> 00:12:52.580
and you can just copy them over for your LLM. And finally,

205
00:12:52.800 --> 00:12:56.600
we're even handling email communications for you with prepackaged

206
00:12:56.640 --> 00:13:00.240
communications. And that's it.

207
00:13:00.520 --> 00:13:04.320
We just set up everything that we needed for an embedded finance program,

208
00:13:04.880 --> 00:13:08.820
and we're ready to deploy.
Now, you're probably wondering,

209
00:13:09.200 --> 00:13:12.700
"What does the experience look like for your users? So let's take a look.

210
00:13:14.480 --> 00:13:16.520
Here we're in ZenFlow's dashboard,

211
00:13:16.920 --> 00:13:20.480
and we're looking at the experience from the perspective of one of their users,

212
00:13:20.700 --> 00:13:23.020
Sunrise Yoga. And like I mentioned,

213
00:13:23.120 --> 00:13:25.420
we've built a bunch of new embedded components,

214
00:13:25.580 --> 00:13:29.460
and you can see them in the purple borders here. Now,

215
00:13:29.900 --> 00:13:33.660
right from the ZenFlow dashboard, Sunrise Yoga can easily

216
00:13:35.220 --> 00:13:37.780
view their balances in multiple different currencies.

217
00:13:37.920 --> 00:13:39.860
They can view all of their recent transactions,

218
00:13:40.340 --> 00:13:43.260
and they can do the same for cards, they can do it for bills,

219
00:13:43.580 --> 00:13:44.900
they can do it for their recipients.

220
00:13:45.580 --> 00:13:48.640
And these components contain entire workflows,

221
00:13:49.120 --> 00:13:51.380
so they can easily send money by uploading a bill,

222
00:13:52.200 --> 00:13:53.620
or they can even create a card.

223
00:13:54.740 --> 00:13:57.860
So Maria Santos can get this beautiful ZenFlow orange card.

224
00:14:01.000 --> 00:14:02.120
So we've built all of this,

225
00:14:02.380 --> 00:14:04.840
so that your users don't have to leave your platform,

226
00:14:05.540 --> 00:14:08.200
and you can launch an embedded finance program much,

227
00:14:08.360 --> 00:14:12.200
much more easily than before. And here's the best part:

228
00:14:13.080 --> 00:14:16.060
the more money that your users store with you,

229
00:14:16.800 --> 00:14:19.720
the more that you're able to earn through a service fee from Stripe.

230
00:14:20.920 --> 00:14:25.400
And platforms are already jumping at this opportunity. Phorest,

231
00:14:25.720 --> 00:14:28.760
Joe Coffee, and CASHDROP, among others,

232
00:14:28.820 --> 00:14:33.280
will be some of the first to embed this directly into their offering. Okay,

233
00:14:33.620 --> 00:14:35.040
so let's bring this all together.

234
00:14:35.620 --> 00:14:40.500
You now have AI-friendly docs and consolidated V2 accounts that

235
00:14:40.540 --> 00:14:42.880
help your teams and agents build faster.

236
00:14:44.160 --> 00:14:46.280
You have 40 new embedded components,

237
00:14:46.620 --> 00:14:49.220
so you can ship once and they just keep working,

238
00:14:50.360 --> 00:14:52.450
and turnkey embedded finance,

239
00:14:52.890 --> 00:14:56.670
so you become the financial home for your users in just a few clicks.

240
00:14:57.710 --> 00:15:00.750
This is how we're helping platforms on Stripe launch new,

241
00:15:01.190 --> 00:15:03.210
durable revenue streams fast.

242
00:15:04.450 --> 00:15:09.190
But building faster only matters if you can capture the value.
Here's

243
00:15:09.230 --> 00:15:10.090
Kadry to show you how.

244
00:15:11.410 --> 00:15:12.243
<v 2>Thanks, Jason.</v>

245
00:15:12.850 --> 00:15:16.390
Our next focus is helping you grow and monetize your embedded finance business.

246
00:15:18.180 --> 00:15:22.430
87% of vertical SaaS companies with an embedded finance offering now have a

247
00:15:22.530 --> 00:15:26.730
payments product in the portfolio. That's up 57% from last year.

248
00:15:27.790 --> 00:15:30.410
So how do you turn that payment product into a growth engine?

249
00:15:31.870 --> 00:15:33.990
You told us the three questions that matter to you most:

250
00:15:34.690 --> 00:15:38.890
how do I win more users, improve my margins, and grow product adoption?

251
00:15:39.830 --> 00:15:43.190
And that's how we shape the roadmap.
Let's start with winning more users.

252
00:15:44.550 --> 00:15:45.990
So you're competing upmarket,

253
00:15:46.590 --> 00:15:50.650
which means maybe serving more price-sensitive users who want to heavily

254
00:15:50.770 --> 00:15:55.250
optimize their cost and understand how that cost changes across factors like

255
00:15:55.270 --> 00:15:58.850
networks, card brands, card categories, and more.

256
00:16:00.570 --> 00:16:03.870
Last year, we launched network cost passthrough in the US,

257
00:16:04.770 --> 00:16:07.730
which help you offer interchange plus pricing to your users,

258
00:16:08.250 --> 00:16:11.930
transparently passing through the network cost and the transaction markup on

259
00:16:11.970 --> 00:16:16.590
top.
Since we launched, platforms like Tekmetric, DaySmart,

260
00:16:16.650 --> 00:16:21.030
and others have processed more than $100 million in that pricing model in no

261
00:16:21.150 --> 00:16:21.983
time.

262
00:16:22.170 --> 00:16:26.210
Some of them are even ramping up the volume more than 100% month over month.

263
00:16:27.490 --> 00:16:31.410
Today, I'm glad to share that network cost passthrough is available in 43 more

264
00:16:31.430 --> 00:16:34.110
countries, including the UK, France, and Germany.

265
00:16:35.990 --> 00:16:39.430
And we've built it right into the Stripe Dashboard so that easily with a few

266
00:16:39.470 --> 00:16:43.670
clicks, you can enable it for a user, add your markup, and start processing.

267
00:16:44.670 --> 00:16:49.530
It also comes with built-in aggregated and transaction-level reporting so

268
00:16:49.550 --> 00:16:53.870
that you and your users have the margin visibility you need to deeply understand

269
00:16:53.890 --> 00:16:57.650
your cost and segment your pricing based on how that cost changes over time.

270
00:16:59.450 --> 00:17:03.530
It's very simple to get started, but other users have a hard requirement:

271
00:17:04.430 --> 00:17:07.770
gross settlement. They would like, sometimes they need,

272
00:17:08.220 --> 00:17:09.610
their payments earnings up front,

273
00:17:10.630 --> 00:17:14.350
and the payment cease to be settled separately.
And that's not a preference.

274
00:17:14.950 --> 00:17:19.930
This is a business constraint for accounting or compliance reasons. Soon,

275
00:17:20.350 --> 00:17:23.460
you'll also be able to turn on gross settlement for users via the Stripe

276
00:17:23.480 --> 00:17:27.770
Dashboard and easily select the billing cadence and the funding source for

277
00:17:27.810 --> 00:17:30.410
collecting these payment fees. All right.

278
00:17:31.190 --> 00:17:33.480
These are two pricing controls to help you win more users,

279
00:17:35.050 --> 00:17:37.460
but controlling pricing is only one part of the equation.

280
00:17:39.720 --> 00:17:43.850
Our vision is to help you monetize any fee you want in any way you

281
00:17:43.890 --> 00:17:47.960
want-whether it's pathing through network cost, FX fees,

282
00:17:48.460 --> 00:17:49.480
marketing operator fees,

283
00:17:50.050 --> 00:17:52.930
or discounting local payment methods to drive their growth,

284
00:17:53.650 --> 00:17:54.850
which takes me to my second topic.

285
00:17:55.990 --> 00:18:00.670
How do you improve your margin and expand product adoption? Well,

286
00:18:00.730 --> 00:18:03.610
we know it's not easy. Why? Two reasons.

287
00:18:04.730 --> 00:18:08.230
You have to be looking at months of your data just to understand your take rate

288
00:18:08.990 --> 00:18:11.950
or identify the next cohort of users to launch a new product tool.

289
00:18:13.050 --> 00:18:16.710
The second reason is that sometimes, or maybe often,

290
00:18:17.030 --> 00:18:19.470
you're only left with your own data for comparison.

291
00:18:20.830 --> 00:18:24.690
So with a quick show of hands, who wanted Stripe to offer benchmarking data?

292
00:18:26.870 --> 00:18:31.290
Quite a few. I'm not surprised. It's one of your most requested features,

293
00:18:32.810 --> 00:18:36.690
followed by tailored recommendations for how you can make more money through

294
00:18:36.710 --> 00:18:37.970
your embedded finance portfolio.

295
00:18:39.030 --> 00:18:43.390
These two capabilities really require the scale of Stripe's network to be

296
00:18:43.470 --> 00:18:47.230
effective and actionable. So I'm glad to share that today,

297
00:18:47.550 --> 00:18:48.410
we're giving you both,

298
00:18:49.130 --> 00:18:53.090
and also an easy way to act on them in the Stripe Dashboard,

299
00:18:53.550 --> 00:18:57.800
all in one place. That's platform's growth studio. Now,

300
00:18:59.320 --> 00:19:01.590
we've seen that in the keynote very briefly.

301
00:19:01.750 --> 00:19:05.090
I'd like to talk about a little bit more in this demo.

302
00:19:07.130 --> 00:19:10.330
The first thing you see in the growth studio are the key business metrics that

303
00:19:10.350 --> 00:19:13.790
you would look at regularly to understand the health of your business-whether

304
00:19:13.810 --> 00:19:17.590
that's your volume, earnings, or account growth.

305
00:19:18.950 --> 00:19:21.850
But does this mean that there is nothing else left for me to optimize?

306
00:19:22.770 --> 00:19:23.603
Let's see.

307
00:19:24.730 --> 00:19:28.270
I can go to the recommendations that can see that growth studio has already

308
00:19:28.390 --> 00:19:32.710
identified few things for me to consider and has ordered these

309
00:19:32.770 --> 00:19:37.630
recommendations based on the impacts they have on my business.
We touched on the

310
00:19:38.050 --> 00:19:41.190
ACH improvement opportunity in the keynote. So in this demo,

311
00:19:41.590 --> 00:19:44.750
I'm going to be particularly interested in looking at that bottom right card

312
00:19:44.950 --> 00:19:45.783
that says,

313
00:19:46.350 --> 00:19:50.810
"Maybe I need to reconsider my pricing for manually entered cards." Why?

314
00:19:51.550 --> 00:19:55.590
Because I am sitting at 125 bps below my industry benchmark.

315
00:19:56.450 --> 00:19:57.550
The industry benchmark,

316
00:19:58.090 --> 00:20:02.350
Stripe has calculated for me based on anonymized and generalized data across the

317
00:20:02.390 --> 00:20:05.490
Stripe network. So I'm digging deeper to learn more.

318
00:20:07.210 --> 00:20:08.530
The first thing I see is this chart.

319
00:20:08.930 --> 00:20:13.870
I can see my take rate in this green line below and the benchmark at the top

320
00:20:14.050 --> 00:20:16.950
in the orange line. And as I understand,

321
00:20:17.390 --> 00:20:22.050
I'm 125 bps below, because I'm actually losing 50 bps on that segment.

322
00:20:23.090 --> 00:20:26.650
So the first question that comes to mind: what do I do next? Well,

323
00:20:27.570 --> 00:20:29.130
growth studio also takes away the guesswork,

324
00:20:29.790 --> 00:20:34.530
because it has calculated two data points to help me guide my decision.
One that

325
00:20:34.570 --> 00:20:37.690
allows me to break even if I want to have a conservative go-to-market strategy.

326
00:20:38.730 --> 00:20:39.563
If I simulate it,

327
00:20:40.010 --> 00:20:44.050
I can see that it keeps my take rate at 0 bps-right between my current and the

328
00:20:44.090 --> 00:20:47.150
benchmark. It also gave me another data point:

329
00:20:49.230 --> 00:20:51.630
3.5% to be on par with the benchmark,

330
00:20:51.830 --> 00:20:55.010
and you can see how the blue dotted line moves to tell me where I would sit.

331
00:20:56.170 --> 00:20:58.710
Now, I know my business more than anyone,

332
00:20:59.170 --> 00:21:00.890
and I have an aggressive go-to-market strategy.

333
00:21:01.610 --> 00:21:04.270
So I'd like to go ahead and charge more than the medium in the industry.

334
00:21:05.170 --> 00:21:07.200
Let's say I'm going to go ahead and charge 3.8%

335
00:21:09.110 --> 00:21:10.470
as growth studio to simulate it,

336
00:21:10.950 --> 00:21:14.650
which back tests that fee across all my historical transaction data in one

337
00:21:14.690 --> 00:21:18.090
click, and I like where it sits. So next,

338
00:21:18.330 --> 00:21:22.250
I actually want to go ahead and update the pricing to reflect that fee.
Super

339
00:21:22.310 --> 00:21:23.910
easy. Update pricing.

340
00:21:24.430 --> 00:21:28.890
I can see that I already have a pricing scheme that allows me to charge for

341
00:21:28.950 --> 00:21:32.000
manually entered cards, but it's currently charging 1%,

342
00:21:32.610 --> 00:21:36.400
which is maybe why I'm losing money. I'm going to change it to 3.8%,

343
00:21:38.030 --> 00:21:41.790
schedule it to happen maybe two weeks later-just to give me a chance to give my

344
00:21:41.850 --> 00:21:46.130
users heads up that a pricing change is coming-confirm, and that's it.

345
00:21:47.010 --> 00:21:47.843
In a few clicks,

346
00:21:48.210 --> 00:21:51.610
I have a pricing change scheduled based on opportunity and the recommendation

347
00:21:51.650 --> 00:21:56.170
that growth studio offered me. But it doesn't stop here, so let's go back.

348
00:21:57.690 --> 00:21:59.990
Now, let's take a look at this upper right card.

349
00:22:00.850 --> 00:22:04.470
Growth studio is telling me that I can launch buy now and pay later products via

350
00:22:04.510 --> 00:22:06.370
Affirm and Klarna. Why?

351
00:22:06.430 --> 00:22:10.850
Because it seems that more than 6,000 of my users can benefit from these

352
00:22:10.870 --> 00:22:13.790
products. They can offer installments to their customers,

353
00:22:13.870 --> 00:22:14.990
capture a higher order size,

354
00:22:15.630 --> 00:22:19.570
and it seems that I can stand to make more than $12,000 of margin if I turn on

355
00:22:19.590 --> 00:22:22.670
these products.
So I'm excited. I want to learn more.

356
00:22:24.670 --> 00:22:29.470
I go in and I see that growth studio has learned and identified that 60% of my

357
00:22:29.530 --> 00:22:31.690
users are eligible to use Affirm and Klarna,

358
00:22:32.570 --> 00:22:37.050
and are likely to use it if I offer it. So how do I go about that?

359
00:22:37.410 --> 00:22:39.770
Again, I know my business and my users better than anyone,

360
00:22:40.310 --> 00:22:45.210
and I think maybe a promotional price can go a long way in nudging users to

361
00:22:45.270 --> 00:22:47.670
try these products. So I create a campaign.

362
00:22:48.530 --> 00:22:52.450
This campaign will allow me to discount Klarna and Affirm for a period of time.

363
00:22:53.550 --> 00:22:55.350
Let's say this is going to be during the month of May.

364
00:23:00.050 --> 00:23:02.290
All right. I give it a name and a period.

365
00:23:03.550 --> 00:23:05.890
I accept that I only want to cover Affirm and Klarna,

366
00:23:06.030 --> 00:23:10.090
but can always add more payment methods if I know my business? Now,

367
00:23:10.150 --> 00:23:11.730
I can also add any user I want,

368
00:23:12.030 --> 00:23:15.670
but growth studio has already curated for me a cohort of all eligible users.

369
00:23:15.810 --> 00:23:20.110
So I'll just go ahead with that. The last thing is configure pricing.

370
00:23:20.790 --> 00:23:23.890
I know that I'm paying 6% and 30¢ for these two methods,

371
00:23:24.670 --> 00:23:28.400
so I'll say maybe 50% discount for a month. So I'll give it 3%,

372
00:23:29.400 --> 00:23:33.710
15¢, continue, review, I'm happy,

373
00:23:33.790 --> 00:23:36.170
I'm going to schedule it. Here you go.

374
00:23:37.390 --> 00:23:40.150
Now it's worth noting that platforms in the Stripe partner program who've

375
00:23:40.190 --> 00:23:43.950
executed promotional pricing campaigns for BNPLs realized incredible gains.

376
00:23:44.730 --> 00:23:48.350
Calendly, for example, saw up to 140% volume uplift,

377
00:23:48.910 --> 00:23:51.670
Intelligent Salon saw 900% volume uplift.

378
00:23:52.450 --> 00:23:56.650
You too can see these results in the campaigns tab after you execute a bunch of

379
00:23:56.670 --> 00:23:59.610
campaigns.
All right, so that's growth studio,

380
00:23:59.910 --> 00:24:01.710
giving you the opportunity and a way to act on it.

381
00:24:02.790 --> 00:24:05.210
But you might have your own ideas,

382
00:24:05.690 --> 00:24:09.150
questions that you want to dig into deeper outside what Stripe is recommending.

383
00:24:10.130 --> 00:24:11.570
Let's see how the Stripe Console can help you.

384
00:24:16.210 --> 00:24:20.030
I'm going to ask the Console a question: "Am I losing money

385
00:24:22.210 --> 00:24:26.690
on users with above-average

386
00:24:27.950 --> 00:24:31.450
cross-border volume?" All right,

387
00:24:31.510 --> 00:24:36.030
I'm glad I was able to type this in one go. All right,

388
00:24:36.450 --> 00:24:37.230
let's keep in mind,

389
00:24:37.230 --> 00:24:42.110
I started that query without knowing what is the average cross-border

390
00:24:42.170 --> 00:24:46.290
volume among my users or which users sit above that average.

391
00:24:47.150 --> 00:24:51.610
The Console will do this for me. It will run the queries, synthesize the data,

392
00:24:52.490 --> 00:24:56.990
and offer me the answer in a format digestible that I can use to make decisions.

393
00:24:58.390 --> 00:25:00.950
It can also do a bunch of more things. You can ask it,

394
00:25:01.670 --> 00:25:05.610
"Can I expand into a new country and how can I simulate a price,

395
00:25:06.050 --> 00:25:09.190
and how?" And you can see that it's starting to offer me the results.

396
00:25:09.570 --> 00:25:13.830
I can see in this chart that it's identified that at least three of my users fit

397
00:25:13.850 --> 00:25:17.650
the criteria that I requested.
One of them is net margin negative on the

398
00:25:17.690 --> 00:25:21.150
cross-border volume, but two are negative overall.

399
00:25:22.130 --> 00:25:24.870
And it's also recommending that I should consider a pricing change,

400
00:25:24.930 --> 00:25:29.630
which I can easily do like we've seen a few minutes ago.
All right,

401
00:25:29.850 --> 00:25:31.150
so let's bring it all back after the demo.

402
00:25:32.770 --> 00:25:35.950
We're investing in key monetization capabilities to help you grow your business.

403
00:25:36.750 --> 00:25:39.310
We're shipping new pricing controls to help you win more users,

404
00:25:40.030 --> 00:25:42.930
giving you growth studio powered by the Stripe network and the data,

405
00:25:43.670 --> 00:25:47.950
and expanding the Stripe Console to help you answer specific platform workflows.

406
00:25:48.890 --> 00:25:51.210
But growing that business is important:

407
00:25:52.050 --> 00:25:55.710
protecting it is equally important. Aakash, over to you.

408
00:25:59.730 --> 00:26:00.563
<v 3>Thanks, Kadry.</v>

409
00:26:01.710 --> 00:26:06.610
Scaling your platform up means navigating new market shifts. And of course,

410
00:26:06.670 --> 00:26:10.170
last year we saw an entirely new kind of buyer in online channels:

411
00:26:10.710 --> 00:26:15.710
agents.
Agentic commerce moved from a hypothetical question of "What

412
00:26:15.770 --> 00:26:19.030
if?" to a very real and concrete question of "What now?"

413
00:26:20.650 --> 00:26:22.650
To power this, we launched the Agentic Commerce Suite,

414
00:26:22.910 --> 00:26:25.830
a complete solution for selling on AI agents.

415
00:26:26.530 --> 00:26:30.290
And although we saw the earliest pull here from retail and physical goods,

416
00:26:30.550 --> 00:26:34.530
we're now seeing a lot of interest across verticals-from hospitality,

417
00:26:34.750 --> 00:26:36.270
to services, to donations.

418
00:26:36.450 --> 00:26:40.350
I'm personally really excited to start booking my haircuts, my hotels,

419
00:26:40.850 --> 00:26:42.930
and my handyman from an LLM.

420
00:26:44.610 --> 00:26:47.350
So we've also launched the Agentic Commerce Suite for platforms,

421
00:26:47.610 --> 00:26:51.930
tailoring our solution to make it easy for platforms to get their users ready

422
00:26:52.110 --> 00:26:52.970
for agentic buying.

423
00:26:53.930 --> 00:26:57.270
You don't have to build and rebuild integrations with dozens of different AI

424
00:26:57.350 --> 00:26:58.430
agents.
Instead,

425
00:26:58.490 --> 00:27:02.230
you build once and your users are ready across all of the AI agents that can

426
00:27:02.290 --> 00:27:05.530
support them. Commerce platforms like Wix, Woo,

427
00:27:05.670 --> 00:27:09.550
and Commerce have been building on our agentic commerce for platforms suite,

428
00:27:09.790 --> 00:27:14.430
and we'll go live this quarter with Microsoft Copilot as a new growth channel

429
00:27:14.490 --> 00:27:18.890
for their users. And we're making it really easy for platforms to get started.

430
00:27:19.310 --> 00:27:21.690
You go to the new agentic commerce section of Connect,

431
00:27:24.730 --> 00:27:26.890
select the agents you want to enable with a few clicks,

432
00:27:28.530 --> 00:27:31.790
configure a product feed with your user's catalogs and inventories,

433
00:27:35.150 --> 00:27:37.590
and that's pretty much it. Everything else works as usual.

434
00:27:37.710 --> 00:27:41.450
We'll apply your existing processing fees and apply your Radar rules just like

435
00:27:41.470 --> 00:27:45.330
every other transaction. So that's agentic commerce for platforms.

436
00:27:45.390 --> 00:27:46.470
We're really excited about it.

437
00:27:46.890 --> 00:27:50.290
We're unlocking a new way for users to scale up on your platforms.

438
00:27:51.830 --> 00:27:55.590
We're of course super excited about how AI is changing the ways that people

439
00:27:55.630 --> 00:27:57.350
discover and buy products online,

440
00:27:58.010 --> 00:28:02.470
but we know it's not all smooth sailing.
AI is also creating an entirely new

441
00:28:02.530 --> 00:28:07.430
terrain of risks and merchant fraud that you need to worry about across

442
00:28:07.470 --> 00:28:10.830
both agentic and traditional sales channels. In fact,

443
00:28:10.890 --> 00:28:15.810
three in four platform leaders tell us that fraud is now evolving too fast

444
00:28:15.930 --> 00:28:16.910
for their business to keep up.

445
00:28:17.550 --> 00:28:22.230
Bad actors are using generative AI to produce fake websites and business

446
00:28:22.270 --> 00:28:27.190
information and documents that can bypass many platforms, fraud,

447
00:28:27.250 --> 00:28:30.750
and verification systems. So this creates a really painful trade off.

448
00:28:32.680 --> 00:28:33.920
On one end of the spectrum,

449
00:28:35.250 --> 00:28:37.870
opening the floodgates and taking on a massive amount of risk,

450
00:28:38.210 --> 00:28:39.530
and on the other end of the spectrum,

451
00:28:41.250 --> 00:28:45.610
making onboarding and interventions so onerous that you miss out on a lot of the

452
00:28:45.670 --> 00:28:49.750
good growth. So Stripe helps you to manage that trade off with two products.

453
00:28:50.090 --> 00:28:51.770
First, Radar for platforms,

454
00:28:52.070 --> 00:28:54.630
a tool from Stripe that helps you manage the risk yourself.

455
00:28:55.350 --> 00:28:57.890
And second with Managed Risk, where we'll handle the risk,

456
00:28:58.210 --> 00:29:00.570
we'll decide which accounts to intervene on,

457
00:29:00.850 --> 00:29:05.250
and we'll take liability for any financial losses.
Let's start with Radar for

458
00:29:05.270 --> 00:29:09.190
platforms. Last year,

459
00:29:09.330 --> 00:29:12.710
we launched Radar for platforms to give you deeper insight and greater control

460
00:29:12.750 --> 00:29:13.950
when it comes to risk management.

461
00:29:14.770 --> 00:29:18.670
You can author and configure and customize rules for assessing connected

462
00:29:18.710 --> 00:29:23.370
accounts and set up interventions like identity checks, payout pauses,

463
00:29:23.530 --> 00:29:26.230
or raise accounts for review when they meet certain criteria.

464
00:29:27.250 --> 00:29:31.030
Radar for platforms draws on signals from prior abuse across the entire Stripe

465
00:29:31.070 --> 00:29:31.530
network.

466
00:29:31.530 --> 00:29:35.830
So we'll flag accounts that are using IP addresses or bank accounts that we've

467
00:29:35.870 --> 00:29:37.430
seen before that look like fraud.

468
00:29:39.210 --> 00:29:41.850
Platforms using Radar for platforms like StyleSeat,

469
00:29:42.050 --> 00:29:46.550
Vimeo and FareHarbor are seeing five times lower losses per fraudulent account.

470
00:29:47.010 --> 00:29:49.150
It's really become a critical tool for their risk teams.

471
00:29:50.590 --> 00:29:54.170
But you've told us that you want even more data to inform your decision-making.

472
00:29:54.670 --> 00:29:56.110
So let's take a look at what's new this year.

473
00:30:00.250 --> 00:30:00.870
Okay.

474
00:30:00.870 --> 00:30:05.630
So here I am in my platform dashboard looking at a list of accounts that match a

475
00:30:05.710 --> 00:30:07.330
Radar rule that I've previously written.

476
00:30:08.070 --> 00:30:12.610
I can see that Stripe is flagging two accounts as having the highest risk level

477
00:30:13.630 --> 00:30:15.150
matching a rule that I had previously created.

478
00:30:15.270 --> 00:30:17.530
I'm going to click into Lauren Martin to see what's going on.

479
00:30:20.310 --> 00:30:21.143
Okay. Right off the bat,

480
00:30:21.250 --> 00:30:24.650
I can see that the fraud score for Lauren Martin is at 95 out of 100,

481
00:30:25.630 --> 00:30:29.590
and Stripe's recommended action is to reject the account entirely and offboard

482
00:30:29.630 --> 00:30:32.890
them. Before I do that, I'd like to see a little more information.

483
00:30:33.030 --> 00:30:34.750
So I'm going to take a look at the risk analysis.

484
00:30:35.830 --> 00:30:39.310
It looks like there are four indicators that Stripe is highlighting for me for

485
00:30:39.330 --> 00:30:42.470
this account. The first is a high-risk web presence.

486
00:30:42.850 --> 00:30:43.990
And if I expand this section,

487
00:30:44.490 --> 00:30:48.650
I can see why Stripe thinks that this user might be risky.
It looks like the

488
00:30:48.670 --> 00:30:49.810
merchant's online presence

489
00:30:51.450 --> 00:30:56.090
is high risk because there are many consumer reports indicating that the

490
00:30:56.110 --> 00:30:59.470
merchant failed to ship goods and also that their storefront is currently

491
00:30:59.670 --> 00:31:03.530
entirely unavailable. Sounds pretty sketchy. Second,

492
00:31:05.390 --> 00:31:07.970
Stripe is flagging that there's suspicious account activity,

493
00:31:08.130 --> 00:31:11.370
in particular that the account was created within... Sorry,

494
00:31:11.430 --> 00:31:15.010
the account submitted their application only a few seconds after the account was

495
00:31:15.050 --> 00:31:20.030
created, which suggests some automated bot going through onboarding. Second,

496
00:31:21.970 --> 00:31:26.110
Stripe is flagging that the owner's email was observed by Stripe only a few

497
00:31:26.170 --> 00:31:27.610
seconds prior to the onboarding,

498
00:31:28.310 --> 00:31:31.570
which is suspicious because Stripe has actually seen most emails as either

499
00:31:31.610 --> 00:31:35.150
buyers or merchants in the past. And last,

500
00:31:35.210 --> 00:31:37.790
there's a yellow flag here on some unusual account data:

501
00:31:38.670 --> 00:31:42.110
URLs and product descriptions that seem to match fraudulent accounts that we've

502
00:31:42.130 --> 00:31:45.470
seen before. Okay, sounds pretty concerning. So what should I do from here?

503
00:31:46.350 --> 00:31:47.770
I have a few options for next steps.

504
00:31:48.030 --> 00:31:50.690
I can take the recommended action and reject the account entirely.

505
00:31:51.550 --> 00:31:55.310
I can place a reserve on the account to limit my exposure while I investigate.

506
00:31:56.590 --> 00:31:56.850
Or,

507
00:31:56.850 --> 00:32:00.290
I can send an identity check to the user to verify that they are who they say

508
00:32:00.330 --> 00:32:02.630
they are. I'm not the fraud expert at the company,

509
00:32:02.690 --> 00:32:07.190
so I'm just going to add a note for my team. And, "Super sketchy.

510
00:32:08.970 --> 00:32:13.710
Fraud." And you can of course make these notes as formal or informal as you

511
00:32:13.730 --> 00:32:16.350
like. All right, we can go back to the slides.

512
00:32:18.710 --> 00:32:21.330
So Radar for platforms helps you limit losses and fraud,

513
00:32:21.670 --> 00:32:24.570
but what about the other side of the equation? Optimizing your growth.

514
00:32:25.090 --> 00:32:26.010
Let's talk about onboardings.

515
00:32:28.050 --> 00:32:32.570
A recent study from our platform partners program found that most platforms

516
00:32:32.790 --> 00:32:36.820
lose users between sign-up and the first thousand dollars of payments that they

517
00:32:36.860 --> 00:32:40.680
process. 10% of users take three days to hit that milestone-not bad.

518
00:32:41.280 --> 00:32:44.560
But almost 50% take 45 days to hit that milestone.

519
00:32:45.780 --> 00:32:47.040
To improve your conversion funnel,

520
00:32:47.340 --> 00:32:50.560
we're building new metrics into the Stripe Dashboard under the compliance

521
00:32:50.580 --> 00:32:51.413
section.

522
00:32:51.440 --> 00:32:55.840
You'll soon be able to analyze your entire onboarding funnel from start to first

523
00:32:55.880 --> 00:32:58.760
payout, track your conversion and drop-off rate,

524
00:32:59.420 --> 00:33:02.100
and unpack where and why users are dropping off.

525
00:33:03.380 --> 00:33:06.620
These updates are going to go out to all platforms using Stripe-hosted or

526
00:33:06.640 --> 00:33:10.740
embedded onboarding experiences. All right, now let's turn to Managed Risk.

527
00:33:11.920 --> 00:33:14.980
Here, Stripe does the heavy lifting.
We monitor risk signals,

528
00:33:15.260 --> 00:33:16.800
execute interventions on your behalf,

529
00:33:17.200 --> 00:33:20.280
and cover losses from transaction or account fraud.

530
00:33:21.120 --> 00:33:25.520
Many platforms opt for this model to protect their bottom line without having to

531
00:33:25.580 --> 00:33:29.000
scale up their own risk team. Today,

532
00:33:29.200 --> 00:33:31.800
I'm really excited to announce that we're making this experience even more

533
00:33:31.920 --> 00:33:34.820
seamless and customizable with API-based Managed Risk.

534
00:33:35.420 --> 00:33:39.520
This lets you retain complete control over your user experience while still

535
00:33:39.620 --> 00:33:40.700
offloading risk to Stripe.

536
00:33:41.640 --> 00:33:45.020
So you can use our new API to build a bespoke UI for onboarding,

537
00:33:45.340 --> 00:33:47.140
handle user login and verification,

538
00:33:47.640 --> 00:33:50.120
edit user information without taking them out of your app,

539
00:33:50.620 --> 00:33:54.000
and even send your own communications when an action is required from the user.

540
00:33:56.320 --> 00:33:59.440
Over the past few years since we've offered Managed Risk, platforms like Xero,

541
00:33:59.660 --> 00:34:00.300
Salesforce,

542
00:34:00.300 --> 00:34:05.140
and Dubsado who use it have collectively averted more than $400 million in

543
00:34:05.460 --> 00:34:08.820
losses. Okay. So to bring it all back,

544
00:34:08.920 --> 00:34:12.360
programmatically blocking bad actors is a critical step in scaling up your

545
00:34:12.380 --> 00:34:13.213
platform.

546
00:34:13.440 --> 00:34:16.400
And you can now put the mite of Stripe's network behind your risk strategy,

547
00:34:16.480 --> 00:34:19.600
whether using Radar for platforms or using our managed risk offering.

548
00:34:21.320 --> 00:34:21.840
All right,

549
00:34:21.840 --> 00:34:24.700
that's a wrap on the most important ways that Stripe is building for platforms.

550
00:34:24.840 --> 00:34:28.180
We're shipping components and turnkey experiences to help you build faster.

551
00:34:28.640 --> 00:34:32.300
We're giving you more pricing controls and a new growth studio powered by

552
00:34:32.320 --> 00:34:34.220
Stripe's data to enable you to monetize better.

553
00:34:34.860 --> 00:34:38.200
And we're expanding the capabilities of the Agentic Commerce Suite, Radar,

554
00:34:38.320 --> 00:34:42.520
and Managed Risk, so you can scale confidently. 10 years ago,

555
00:34:43.860 --> 00:34:47.180
SaaS platforms, embedding payments and finance were the exception,

556
00:34:47.720 --> 00:34:52.420
and now they're really the playbook to build a retention and revenue flywheel,

557
00:34:52.550 --> 00:34:56.280
especially in the age of AI.
We're here to make sure that your financial suite

558
00:34:56.320 --> 00:34:58.860
is the best offering in the market. And of course,

559
00:34:58.920 --> 00:35:00.900
the biggest input to our roadmap is all of you.

560
00:35:01.280 --> 00:35:04.200
So please keep telling us what you need to be the financial home for your users,

561
00:35:04.300 --> 00:35:05.880
and thank you so much for your partnership.

