GoHighLevel AI Studio Can Take Payments Now — Checkout, Upsells and the Two-Step Trap

Disclosure: I earn a commission if you sign up for GoHighLevel through links on this page. How that works is in the editorial policy.

The pitch for GoHighLevel AI Studio is “describe an app and it builds it.” Fine. Every AI builder says that now. But the part that matters to anyone actually selling something is quieter: the checkout it builds is HighLevel’s own checkout, wired to your products, your payment processor and your CRM.

That’s the difference between a demo and a store. This walkthrough is built from HighLevel’s changelog entries and help docs — what they say the feature does, and how you’d set it up. And it comes with two catches — one about which projects get it, one about which workflow trigger fires — that will bite you if you skim the release notes.

An AI app builder that already knows your product catalog

Quick context. AI Studio is HighLevel’s AI builder for apps and sites inside your account. HighLevel’s changelog announced it “now live from Labs for all locations” — with one detail that matters before you go looking for it: sub-account user and admin permissions for AI Studio are off by default. Users who’d already turned it on in Labs keep access; everyone else needs it granted (the entry says to open Configure, pick users, and confirm).

So if your client says “I don’t see AI Studio,” check that first. It may not be broken. Nobody flipped the permission.

Then came selling products and accepting payments, followed by checkout upgrades. Together they turn an AI-built site into something that can take money. If you’ve been following the funnels pillar, you’ll recognise most of the pieces. They’re just showing up in a new place — one built by an AI agent, which is the territory of the AI marketing workflows pillar.

”Add payments” is a prompt, not a project

Here’s the setup, per the changelog. There’s a new More → Payments settings tab in the project. You turn Payments on, choose test or live mode, and pick which products from your catalog this app is allowed to sell. Each product can be offered at a single fixed price, a chosen set of variations (sizes, tiers, plans), or its full catalog. Only the products and prices you allow can be shown or charged.

Then you ask the agent to add payments. It shows an approval card for the connection, and once you approve, it builds a storefront and checkout into the app.

Notice what that product-selection step is really doing. It’s a fence. The AI can design the page however it likes, but it can’t invent a price or sell something you didn’t approve. For anyone who’s watched an AI tool confidently make things up, that’s the most reassuring sentence in the whole release.

Stay in test mode until you’ve run a full order. Yes, even if it looks finished. Especially if it looks finished.

The checkout you don’t get to break

This is the most reassuring part of the release, and it’s not flashy. According to the payments changelog, card details are entered and processed in the platform’s hosted checkout, “never in your app’s code.” The payment code is platform-managed — and if it gets edited, it’s restored on the next turn.

Translation: by HighLevel’s description, you can prompt the agent to redesign the hero section forty times and it still shouldn’t be able to mangle the part that takes the card. The checkout also supports:

• PayPal express checkout
• Promo codes, and orders brought to zero by a code complete without a card
• Subscriptions in checkout and upsells, including carts with more than one subscription product
• Bot protection on every purchase
• Your site’s colour scheme, so it doesn’t look bolted on

If you’ve ever had a developer “just tweak” a Stripe integration on a Friday afternoon, you already know why a checkout you can’t touch is a feature, not a limitation.

Two-step checkout, now in an app — and the trigger trap

The checkout upgrades added three things. Configurable fields — phone and each billing address field can be shown, hidden or required, while name and email are always required. An order summary after payment, showing order ID, items, taxes, total and the next charge for subscriptions, or a redirect to your own thank-you page. And the big one: two-step checkout.

HighLevel describes it as “capture the lead first and take the payment second, just like the Two Step Order form in Funnels.” Step 1 saves the buyer as a CRM contact. Step 2 takes the payment. So someone who bails at the card field is still a lead you can follow up with — the whole argument in two-step order forms vs one-page funnels, now available in an AI-built app.

You set all of this by prompting. The changelog’s own examples: “Make it a two-step checkout,” “Make phone required and hide the billing address,” “Send buyers to my own thank-you page after payment.” Existing Payments projects pick it up on their next prompt.

Now the trap. Same entry: “new leads fire the Contact Created trigger, not Order Form Submission.”

Picture it. You’ve got an abandoned-cart workflow that’s run for two years off Order Form Submission on your funnel. You launch an AI Studio store with two-step checkout. A lead fills step 1, closes the tab. Your workflow never hears about it. Nothing errors. Nothing alerts. The follow-up just doesn’t happen — which is the quietest, most expensive kind of failure there is.

