Payment Integrations in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers the four payment processors HighLevel supports, how each connects, which features each processor enables, and how agencies manage payment integrations across client sub-accounts.

Reading time: about 7 minutes.

What Are Payment Integrations in HighLevel?

Payment integrations in HighLevel are the connections between the platform and external payment processors that enable actual money to change hands.

HighLevel provides the checkout infrastructure – order forms, payment links, invoice pages, subscription billing interfaces – but does not process payments directly. Every transaction flows through a connected third-party processor: Stripe, NMI, Authorize.net, or PayPal.

Without a connected payment integration, the checkout pages exist but cannot complete transactions. A HighLevel sub-account without a payment processor connected is like a storefront without a register.

Connect payment processors at Settings, then Payments, then Integrations.

The Four Supported Processors

HighLevel supports four payment processors, each covering a different set of use cases and customer preferences.

Stripe is the primary and most fully featured processor within HighLevel. Recommended for most businesses.

NMI (Network Merchants Inc.) is an alternative processor that connects via API keys. Used by businesses with existing NMI relationships or those that need a processor NMI supports that Stripe does not in their market.

Authorize.net is another API key-based alternative. Well-established in the US market, particularly among businesses that have been using it for years and prefer not to migrate to Stripe.

PayPal adds PayPal wallet and Venmo as checkout options. Connects via OAuth with a PayPal Business account.

Typically used alongside Stripe rather than as a replacement.

Stripe – The Primary Recommendation

Stripe is the most deeply integrated payment processor in HighLevel. The broadest range of HighLevel payment features work exclusively or most reliably with Stripe.

Stripe supports one-click order bumps on funnel checkout pages – the customer adds a product to their order without re-entering payment details because the card is tokenized in Stripe. One-click upsells on order confirmation pages use the same mechanism.

Stripe handles HighLevel’s full subscription billing infrastructure – recurring charges, automatic retry logic, dunning notifications, subscriber management, and cancellation workflows. The subscription system in HighLevel is built around Stripe’s subscription API.

Stripe also provides payment links, invoice payment collection, calendar booking deposits, and the most complete international payment support of any HighLevel-connected processor.

The connection uses OAuth – you authorize HighLevel to create charges on your Stripe account without sharing your Stripe API keys directly. The connection is established in minutes and can be revoked from either platform at any time.

NMI and Authorize.net

NMI and Authorize.net are established payment processors that connect to HighLevel via API key entry rather than OAuth.

Both support standard checkout functionality – credit and debit card processing on funnel order forms and checkout pages. Both are widely used in the US market and are appropriate for businesses with existing relationships with those processors who prefer not to migrate to Stripe.

The trade-off compared to Stripe is feature depth. One-click order bumps and upsells, the full subscription management system, and some of the more advanced payment features in HighLevel are most reliable or exclusively available with Stripe.

Businesses choosing NMI or Authorize.net for specific reasons should verify that the specific HighLevel payment features they need work with their chosen processor.

PayPal

PayPal adds PayPal wallet and Venmo as payment options on HighLevel checkout pages. It connects via OAuth with a PayPal Business account – the same type of authorization flow as Stripe.

PayPal is most useful as an addition to Stripe rather than a replacement. Stripe handles credit card processing and subscription billing.

PayPal handles customers who prefer to pay with their PayPal balance or Venmo rather than entering card details.

The full details of the PayPal and Venmo integration are in the dedicated PayPal and Venmo Integration post.

Using Multiple Processors Together

Multiple payment processors can be connected to the same HighLevel sub-account simultaneously. The most common combination is Stripe plus PayPal.

When both are connected and enabled on a checkout page, the customer sees their choice: pay by credit card (processed through Stripe) or pay with PayPal or Venmo (processed through PayPal). Each transaction routes to the appropriate processor based on the customer’s selection.

There is no conflict between having multiple processors connected. Each processes only the transactions that go through its specific payment button.

Revenue from each processor appears in that processor’s dashboard separately – and all transactions appear in HighLevel’s Payments section together.

