Stripe is rebuilding checkout for robots. Your intro offer is next in line.

Every studio owner knows the moment a sale is won or lost. It is not the ad and it is not the homepage. It is the payment page. Someone picks the intro offer, lands on checkout, and either types in a card or closes the tab.

Now picture the same moment with nobody's thumbs involved. A customer tells an assistant to "book me the three-class intro pack at the pilates place near work." The assistant finds you, picks the offer, and arrives at your checkout. What happens next depends on whether that page was built for a person squinting at a phone, or for software that needs to know which field is which.

Stripe has spent the past year making sure its pages work for both. In Part 2 we covered the plumbing that lets an agent read your website. This part follows the money: what Stripe and the card networks have built so an agent can pay, what has worked, what has not, and what it means for a business selling memberships, packages and deposits.

A year of building, one launch at a time

Stripe did not ship this in one announcement. It came in pieces, and one of the biggest pieces was walked back.

That March line deserves a second look. OpenAI's in-chat checkout was the headline launch of the whole effort, and six months later OpenAI's own developer docs call external checkout, meaning the merchant's own site, the "recommended and generally available approach." The in-chat payment sheet is "limited to select marketplaces today." What survived is the protocol underneath: ChatGPT now leans on it for product discovery and hands the shopper to the retailer to pay, as reported by Times of AI.

The lesson is useful for anyone selling services. Getting the agent to the payment page turned out to matter more than replacing the payment page.

Four pieces, in plain English

You will hear a lot of new terms. Here is what each one does.

The Agentic Commerce Protocol (ACP) is a shared language between an AI app and a business: here is my catalog, here is the cart, here is the payment. Stripe says businesses can adopt it even if they do not process payments with Stripe. OpenAI's documentation is explicit that OpenAI is not the merchant of record. The business still takes the money and owns the customer.

Shared Payment Tokens solve the scariest part. An agent should never hold your customer's card number. Instead Stripe issues a token after the buyer pays with their saved method, and each token is limited to one specific business and one cart total. If it leaks, it is useless anywhere else.

Link for agents is the wallet. Stripe's Link already has more than 250 million users, according to Stripe. Since Sessions, an agent can pay with Link on a person's behalf: Stripe issues a one-time card for each task, the agent never sees the real card, and the user approves each payment. Stripe's own example is an agent watching a restaurant for an opening and paying the deposit. Swap "restaurant" for "facial" and that is your booking deposit.

WebMCP on Stripe Checkout is the piece most likely to touch you without you doing anything. More on that next.

Source: Stripe developer blog, September 22, 2026; Stripe newsroom, April 29, 2026

Your checkout page may already speak agent

In September two Stripe engineers wrote that Stripe had "enabled WebMCP on all Stripe Checkout UIs," and that Stripe Checkout powers more than 7.8 million businesses. Stripe's documentation lists where it works: the full-page hosted checkout, the embedded checkout form, Elements built on Checkout, and the hosted invoice page.

WebMCP, which we explained in Part 2, lets a page hand an agent a short menu of things it can do. On a Stripe payment page that menu includes reading the amount due and the payment methods on offer, picking a payment method, filling in fields and, where Stripe controls the button, submitting payment. No guessing where to click.

Stripe tested it. Across 60 runs with six AI models on a pretend outdoor retailer, every agent finished checkout either way. The ones using the tools did it with far less effort.

Source: Stripe developer blog, September 22, 2026. 60 test runs, six models, one fictional store; Stripe's own evaluation, not independent.

Two cautions. These are Stripe's own tests on a fake store, not live traffic. And Stripe's documentation calls WebMCP "an experimental browser capability based on a proposed web standard," so tools and browser support can change.

The most important line in those docs is about permission:

Before calling a tool with this hint, get the user's confirmation. Don't interpret the hint itself as confirmation.

Every system in this story puts a person at the final step. Muse asks for approval before a purchase. Link asks the user to approve each payment. The agent does the legwork, the customer still says yes. That means the agent will read your offer back to your customer in a sentence or two, so the terms had better survive being summarized.

Stripe is not the only one laying track

