01Who this is for
- Founders who run agencies and need to control client payment methods and Stripe connections.
- Small business owners using subaccounts to separate client work and want to reassign subscriptions.
- Agency admins responsible for maintaining accurate billing information across multiple clients.
02SaaS mode, explained
The FAQs address three common tasks in the SaaS configurator. First, they explain why the final payment card cannot be removed from a subaccount and what conditions must exist to delete a card. Second, they outline the process for disconnecting Stripe Connect, including the need to disable SaaS for any blocked subaccounts. Third, they describe how to transfer a subscription from one subaccount to another when both share the same Stripe customer.
All three procedures are found under the SaaS Configurator area of HighLevel. Card management actions are performed on the subaccount billing page, while Stripe Connect settings live in Agency Settings > Stripe Connect. Subscription moves require disabling SaaS on the source account without cancelling the underlying Stripe subscription, then reloading the target account so the subscription attaches automatically.
03How businesses use saaS mode
- Digital marketing agency. The agency disables SaaS for a client subaccount that blocks Stripe disconnect, then removes the Stripe integration. This clears the path to connect a new payment processor.
- Online course platform. When a student’s enrollment moves to a different subaccount, the platform disables SaaS on the original subaccount, reloads the new subaccount, and lets the existing subscription attach automatically.
- Co working space manager. If only one card remains on a member’s billing page, the manager adds a second payment method, ensures the primary card stays active, and then deletes the unwanted card through the billing interface.
04The numbers and rules that matter
- Autorecharge does not support 3DS only cards.
- SaaS V1 uses Stripe only and is configured at agency level.
- SaaS V2 supports Stripe, NMI, Authorize.net, Square and is configured per subaccount.
- 2FA is required even if turned off because email verification is mandatory.
05Before you start
- A second payment method must be added before attempting to delete the last card.
- Both subaccounts must be linked to the same Stripe customer before moving a subscription.
06How to set up and use saaS mode in HighLevel
Delete last card from billing page
- Confirm that another payment method is already attached to the subaccount.
- Make sure the card you want to delete is not set as the primary card.
- Remove the unwanted card using the billing page controls.
Disconnect Stripe Connect
- Open Agency Settings and select Stripe Connect.
- Locate any subaccounts that block the disconnect.
- Turn off SaaS for each blocked subaccount.
- Attempt the Stripe disconnect again.
Move subscription between subaccounts
- Verify that the source and target subaccounts share the same Stripe customer ID.
- Disable SaaS on the source subaccount without cancelling the subscription.
- Reload the target subaccount so the subscription attaches automatically.
07Settings that matter
- SaaS Configurator → Advanced Settings. Controls custom values that appear in the welcome email template.
- [Do Not Edit] SaaS Configurator Templates. Stores the default welcome email template; resetting it restores the standard email.
- Agency Settings → Stripe Connect. Allows connection or disconnection of a Stripe account used for SaaS billing.
- SaaS Configurator → Security → Pause new sub, accounts. Determines whether new subaccounts are automatically paused pending approval.
08Things to know before you rely on it
- The final card on a subaccount cannot be deleted; a primary card also cannot be removed.
- Auto recharge fails with cards that are 3 DS only; a non 3 DS only card is required.
- SaaS V2 subscriptions cannot change billing interval; only same interval upgrades are permitted.
- Disabling SaaS cancels the subscription and permanently deletes the wallet; refunds must be handled manually.
09If something goes wrong
- Auto recharges are failing. Replace the 3 DS only card with a card that supports 3 DS but is not 3 DS only, or switch to manual recharge.
- Cannot disconnect Stripe because of active clients. Disable SaaS for every subaccount that relies on the Stripe account, then retry the disconnect.
- Rebilling is not enabled or not moved to LC. Complete the required email and phone verification or verify the subaccount manually via Manage Client.
10How it connects to the rest of HighLevel
- How to activate phone rebilling in HighLevel SaaS mode Phone rebilling guide
- Managing SaaS wallet credits in HighLevel Wallet credit management
- HighLevel guide to canceling SaaS subaccounts and client self cancellation Cancel SaaS subaccounts
Michael's take

Can I really manage all my client subscriptions from one place? Absolutely. SaaS mode gives you a single hub to control billing, wallets, and plan changes for every subaccount. The biggest win is that you can turn software on or off per client, move subscriptions between accounts, and keep payment methods linked without juggling separate Stripe dashboards.
If I were setting this up, I’d start by mapping each client to its own Stripe customer so card updates stay isolated. Then I’d test a welcome email template, make sure the Custom Values appear, and finally verify that the dashboard visibility matches who needs to see it. A quick check on 2FA and email verification saves you from surprise blocks later.