The short answer
The GoHighLevel Stripe integration connects a Stripe account to a HighLevel sub-account so it can take card payments through invoices, payment links, order forms, forms, stores, calendars, courses and communities. Each sub-account connects to one Stripe account at a time, and card processing fees are charged by Stripe to your Stripe account. HighLevel only tracks payments made through HighLevel after you connect; earlier Stripe charges are not imported. Agencies also use Stripe on the agency side to rebill clients for usage and to run SaaS Mode on Agency Pro.
| Plans | All plans (Payments and Invoicing is a core feature). One Stripe account per sub-account. |
|---|---|
| Cost | No HighLevel add-on fee listed for connecting Stripe; Stripe's processing fees apply under your Stripe account. |
| Checked | 2026-09-29, against HighLevel's help center and pricing page |
Where Stripe works in HighLevel
Once connected, Stripe becomes the payment provider for the sub-account's eligible payment experiences: invoices, payment links, order forms on funnels, payment fields on forms, e-commerce stores, paid calendar bookings, and course and community offers. Customers pay by card through your own Stripe account. Payment methods can be managed from inside HighLevel and configured separately for live and test environments, and Stripe test mode lets you push a fake payment through a funnel or calendar before launch, so a broken checkout is caught before a real customer finds it.
One Stripe account per sub-account
Each sub-account can connect to one Stripe account at a time. A business with two legal entities that need separate payouts therefore needs two sub-accounts. Stripe is not the only option: HighLevel also supports PayPal, NMI, Authorize.net and Square, among others. Before connecting, confirm Stripe supports the client's country and that the person connecting has permission to authorize that Stripe account. Payments created directly in Stripe before the connection are not imported, so HighLevel's revenue reporting starts from the day you connect, which is worth telling a client who expects to see last year's sales.
Charging a saved card from a workflow
The Stripe One Time Charge workflow action charges a set amount when an event happens, such as a form submission or appointment booking. It needs a Stripe customer ID with a saved payment method, so it only works for customers who already have a card stored in Stripe. HighLevel's example is an agency on a pay-per-lead model charging its client automatically each time a qualified lead submits a form, with no manual invoicing. Because it charges a card without a fresh checkout, get the customer's clear agreement to automatic charges first, and test it in Stripe test mode.
Stripe at the agency level
Agencies also use Stripe to bill their own clients. When rebilling is on, the agency's Stripe account charges each client's card for the usage HighLevel billed to the agency wallet; HighLevel's own Stripe never charges a sub-account directly. On Agency Pro, SaaS Mode sells subscription plans to clients. In the original SaaS setup, a Stripe account connected in agency settings is the billing system of record, while the newer setup runs through an Agency Sub-Account and supports Stripe, NMI, Authorize.net and Square. Our SaaS Mode guide covers that side in depth.
Costs add up differently for every account. Put your numbers into the HighLevel cost calculator, or browse every HighLevel feature.
Cost your account Try HighLevel