The card networks and Google are building the trust layer around the same moment. Google announced the Agent Payments Protocol (AP2) in September 2025 with more than 60 organizations. It uses signed "mandates": one records what the person asked for, such as a price limit, and one locks in the exact cart they approved. Visa introduced its Trusted Agent Protocol in October 2025, built with Cloudflare, so merchants can tell an approved shopping agent from a malicious bot. Stripe and Shopify were among the companies Visa named. And as we noted in Part 1, Mastercard added a score in September 2026 that estimates whether an agent started a transaction, as reported by FinTech Weekly.

None of these compete with your studio. They decide whether the agent at your checkout is trusted, and whether your processor will let the payment through.

What it means for memberships, packs and deposits

Most of this was built for retail first. Stripe's Agentic Commerce Suite asks businesses to upload a product catalog, and OpenAI's checkout approvals are currently limited to physical goods. A 10-class pack or a monthly membership does not sit neatly in a shopping cart, and nobody has announced a fix for that yet. But the part that matters most for local businesses, the payment page itself, is moving now.

Where you stand depends on where your money is actually taken:

• If your intro offer or deposit goes to a Stripe-hosted checkout or a Stripe invoice, those pages now carry agent tools. Your job is to make sure an agent can find the link and understand the offer.
• If you run on GoHighLevel, its help center says connecting Stripe makes it the payment provider for invoices, payment links and order forms. Whether a given form shows Stripe's own checkout page or HighLevel's is worth checking with whoever built your funnels.
• If memberships run through Mindbody, Zenoti or a similar platform, the payment page belongs to that platform, and so does the agent question. We found no announcement from them on agent checkout. Ask.

1. Find your real checkout

   Click your own "Buy" or "Book" button for the intro offer, a package and a deposit. Write down whose page you land on.

2. Make the offer readable

   Put price, what is included and the renewal terms in plain text beside the button. An agent will summarize it to your customer before they approve.

3. Fix the price trap

   If an intro offer rolls into a full membership, say so in one sentence. A hidden auto-renewal that a person might miss, an agent will read aloud.

4. Ask your platform

   Ask Mindbody, Zenoti, HighLevel or your booking tool, in writing, what they support for AI agents and when.

The next question is price

Every payment in this story is the size of a normal purchase: a dress, a class pack, a deposit. The newer work at Stripe, like the per-use payments it showed at Sessions, points at something stranger: agents paying a few cents at a time, for an answer, a data lookup or a spot on a waitlist. Card fees have always made that impossible. In Part 4: Micropayments finally have a reason, we look at why tiny payments are suddenly back, and whether any of it touches a business that sells sweat and skincare.

If you missed the start, Part 1 makes the case that the customer is already sending software ahead of them.

---

Sources

• Stripe, "Stripe powers Instant Checkout in ChatGPT and releases Agentic Commerce Protocol codeveloped with OpenAI," September 29, 2025. stripe.com
• Stripe, "Stripe launches the Agentic Commerce Suite," December 11, 2025. stripe.com
• Stripe, "Stripe brings a new checkout experience for Facebook," March 24, 2026. stripe.com
• Stripe, "Stripe builds out the economic infrastructure for AI with 288 launches," April 29, 2026. stripe.com
• Stripe, "Everything we announced at Sessions 2026," April 29, 2026. stripe.com
• Cara Mecozzi and Steve Kaliski, Stripe, "How Stripe is designing checkout for AI agents," September 22, 2026. stripe.dev
• Stripe Docs, "Use WebMCP to complete Stripe payments in a browser." docs.stripe.com
• OpenAI Developers, Agentic Commerce "Key concepts." developers.openai.com
• OpenAI Developers, Apps SDK "Monetization." developers.openai.com
• Times of AI, "OpenAI Upgrades ChatGPT Shopping While Retreating From Checkout," March 26, 2026, quoting OpenAI's March 24 post. timesofai.com
• The Paypers, "Meta launches personal AI agent with Stripe-powered checkout," September 9, 2026. thepaypers.com
• Google Cloud, "Announcing Agent Payments Protocol (AP2)," September 16, 2025. cloud.google.com
• Visa, "Visa Introduces Trusted Agent Protocol," October 14, 2025. usa.visa.com
• FinTech Weekly, "Agentic Commerce Had Its Biggest Launch Month," October 4, 2026, on Mastercard Agent Pay. fintechweekly.com
• HighLevel Support Portal, "Getting Started: Connect Stripe." help.gohighlevel.com