How to Manage Unified Payments in GoHighLevel — V1 & V2

Managing payments across multiple SaaS locations shouldn't require juggling different platforms, payment processors, and billing workflows. If you're running a GoHighLevel agency or managing multiple sub-accounts, you've probably experienced the friction of version-specific payment quirks—different checkout experiences, inconsistent payment methods, and fragmented billing dashboards.

GoHighLevel's Unified Payment Options solve this problem by standardizing payments across V1 and V2, letting you configure your payment processors once and apply them globally across all locations. In this guide, I'll walk you through exactly how to set up and manage unified payments so your teams and clients experience seamless, consistent billing every time.

Already interested? Start your free 30-day trial here to see unified payments in action across your entire account.

What Are Unified Payment Options in GoHighLevel?

Unified Payment Options represent a paradigm shift in how GoHighLevel handles billing. Rather than managing separate payment configurations for V1 and V2 locations, or configuring payment processors independently for each sub-account, you now configure them once at the parent account level and they apply uniformly across your entire infrastructure.

This means:

• Single source of truth: One Stripe or Authorize.net account, configured in one place, serving all your locations
• Consistent checkout experience: Your clients and customers see the same payment interface regardless of which version they're using
• Simplified reconciliation: All transactions feed into one payment processor account, making accounting and financial reporting straightforward
• Reduced configuration errors: No more mismatched API keys, missing webhooks, or location-specific setup mistakes

For agencies managing 5, 15, or 50+ client locations, unified payments eliminate the operational overhead of managing individual payment configurations for each location.

Key Differences Between V1 and V2 Payment Handling

GoHighLevel V1 and V2 historically had different payment flows. V1 used a more traditional workflow, while V2 introduced modernized payment architecture. Without unified payments, you'd need to understand and maintain both systems.

V1 Payment Characteristics:

• Direct Stripe integration at the location level
• Payment forms embedded in workflows and funnels
• Webhook handling managed per location
• Subscription management routed through location-specific settings

V2 Payment Characteristics:

• Enhanced payment UI with improved error handling
• Native support for multiple payment methods in a single checkout
• Advanced subscription and recurring billing features
• Better webhook standardization and event handling

Unified Payments bridge these differences by creating a standard payment layer that both versions use. You no longer need to worry about version-specific quirks because the underlying payment infrastructure is the same.

How to Configure Stripe and Authorize.net Across All Sub-Accounts

Setting up unified payments is straightforward. Here's the step-by-step process:

Step 1: Access Your Parent Account Settings

Log into your GoHighLevel master account (not a sub-account). Navigate to Settings → Payment Processors or Billing → Payment Methods depending on your account age and plan tier.

Step 2: Connect Your Payment Processor

Choose either Stripe or Authorize.net. For Stripe, you'll need:

• Your Stripe Account ID
• Your Publishable Key
• Your Secret Key

For Authorize.net, you'll need your API Login ID and Transaction Key.

Once you've entered these credentials and clicked Connect, GoHighLevel validates the connection and begins syncing with your processor.

Step 3: Enable Unified Payment Distribution

Look for an option labeled "Apply Payment Settings Across All Sub-Accounts" or similar. Check this box. This setting tells GoHighLevel to use your parent account's payment processor credentials for all child locations.

Step 4: Verify Sub-Account Configuration

Log into one of your sub-accounts and navigate to its payment settings. You should see that the payment processor is now inherited from the parent account, with a note like "Using parent account payment configuration." No local configuration is needed or allowed.

Step 5: Test a Transaction

Create a test product or invoice in both a V1 and V2 location. Attempt a payment on each. Both should route through your unified payment processor without errors. If either fails, double-check that your API credentials are correct and that webhooks are enabled in your processor account.

This is built into GoHighLevel. Try it free for 30 days →

Payment Methods Available: Cards, Wallet Credits, and Agency Cards

Unified payments support multiple payment method types, giving your customers flexibility while keeping your configuration centralized.

Saved Credit Cards

Customers can save their card details during checkout. On subsequent transactions, they select their saved card without re-entering information. This reduces checkout friction and improves conversion rates. GoHighLevel stores tokenized card data securely; your payment processor (Stripe or Authorize.net) handles PCI compliance.

Wallet Credits

Wallet credits allow customers to prepay a balance that's deducted from future invoices or purchases. This is valuable for SaaS billing, retainers, or any recurring revenue model. Customers can add credit through your payment processor, and GoHighLevel tracks their balance in real-time.

Agency Cards

Agency cards enable team members within your organization to charge transactions to a company card without exposing full card details. This is particularly useful for agencies where multiple team members need to process payments on behalf of clients but shouldn't have access to master billing information.

To enable these methods:

• Go to Settings → Payment Methods
• Check the boxes for each method you want to support
• Save your changes
• The options will immediately appear to customers in checkout flows

Role-Based Billing for Agencies and Location Users

Unified payments respect role-based access control. Different team members have different permissions based on their role within GoHighLevel.

Parent Account Owners: Full access to unified payment configuration, processor credentials, and billing across all sub-accounts.

Sub-Account Admins: Can view payment history and invoices but cannot modify payment processor settings (because those are centralized). They can create invoices, products, and checkout flows that use the unified payment processor.

Location Users: Can accept payments through forms, funnels, and invoices but have no access to payment processor configuration or financial reporting.

This structure ensures that billing security and compliance remain at the parent account level while empowering sub-account teams to actually use the payment functionality without exposing sensitive credentials.

Best Practices for Streamlining Your Billing Workflow

1. Centralize Your Payment Processor Account

Use a single Stripe or Authorize.net account for your entire agency. This simplifies reconciliation, reduces monthly subscription costs (you're not paying per-location fees), and gives you a clear view of all transactions in one dashboard.

2. Automate Invoice Reminders

GoHighLevel's unified payment system integrates with automation workflows. Create a workflow that sends invoice reminders 3 days before due date, 1 day after due date, and 7 days after. Link these workflows to your payment processor so when a payment is received, the reminder stops automatically.

3. Use Saved Cards for Recurring Billing

For subscription or membership products, enable saved cards and set up recurring charges. Your customers save their card once, and subsequent charges happen automatically, reducing payment failures and churn.

4. Monitor Webhook Logs

Webhook failures silently break payment workflows. Monthly, check your payment processor's webhook event log in GoHighLevel. Look for failed events (usually indicated by a red status). If you see failures, verify that your webhook URL hasn't changed and that your processor's firewall isn't blocking GoHighLevel's servers.

5. Reconcile Monthly

Export your GoHighLevel transaction report and compare it to your payment processor's settlement report. Discrepancies usually indicate webhook failures or partially processed transactions. Catching these monthly prevents accounting headaches at year-end.

6. Test Payment Flows Before Going Live

Whenever you add a new product, invoice template, or payment form, test it in a sandbox or staging location first. Process a real test transaction (using Stripe's test card 4242 4242 4242 4242) and verify that the charge appears in your processor account and that the customer receives a confirmation email.

Conclusion

Unified Payment Options in GoHighLevel eliminate the complexity of managing payments across multiple versions and locations. By configuring your payment processor once at the parent account level, you gain consistency, reduce errors, and free up time your team was spending on payment troubleshooting. Whether you're managing 2 sub-accounts or 50, unified payments scale with you.

The three key takeaways: (1) Set up your payment processor in your parent account and enable unified distribution; (2) leverage the full range of payment methods—saved cards, wallet credits, and agency cards—to give customers options; (3) automate your billing workflows so payments, invoices, and reminders work together seamlessly.

Ready to simplify your billing? Start your free 30-day trial today and experience how unified payments transform your agency's financial operations.