A future where we buy with AI agents feels inevitable. Making it actually work is another story. The moment agents meet live product catalogs, inventory, fraud systems, and customer support queues, sellers quickly run into a long list of real-world edge cases to solve for. 

Over the past six months, we launched the Agentic Commerce Protocol (ACP), an open checkout specification that lets buyers, AI agents, and sellers transact through APIs; introduced a complete agentic solution with the Agentic Commerce Suite; integrated businesses such as Etsy and URBN; and powered AI shopping experiences across agents. That’s given us an insider’s view into what matters in production, from the unglamorous integration work to the failure modes we’ve seen early adopters grapple with.

These lessons from the first generation of agentic commerce are meant to help sellers decide what to tackle first, avoid common bottlenecks, and be proactive about what’s coming.

Your product catalog is the entry point to agents, but different AI agents want your data in different formats. One needs an SFTP file drop. Another wants a custom API integration. A third has its own feed spec entirely. We’ve seen brands reformat the same product catalog in six different ways to get listed across multiple AI agents. It creates an ongoing maintenance burden that’s a drag on time and resources. 

We’ve heard frustration from sellers about having to build (and rebuild) custom integrations for every agent. It’s why we designed the Agentic Commerce Suite: to prevent catalog fragmentation and support the full transaction lifecycle, from discovery to checkout. Upload your product catalog data to Stripe, and we syndicate it across supported agents. No duplicate work or reformatting required.  

In practice, getting “ingestion-ready” product data is what determines whether you show up reliably across agent surfaces.

Formatting your catalog is the starting point. Sellers are also increasingly focused on avoiding data lag. When a potential customer is looking at a specific product in an agentic channel, the agent needs to verify it’s in stock right now, not 15 minutes ago. One platform recently asked us if inventory verification happens down to the millisecond, underscoring how close to real time agents must confirm availability before showing customers a checkout option. 

This gets even more complicated when you add variants to the mix, which are difficult to format in a way that agents can reliably understand. Take a shirt where the shopper can choose a size, a color, and even add custom embroidery. Or consider a sneaker in 14 different colorways, each with its own size availability. In cases like these, agents will need real-time checks to confirm that a specific item or combination is actually in stock, or to know when to prompt the customer with alternative options. 

We worked with partners like OpenAI to stress-test the ACP against market complexity. With your Stripe-hosted ACP endpoint (via the Agentic Commerce Suite), you can share availability with AI agents in the checkout API call. As agentic commerce scales, real-time systems will be key for customer trust and brand reputation.

Since we codeveloped ACP with OpenAI in September 2025, we’ve shipped four releases and added payment handlers, scoped tokens, extensions (starting with discounts), built-in buyer auth, and native MCP transport. That protocol work is important, but sellers can’t afford to rebuild their stack every time a protocol changes. We built the Agentic Commerce Suite as a protocol-agnostic commerce layer that works across standards, including Google’s UCP, so sellers don’t have to bet their roadmap on any single spec. 

The businesses we talk to are wary of building zombie integrations: something they ship for a specific AI agent that becomes obsolete six months later after a strategic pivot. Unless you want to staff a team dedicated to tracking protocol changes, you need a partner that can absorb that volatility. Integrate with Stripe once, and we’ll keep you compatible across agents as protocols evolve.

One key link between agents and existing payment rails is the token layer. To enable agentic transactions, the Agentic Commerce Suite handles and processes Shared Payment Tokens (SPTs), a payment primitive built for agentic commerce that allows agents to initiate payments with a buyer’s permission and preferred payment method, without exposing credentials. For many retailers, especially large enterprises, this token layer is where Stripe adds particular value. They need infrastructure that makes agentic transactions possible in the first place: secure, scoped tokens that let agents transact on behalf of buyers.

But agentic transactions aren’t only about the payment. There are multiple steps that have to work correctly in the flow: catalog discovery, checkout state management, shipping, and post-sale details such as returns and refunds. Stripe has a part in all of them. 

We’re playing an open source role by bringing a protocol into the world alongside OpenAI. But we’re also building the business layer on top, providing fraud tools, onboarding of businesses, catalog management, and more, so businesses can support agent-driven commerce end to end, not just at the moment of payment.

One of the most common questions we hear from sellers is about whether we’re seeing an uptick in fraud as agentic commerce grows in volume. The answer is reassuring: since launching the Agentic Commerce Suite with major retailers like Coach, Kate Spade, and Ashley Furniture, fraud rates have been near zero.

Traditional fraud detection relies on signals tuned to human traffic: everything from browser fingerprinting and mouse movements to device battery level and window size. Those signals vanish in an agentic world where there’s no human buyer on the frontend. Instead, we leverage the density of the Stripe network. Even if an agentic purchase is “new” to a given business, the end customer and their payment method likely aren’t new to Stripe, which gives an immediate source of history and risk context.

By using SPTs (described above), Stripe Radar can apply the same scrutiny to agentic transactions as it does to direct checkout flows, even when authorization happens off-Stripe. The result is enterprise-grade fraud protection that works without needing weeks of seller-specific data history.

Don’t flip the switch on your entire catalog. One approach we’ve seen work is to start with a focused set of SKUs you believe will convert, so you can measure performance and watch how the channel actually behaves. When starting out, stick to straightforward products that ship directly to the buyer’s home (nothing that requires installation or complex fulfillment coordination) as the frontend user experience develops.

URBN, the parent company of Anthropologie, Free People, and Urban Outfitters, sells everything from plants to custom furniture. When launching agentic commerce, the brand focused on a subset of its most popular products (dresses and denim) that would provide value early. 

