GoHighLevel How-To Guides

The GoHighLevel Stripe integration is the commercial engine of GoHighLevel. Without it, your order forms are placeholders. Your membership sites can’t bill anyone. Your SaaS mode is an idea rather than a business. With it — set up correctly — every payment event in Stripe triggers an automation in GoHighLevel, which means new clients get onboarded automatically, failed payments get a recovery sequence, and subscription changes update contact records without anyone lifting a finger.

Most people connect Stripe in five minutes and assume the job is done. It isn’t. The connection to the GoHighLevel dashboard is step one. The webhook configuration — the part that tells GHL what happened in Stripe and when — is step two, and it’s the one most often skipped. Skip it, and your payment confirmation workflows won’t fire. Every client who pays sits in your pipeline with no automation triggered until someone checks manually.

This guide covers the full setup: connecting Stripe, configuring your UK account correctly, building order forms and subscription plans, thoroughly testing in the Stripe test environment, and ensuring every billing event triggers the correct GoHighLevel workflow.

Step 1: Connect Your Stripe Account

In GoHighLevel: Settings → Payments → Integrations → Stripe

Click Connect with Stripe. You’ll be redirected to Stripe’s OAuth flow to authorise the connection. Log into your existing Stripe account or create one if you haven’t already.

[SCREENSHOT: GoHighLevel Settings → Payments → Integrations tab showing Stripe connection button]

Once connected, return to GoHighLevel. You’ll see your Stripe account name confirmed in the integrations panel.

Critical for UK accounts: Before building any products, go to your Stripe Dashboard → Settings → Business settings and confirm your account currency is set to GBP. If it’s set to USD, every transaction converts at Stripe’s exchange rate, adding unnecessary cost for UK clients paying in pounds. This is the most common configuration error on UK Stripe accounts connected to GHL.

Step 2: Switch from Test Mode to Live Mode

GoHighLevel connects to whichever Stripe mode is active at the time of connection. If you built funnels or tested payments in Stripe test mode, your GHL integration may still point to test keys.

Check this: Stripe Dashboard → Developers → API keys. Confirm the keys shown are your live secret and publishable keys, not test keys (test keys start with sk_test_ and pk_test_). If you’re in test mode, toggle to live mode in the Stripe dashboard before reconnecting to GoHighLevel.

Test mode payments will show as successful in GHL but will never actually charge anyone. This is a useful discovery to make before you launch — less useful to discover after.

Step 3: Configure the Stripe Webhook

This is the step that most GHL tutorials miss, and missing it is why payment confirmation workflows don’t fire.

GoHighLevel communicates with Stripe in two directions. GHL sends payment requests to Stripe when someone clicks Pay. Stripe sends event notifications back to GHL when payments succeed, fail, subscriptions renew, or billing changes occur. Those inbound notifications travel via a webhook — a specific URL in your GHL account that Stripe posts data to.

Check your webhook is active:

Stripe Dashboard → Developers → Webhooks
Look for an endpoint URL containing gohighlevel or leadconnectorhq
Confirm the endpoint shows a recent “Delivered” event (not Failed or Pending)
If no GHL endpoint exists, go back to GoHighLevel Settings → Payments → Integrations → Stripe and reconnect — the webhook should be registered automatically on reconnection

Which Stripe events should the webhook listen for?

At minimum: payment_intent.succeeded, payment_intent.payment_failed, customer.subscription.created, customer.subscription.updated, customer.subscription.deleted, invoice.payment_succeeded, invoice.payment_failed.

If you’re using SaaS mode, add: customer.created, customer.updated.

Test the webhook by going to Stripe Dashboard → Developers → Webhooks → your GHL endpoint → Send test webhook. Send a payment_intent.succeeded event and confirm it appears in GHL’s event log within thirty seconds.

Step 4: Build Your Payment Products

In GoHighLevel: Payments → Products

Create each service, subscription, or membership as a product in GoHighLevel’s product library. Each product is linked to a corresponding Stripe price object — GHL creates it automatically when you save the product.

For one-off payments: Set the pricing type to One Time. Set the currency to GBP.

For recurring subscriptions: Set the pricing type to Recurring. Choose the billing interval (monthly, annual, weekly). Set trial periods if applicable. Every subscription created this way automatically generates a Stripe subscription object and a recurring invoice schedule.

For order bumps: When building an order form, add additional products as order bumps in the form settings. A client who adds an order bump at checkout creates a separate line item on their Stripe invoice — all handled natively, with no Zapier involvement.

Step 5: Build Order Forms That Actually Convert

In GoHighLevel: Funnels/Websites → Order Forms or within a funnel page using the order form element

GoHighLevel’s order form pulls your Stripe products directly. Select the product, choose whether to collect the card on the form or redirect to Stripe Checkout, and configure the post-payment redirect page.

The post-payment redirect is where most people lose conversions. After a successful payment, clients should land on a dedicated thank-you page — not a generic confirmation page, but one that confirms exactly what they’ve bought, explains what happens next, and removes any post-purchase doubt. A strong thank-you page also reduces the likelihood of refund requests from buyers who weren’t sure what they’d signed up for.

