GoHighLevel SaaS V2 Payments Guide

/ CRM, GHL / By

How to Use GoHighLevel SaaS V2 Payment Providers

ClickUp users who also manage agencies in GoHighLevel often want a clear process for reselling and rebilling SaaS V2 plans. This guide walks you through how reselling works, which payment providers are supported, and how to connect everything so your clients can pay you directly from their own accounts.

This article is based on the official documentation for reselling and rebilling through SaaS V2 payment providers in GoHighLevel and explains the behavior you can expect when you activate these options for your agency and sub-accounts.

Overview of SaaS V2 in GoHighLevel

SaaS V2 in GoHighLevel lets you bundle the platform into your own plans and charge your clients for access. Instead of your agency handling every invoice manually, each sub-account can have its own payment setup while still using your SaaS configuration.

With SaaS V2 enabled, you can:

  • Sell access to your GoHighLevel-based services as a subscription.
  • Allow sub-accounts to manage their own payment connections.
  • Use the built-in SaaS configurator to define pricing and limits.

The reselling and rebilling options depend on how the payment provider is connected inside GoHighLevel.

Supported Payment Providers in GoHighLevel

Not every provider can be used for reselling SaaS directly. GoHighLevel supports specific payment integrations that work with SaaS V2 plans.

From the SaaS V2 perspective, you will see two main categories:

  • Providers that can be used for SaaS billing and subscriptions.
  • Providers that can only be used for regular funnels, websites, or one-off payments.

Your choice of provider will determine how you can rebill clients and whether you can rely on SaaS automations inside GoHighLevel.

How Reselling and Rebilling Work in GoHighLevel

When you enable SaaS V2, GoHighLevel offers you a way to resell the platform with your own pricing. The core idea is that your customer (sub-account) is billed using a payment method they connect, but the products and plans are configured at the agency level.

The typical flow looks like this:

  1. You configure SaaS V2 packages at the agency level.
  2. Your client signs up through your SaaS offer.
  3. The sub-account connects an approved payment provider.
  4. Billing for that sub-account runs through the connected provider.

This structure allows you to scale your business and keep subscription management inside GoHighLevel instead of using multiple external systems.

Connecting Payment Providers Inside GoHighLevel

To use SaaS V2 reselling, you must connect a supported provider at the correct level. In GoHighLevel, payment connections can be made at:

  • The agency level, for your main billing needs.
  • The sub-account level, for individual client billing.

When you configure a provider for SaaS V2, make sure you follow the steps from the provider’s integration screen inside your GoHighLevel account. The exact options and labels you see will follow the latest version of the platform.

Agency-Level vs Sub-Account-Level Connections in GoHighLevel

The level where a provider is connected affects who is charged and where transaction data flows:

  • Agency level: Used for your core agency billing and certain global products.
  • Sub-account level: Used when you want the client to handle payments directly from their own account for SaaS plans or other offers.

For SaaS V2, GoHighLevel relies heavily on sub-account-level connections so that each client’s payments, invoices, and subscriptions are handled separately.

Rebilling SaaS Plans to Clients in GoHighLevel

Rebilling means charging your clients for the SaaS plan that you originally purchased from the platform. In GoHighLevel, this is done using your SaaS configuration, but each client still pays through their own connection.

At a high level, the rebilling logic works like this:

  • You buy or activate SaaS V2 at the agency level.
  • You define pack limits, features, and pricing structures.
  • Your client signs up via your SaaS funnel or direct link.
  • The sub-account billing is executed through the connected payment provider for that client.

From the user’s point of view, they are paying you for access to the tools you have packaged, even though the underlying platform is GoHighLevel.

Managing Existing Subscriptions in GoHighLevel

If you migrate clients from older offers to SaaS V2, GoHighLevel may treat those subscriptions differently depending on which provider and connection level was used before. You should review each sub-account’s current setup and confirm that:

  • The sub-account is connected to a supported provider.
  • Any legacy subscriptions are either canceled or updated to match your new SaaS V2 pricing.
  • Your SaaS automations are active and correctly mapped to the new plans.

Always verify that the first billing cycle after migration runs correctly and that invoices appear where expected inside GoHighLevel.

GA4 Tracking for SaaS V2 Payments in GoHighLevel

The official documentation explains that you can use GA4 tracking codes alongside your SaaS V2 funnels and payment pages. When configured correctly, GoHighLevel will allow you to track key events around signups and purchases.

To implement this, you generally need to:

  1. Add your GA4 measurement ID to your GoHighLevel funnel or site.
  2. Ensure your tags or scripts are published and firing on the pages where SaaS V2 checkouts occur.
  3. Confirm that GA4 events are receiving data when test purchases are made.

This data helps you analyze how well your SaaS V2 offers convert and which traffic sources bring in the most paying clients.

Best Practices for Accurate GA4 Data in GoHighLevel

To keep your analytics clean, follow these recommendations:

  • Use a dedicated GA4 property for SaaS V2 funnels in GoHighLevel if you want separate reporting.
  • Test with a staging or low-price test product before full launch.
  • Check that cookie consent settings do not block essential GA4 scripts.

When implemented correctly, your GoHighLevel SaaS V2 setup and GA4 implementation will give you a clear view of your revenue and marketing performance.

Troubleshooting SaaS V2 Payment Issues in GoHighLevel

If payments are not processing as expected, GoHighLevel suggests checking the following areas first:

  • Is the payment provider correctly connected at the sub-account level?
  • Is the SaaS configuration assigned to the right sub-account or funnel?
  • Does the client’s payment method meet the provider’s requirements?
  • Are any failed webhooks or integration errors showing in the provider’s dashboard?

In many cases, correcting the connection level or resetting the provider authorization solves issues with new SaaS signups.

Where to Learn More About GoHighLevel SaaS V2

For the most detailed and current technical information, always refer to the official GoHighLevel help article on reselling and rebilling through SaaS V2 payment providers. You can view it here: Reselling and Rebilling Through SaaS V2 Payment Providers.

If you want strategic guidance on how to package, price, and market your SaaS V2 offers built on GoHighLevel, you can also consult specialist agencies such as Consultevo, which focuses on helping businesses optimize their sales and automation stacks.

By understanding how payment providers, GA4 tracking, and SaaS configurations work together inside GoHighLevel, you can confidently resell the platform as your own solution and manage scaling without losing control of billing and analytics.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.

Scale GoHighLevel

“`