Agency Setup – Per-Sub-Account Processors

Each HighLevel sub-account has its own independent payment integration settings. This is critical for agencies managing multiple client accounts.

A client sub-account connects the client’s own Stripe or PayPal account – not the agency’s. Money from the client’s checkouts, funnels, and invoices flows directly into the client’s processor account, not the agency’s.

The agency never touches the client’s funds.

This per-sub-account structure means the agency sets up the payment integration for each client during onboarding – guiding the client to connect their own processor rather than connecting a shared agency processor to all accounts.

The exception is when an agency wants to sell HighLevel-based products through its own funnel using its own processor. That uses the agency’s own sub-account with the agency’s connected processor – completely separate from client sub-accounts.

What Features Require a Payment Integration

A connected payment processor is the prerequisite for every HighLevel feature that involves a financial transaction.

Features that require a payment integration: funnel checkout pages and order forms, payment links, invoices with online payment, subscription products, calendar booking deposits, course and membership sales, order bumps and upsells on funnels.

Features that do not require a payment integration: forms, surveys, CRM, conversations, calendars without deposits, workflows, automations, email and SMS marketing, social media, reporting.

Many businesses set up HighLevel and use the CRM and automation features for weeks or months before connecting a payment processor. The integration is not a prerequisite for the platform overall – only for the specific features that involve collecting money.

What Can You Do With It?

• Accept credit and debit card payments through HighLevel funnels: Connect Stripe and every checkout page, order form, and payment link in HighLevel can process real transactions immediately. The entire purchase flow – add to cart, enter card, confirm, thank you – is handled within the platform.
• Add PayPal and Venmo as checkout options alongside credit cards: Connect PayPal in addition to Stripe and customers can choose their preferred payment method on the same checkout page.
• Enable subscription billing for recurring revenue: With Stripe connected, all of HighLevel’s subscription infrastructure – recurring charges, retries, dunning, subscriber management – is available for any subscription product.
• Collect invoice payments online: With a processor connected, every invoice sent from HighLevel includes an online payment link – no bank transfer coordination, no chasing checks. The client clicks the link and pays by card.
• Collect deposits on calendar bookings: Booking pages with a required deposit connected to Stripe can collect payment when a client confirms an appointment – the appointment is not booked until the deposit is paid.
• Keep client payments separate from agency funds: Each client sub-account connects the client’s own processor. Client revenue goes directly to the client. The agency’s processor handles only the agency’s own transactions.

Key Definitions

Use Cases by Industry

New HighLevel User – First Setup

A business coach sets up HighLevel for the first time. They go to Settings, then Payments, then Integrations and connect their existing Stripe account via OAuth.

The connection takes under 5 minutes.

Immediately after connecting, they can create a checkout page for their coaching package, enable payment on their calendar booking page for a deposit, and send invoices with online payment – none of which required any coding or third-party tool beyond the Stripe connection.

Result: Full payment infrastructure – checkout, booking deposit, invoices – available within 10 minutes of a new HighLevel setup. The Stripe connection is the single prerequisite for all of it.

Marketing Agency – Client Onboarding

An agency builds a complete HighLevel funnel for a new client. As part of onboarding, they guide the client to Settings, then Payments, then Integrations in the client’s sub-account to connect the client’s own Stripe account.

Once the client’s Stripe is connected, all revenue from the client’s funnel goes directly to the client’s Stripe account. The agency has no access to the client’s funds and no involvement in the client’s payment processing – the infrastructure is in place, and the client owns it.

Result: Clean client money separation. The agency’s payment processor is never at risk from client transactions, and clients retain direct ownership of their revenue stream from day one.

E-Commerce Store – Multiple Payment Methods

An e-commerce store connects both Stripe and PayPal to the same sub-account. The checkout page displays a credit card form (Stripe) and a PayPal button (PayPal) as equally prominent options.

Customers who prefer card entry use Stripe. Customers who prefer PayPal use PayPal.

Customers on mobile who use Venmo use Venmo via the PayPal flow. All orders appear in HighLevel’s Payments section regardless of which processor handled the transaction.

