WEBVTT 1 00:00:10.020 --> 00:00:13.880 Hello, hello, everybody. Welcome to Beyond checkout: 2 00:00:14.440 --> 00:00:16.600 where agentic commerce actually starts. 3 00:00:17.560 --> 00:00:21.520 Really great to see so many of you here today. My name is Darren Moore, 4 00:00:21.560 --> 00:00:25.380 and I lead agentic commerce at Klarna. And because of that, 5 00:00:26.460 --> 00:00:30.760 I have a lot of conversations every single day about agentic commerce. 6 00:00:30.820 --> 00:00:32.760 I read a lot about agentic commerce, 7 00:00:32.760 --> 00:00:35.280 and I'm sure many of you in this room do as well. 8 00:00:35.580 --> 00:00:38.460 So I'm not sure if you agree with me, but right now, 9 00:00:38.520 --> 00:00:42.720 the state of things is that there are very few absolute facts 10 00:00:43.540 --> 00:00:47.920 in agentic commerce, but there are a huge number of opinions, 11 00:00:48.280 --> 00:00:51.700 hypotheses, educated guesses. 12 00:00:52.260 --> 00:00:54.420 And that's what makes this space so exciting right now. 13 00:00:55.580 --> 00:00:58.340 We are seeing in real time this play out, 14 00:00:58.740 --> 00:01:02.120 validating what's actually going to work in the agentic commerce world. 15 00:01:03.180 --> 00:01:05.600 And I think that's what we love to see. 16 00:01:07.740 --> 00:01:09.480 So with that being said, 17 00:01:09.620 --> 00:01:14.220 some of what we're going to talk about today may sound like another opinion, 18 00:01:15.120 --> 00:01:17.340 but I hope that as we go through some of these slides, 19 00:01:17.400 --> 00:01:21.960 you will see that that's actually grounded in what we've learned so far about 20 00:01:22.280 --> 00:01:27.180 how agents actually behave when they are discovering products and when they are 21 00:01:27.240 --> 00:01:29.540 buying products on behalf of a consumer. 22 00:01:30.660 --> 00:01:34.220 So for those of you who managed to catch our theater talk yesterday, 23 00:01:34.400 --> 00:01:37.020 I promised a number. That number is still coming. 24 00:01:37.600 --> 00:01:40.240 I'm going to give you one number, one fix, 25 00:01:40.900 --> 00:01:43.360 and one fact to take home with you. 26 00:01:43.360 --> 00:01:43.360 "Discovery wins before checkout begins." This is what happens when you work 27 00:01:43.360 --> 00:01:43.360 closely with your marketing team. You get a good catchy slogan. 28 00:01:43.360 --> 00:01:43.360 Catchy and in this case, very, very true. 29 00:01:43.360 --> 00:01:43.360 "Discovery wins before checkout begins." So you might have caught this 30 00:01:43.360 --> 00:01:44.113 yesterday, but AI traffic is up 393% year-on-year. 31 00:02:06.080 --> 00:02:10.740 That comes from the AI Adobe report for 2026, from Q1. 32 00:02:12.280 --> 00:02:16.660 And alongside that, with all of those agents driving growth, 33 00:02:18.100 --> 00:02:22.800 66% of the product pages they are reading, they can't actually read at all. 34 00:02:23.100 --> 00:02:26.780 That means a third of your product pages are missing completely. 35 00:02:28.120 --> 00:02:28.953 So 36 00:02:30.040 --> 00:02:33.420 while the industry is focused on the problem of the checkout, 37 00:02:33.860 --> 00:02:36.980 Klarna is not only prepared and building for that, 38 00:02:37.480 --> 00:02:40.020 but building to solve the discovery layer. 39 00:02:40.720 --> 00:02:45.520 And what we're going to look at in a minute is the case of an actual 40 00:02:45.580 --> 00:02:50.540 merchant who not only are they one of those where a third of their 41 00:02:50.600 --> 00:02:54.260 product pages are not being read, but in fact, 42 00:02:54.360 --> 00:02:58.260 them alongside many, many other ecommerce merchants, 43 00:02:58.440 --> 00:02:59.520 have an even bigger problem, 44 00:03:00.080 --> 00:03:04.760 where the majority of their catalogs are not visible to AI agents today. 45 00:03:06.920 --> 00:03:11.420 Massive inventory, minimal visibility: not a good combination, 46 00:03:12.080 --> 00:03:16.660 especially if you are a major global activewear brand 47 00:03:17.160 --> 00:03:22.040 that has 160,000 products. Those products are in stock, live, 48 00:03:22.480 --> 00:03:24.860 being sold in a number of different Klarna markets, 49 00:03:25.520 --> 00:03:29.040 but only 10,000 of those are discoverable by AI agents. 50 00:03:29.860 --> 00:03:31.880 That seems like a very, very small number. 51 00:03:32.480 --> 00:03:36.340 Probably something that if that had to happen to anyone in this room, 52 00:03:36.720 --> 00:03:40.740 that would be something that you would be prioritizing the fix for right away. 53 00:03:42.300 --> 00:03:46.140 So now you ask yourself, how does this happen? 54 00:03:47.760 --> 00:03:52.720 How does a major global activewear brand with 160,000 products 55 00:03:53.180 --> 00:03:57.680 only have 10,000 products available and discoverable by AI 56 00:03:57.860 --> 00:03:58.693 agents? 57 00:03:59.880 --> 00:04:04.460 So if any of you are able to do fast math, definitely not me, 58 00:04:04.840 --> 00:04:07.980 that's 6%. That's a tiny, tiny number. 59 00:04:08.800 --> 00:04:10.360 And if we ask ourselves, 60 00:04:10.440 --> 00:04:15.180 why is only 6% of this global brand's catalog visible to AI 61 00:04:15.440 --> 00:04:19.700 agents? It comes down to, in this case, one thing, 62 00:04:20.420 --> 00:04:24.800 which is the GTIN. The GTIN is the Global Trade Item Number, 63 00:04:25.100 --> 00:04:27.440 which is basically the barcode on the box. 64 00:04:28.160 --> 00:04:32.800 It's a unique identifier that actually allows AI agents to 65 00:04:33.000 --> 00:04:37.440 reconcile your product listing against the same product sold by other 66 00:04:37.480 --> 00:04:40.240 retailers or other merchants. In this case, 67 00:04:41.140 --> 00:04:45.760 this brand has 0% coverage of the GTIN across all of their feeds. 68 00:04:46.500 --> 00:04:47.620 And for that reason, 69 00:04:48.620 --> 00:04:53.340 the AI agents are not able to confidently compare, 70 00:04:53.640 --> 00:04:57.820 rank, and recommend this product. Basically, 71 00:04:57.960 --> 00:04:58.793 they can't build, 72 00:04:58.820 --> 00:05:02.340 the AI agent cannot build what is sometimes referred to as the "product 73 00:05:02.340 --> 00:05:02.340 card"-the product card that allows an agent to confidently surface your product 74 00:05:02.340 --> 00:05:02.340 to actually allow it to be purchased. 75 00:05:02.340 --> 00:05:02.340 So that comes back to the previous slide that "discovery wins before checkout 76 00:05:02.340 --> 00:05:02.340 even begins." If you can't be found in this level, in this layer, 77 00:05:02.340 --> 00:05:03.093 your product doesn't ever have a chance of being purchased at all. 78 00:05:27.380 --> 00:05:32.380 And 79 00:05:32.380 --> 00:05:32.380 that's 80 00:05:32.380 --> 00:05:32.380 really 81 00:05:32.380 --> 00:05:32.380 why 82 00:05:32.380 --> 00:05:32.380 Klarna 83 00:05:32.380 --> 00:05:32.380 built 84 00:05:32.380 --> 00:05:32.380 the 85 00:05:32.380 --> 00:05:32.380 discovery 86 00:05:32.380 --> 00:05:32.380 layer 87 00:05:32.380 --> 00:05:32.380 that 88 00:05:32.380 --> 00:05:32.380 AI 89 00:05:32.380 --> 00:05:32.380 agents 90 00:05:32.380 --> 00:05:32.380 can 91 00:05:32.380 --> 00:05:32.380 actually 92 00:05:32.380 --> 00:05:32.380 query. 93 00:05:32.380 --> 00:05:32.380 One 94 00:05:32.380 --> 00:05:32.380 API 95 00:05:32.380 --> 00:05:32.380 normalized 96 00:05:32.380 --> 00:05:32.380 across 97 00:05:32.380 --> 00:05:32.380 merchants, 98 00:05:32.380 --> 00:05:32.380 LLM 99 00:05:32.380 --> 00:05:32.380 optimized 100 00:05:32.380 --> 00:05:32.380 and 101 00:05:32.380 --> 00:05:32.380 protocol 102 00:05:32.380 --> 00:05:32.380 agnostic. 103 00:05:32.380 --> 00:05:32.380 So 104 00:05:32.380 --> 00:05:32.380 what 105 00:05:32.380 --> 00:05:32.380 does 106 00:05:32.380 --> 00:05:32.380 this 107 00:05:32.380 --> 00:05:32.380 really 108 00:05:32.380 --> 00:05:32.380 mean? 109 00:05:32.380 --> 00:05:32.380 "One 110 00:05:32.380 --> 00:05:32.380 API" 111 00:05:32.380 --> 00:05:32.380 that 112 00:05:32.380 --> 00:05:32.380 allows 113 00:05:32.380 --> 00:05:32.380 agents 114 00:05:32.380 --> 00:05:32.380 to 115 00:05:32.380 --> 00:05:32.380 query 116 00:05:32.380 --> 00:05:32.380 the 117 00:05:32.380 --> 00:05:32.380 product 118 00:05:32.380 --> 00:05:32.380 graph, 119 00:05:32.380 --> 00:05:32.380 "normalized 120 00:05:32.380 --> 00:05:32.380 across 121 00:05:32.380 --> 00:05:32.380 merchants" 122 00:05:32.380 --> 00:05:32.380 means 123 00:05:32.380 --> 00:05:32.380 that 124 00:05:32.380 --> 00:05:32.380 we 125 00:05:32.380 --> 00:05:32.380 build 126 00:05:32.380 --> 00:05:32.380 a 127 00:05:32.380 --> 00:05:32.380 unique 128 00:05:32.380 --> 00:05:32.380 product-a 129 00:05:32.380 --> 00:05:32.380 unique, 130 00:05:32.380 --> 00:05:32.380 stable 131 00:05:32.380 --> 00:05:32.380 product 132 00:05:32.380 --> 00:05:32.380 entity-looking 133 00:05:32.380 --> 00:05:32.380 at 134 00:05:32.380 --> 00:05:32.380 the 135 00:05:32.380 --> 00:05:32.380 same 136 00:05:32.380 --> 00:05:32.380 product 137 00:05:32.380 --> 00:05:32.380 across 138 00:05:32.380 --> 00:05:32.380 different 139 00:05:32.380 --> 00:05:32.380 merchants 140 00:05:32.380 --> 00:05:32.380 and 141 00:05:32.380 --> 00:05:32.380 retailers, 142 00:05:32.380 --> 00:05:32.380 which 143 00:05:32.380 --> 00:05:32.380 allows 144 00:05:32.380 --> 00:05:32.380 the 145 00:05:32.380 --> 00:05:32.380 agent 146 00:05:32.380 --> 00:05:32.380 to 147 00:05:32.380 --> 00:05:32.380 do 148 00:05:32.380 --> 00:05:32.380 exactly 149 00:05:32.380 --> 00:05:32.380 that: 150 00:05:32.380 --> 00:05:32.380 to 151 00:05:32.380 --> 00:05:32.380 compare, 152 00:05:32.380 --> 00:05:32.380 rank, 153 00:05:32.380 --> 00:05:32.380 and 154 00:05:32.380 --> 00:05:32.380 recommend 155 00:05:32.380 --> 00:05:32.380 confidently. 156 00:05:32.380 --> 00:05:32.380 "Optimized 157 00:05:32.380 --> 00:05:32.380 for 158 00:05:32.380 --> 00:05:32.380 LLMs 159 00:05:32.380 --> 00:05:32.380 in 160 00:05:32.380 --> 00:05:32.380 real 161 00:05:32.380 --> 00:05:32.380 time," 162 00:05:32.380 --> 00:05:32.380 that 163 00:05:32.380 --> 00:05:32.380 means 164 00:05:32.380 --> 00:05:32.380 that 165 00:05:32.380 --> 00:05:32.380 it's 166 00:05:32.380 --> 00:05:32.380 structured 167 00:05:32.380 --> 00:05:32.380 JSON, 168 00:05:32.380 --> 00:05:32.380 which 169 00:05:32.380 --> 00:05:32.380 is 170 00:05:32.380 --> 00:05:32.380 built 171 00:05:32.380 --> 00:05:32.380 for 172 00:05:32.380 --> 00:05:32.380 AI 173 00:05:32.380 --> 00:05:32.380 consumption, 174 00:05:32.380 --> 00:05:32.380 not 175 00:05:32.380 --> 00:05:32.380 just 176 00:05:32.380 --> 00:05:32.380 for 177 00:05:32.380 --> 00:05:32.380 search 178 00:05:32.380 --> 00:05:32.380 indexing. 179 00:05:32.380 --> 00:05:32.380 And 180 00:05:32.380 --> 00:05:32.380 that 181 00:05:32.380 --> 00:05:32.380 means 182 00:05:32.380 --> 00:05:32.380 that 183 00:05:32.380 --> 00:05:32.380 when 184 00:05:32.380 --> 00:05:32.380 we 185 00:05:32.380 --> 00:05:32.380 have 186 00:05:32.380 --> 00:05:32.380 agents 187 00:05:32.380 --> 00:05:32.380 trying 188 00:05:32.380 --> 00:05:32.380 to 189 00:05:32.380 --> 00:05:32.380 do 190 00:05:32.380 --> 00:05:32.380 structured 191 00:05:32.380 --> 00:05:32.380 searches, 192 00:05:32.380 --> 00:05:32.380 natural 193 00:05:32.380 --> 00:05:32.380 language 194 00:05:32.380 --> 00:05:32.380 searches, 195 00:05:32.380 --> 00:05:32.380 and 196 00:05:32.380 --> 00:05:32.380 constrained 197 00:05:32.380 --> 00:05:32.380 searches-which 198 00:05:32.380 --> 00:05:32.380 is 199 00:05:32.380 --> 00:05:32.380 really 200 00:05:32.380 --> 00:05:32.380 the 201 00:05:32.380 --> 00:05:32.380 majority 202 00:05:32.380 --> 00:05:32.380 of 203 00:05:32.380 --> 00:05:32.380 real 204 00:05:32.380 --> 00:05:32.380 shopping 205 00:05:32.380 --> 00:05:32.380 intents 206 00:05:32.380 --> 00:05:32.380 today-that's 207 00:05:32.380 --> 00:05:32.380 what 208 00:05:32.380 --> 00:05:32.380 allows 209 00:05:32.380 --> 00:05:32.380 those 210 00:05:32.380 --> 00:05:32.380 agents 211 00:05:32.380 --> 00:05:32.380 to 212 00:05:32.380 --> 00:05:32.380 search 213 00:05:32.380 --> 00:05:32.380 the 214 00:05:32.380 --> 00:05:32.380 product 215 00:05:32.380 --> 00:05:32.380 graph 216 00:05:32.380 --> 00:05:32.380 and 217 00:05:32.380 --> 00:05:32.380 find 218 00:05:32.380 --> 00:05:32.380 that 219 00:05:32.380 --> 00:05:32.380 product 220 00:05:32.380 --> 00:05:32.380 confidently. 221 00:05:32.380 --> 00:05:32.380 And 222 00:05:32.380 --> 00:05:32.380 then 223 00:05:32.380 --> 00:05:32.380 of 224 00:05:32.380 --> 00:05:32.380 course, 225 00:05:32.380 --> 00:05:32.380 "protocol 226 00:05:32.380 --> 00:05:32.380 agnostic." 227 00:06:37.540 --> 00:06:40.560 I'm sure over the course of this week and probably the last couple of months, 228 00:06:40.700 --> 00:06:43.300 you've heard about ACP, UCP, 229 00:06:44.040 --> 00:06:47.360 and whichever other acronym is probably launched this morning. 230 00:06:48.500 --> 00:06:53.280 The good thing is that your product will be discovered in the product graph, 231 00:06:53.880 --> 00:06:56.180 through the Agentic Product Protocol, 232 00:06:56.980 --> 00:07:00.000 no matter which protocol is used for the payment. 233 00:07:00.540 --> 00:07:04.980 And this is already product discovery that's operating at scale with 100 million 234 00:07:05.080 --> 00:07:05.913 unique products, 235 00:07:06.340 --> 00:07:11.020 400 million merchant offers across 4,300 product subcategories, 236 00:07:11.580 --> 00:07:16.220 and with one million merchant partners. 237 00:07:16.220 --> 00:07:19.420 This graph really is what allows your products to be found. 238 00:07:20.060 --> 00:07:24.700 And this comes back to having the structured data and the rich quality 239 00:07:25.420 --> 00:07:30.060 in order to allow those agents to query and find your 240 00:07:30.120 --> 00:07:33.520 product. If your product is not in the product graph, 241 00:07:33.540 --> 00:07:37.480 and it doesn't have the GTIN and other structured attributes that make it 242 00:07:37.560 --> 00:07:38.393 discoverable, 243 00:07:40.020 --> 00:07:44.300 it's kind of the equivalent of being at Stripe Sessions, 244 00:07:44.680 --> 00:07:47.520 having the opportunity to connect with a lot of great people, 245 00:07:48.140 --> 00:07:51.400 but you don't realize you're invisible. No one can see you. 246 00:07:52.080 --> 00:07:53.560 Except in this case, 247 00:07:54.100 --> 00:07:58.340 the conference is a multitrillion dollar industry, 248 00:07:59.520 --> 00:08:02.780 and the people that you want to meet are AI shopping agents. 249 00:08:06.080 --> 00:08:08.960 So that brings us to what we've built with Stripe. 250 00:08:09.320 --> 00:08:13.240 We've already been talking about the fact that if today you're on Stripe with 251 00:08:13.380 --> 00:08:14.213 Klarna, 252 00:08:14.740 --> 00:08:18.540 the payment layer is already built with Klarna available within the Stripe 253 00:08:18.560 --> 00:08:19.393 Shared Payment Token. 254 00:08:20.160 --> 00:08:24.760 And what we're working towards is the full life cycle, 255 00:08:24.760 --> 00:08:28.720 where an agent will be able to query the product graph to find your product, 256 00:08:29.880 --> 00:08:33.040 get this Shared Payment Token to complete the payment, 257 00:08:33.480 --> 00:08:37.040 and then have the full Klarna life cycle for the 258 00:08:37.120 --> 00:08:39.560 post-purchase, all provided through the Stripe integration. 259 00:08:45.200 --> 00:08:49.560 Important to remember that when it comes to agentic flows, 260 00:08:51.400 --> 00:08:55.160 a declined transaction in agentic flow isn't the same as an abandoned cart. 261 00:08:55.480 --> 00:08:59.280 An abandoned cart, you can retarget, you can send an email, you can try again. 262 00:09:00.520 --> 00:09:05.000 That's very different when there's a failed experience in an agentic flow 263 00:09:05.120 --> 00:09:07.920 because that's something that a consumer might not recover from, 264 00:09:08.160 --> 00:09:11.760 at least not quickly. They might not trust that agent very quickly again, 265 00:09:12.080 --> 00:09:14.320 and that changes what agents optimize for. 266 00:09:15.200 --> 00:09:19.960 They optimize for consumer trust, payment flexibility, post-purchase liability, 267 00:09:20.080 --> 00:09:22.240 and approval certainty-in that order. 268 00:09:22.560 --> 00:09:26.280 And remembering that if your product can't be discovered, 269 00:09:26.640 --> 00:09:28.680 we don't get into this conversation at all. 270 00:09:31.480 --> 00:09:32.880 So I want to just 271 00:09:34.440 --> 00:09:39.320 finish off with three attributes that really unlock 272 00:09:39.440 --> 00:09:42.920 discoverability: GTIN, shipping costs, and delivery time. 273 00:09:43.720 --> 00:09:48.560 I point these out because these are what so many merchant catalogs 274 00:09:49.480 --> 00:09:53.140 are missing today, and they don't even know it. GTIN, 275 00:09:53.320 --> 00:09:55.300 you saw in the case study that I showed earlier on, 276 00:09:55.340 --> 00:09:59.840 that GTIN was zero across every feed, and that meant that the AI agent, 277 00:09:59.960 --> 00:10:01.400 when it was querying the graph, 278 00:10:01.560 --> 00:10:06.040 couldn't build the complete product card to be able to confidently recommend 279 00:10:06.200 --> 00:10:09.360 that product. That meant that the products were invisible to agents. 280 00:10:09.620 --> 00:10:12.360 No one could find it. Shipping costs, 281 00:10:12.420 --> 00:10:15.740 because agents actually rank on a total price. 282 00:10:16.160 --> 00:10:19.380 So if you're not giving a full picture to the agent and the consumer, 283 00:10:19.940 --> 00:10:23.180 your product won't be picked. And then finally, delivery time, 284 00:10:23.560 --> 00:10:27.600 because when I tell my agent that I need these running shoes by Friday, 285 00:10:28.600 --> 00:10:31.830 unless that data is part of my feed and I'm providing that to 286 00:10:33.440 --> 00:10:34.600 where the agent is querying, 287 00:10:36.080 --> 00:10:38.940 I'm not going to be included in any time-constrained queries, 288 00:10:39.500 --> 00:10:40.980 which let's be honest, 289 00:10:41.140 --> 00:10:45.520 is the part of all of major searching queries today. 290 00:10:46.820 --> 00:10:51.780 So fixing these three is what allows your product catalog to be 291 00:10:51.980 --> 00:10:55.820 answerable by the majority of searching intents today. 292 00:10:56.460 --> 00:10:57.260 Fantastic. 293 00:10:57.260 --> 00:11:02.000 So now that we've had a chat about the discovery layer and how important 294 00:11:02.040 --> 00:11:05.760 discovery is in order to even get into the payment conversation, 295 00:11:07.120 --> 00:11:11.220 I'm really happy to dive into the payment layer. And to do that, 296 00:11:11.600 --> 00:11:16.240 I'm super pleased to have Allison Xu with me today from Stripe, 297 00:11:16.560 --> 00:11:20.120 who's an agentic commerce lead. Allison, please join us on the 298 00:11:20.160 --> 00:11:25.160 stage. 299 00:11:26.760 --> 00:11:28.760 Have a seat. 300 00:11:28.760 --> 00:11:28.760 Awesome. 301 00:11:29.100 --> 00:11:32.760 Cool. So maybe we can start off, I had the chance to introduce myself. 302 00:11:32.840 --> 00:11:35.900 So maybe you can introduce yourself to the people out here. 303 00:11:36.200 --> 00:11:38.340 Happy to. Hi, everyone. I'm Allison. 304 00:11:38.440 --> 00:11:41.640 I work on the agentic commerce product team at Stripe. 305 00:11:42.040 --> 00:11:44.820 I've been working on agentic commerce for about a year now, 306 00:11:45.240 --> 00:11:48.940 which is really fun to say because that's basically the entirety of how long 307 00:11:48.960 --> 00:11:52.300 we've been thinking about it. A year ago, that was not a team. 308 00:11:52.420 --> 00:11:55.260 And now at Stripe, as you can see across all of Sessions, 309 00:11:56.080 --> 00:11:59.680 it is very much a dedicated team and effort across the whole company, 310 00:12:00.140 --> 00:12:02.120 so it's been really fun to watch the evolution. 311 00:12:02.800 --> 00:12:03.633 Cool. 312 00:12:04.420 --> 00:12:08.980 And have you enjoyed all the agentic commerce talk so far at Stripe Sessions? 313 00:12:09.860 --> 00:12:11.740 If you didn't want to hear about agentic commerce, 314 00:12:11.800 --> 00:12:14.980 this was not the event to come to, I would say. 315 00:12:15.280 --> 00:12:18.540 So let's dive in with another one. So I mean, 316 00:12:18.980 --> 00:12:23.460 really what we want to talk about is a couple of things to really dive into how 317 00:12:23.480 --> 00:12:27.360 the payment infrastructure works for agentic commerce and what we can tell 318 00:12:27.680 --> 00:12:31.020 merchants and users about how to take advantage of that. 319 00:12:31.360 --> 00:12:36.240 So let's start off with the basics of the Shared Payment Token. I mean, 320 00:12:36.820 --> 00:12:40.860 the Shared Payment Token is what really powers the agentic flows in a Stripe 321 00:12:40.880 --> 00:12:45.540 context. So maybe tell us a little bit about how you thought about, 322 00:12:45.640 --> 00:12:46.473 how Stripe thought about, 323 00:12:46.500 --> 00:12:51.040 building that-especially when it comes to plugging in different payment methods 324 00:12:51.080 --> 00:12:53.400 and making that seamless from a user perspective. 325 00:12:53.720 --> 00:12:56.460 Totally. If you attended my talk yesterday, 326 00:12:56.520 --> 00:12:59.300 this might sound a little repetitive, but just taking a step back. 327 00:13:00.280 --> 00:13:03.700 So why Shared Payment Tokens and why do they need to exist? 328 00:13:04.260 --> 00:13:07.060 In a traditional payment, I, as a buyer, 329 00:13:07.120 --> 00:13:10.540 would go to a seller and give them my payment credentials, 330 00:13:10.660 --> 00:13:15.540 and that seller is the one who processes the payment. Now with agentic payments, 331 00:13:16.200 --> 00:13:20.220 the key difference here is that that payment intent is being separated from the 332 00:13:20.240 --> 00:13:23.040 payment processing. So I, as a buyer, 333 00:13:23.180 --> 00:13:26.860 would tell an agent-let's use ChatGPT, Copilot, 334 00:13:26.920 --> 00:13:31.400 any of these-that I want to buy a dress, for example, from, let's say, 335 00:13:32.060 --> 00:13:34.560 Anthropologie. And Anthropologie, the seller, 336 00:13:34.640 --> 00:13:37.920 is still the one that needs to process that payment, 337 00:13:39.520 --> 00:13:43.800 not the agent. And so that credential needs to be handed off. 338 00:13:45.000 --> 00:13:49.820 Now you could pass raw card numbers and probably break a lot of rules and 339 00:13:50.060 --> 00:13:52.740 PCI compliance, and you wouldn't like that. And so, therefore, 340 00:13:52.740 --> 00:13:52.740 we created the Shared Payment Token to be able to manage that handoff between 341 00:13:52.740 --> 00:13:52.740 agent and seller. Now one question I often get is, 342 00:13:52.740 --> 00:13:52.873 "The idea of tokenization is not new. We've been-". 343 00:14:05.400 --> 00:14:06.440 We've had tokens forever. 344 00:14:06.600 --> 00:14:07.433 Absolutely. 345 00:14:08.020 --> 00:14:12.880 And I think what's important to know is Shared Payment Tokens work with existing 346 00:14:12.960 --> 00:14:17.520 tokens, with existing network tokens, with existing device tokens, 347 00:14:18.080 --> 00:14:23.060 Klarna tokens. And you can... The best analogy I like to think of, 348 00:14:23.620 --> 00:14:27.440 every time I think of an SPT, I think of a little package being delivered. 349 00:14:27.580 --> 00:14:30.920 So like the agent has a home, and the seller has a home. 350 00:14:30.920 --> 00:14:34.220 And the agent has a payment credential and a payment method, 351 00:14:34.320 --> 00:14:38.780 and they wrap it up in this box-and that box is the Shared Payment Token-and 352 00:14:38.960 --> 00:14:42.260 they wrap it up and they write, "It's going to X, Y, Z, 353 00:14:42.460 --> 00:14:47.060 and it needs to be delivered in this amount of time." And so that's the kind of 354 00:14:47.300 --> 00:14:49.100 special part of the Shared Payment Token. 355 00:14:49.160 --> 00:14:52.720 You're able to scope it to a specific seller, a specific time, 356 00:14:53.210 --> 00:14:58.130 and then you issue that to the seller. And the seller, at that time, 357 00:14:58.190 --> 00:15:02.310 when they receive it, can open it up and they can say, "I like what I see. 358 00:15:02.470 --> 00:15:06.450 I'm going to process this payment." And they grant that token. 359 00:15:06.450 --> 00:15:09.200 Or they can decide not to based... 360 00:15:09.730 --> 00:15:12.270 If you're working with Stripe and you work with Radar, 361 00:15:12.370 --> 00:15:15.930 we can give you risk signals and risk scores. And so again, 362 00:15:15.990 --> 00:15:20.950 there is kind of that added control or variability for a 363 00:15:21.030 --> 00:15:25.690 seller to decide whether to process that payment. So all of that to say, 364 00:15:26.190 --> 00:15:29.530 again, payment intent being separated from the actual payment, 365 00:15:30.310 --> 00:15:34.790 we are still working with the underlying payment methods and tokens to enable 366 00:15:34.810 --> 00:15:35.090 that. 367 00:15:35.090 --> 00:15:39.850 So it's great that we very recently announced the Klarna partnership to 368 00:15:40.150 --> 00:15:44.270 be able to support SPTs with Klarna. Initially, 369 00:15:44.350 --> 00:15:49.270 when we launched-Stripe has over a hundred payment methods-when we launched 370 00:15:49.290 --> 00:15:50.090 Shared Payment Tokens, 371 00:15:50.090 --> 00:15:52.590 it supported cards only. And so we are slowly building that up, 372 00:15:53.470 --> 00:15:54.303 actually not so slowly, 373 00:15:54.450 --> 00:15:58.370 but quickly building that up to support more and more different payment methods 374 00:15:58.430 --> 00:16:02.510 so that a consumer-regardless of whether it's an agentic payment or a 375 00:16:03.130 --> 00:16:06.770 nonagentic payment- still sees the same payment interface and can kind of 376 00:16:06.850 --> 00:16:10.590 decide, or the agent can see it and decide, which one they want to use. 377 00:16:12.070 --> 00:16:13.050 Cool. And I mean, 378 00:16:13.150 --> 00:16:17.550 I think the important thing there probably is what often 379 00:16:17.630 --> 00:16:19.670 concerns merchants and sellers, 380 00:16:20.050 --> 00:16:23.230 which is like a loss of control in an agentic context. 381 00:16:23.890 --> 00:16:27.470 So I like what you said there about the fact that ultimately it's still up to 382 00:16:27.510 --> 00:16:28.343 the merchant. 383 00:16:28.730 --> 00:16:32.890 It's up to the seller if they want to accept and process that Shared Payment 384 00:16:32.890 --> 00:16:36.230 Token, which means that the control still stays in the merchant's hands. 385 00:16:36.290 --> 00:16:37.123 Exactly. 386 00:16:37.370 --> 00:16:42.070 So this is actually a question that I touched on in one of the slides earlier 387 00:16:42.150 --> 00:16:44.590 on, when it comes to what agents optimize for. 388 00:16:44.970 --> 00:16:48.350 I was really curious to hear your thoughts on that as well, 389 00:16:49.150 --> 00:16:52.190 considering that obviously you guys have been working with a couple of different 390 00:16:52.270 --> 00:16:56.310 agents and maybe seeing some early signs about what we can expect. 391 00:16:57.310 --> 00:16:58.910 So what can you tell us about that? 392 00:16:59.310 --> 00:17:03.990 Totally. So caveat this by saying we're still very early, 393 00:17:04.330 --> 00:17:09.290 and so we are very closely monitoring trends and behaviors of how 394 00:17:09.430 --> 00:17:11.890 agents behave differently than humans. 395 00:17:13.090 --> 00:17:16.290 And early in a number of different dimensions: one, of course, 396 00:17:16.390 --> 00:17:19.430 just transaction volume. Stripe processes, 397 00:17:19.810 --> 00:17:22.410 I think the latest number was 1.9 trillion. 398 00:17:22.890 --> 00:17:25.690 We are not at 1.9 trillion in agentic payments volume, 399 00:17:26.170 --> 00:17:27.390 in case you didn't know that. 400 00:17:28.150 --> 00:17:28.630 Not yet. 401 00:17:28.630 --> 00:17:33.390 Not yet, exactly. But also in the number of, let's say, 402 00:17:33.670 --> 00:17:36.370 options shown at checkout. Again, as I just alluded to, 403 00:17:36.570 --> 00:17:39.530 we have a hundred plus payment methods typically supported 404 00:17:41.370 --> 00:17:42.203 by Stripe Payments, 405 00:17:42.390 --> 00:17:45.740 and we're at a little bit less than a dozen today for the SPT. 406 00:17:46.050 --> 00:17:50.930 So with a limited kind of option set or limited menu today, 407 00:17:50.980 --> 00:17:55.330 I think we're also kind of learning even with this kind of like smaller pool, 408 00:17:55.930 --> 00:17:59.950 how those behaviors differ. But I think that will continue to evolve, of course, 409 00:18:00.110 --> 00:18:04.290 as the option sets increase. And then I think the other thing is 410 00:18:05.390 --> 00:18:07.850 at the stage where we are in the market today, 411 00:18:08.870 --> 00:18:10.890 particularly in consumer use cases, 412 00:18:10.950 --> 00:18:15.130 we're largely still seeing human-in-the-loop transactions. 413 00:18:16.070 --> 00:18:18.470 And for the near term, 414 00:18:18.550 --> 00:18:22.350 I think we're already starting to see B2B use cases emerge where there isn't a 415 00:18:22.430 --> 00:18:27.210 human-in-the-loop. You saw some of those demos yesterday. But for consumer, 416 00:18:27.630 --> 00:18:30.250 I think that's important to know because 417 00:18:31.950 --> 00:18:33.480 I actually think the agent is quite... 418 00:18:34.310 --> 00:18:37.650 The things the agent cares about are actually quite aligned with the consumer. 419 00:18:38.390 --> 00:18:39.840 The agent wants a... 420 00:18:42.690 --> 00:18:46.350 Let's say they're thinking about the financial impact of a transaction. Well, 421 00:18:46.490 --> 00:18:48.170 I care too. I look at fees. 422 00:18:48.950 --> 00:18:53.830 They care about payment success and payment flexibility, and the human cares. 423 00:18:54.670 --> 00:18:59.610 And there are a lot of maybe implicit decisions that a human 424 00:18:59.670 --> 00:19:03.530 when they get to a checkout page is kind of making. 425 00:19:03.530 --> 00:19:05.390 I'm choosing my payment methods based on habit, 426 00:19:05.910 --> 00:19:09.090 but that habit is because I know the fees, I know the-. 427 00:19:09.350 --> 00:19:10.290 Because it's worked before. 428 00:19:10.430 --> 00:19:12.370 It's worked before. Exactly. And it's trusted. 429 00:19:12.890 --> 00:19:16.530 And I think that the agents will care about really similar things as well. 430 00:19:17.850 --> 00:19:22.010 And particularly as we move away or kind of 431 00:19:22.810 --> 00:19:25.090 graduate from fully human-in-the-loop, 432 00:19:25.970 --> 00:19:28.990 I still think we'll have human guardrails. For example, 433 00:19:29.950 --> 00:19:34.350 I can tell my agent to work within a budget or work within a certain 434 00:19:35.270 --> 00:19:39.210 set of payment methods, or I want this to go through in this amount of time, 435 00:19:39.610 --> 00:19:43.030 and that, by default, will kind of limit the number of options. 436 00:19:43.090 --> 00:19:47.030 So I still think there will be a world where we get to set the guardrails and 437 00:19:47.050 --> 00:19:50.770 then, within there, have agents make more microdecisions, 438 00:19:50.830 --> 00:19:53.850 and we're going to closely monitor what those look like as we get to more 439 00:19:54.070 --> 00:19:54.910 autonomous payments. 440 00:19:56.390 --> 00:19:57.223 Yeah. Coming soon. 441 00:19:58.490 --> 00:20:02.290 So then I think what probably many people in the room are interested in, 442 00:20:02.670 --> 00:20:05.690 especially those that are merchants or sellers, is: 443 00:20:06.630 --> 00:20:10.990 what is the merchant experience when it comes to activating agentic flows 444 00:20:11.630 --> 00:20:16.610 through Stripe? I mean, I, myself, have spoken about how easy it is. 445 00:20:17.670 --> 00:20:22.530 So what are the things that you actually need to do if I'm processing with 446 00:20:22.550 --> 00:20:23.383 Stripe today? 447 00:20:23.490 --> 00:20:24.323 Yeah. 448 00:20:44.330 --> 00:20:44.330 Our motto at Stripe more generally is like we-this is not an official motto, 449 00:20:44.330 --> 00:20:44.330 by the way, but more of a philosophy-is like, 450 00:20:44.330 --> 00:20:44.330 "We want to do the grungy work so that our users can really focus on what they 451 00:20:44.330 --> 00:20:44.330 do best." And so that same mentality applies to the agentic world, 452 00:20:44.330 --> 00:20:49.210 where we are building what we call the Agentic Commerce Suite to be that 453 00:20:49.430 --> 00:20:54.190 infrastructure layer to do some of that grungy work that you guys shouldn't have 454 00:20:54.230 --> 00:20:54.930 to do. 455 00:20:54.930 --> 00:20:59.810 And so that spans across the kind of checkout 456 00:21:00.050 --> 00:21:03.570 lifespan, across discovery, checkout, fraud, and payments. 457 00:21:04.070 --> 00:21:08.990 And for a Stripe user, we are trying to make it as easy lift as possible. 458 00:21:09.050 --> 00:21:11.150 So we call it our, internally, we call it the "turnkey integration" 459 00:21:12.770 --> 00:21:17.430 because it is meant to be turnkey with all of the existing Stripe components and 460 00:21:17.470 --> 00:21:18.170 elements. 461 00:21:18.170 --> 00:21:22.290 I think the biggest lift probably is actually what you've spent the kind of 462 00:21:22.310 --> 00:21:26.990 first half of this talk talking about, which is discovery. For discovery, 463 00:21:27.390 --> 00:21:28.510 this is kind of a newer motion, 464 00:21:29.030 --> 00:21:33.540 where merchants can upload product catalogs or using... 465 00:21:34.290 --> 00:21:37.530 It could be as simple as a CSV, it could be our import APIs, 466 00:21:37.610 --> 00:21:38.750 but also importantly, 467 00:21:39.510 --> 00:21:43.410 we're opening to an ecosystem of commerce partners or catalog syndication 468 00:21:43.450 --> 00:21:47.770 partners so that you can take your existing stack and just plug it in, 469 00:21:47.770 --> 00:21:51.430 rather than having to reconfigure it. On the checkout side, 470 00:21:53.050 --> 00:21:55.890 again, we work with Checkout elements. 471 00:21:56.710 --> 00:22:00.750 The payment methods shown are the same payment methods that a merchant is 472 00:22:00.770 --> 00:22:03.050 already configuring in their Stripe Dashboard. 473 00:22:03.130 --> 00:22:06.490 And so all of that translates if you have enabled Klarna, 474 00:22:06.710 --> 00:22:09.550 it is already enabled in your agentic flows. 475 00:22:10.790 --> 00:22:13.930 And on the merchant, or I should say on the agent side, 476 00:22:14.790 --> 00:22:19.310 delegated Checkout API, which is the agent-facing UI, 477 00:22:20.330 --> 00:22:23.550 is actually already... It's also built on Stripe Checkout elements. 478 00:22:23.670 --> 00:22:28.110 And so all of those payment methods will dynamically show by default. 479 00:22:28.870 --> 00:22:31.890 And then fraud, if you were working with Stripe Radar, 480 00:22:33.480 --> 00:22:38.190 will also port over, and of course, Stripe Payments, 481 00:22:38.610 --> 00:22:42.830 if you're a Stripe Payments user, it will also be seamless. 482 00:22:42.990 --> 00:22:45.430 So we've really built it so that, for a Stripe user, 483 00:22:45.590 --> 00:22:48.430 it can be as low lift as possible. 484 00:22:49.250 --> 00:22:49.590 Yeah. I mean, 485 00:22:49.590 --> 00:22:54.130 what I'm hearing is that if I'm on Stripe and I already have Klarna for normal 486 00:22:54.250 --> 00:22:55.083 ecommerce, 487 00:22:55.530 --> 00:23:00.230 bringing that over to my agentic flows is a very small lift. 488 00:23:01.190 --> 00:23:02.023 It's no lift. 489 00:23:02.610 --> 00:23:03.670 Even better, even better. 490 00:23:04.150 --> 00:23:04.983 Exactly. 491 00:23:05.230 --> 00:23:10.070 So now that we've kind of nailed down how easy it 492 00:23:10.170 --> 00:23:11.450 is to activate, 493 00:23:12.970 --> 00:23:17.650 let's look a little bit more into the future and think 494 00:23:17.690 --> 00:23:19.310 about what are 495 00:23:20.970 --> 00:23:24.370 the most important thing that you think right now-considering that we are still 496 00:23:24.390 --> 00:23:28.730 at such an early stage-what's the most important thing that's still being built, 497 00:23:29.690 --> 00:23:30.810 or what are you excited about? 498 00:23:31.050 --> 00:23:31.883 Totally. 499 00:23:31.890 --> 00:23:36.350 This is really hard because there's so many things that we are building and need 500 00:23:36.390 --> 00:23:37.290 to be built still. 501 00:23:37.430 --> 00:23:38.510 You can even have more than one. 502 00:23:41.330 --> 00:23:43.590 And again, walking through the transaction life cycle, 503 00:23:43.710 --> 00:23:46.970 I kind of mentioned discovery, checkout, fraud, payments. 504 00:23:47.130 --> 00:23:51.010 There is a whole lot of things that happen beyond the payments and 505 00:23:51.050 --> 00:23:55.710 post-checkout. And we are still early in actively building those today. 506 00:23:55.790 --> 00:23:59.970 And so I'm very excited about how do you complete that visibility across the 507 00:24:00.050 --> 00:24:03.510 end-to-end life cycle. But I would also say, taking a step back, 508 00:24:04.630 --> 00:24:09.290 the thing that spans across the entire transaction life cycle and not just 509 00:24:09.710 --> 00:24:12.210 one part of it, to me, is identity. 510 00:24:13.310 --> 00:24:17.150 We are already doing some things to make sure 511 00:24:18.090 --> 00:24:21.130 transactions are secure. We verify agent identity, 512 00:24:21.590 --> 00:24:25.610 we verify merchant identity, we are doing transactional monitoring; 513 00:24:25.990 --> 00:24:30.750 so we feel good that we are still making a secure transaction, 514 00:24:31.350 --> 00:24:35.690 but I think there's so many more sophisticated things that we could be doing on 515 00:24:35.750 --> 00:24:39.480 top with identity. Can we link your... 516 00:24:40.070 --> 00:24:42.430 If I know an agent is Darren's agent, 517 00:24:42.850 --> 00:24:45.870 can I personalize the experience more 518 00:24:47.590 --> 00:24:50.810 towards your preferences, both from a discovery standpoint, 519 00:24:50.870 --> 00:24:55.830 but also I know which payment methods you like to use and configure 520 00:24:55.850 --> 00:24:57.710 the checkout. And also, 521 00:24:57.770 --> 00:25:02.370 can I link it to-Darren has accounts at XYZ 522 00:25:03.230 --> 00:25:06.690 services or retailers-and can we link all of that loyalty? 523 00:25:06.870 --> 00:25:09.150 Can we link all of your existing services together? 524 00:25:09.630 --> 00:25:12.990 I think there's a really powerful world where 525 00:25:14.410 --> 00:25:19.230 agent identity and the human behind that agent are more closely linked 526 00:25:19.450 --> 00:25:20.283 and 527 00:25:21.530 --> 00:25:26.230 are more threaded across experiences rather than every 528 00:25:26.290 --> 00:25:29.870 experience being a new one. I think if you saw the keynote, 529 00:25:30.290 --> 00:25:34.770 we just launched Link CLI Wallet and Stripe Projects. 530 00:25:34.830 --> 00:25:39.610 And I think we're starting to see this idea of like a developer identity really 531 00:25:40.090 --> 00:25:41.470 emerge in the B2B world. 532 00:25:41.530 --> 00:25:45.350 And I'm just really excited to kind of use those concepts and bring that to the 533 00:25:45.650 --> 00:25:46.530 consumer world as well. 534 00:25:47.530 --> 00:25:48.363 Cool. I mean, 535 00:25:48.690 --> 00:25:53.490 I think fully agree on both of those points because what we've seen, 536 00:25:53.590 --> 00:25:56.410 I think, is something that, post-purchase, 537 00:25:56.430 --> 00:26:01.210 is something that merchants and sellers potentially haven't fully caught 538 00:26:01.290 --> 00:26:06.270 onto how important it will be for agentic flows when it comes to full 539 00:26:06.310 --> 00:26:10.230 transparency in the pos-purchase life cycle-how returns, disputes, 540 00:26:10.290 --> 00:26:11.290 tracking is handled, 541 00:26:11.750 --> 00:26:16.530 and how much that's going to play into getting recommended again for this 542 00:26:16.610 --> 00:26:17.370 agent, right? 543 00:26:17.370 --> 00:26:20.090 And by the way, I mean, I think that's one of the... As, 544 00:26:20.730 --> 00:26:25.670 we're at a Klarna talk, but when we're thinking about payment methods, 545 00:26:26.290 --> 00:26:28.490 that's one of those things that's like really important and kind of 546 00:26:28.530 --> 00:26:31.170 differentiates certain payment methods. Klarna, for example, 547 00:26:31.330 --> 00:26:35.690 has dispute and return management in the app and more 548 00:26:36.010 --> 00:26:37.950 post-purchase visibility in the app. 549 00:26:38.050 --> 00:26:42.090 So as I think both in the way that consumers appreciate that, 550 00:26:42.170 --> 00:26:47.070 I think the agents will appreciate that data transparency pre- and 551 00:26:47.170 --> 00:26:48.190 post-purchase. 552 00:26:49.190 --> 00:26:49.550 No, 100%. 553 00:26:49.550 --> 00:26:50.383 Shout out to Klarna. 554 00:26:53.050 --> 00:26:57.330 And I think then also to touch on the identity, that's probably, 555 00:26:57.870 --> 00:26:59.330 especially on the account linking side, 556 00:26:59.390 --> 00:27:03.510 that's probably one of the things in our conversations with merchants and 557 00:27:03.550 --> 00:27:04.383 sellers so far, 558 00:27:05.350 --> 00:27:10.090 that's a theme that's come across really clearly in terms of the fact that 559 00:27:11.050 --> 00:27:14.010 they have this established relationship with a consumer, 560 00:27:14.390 --> 00:27:18.090 which includes that consumer's preferences, their discounts, 561 00:27:18.810 --> 00:27:22.490 special rates when it comes to shipping, and they don't want to let go of that, 562 00:27:22.550 --> 00:27:27.150 right? Rightly so. It's taken time to develop that relationship. 563 00:27:27.750 --> 00:27:32.670 And I think solving the account linking challenge is what will allow them to 564 00:27:32.710 --> 00:27:37.690 really bring that rich experience and the personalization into agentic flows as 565 00:27:37.710 --> 00:27:37.890 well. 566 00:27:37.890 --> 00:27:38.430 Absolutely. 567 00:27:38.430 --> 00:27:42.890 That's probably one of the number one pieces of pushback we hear from merchants 568 00:27:42.990 --> 00:27:45.310 when we're talking about agentic commerce, which is: 569 00:27:45.690 --> 00:27:50.250 how do I maintain that relationship with my customer? 570 00:27:50.370 --> 00:27:53.570 How do I track that relationship with the customer over time? 571 00:27:53.630 --> 00:27:56.470 And account linking, of course, is going to be really important. 572 00:27:57.070 --> 00:28:01.870 100%. I think it almost becomes like a table stakes at some point. 573 00:28:01.930 --> 00:28:02.763 Totally. 574 00:28:04.210 --> 00:28:08.350 So then I think to kind of round this off, 575 00:28:08.790 --> 00:28:10.410 because we've gotten now, I think, 576 00:28:10.510 --> 00:28:14.570 a really good view of how the Shared Payment Token works, 577 00:28:15.030 --> 00:28:17.850 how easy it is to switch that on for Klarna, 578 00:28:18.390 --> 00:28:20.110 for merchants who currently have both, 579 00:28:20.670 --> 00:28:24.710 who want to get involved in agentic flows, and also what's coming next. 580 00:28:26.170 --> 00:28:30.210 If, to some of the merchants and sellers in this room especially, 581 00:28:31.830 --> 00:28:34.950 if you're to give them some advice walking out of this room today, 582 00:28:35.370 --> 00:28:39.530 very excited about the traffic that's being driven through agentic flows, 583 00:28:39.950 --> 00:28:44.440 the conversion swing from like 38% worse to 42% 584 00:28:45.030 --> 00:28:48.890 better, if they want to take advantage of that 80-point swing, 585 00:28:50.150 --> 00:28:53.850 what should they do walking out of this room today, in the next weeks? 586 00:28:54.370 --> 00:28:58.010 Yeah. I think it depends on, I guess, 587 00:28:58.230 --> 00:29:02.410 the level of maturity of the conversations that you're already having. 588 00:29:02.490 --> 00:29:05.410 But to me, I see it as like two tracks, 589 00:29:05.830 --> 00:29:10.470 which is like business decisions and then technical decisions. I think, first, 590 00:29:10.470 --> 00:29:13.090 you have to really have those business decisions internally. 591 00:29:13.230 --> 00:29:17.550 So I hope Stripe Sessions has given you a really kind of well-rounded view of 592 00:29:17.610 --> 00:29:18.790 where we see the market going. 593 00:29:18.850 --> 00:29:21.570 And I think understanding what does success look like? 594 00:29:22.590 --> 00:29:25.730 What is the first way you want to dip your toe into agentic? 595 00:29:25.790 --> 00:29:30.450 Is it a small number of SKUs? Is it a full catalog? Is it one of your brands, 596 00:29:30.450 --> 00:29:34.850 if you have a portfolio? Kind of look at what that looks like internally. 597 00:29:34.970 --> 00:29:37.870 And then there's the technical front, which is, 598 00:29:39.650 --> 00:29:43.430 what does your product catalog look like today-and have a real honest 599 00:29:43.450 --> 00:29:47.330 conversation-or is it structured? Do you have very clear attributes? 600 00:29:48.190 --> 00:29:51.710 Is your commerce stack or are your endpoints ready to be connected to an agent? 601 00:29:52.610 --> 00:29:54.430 All of the kind of just up and down the stack, 602 00:29:54.490 --> 00:29:58.450 do you have the right fraud systems in place? Now, 603 00:29:58.510 --> 00:30:03.470 if you're on-this is a shameless plug-but if you're on Stripe Radar and 604 00:30:03.530 --> 00:30:05.570 Checkout elements and all of that, 605 00:30:06.350 --> 00:30:09.470 we think that the answer is you're pretty much there already, 606 00:30:10.150 --> 00:30:13.710 and with the agentic commerce suite, can get there very soon. But if not, 607 00:30:13.770 --> 00:30:17.310 always happy to have conversations and help our merchants get there. 608 00:30:18.950 --> 00:30:23.550 Yeah. And I just want to double up on the product and catalog data point. 609 00:30:24.490 --> 00:30:26.690 And if you want to talk further about that, 610 00:30:27.650 --> 00:30:30.510 please come find us at the Klarna booth later. 611 00:30:31.440 --> 00:30:34.840 But other than that, thank you so much, Allison, 612 00:30:34.960 --> 00:30:37.460 for talking us through a lot of these things. 613 00:30:37.460 --> 00:30:37.760 Thank you. 614 00:30:37.760 --> 00:30:41.880 It was really great to hear about how Stripe is thinking about these things 615 00:30:42.220 --> 00:30:45.480 because I think it resonates so much with how we've been building towards, 616 00:30:45.540 --> 00:30:49.260 which is obviously why we've been working so closely on this for quite some 617 00:30:49.300 --> 00:30:51.160 time. And thanks everybody for coming. 618 00:30:51.710 --> 00:30:51.950 Thanks.