Before you go live, open every workflow that’s meant to catch these buyers and check what it listens for.

One-click upsells, with processor fine print

After a purchase, buyers can accept an offer with one click without re-entering card details — classic post-purchase upsell, the same idea behind tripwires and order bumps. The changelog is specific about where it works: saved cards from Stripe (3D Secure supported), Square, Authorize.net, NMI, Adyen and Mercado Pago. Other methods use the regular form instead.

Two more guardrails worth knowing: an upsell is only charged after the original order is paid, and only once per order. So check which processor your sub-account runs before you build an offer flow around one-click. If you’re on something else, it’s a two-click upsell. Still works. Just not the same thing.

The TanStack Start catch

Here’s the line that’ll stop some of you cold. Per the payments entry, Payments only works on apps built on TanStack Start — a server-rendered web framework (SSR, in the settings label). If you built an app earlier on a plain React project, you won’t get Payments until you migrate.

The migration path is Project Settings → Migrate to SSR. And the good news: it creates an upgraded copy. Your original stays live and unchanged, and you can test the copy before publishing. Do that. Run a test order on the copy, check the contact and the workflow trigger, then swap.

What it costs to run is the part to check before you build

Nobody’s release notes lead with this, so I will. AI Studio isn’t a flat fee you can forget about.

HighLevel’s AI Studio pricing article (checked Oct 2026) calls it a “usage-based model” — each session is “measured by the work performed rather than simply the number of prompts submitted,” and AI-generated images and media have a larger impact on usage. The AI product pricing article lists AI Studio as “usage included” on AI Employee Growth ($50/month per enabled location), “3x usage included” on Unlimited ($97/month), and “at token cost” on Pay-Per-Use, with usage measured in 5-hour windows.

Then there’s AI Studio Cloud — a built-in database, user accounts and file storage. The database starts at a free Tiny size; larger sizes list an hourly price, and reserved database storage is billed hourly even while paused. If your balance can’t cover Cloud, it pauses automatically, and nothing is deleted. A simple store doesn’t need Cloud. A member area might — and membership sites in GHL may already cover that need without it.

None of that is a reason not to build. It’s a reason to check your usage after the first few sessions, and to run your real numbers through the true cost calculator before you promise a client a monthly price. The real cost of GoHighLevel in 2026 shows where AI usage sits in the wider bill.

FAQ

Can GoHighLevel AI Studio accept payments?

Yes. HighLevel’s changelog says you enable Payments in a More → Payments tab, choose test or live mode, select which catalog products and prices the app can sell, then ask the AI agent to add payments. It asks you to approve, then builds a storefront and checkout into the app.

Which payment processors support one-click upsells in AI Studio?

Per the changelog, one-click post-purchase upsells work with saved cards from Stripe (with 3D Secure), Square, Authorize.net, NMI, Adyen and Mercado Pago. Other payment methods use the regular checkout form. An upsell is only charged after the original order is paid, and only once per order.

Why don’t I see Payments in my AI Studio project?

Payments only works on apps built on TanStack Start. For an existing React project, HighLevel says to use Project Settings → Migrate to SSR, which creates an upgraded copy and leaves the original live and unchanged. Also check that your sub-account user has AI Studio access, since sub-account permissions are off by default.

Does AI Studio two-step checkout trigger Order Form Submission?

No. HighLevel’s checkout-upgrades entry says new leads from two-step checkout fire the Contact Created trigger, not Order Form Submission. If your follow-up workflows listen for Order Form Submission, they won’t fire for these leads until you add the right trigger.

How much does AI Studio cost to use?

HighLevel describes AI Studio as usage-based, measured by the work each session performs rather than the number of prompts, with included usage on AI Employee Growth and Unlimited plans and token-cost billing on Pay-Per-Use. AI Studio Cloud adds its own billing for databases and storage. Check your own usage and wallet before building anything large.

What to do this week

Grant yourself AI Studio access in a demo sub-account. Start a TanStack Start project, turn on Payments in test mode with two products, and prompt “add payments,” then “make it a two-step checkout.” Run one test order. Then — the step that actually matters — check that the new contact landed in the CRM and that a workflow listening for Contact Created picked it up. The landing page anatomy breakdown is worth a reread before you prompt the design.

The pitch says it builds the app. Fine. Your job is to make sure the store behind it actually follows up. That’s still the difference between a demo and a store.