Two-step order forms — where you collect name, email, and phone before showing the payment fields — outperform single-step forms in almost every service business context. The reason is data capture: even if someone abandons before paying, their contact details are in GoHighLevel and can trigger an abandoned checkout recovery sequence.

Step 6: Connect Payments to GoHighLevel Workflows

Every Stripe event that fires a webhook to GHL can be used as a workflow trigger.

The payment received workflow is the highest-priority automation to configure. When payment_intent.succeeded fires, GoHighLevel creates a transaction record and can trigger: contact tag addition, pipeline stage movement, welcome email and SMS, calendar invite creation, onboarding sequence start, access provisioning for membership sites.

Set this up before you take a single live payment. Every client who pays deserves an immediate, automated acknowledgement and a clear onboarding path. The businesses that get referrals from new clients within the first week are almost always the ones whose onboarding automation is in place before launch.

The failed payment workflow is the second priority. When invoice.payment_failed fires, GoHighLevel should tag the contact as “Payment Failed” and trigger a recovery sequence: a polite SMS or email asking them to update their card details, followed by a reminder, followed by a courtesy call task for your team if the first two fail. Recovering a failed payment costs nothing compared to finding a new client to replace a churned one.

UK-Specific Notes

VAT: If your business is VAT-registered, Stripe Tax can automatically calculate and add VAT at checkout. Connect Stripe Tax in your Stripe dashboard before building order forms — retrofitting it after orders are live is considerably more work. GoHighLevel’s order forms pass the correct tax amounts through to Stripe when Stripe Tax is active.

GDPR and payment data: GoHighLevel does not store card numbers or bank details — Stripe handles all PCI-compliant data storage. Your GHL contact records store only transaction IDs and amounts. This is correct and compliant. GoHighLevel’s data processing is separate from Stripe’s. Review both companies’ DPAs and add them to your data processing records.

Strong Customer Authentication (SCA): UK and EU card regulations require SCA (3D Secure) for most card transactions. Stripe handles SCA compliance automatically. GoHighLevel’s native Stripe integration supports SCA — if you’re using a custom Stripe Elements checkout outside GHL, verify that your implementation includes the SCA flow. Failed SCA checks return as authentication errors in Stripe rather than payment failures.

Testing Before Go-Live

Use Stripe’s test card numbers to verify every payment flow before switching to live mode:

Successful payment: 4242 4242 4242 4242
Card declined: 4000 0000 0000 0002
Insufficient funds: 4000 0000 0000 9995
SCA required: 4000 0025 0000 3155

For each test, confirm: the contact record is created or updated in GHL, the correct tags are applied, the correct workflow fires, and the thank-you page loads correctly. Any failure at any of these points is a workflow configuration issue, not a Stripe issue.

Frequently Asked Questions

How do I connect Stripe to GoHighLevel? Go to GoHighLevel Settings → Payments → Integrations → Stripe and click Connect with Stripe. You’ll be redirected to Stripe’s authorisation page. Log in to your Stripe account and grant access. Once connected, verify that the webhook endpoint is registered in your Stripe dashboard under Developers → Webhooks.

Does GoHighLevel work with Stripe in the UK? Yes. GoHighLevel’s Stripe integration is fully compatible with UK Stripe accounts and GBP billing. Set your Stripe account currency to GBP before building products to avoid unnecessary currency conversion costs. Stripe Tax automatically handles UK VAT when configured.

What does the Stripe webhook do in GoHighLevel? The webhook is the notification channel from Stripe to GoHighLevel. When a payment succeeds, fails, a subscription renews, or billing changes, Stripe posts an event to the GoHighLevel webhook URL. This event triggers GoHighLevel workflows — onboarding sequences, failed payment recovery, subscription management automations. Without an active webhook, GoHighLevel receives no notification of payment events, and automations don’t fire.

Can GoHighLevel handle recurring subscriptions through Stripe? Yes. Products set to Recurring billing in GoHighLevel create Stripe subscription objects that automatically renew. Subscription lifecycle events — creation, renewal, upgrade, downgrade, cancellation — all trigger GoHighLevel workflow triggers when the webhook is correctly configured.

What happens if a Stripe payment fails in GoHighLevel? GoHighLevel receives a invoice.payment_failed webhook event from Stripe. This can trigger a failed payment recovery workflow: an automated email or SMS to the client asking them to update their payment method, followed by reminders, then a manual task for your team. Stripe also retries failed payments automatically according to your configured retry schedule.

Do I need Stripe for GoHighLevel SaaS mode? Yes. GoHighLevel’s SaaS mode — where you resell GHL as your own branded software to clients — uses Stripe to manage sub-account billing. Every client subscription, plan change, and billing event runs through your connected Stripe account. SaaS mode cannot operate without Stripe.

Ready to set up GoHighLevel payments correctly from the start? To discuss your implementation.