Learn how SaaS V1 and V2 differ, where subscriptions are managed, how payment providers work, which billing capabilities are currently different, and how the SaaS V1 subscription bridge keeps eligible subscription records aligned after supported plan changes.
SaaS V2 is not an upgrade or replacement for SaaS V1. They are separate billing architectures and can operate side by side. The SaaS V1 subscription bridge improves synchronization for eligible V1 subscriptions without changing Stripe's role as the V1 system of record.
What is the Difference Between SaaS V1 and SaaS V2?
SaaS V1 and SaaS V2 provide two different ways to manage recurring SaaS subscriptions. The primary difference is where the subscription is owned and managed: V1 uses Stripe as the system of record, while V2 uses an Agency Sub-Account. This architectural difference affects payment-provider options, subscription management, integrations, and some billing capabilities.
| Area | SaaS V1 | SaaS V2 |
|---|---|---|
| System of record | Stripe | Selected Agency Sub-Account |
| Products managed in | Stripe | HighLevel through the Agency Sub-Account |
| Primary payment-provider model | Stripe | Multiple supported payment providers |
| Plan-change proration | Available through supported V1/Stripe workflows | Not supported |
| Monthly ↔ annual changes | Handled through supported V1/Stripe subscription workflows | Supported as part of a qualifying upgrade or downgrade |
Key Benefits of Understanding SaaS V1 vs SaaS V2
Choosing the architecture that matches your billing requirements helps prevent subscription-management issues later. Understanding the differences also makes it easier to determine where to configure payments, troubleshoot billing, and manage future plan changes.
- Billing Clarity: Know which system owns the subscription and where billing changes should be managed.
- Payment Flexibility: Choose Stripe-based V1 or V2 with a supported Agency Sub-Account payment provider.
- Feature Planning: Identify billing and recovery capabilities that differ between V1 and V2 before onboarding customers.
- Accurate Plan Changes: Understand how upgrades, downgrades, billing intervals, and proration behave for each architecture.
- Better Troubleshooting: Start in Stripe for V1 billing issues or the appropriate Agency Sub-Account for V2 billing issues.
SaaS V1 Architecture
SaaS V1 is the longer-established Stripe-based architecture. Stripe remains the system of record for the SaaS subscription, while HighLevel connects the client sub-account to the applicable SaaS and billing configuration.
- Stripe is the SaaS V1 system of record.
- The agency connects Stripe at the agency level.
- V1 SaaS products and prices originate in Stripe.
- Stripe-native billing capabilities can be used where supported.
- Some V1 sales workflows also create a corresponding subscription record inside the sub-account used to sell the subscription.
Best fit: SaaS V1 is a strong choice when your agency uses Stripe and relies on Stripe-native billing capabilities or SaaS functionality that is not currently available in V2.
SaaS V2 Architecture
SaaS V2 uses a selected Agency Sub-Account to manage SaaS products, subscriptions, and payment-provider configuration. This enables SaaS billing to operate more directly through HighLevel's Payments and CRM ecosystem instead of relying on Stripe as the subscription system of record.
- The selected Agency Sub-Account is the SaaS V2 billing system of record.
- Products and subscriptions are managed through HighLevel.
- V2 can use multiple supported payment providers configured through the Agency Sub-Account.
- Subscription activity can integrate more closely with CRM, contacts, workflows, and other HighLevel tools.
- Monthly and annual billing intervals can be changed as part of a supported plan upgrade or downgrade.
Proration: SaaS V2 does not support proration for tier changes, billing-interval changes, or plan changes that combine both.
SaaS V1 Subscription Sync After Plan Changes
Some SaaS V1 subscriptions are sold by importing the Stripe-based SaaS product into a selling sub-account and using that product in a funnel or supported payment flow. These subscriptions can have both the Stripe subscription and a corresponding subscription record in the selling sub-account. Supported SaaS upgrades and downgrades now keep those records aligned.
| Before | After a Qualifying V1 Plan Change |
|---|---|
| Stripe could update while the selling-sub-account subscription retained older plan information. | Stripe and the corresponding selling-sub-account subscription are updated in the same supported plan-change flow. |
| The selling-sub-account record could reference an outdated product or price. | The current product and price can remain aligned. |
| Invoices generated from stale sub-account information could reference the previous plan. | Downstream invoices can reflect the current synchronized plan information. |
| Applicable tax calculations could use older plan information. | When tax is already configured and applicable, current plan information can be used for recalculation. |
Covered V1 pattern: SaaS plan → Stripe product → product imported into a selling sub-account → subscription sold through that selling sub-account → supported SaaS upgrade or downgrade.
Not retroactive: Historical mismatches between Stripe and an existing selling-sub-account subscription are not automatically backfilled. A future qualifying upgrade or downgrade can update both records through the supported synchronization flow.
Manual Stripe edits: Do not assume that arbitrary subscription changes made directly in Stripe trigger this synchronization. The bridge is documented for supported SaaS upgrade and downgrade events.
Current Feature Differences
The two architectures do not currently provide identical subscription-management capabilities. Review the differences that matter to your billing model before selecting an architecture for new SaaS plans.
| Capability | SaaS V1 | SaaS V2 |
|---|---|---|
| Proration for supported subscription plan changes | Available through supported V1/Stripe billing workflows | Not currently supported |
| Coupon/discount deflections during downgrade or cancellation flows | Available where supported | Not currently supported |
| Self-service reactivation | Available in supported V1 flows | Not currently supported |
| Primary subscription payment-method updates | Available through supported V1/Stripe workflows | Not currently supported in the same self-service flow |
| Monthly ↔ annual plan changes | Supported through applicable V1/Stripe workflows | Supported as part of a qualifying upgrade or downgrade; no proration |
Which SaaS Version Should You Choose?
Neither architecture is universally better. The right choice depends on your payment provider, required subscription-management features, and how closely you want SaaS billing connected to HighLevel's CRM and Payments ecosystem.
Choose SaaS V1 When
V1 is better suited to agencies that primarily use Stripe and depend on Stripe-native or V1-specific subscription capabilities.
- Stripe is your preferred SaaS payment processor.
- You require supported proration workflows.
- You rely on discount/coupon deflection behavior.
- You want to use Stripe-native subscription-management capabilities.
Choose SaaS V2 When
V2 is better suited to agencies that need multi-provider flexibility or want subscription management centered inside an Agency Sub-Account.
- You want to use a supported provider other than Stripe.
- You want products and subscriptions managed through HighLevel.
- You want tighter CRM and workflow integration.
- You do not rely on the V1-only capabilities listed above.
How To Set Up the Right SaaS Billing Architecture
Selecting the billing architecture before creating and selling plans helps keep products, payment providers, subscription records, and future plan-change behavior consistent. Review the requirements below before configuring your first plan.
- Identify your payment-provider requirement. If SaaS billing must use Stripe, V1 may fit. If you need another supported provider, review V2.
- Review required billing capabilities. Confirm whether your workflow depends on proration, deflections, reactivation, or other architecture-specific behavior.
- For V1, connect Stripe at the agency level. Stripe will remain the SaaS subscription system of record.
- For V2, select an Agency Sub-Account. Configure the appropriate supported payment provider inside that sub-account.
- Create compatible plan categories and pricing. Plan hierarchy determines future upgrade and downgrade paths.
- Test the intended checkout and plan-change flow. Confirm the subscription is created in the expected architecture before scaling the setup.
Running both architectures: An agency can maintain existing V1 plans while also creating V2 plans. Each subscription continues to follow the system of record associated with its architecture.
Frequently Asked Questions
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article