Home/HighLevel/Features/SaaS Configurator/Understanding HighLevel SaaS V1 vs V2 billing architectures

Agency, Settings and Integrations

Understanding HighLevel SaaS V1 vs V2 billing architectures

In short

HighLevel offers two SaaS billing architectures. V1 uses Stripe as the system of record, while V2 uses an Agency Subaccount and can work with multiple payment providers. The choice determines where subscriptions are managed, which billing features are available, and how plan changes behave.

AreaSaaS Configurator · SaaS Mode
Used forDigital marketing agency, Multi provider SaaS provider, Legacy SaaS reseller
Setup steps6 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners who bill clients with Stripe and need proration support will prefer SaaS V1 because Stripe remains the subscription record.
  • Agencies that want to use a payment provider other than Stripe and keep subscription data inside HighLevel benefit from SaaS V2.
  • Businesses that maintain legacy plans while adding new ones can run both V1 and V2 architectures side by side.

02SaaS V1 vs SaaS V2, explained

SaaS V1 and V2 are separate billing architectures within HighLevel. V1 keeps Stripe as the primary system of record; products, prices, and subscription actions are managed in Stripe and linked to the client subaccount. V2 stores products and subscriptions inside a selected Agency Subaccount, allowing multiple supported payment providers and tighter integration with HighLevel’s workflow tools.

The architecture you choose controls where subscription changes are processed. V1 supports Stripe native proration, coupon deflection, and self service reactivation. V2 does not support proration but allows monthly to annual changes as part of qualifying upgrades or downgrades. Both architectures can coexist, letting you preserve existing V1 plans while creating new V2 plans.

Configuration lives in the agency settings area of HighLevel. For V1 you connect Stripe at the agency level. For V2 you select an Agency Subaccount and configure a supported payment provider inside that subaccount before creating plan categories and pricing.

03How businesses use saaS V1 vs SaaS V2

  • Digital marketing agency. If the agency processes client subscriptions through Stripe and needs proration, it connects Stripe at the agency level (V1). The agency then creates plans in Stripe and sells them via subaccounts.
  • Multi provider SaaS provider. When the provider wants to accept a payment processor other than Stripe, it selects an Agency Subaccount (V2) and configures the chosen provider. Plans and subscriptions are then created directly in HighLevel.
  • Legacy SaaS reseller. To keep existing Stripe based plans while launching new offerings, the reseller runs both V1 and V2 architectures. Existing V1 subscriptions stay linked to Stripe, and new V2 plans are managed through an Agency Subaccount.

04The numbers and rules that matter

  • System of record | Stripe (V1) | Selected Agency Subaccount (V2).
  • Products managed in | Stripe (V1) | HighLevel through the Agency Subaccount (V2).
  • Primary payment provider model | Stripe (V1) | Multiple supported payment providers (V2).
  • Plan change proration | Available through supported V1/Stripe workflows (V1) | Not supported (V2).
  • Monthly annual changes | Handled through supported V1/Stripe subscription workflows (V1) | Supported as part of a qualifying upgrade or downgrade (V2).
  • Proration for supported subscription plan changes | Available (V1) | Not currently supported (V2).
  • Coupon/discount deflections during downgrade or cancellation flows | Available where supported (V1) | Not currently supported (V2).
  • Self service reactivation | Available in supported V1 flows (V1) | Not currently supported (V2).
  • Primary subscription payment method updates | Available through supported V1/Stripe workflows (V1) | For an active SaaS V2 subscription, changing the subaccount’s primary card also updates the payment method used for that subaccount’s SaaS subscription. Other subscriptions associated with the same contact are not updated.

05How to set up and use saaS V1 vs SaaS V2 in HighLevel

Set up the right SaaS billing architecture

  1. Identify the required payment provider; choose Stripe for V1 or another supported provider for V2.
  2. Confirm which billing capabilities (proration, coupon deflection, reactivation) your workflow depends on.
  3. For V1, connect Stripe at the agency level; Stripe remains the system of record.
  4. For V2, select an Agency Subaccount and configure the appropriate payment provider inside it.
  5. Create plan categories and pricing that align with the chosen architecture.
  6. Test the checkout and plan change flow to verify the subscription is created in the intended architecture.

06Things to know before you rely on it

  • SaaS V2 does not support proration for tier changes, billing interval changes, or combined plan changes.
  • Coupon or discount deflection during downgrade or cancellation is only available in V1.
  • Self service reactivation is only provided by supported V1 workflows.
  • Historical mismatches between Stripe and a selling subaccount subscription are not automatically repaired; only a qualifying upgrade or downgrade updates both records.
  • Direct manual changes made in Stripe do not trigger synchronization to the selling subaccount subscription.
  • Stripe Tax must already be enabled; the V1 subscription bridge does not enable it.

07How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Choosing between SaaS V1 and SaaS V2 should align with an agency’s payment provider strategy and workflow requirements.

Don’t assume a random Stripe edit will keep V1 subscription data in sync.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about saaS V1 vs SaaS V2.

Is SaaS V2 replacing SaaS V1?

No. They are separate billing architectures and can operate side by side.

Does the V1 subscription bridge change the V1 system of record?

No. Stripe stays the system of record; the bridge only synchronizes subscription records after supported plan changes.

Are old V1 subscription mismatches automatically repaired?

No. Historical mismatches are not backfilled. A future qualifying upgrade or downgrade can align the records.

Can SaaS V2 clients switch between monthly and annual billing?

Yes. Monthly and annual intervals can be changed as part of a supported V2 upgrade or downgrade, though proration is not supported.

Will a direct manual change in Stripe always synchronize to the V1 selling subaccount subscription?

No. Only supported V1 upgrade or downgrade events trigger the synchronization bridge.

Can an agency use V1 and V2 at the same time?

Yes. Both architectures can coexist, with each subscription following its own system of record.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.