Learn what appears on the Subscriptions page, how provider statuses are represented, which subscription information stays synchronized, what is excluded, and how eligible SaaS V1 plan changes affect the corresponding subscription record.

The actions available for a subscription can depend on its payment provider, current status, and your Payments permissions. Subscription actions are managed from the Subscriptions area when supported, while eligible payment refunds are handled from Payments > Transactions.

The Payments Subscriptions page is the central location for reviewing recurring subscription records created through supported payment flows in a sub-account. It brings provider, customer, source, billing, status, and available transaction information together so billing teams can monitor active and historical subscriptions without checking each provider separately.

Keeping subscription information in one billing workspace makes it easier to monitor customers, investigate subscription issues, and manage supported lifecycle changes. The page also provides a consistent subscription view even when provider-specific terminology differs.

• Centralized Visibility: Review recurring subscription records without opening each payment provider dashboard.
• Customer Context: See customer, source, provider, amount, creation date, and status information together.
• Billing Tracking: Review supported subscription transactions and current subscription details.
• Status Clarity: Provider-specific subscription states are grouped into consistent subscription statuses.
• Subscription Management: Eligible subscriptions can be updated, paused, resumed, canceled, or otherwise managed when the provider, status, and user permissions support the action.
• SaaS V1 Alignment: Supported SaaS V1 upgrades and downgrades can keep the corresponding selling-sub-account subscription aligned with the current Stripe product and price.

Subscriptions can reach the Payments area through more than one supported sales or billing flow. Understanding the source and fields shown on each record helps you determine where a subscription originated and which provider is managing it.

The page can include subscriptions created through supported sources such as:

• Manual subscription creation, such as from a contact's Payments area, when supported by the selected provider.
• Supported 1-Step and 2-Step Order Form subscription purchases.

Available list information can include:

• Payment provider and subscription ID
• Customer details
• Source of subscription creation
• Creation date
• Subscription amount
• Subscription status

Opening a subscription gives you more context than the list view alone. The available details help connect the subscription to its payment provider, original source, customer, and supported billing activity.

• Payment provider information
• Source of subscription creation
• Available customer and billing details
• Current subscription information
• Subsequent transactions for supported Stripe-created subscriptions

Metadata

Some subscriptions can include additional metadata captured during checkout or subscription creation, such as a company name or other supported contextual information.

Payment providers can use different names for similar lifecycle states. HighLevel groups supported provider states into subscription statuses so teams can interpret subscription health more consistently from the Payments area.

Synchronization behavior depends on the payment provider and the type of subscription workflow involved. Separating general provider status synchronization from SaaS-specific plan-change synchronization prevents broader sync expectations than the platform supports.

Stripe Subscriptions

For supported Stripe-created subscriptions, subscription status and received payment information can remain synchronized with Stripe. For example, when a supported subscription is canceled in Stripe, the corresponding subscription can reflect a Canceled status in the Subscriptions list.

PayPal Subscriptions

PayPal-created subscriptions can appear in the Subscriptions list, but the documented PayPal behavior does not continuously synchronize subscription status or capture subsequent payments in the same way as Stripe.

Not every recurring payment or recurring billing configuration creates a record in the Payments Subscriptions list. Knowing the exclusions helps prevent a missing record from being mistaken for a synchronization problem.

• Failed initial subscription creation: If the first payment fails while the order form is being submitted and the subscription is never successfully created, it is not registered as a subscription on this page.
• Recurring invoice templates: Recurring templates created in the Invoices area are not listed as subscription records here.
• Membership-created subscriptions: Subscriptions created inside the Memberships area are not included in this documented Subscriptions-page list.

Opening the Subscriptions page gives you access to recurring billing records and the actions supported for each subscription. Review the provider, status, and available actions before making a lifecycle change because available controls can vary by subscription.

Step 1: Open the Subscriptions Page

Step 2: Open a Subscription

Step 3: Use the Appropriate Billing Action

Subscription and payment actions are handled in different areas:

• Update a supported subscription: Use the available subscription actions to modify eligible products, quantities, dates, or other supported settings.
• Pause, resume, or cancel: Use the subscription action when it is supported by the provider, status, and your permissions.
• Refund an eligible payment: Go to Payments > Transactions and use the refund action on the applicable transaction.
• Export subscription records: Use the available download/export action from the Subscriptions page when your permissions allow it.