For sellers, the early phase of agentic commerce means being strategic about which SKUs, payment methods, and fulfillment options you enable first. Think of it as gathering data so you can scale intelligently. The good news is that the scope of what’s possible is expanding quickly. In time, agents will enable new buying experiences beyond single-item, single-business carts. Starting small positions sellers to take advantage of those capabilities as they go live.

Early retail happened in store. First-wave ecommerce happened on your site. Mobile maintains your brand’s look and feel. Agentic commerce shifts buying intent onto AI surfaces. That changes how sellers need to think about discovery, brand control, dispute resolution, and trust. 

It also demands a strategic reframe. Agents often sit between the seller and the customer; they’re helping people discover products and decide where to buy. “Showing up” starts to look less like launching a new channel and more like work you already do for SEO and performance marketing: making sure you’re easy to find and choose. Commerce has always been about meeting customers where they are. It’s the “where” (and who controls it) that’s shifting.

Visibility isn’t the only challenge. Once an agent is in the loop, the messy parts of commerce don’t go away, but they pop up in different places. If an agent confirms an order but a legacy backend rejects it after a fraud check, how do you notify the customer? If a customer returns to an AI surface and says, “Cancel my order,” does the agent reliably route that request to the seller? We’re working with sellers and our AI partners to anticipate these issues and build solutions proactively.

The logged-in state is the holy grail for sellers. It allows them to recognize customers across sessions and channels, personalize experiences, and apply benefits such as loyalty and saved preferences. Right now, most agentic commerce still behaves like a guest checkout: the agent acts as proxy, and the customer’s identity isn’t revealed until the moment they hit “buy.” Identity signals exist, but sellers have to do a lot of manual work to capture what’s available and map it into existing customer and order management systems. 

As a result, brands we talk to are struggling to honor loyalty benefits, apply targeted discounts, and attribute conversion (or diagnose abandoned carts) with the same fidelity they’re used to. And as agents get better at making timely, relevant recommendations, the decision to buy can happen faster. If checkout then forces extra steps (whether that’s a click-out to a business’s site or additional confirmation and form-fills), sellers risk losing that intent.

It’s one reason we’re continuing to improve Link, a digital wallet built by Stripe. For returning Link customers, shipping and payment details are already saved, so checkout is faster. Link can also give agents a safer way to complete purchases without exposing a shopper’s personal or payment details. 

Over time, as the agentic ecosystem matures, we expect to see loyalty programs plug in, more complex fulfillment options supported, and upgrades to post-purchase engagement.

A recurring question we’re hearing from sellers: should you build a first-party agentic experience (like a brand-owned assistant on your site or app), or lean into third-party agentic commerce on external AI agents? In practice, this isn’t an either-or decision so much as a measurement challenge. The two approaches show up in different points in the customer journey. 

First-party agents, such as NikeAI, Magic Apron from Home Depot, or Ask Ralph from Ralph Lauren, are primarily about engagement. They deepen relationships with known customers, preserve brand control, and make it easier to maintain customer context like identity and preferences. Third-party agent surfaces are largely about acquisition. They meet customers where they already are and help capture net-new demand. We’ve seen this dynamic emerge early on with Etsy, for example.

There’s an opportunity to design for both. Use first-party agentic experiences to improve retention and lifetime value, and treat third-party surfaces as a new distribution surface that can bring customers to your owned channels over time.

Most of what we’ve covered here is everyday checkout, where a person decides to buy and pays through familiar rails. In parallel, we’re starting to see agents pay other services directly, per request, while they’re completing a task. That’s outside the standard ACP flow. It’s not a checkout session with shipping, loyalty, and a human confirmation step. It’s typically a fast, programmatic payment inside an HTTP call.  

Agents also don’t pay like humans. They might make thousands of small decisions a day and need low-latency, HTTP-native payments for pay-per-call or pay-per-task business models. Builders tell us they want to charge agents directly for things like tool usage, data access, or automated workflows, but the existing tooling is mostly built around human checkout. 

To help bridge the gap, we previewed machine payments using stablecoins on Stripe. With a few lines of code, you can use the PaymentIntents API to charge agents for things such as API usage, MCP calls, or HTTP requests. You specify the amount and currency, then Stripe generates a unique deposit address for that transaction.

From there, you return the deposit address to the agent, so it can pay programmatically. In an x402 flow, for example, the protocol passes the address back to the agent so it knows exactly where to remit payment. You can track status via API, webhooks, or the Stripe Dashboard, and funds settle into your Stripe balance. We’re starting with support for x402 using USDC on Base, with more protocols coming. 

We’re already seeing early examples, like charging agents per API call for inventory, pricing, delivery quotes, or pick-up-slot holds, and charging per task for automation such as fitment checks, bundle building, quote generation, or replenishment. This isn’t common in traditional retail yet, and today it’s stablecoin-based, but it points to where agent-native monetization can go as protocols and rails mature.  

What’s next

Agentic commerce is changing fast. In the near future, agents, humans, and businesses will be able to transact as reliably as today’s checkout, with richer context and better controls. Stripe is building the economic infrastructure for that future. 

As agents start buying, selling, and coordinating work on our behalf, we want it to be easy for any business to show up on AI surfaces and get paid reliably. If you already use Stripe for payments, you’re well positioned as agentic commerce expands. 

To get there, we’re continuing to improve the Agentic Commerce Suite: pushing more real-time updates, expanding SPT support to more payment methods, strengthening fraud signals as new vectors emerge, and building the identity resolution logic that helps sellers recognize customers across agentic surfaces. In addition, as agentic commerce becomes more global, we’re investing in broader geographic coverage and support for new verticals. 

To learn more about how we’re expanding our agentic commerce solutions, join us at Stripe Sessions.