Result: Maximum payment method coverage without duplicating checkout infrastructure. One checkout page, two processors, three payment options for customers.

SaaS Business – Subscription Revenue

A SaaS business built on HighLevel sells monthly and annual subscription plans. Stripe is connected as the payment processor.

All subscription products are configured to use Stripe.

Recurring billing, failed payment retries, dunning notifications, and subscriber management all operate through Stripe’s subscription infrastructure within HighLevel. The business’s monthly recurring revenue is visible in both Stripe’s dashboard and HighLevel’s Payments section.

Result: The complete subscription billing lifecycle is handled by Stripe’s infrastructure, accessed and managed through HighLevel’s interface. No separate subscription billing tool required.

Healthcare Practice – Existing Authorize.net Relationship

A medical practice has used Authorize.net for years and has existing relationships with their merchant services provider. They connect Authorize.net to HighLevel via API key entry rather than migrating to Stripe.

Standard checkout functionality – collecting patient payments for services not covered by insurance – works through Authorize.net. The practice acknowledges that advanced subscription features are limited compared to Stripe, but standard payment collection is all they need.

Result: The practice integrates HighLevel with their existing payment infrastructure without disrupting a long-established processor relationship. Standard payment collection works reliably without a migration.

Who Is This For?

How to Connect a Payment Processor

Step 1: Go to Payment Integrations

In the sub-account, go to Settings, then Payments, then Integrations.

The integrations list shows all available processors and their current connection status.

Step 2: Choose your processor

For most businesses: Stripe. For PayPal and Venmo checkout options as well: PayPal in addition to Stripe.

For businesses with existing NMI or Authorize.net accounts: the respective processor.

Step 3: Connect Stripe

Click the Stripe option. Follow the OAuth authorization flow – you are redirected to Stripe, you log in and approve, and you return to HighLevel with the connection confirmed.

A new Stripe account can be created from this flow if you do not have one yet.

Step 4: Connect NMI or Authorize.net if applicable

For NMI or Authorize.net, enter the required API keys from your processor account. These are found in your processor’s dashboard under developer settings or API credentials.

Save the credentials. The processor shows as active when the keys are verified.

Step 5: Connect PayPal if needed

Click the PayPal option and follow the OAuth flow with your PayPal Business account. PayPal connects alongside Stripe without any conflict.

Step 6: Verify all connections

Confirm all connected processors show as active in the integrations list. Check that the account names match the expected accounts.

Step 7: Test with Stripe test mode

Use a Stripe test card number to complete a test purchase on a checkout page. Confirm the order records in Payments, the contact is in the CRM, and any configured workflows fire.

Step 8: Set currency

In the sub-account payment settings, confirm the currency is correct for the primary market. Currency configuration affects how prices display to customers at checkout.

Step 9: Enable payment on specific pages and products

With the integration connected, configure individual funnel checkout pages to use the connected processor. For subscription products, confirm Stripe is selected – Stripe provides the most complete subscription support in HighLevel.

How Does It Connect to HighLevel?

• Subscriptions: HighLevel Subscriptions run on Stripe’s subscription infrastructure. Connecting Stripe is the prerequisite for recurring billing, automatic retries, dunning workflows, and the full subscriber management system.
• Invoicing: HighLevel Invoicing sends invoices with a payment link that routes through the connected processor. The client clicks the link and pays by card. Without a connected processor, the invoice can be created but the payment link does not function.
• PayPal and Venmo Integration: The PayPal and Venmo Integration is one component of the broader payment integrations system – a second processor that adds PayPal wallet and Venmo as checkout options alongside Stripe.
• Tax and International Billing: Tax configuration and international payment acceptance both depend on the connected payment processor. Stripe’s international reach and Stripe Tax compatibility make it the preferred processor for businesses selling across multiple markets.
• Workflow Builder: Payment events – Order Placed, Subscription Payment Received, Payment Failed – fire workflow triggers in Workflow Builder regardless of which connected processor handled the transaction. Post-purchase automation operates consistently across processors.

