Understanding the Two CRM Billing Architectures: V1 and V2

Overview

The CRM platform supports two distinct architectures for managing Software-as-a-Service (SaaS) subscriptions, referred to as V1 and V2. These are not sequential upgrades but rather separate systems built on different technical foundations. Your choice between them depends on your agency's specific needs, preferred payment processors, and desired level of integration with the CRM's internal tools.

What is SaaS V1?

SaaS V1 is an architecture where the Stripe payment platform serves as the central system of record. All aspects of your subscription billing—including product definitions, customer profiles, active subscriptions, invoices, and payment details—are managed directly within your Stripe account. The CRM links each of your client sub-accounts to a specific Stripe customer record. To use V1, you must connect your Stripe account at the agency level. This system is ideal if you primarily use Stripe and value its robust, native billing tools and ecosystem.

What is SaaS V2?

SaaS V2 uses your agency's master sub-account within the CRM as the system of record. Your products, customers, and subscriptions are all managed inside the CRM platform itself. Payment providers, including Stripe and others, function purely as transaction processors. Your client sub-accounts are linked to contacts within your agency's master account. To use V2, you connect your chosen payment provider inside that master sub-account. This architecture is best if you want to use payment providers other than Stripe or seek deeper integration with the CRM's internal features like automation and contact management.

Important: V2 is Not an Upgrade from V1

It is a common misconception that V2 is a newer, superior version of V1. This is not the case. They are two different systems. V1 remains a mature, stable, and fully supported option with a robust feature set. V2 offers greater payment flexibility and CRM integration but is a newer system that does not yet support every feature available in V1.

SaaS V1: Pros and Cons

Pros

• Proven Stability: V1 is a well-established, battle-tested system that has been used reliably for a long time.
• Comprehensive Feature Support: It supports the full range of SaaS billing features currently available on the platform.
• Direct Stripe Integration: By using Stripe as its core, V1 gives you access to Stripe's powerful native tools for subscription management, dunning, notifications, and third-party integrations.

Cons

• Limited CRM Integration: Because the data lives in Stripe, the integration with CRM tools like automations, the affiliate manager, and other sub-account features is not as deep.
• Stripe-Only: V1 is exclusively compatible with the Stripe payment processor.

SaaS V2: Pros and Cons

Pros

• Multiple Payment Providers: V2 supports several payment processors, including Stripe, Square, Adyen, Mercado Pago, NMI, and Authorize.net, giving you more choice.
• Deeper CRM Integration: With the CRM as its system of record, V2 integrates seamlessly with native features like the CRM, contact management, workflows, and automations.

Cons

• Newer System: As a more recent architecture, V2 does not yet support all the advanced billing and subscription features that are available in V1.

Which Version Should I Choose?

Your decision should be guided by your agency's priorities. Choose SaaS V1 if you are committed to using Stripe and require the most stable, feature-complete billing system. Choose SaaS V2 if you need to use a payment provider other than Stripe or want your subscription data to be deeply integrated with your CRM's tools and automations. Carefully review the specific features you need before making a selection.

Conclusion

Both SaaS V1 and V2 are actively maintained and developed. They represent two different approaches to subscription management, each with its own strengths. There is no single correct choice; the best architecture for your business depends on your specific technical requirements and strategic goals.