Common Questions

What payment processors does HighLevel support?

Stripe, NMI, Authorize.net, and PayPal. Stripe is recommended for most businesses – it supports the broadest range of HighLevel payment features.

PayPal is typically added alongside Stripe for PayPal and Venmo checkout options.

Where do I connect a payment processor in HighLevel?

Go to Settings, then Payments, then Integrations in the sub-account. Click the processor to connect and follow the steps – OAuth for Stripe and PayPal, API key entry for NMI and Authorize.net.

Can I use multiple payment processors in HighLevel at the same time?

Yes. Multiple processors can be connected and active simultaneously.

Stripe and PayPal are commonly used together on the same checkout page – credit cards through Stripe, PayPal and Venmo through PayPal.

Is Stripe the best payment processor for HighLevel?

Yes for most businesses. Stripe supports one-click order bumps and upsells, full recurring subscription billing, the complete dunning system, payment links, and multi-currency.

NMI and Authorize.net support standard checkout but have more limited advanced feature support.

How do I connect Stripe to HighLevel?

Go to Settings, then Payments, then Integrations. Click Stripe and follow the OAuth flow – redirected to Stripe, log in, approve, return to HighLevel.

The connection confirms in minutes.

What HighLevel features require a payment integration?

Funnel checkouts, payment links, invoices with online payment, subscription products, calendar booking deposits, and course or membership sales all require a connected payment processor.

Can agencies connect different payment processors for different client sub-accounts?

Yes. Each sub-account has independent payment integration settings. Client sub-accounts connect the client’s own processor – money flows directly to the client, not the agency.

Does HighLevel have its own payment processing?

No. HighLevel provides checkout infrastructure but all transactions are processed by the connected third-party processor – Stripe, NMI, Authorize.net, or PayPal.

Can I test payments in HighLevel before going live?

Yes. Use Stripe test cards to verify checkout flows, CRM contact creation, and workflow triggers without processing real transactions. Test mode is available in the Stripe dashboard.

Does connecting a payment processor to HighLevel affect my existing Stripe or PayPal account?

No. The connection authorizes HighLevel to create charges on your behalf. It does not alter your existing account settings, products, subscriptions, or data in Stripe or PayPal.

To Wrap It Up

Payment integrations are the foundation of every revenue-generating feature in HighLevel. Without a connected processor, the checkout pages are display-only, the invoices cannot be paid online, and the subscriptions cannot bill.

The decision of which processor to connect is straightforward for most businesses: Stripe. It connects in minutes via OAuth, supports the full range of HighLevel payment features, and is available in most countries where HighLevel’s user base operates.

PayPal is the most common addition – connected alongside Stripe to add PayPal wallet and Venmo as checkout options for customers who prefer those methods. The two processors work together without conflict.

NMI and Authorize.net serve businesses with existing processor relationships that outweigh the advantages of migrating to Stripe. Both support standard checkout functionality, though the advanced features like one-click upsells and full subscription management are most reliable with Stripe.

For agencies, the key operational detail is that each client sub-account connects the client’s own processor. Client money never passes through the agency’s processor.

That separation is not just a technical detail – it is a legal and trust boundary that the per-sub-account payment integration structure enforces automatically.

Here is how to get started:

1. Go to Settings, then Payments, then Integrations in the sub-account
2. Click Stripe and follow the OAuth authorization flow
3. Verify the connection shows as active with the correct Stripe account
4. Connect PayPal if PayPal and Venmo checkout options are needed
5. Set the sub-account currency to match the primary market
6. Use a Stripe test card to complete a test purchase and verify the full flow
7. Confirm CRM contact creation and post-purchase workflow triggers are working
8. For agencies: guide each client to connect their own processor to their sub-account during onboarding

The test purchase step is not optional. A payment integration that looks connected in the settings but has an issue with currency, webhook configuration, or account status will only surface the problem on the first real customer transaction.

A test purchase takes 3 minutes and confirms everything is working before a real customer’s experience depends on it.