GoHighLevel Stripe Integration: Payments Setup Guide (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 15 July 2026 · 10 min read

On this page: Connecting Stripe · Products and prices · Order forms in funnels · Invoices and payment links · Subscriptions and payment plans · Tap to Pay and Text2Pay · Documents and contracts · Automating with Workflows · Fees, GST and AUD settings · Reconciling in Stripe · Common mistakes · FAQ

A working GoHighLevel Stripe integration is the difference between a CRM that tracks leads and a system that actually banks revenue. Having set up payments in well over a hundred Australian sub-accounts, I see the same pattern every time: the connection takes five minutes, but the configuration around it — products, currency, GST, workflows — decides whether you get a clean revenue engine or a reconciliation headache.

This guide walks through the full stack in order: connecting Stripe, building products, taking payment through order forms, invoices, subscriptions, Text2Pay and documents, then automating the follow-up with Workflows — written for Australian businesses, so AUD settings, GST and Stripe's local pricing get proper coverage.

Connecting Stripe in Settings → Payments → Integrations

In the sub-account you want to charge from, go to Settings → Payments → Integrations and click Connect on the Stripe card. You will be bounced to Stripe's OAuth screen, where you either sign in to an existing Stripe account or create one on the spot. Once authorised, GoHighLevel registers its webhooks against that Stripe account automatically — you do not need to paste API keys or build webhook endpoints by hand.

Three things to check immediately after connecting:

• Live vs test mode. GoHighLevel lets you connect both a live and a test Stripe key set. Confirm the toggle is on live before launch; a test-mode connection will happily accept the 4242 test card and nothing real.
• Default currency. Under Settings → Company (or the payments settings in newer builds), set the sub-account currency to AUD. Changing it later does not retro-fix existing prices.
• One Stripe account per sub-account. Each client sub-account should connect its own Stripe account so money settles to the right business. If you run SaaS Mode to resell GoHighLevel, your agency-level Stripe handles the SaaS subscriptions while each client's Stripe handles their customer payments — keep the two mentally separate.

Products, one-time prices and recurring prices

Under Payments → Products, create each thing you sell as a product, then attach one or more prices to it. A price is either one-time (a flat charge) or recurring (weekly, monthly, quarterly or annually, with an optional trial period and setup fee). One product can carry several prices — a coaching program might have a $2,970 pay-in-full price and a $550/month × 6 recurring price on the same product.

Products created in GoHighLevel sync to Stripe, and this is where discipline matters. Build products once, name them clearly (include the price and billing cycle in the name, e.g. “Foundations Program — $550/mo x6”), and reuse them across order forms and invoices. Teams that create a fresh product for every funnel end up with dozens of near-duplicates in Stripe that make reporting useless. If you deploy snapshots across client sub-accounts, remember that snapshots do not carry live Stripe products — rebuild or verify products in each sub-account after import.

Order forms in funnels: 1-step, 2-step, bumps and upsells

Order forms are the funnel builder's payment element. Drop an order form onto a funnel step, attach a product and price, and the page can take cards. There are two formats:

1-step vs 2-step order forms

A 1-step order form shows contact and card fields together — best for low-priced, low-friction offers where the buyer has already decided. A 2-step order form captures name, email and phone on step one, then card details on step two. The 2-step format powers abandoned-checkout follow-up: complete step one and the buyer exists as a contact even if no card is ever entered, so a Workflow can chase them. Over about $50, I default to 2-step. If you are still designing the funnel itself, my GoHighLevel funnel and lead-capture guide covers page structure before the payment layer.

Order bumps and one-click upsells

An order bump is a tick-box offer on the order form itself — a $27–$97 add-on that typically lifts average order value 15–30% with zero extra traffic. A one-click upsell lives on the step after purchase: Stripe has already vaulted the card, so the buyer accepts with a single click. Both are configured in the funnel step settings, not the product.

Invoices and payment links

Not everything belongs in a funnel. For service businesses, Payments → Invoices is often the real workhorse: build an invoice from your products, add tax, and send it by email or SMS. Invoices support one-off billing, recurring schedules and partial payments, paid on a hosted Stripe-powered page. Payment links are lighter again — a reusable URL tied to a product and price, pasted into a DM, quote email or QR code with no funnel page required.

Here is where each payment feature lives and where it fits best:

Subscriptions and payment plans

Attach a recurring price to a product and any order form or invoice using it becomes a subscription. Stripe manages the billing engine — retries, card updates, proration — while GoHighLevel records each cycle and can react to it in Workflows. For fixed-length payment plans (six monthly instalments rather than an open-ended retainer), use a recurring invoice schedule with an end date. Automate failed-payment recovery from day one: a charge failure can trigger an SMS with a fresh payment link before Stripe's dunning gives up.

Tap to Pay and Text2Pay

Text2Pay drops a payment request straight into an SMS or email conversation: tap the payment icon in the composer, pick a product or enter an amount, and the contact receives a secure Stripe checkout link. It is the fastest way to close over the phone — quote, text the link, get paid while you are still talking. Tap to Pay, via the HighLevel mobile app on supported phones, turns the device into a contactless terminal for in-person payments — handy for clinics, trades and market stalls. Both route through the same Stripe account, so everything reconciles in one place.

Documents and contracts with payment collection

Under Payments → Documents & Contracts, build proposals and agreements with signature fields and an attached product list. Enable payment collection and the client signs and pays in a single flow, with the deposit or first instalment charged the moment the signature lands. This collapses the classic three-step chase (proposal, contract, invoice) into one link, and the signed document plus the transaction both attach to the contact record automatically.

Automating payments with Workflows

The payment tools earn their keep when Workflows react to them. The triggers I wire into almost every build:

• Payment Received — fires on successful order form, Text2Pay or subscription payments. Filter to a specific product, then add a tag (e.g. customer-foundations), move the opportunity to “Won” in the pipeline, grant course access and send the welcome email.
• Invoice triggers — separate triggers for invoice sent, viewed, paid and partially paid. A polite SMS nudge three days after “viewed but unpaid” recovers a surprising amount of revenue with zero awkward phone calls.
• Abandoned checkout — fires when someone completes step one of a 2-step order form but never pays. A three-touch sequence (email at 1 hour, SMS at 24 hours, final email at 72 hours with the checkout link) is standard; recovery rates of 10–15% are realistic.
• Payment failed / subscription events — catch failed recurring charges and send an update-card link before the subscription churns.

Store useful values — amount paid, product name — in custom fields so your templates can reference them, and standardise tag names across sub-accounts. The payments layer is one slice of the broader build; my 75-task GoHighLevel implementation checklist sequences it against everything else.

Stripe fees, GST and AUD settings for Australian businesses

GoHighLevel does not add a platform surcharge to standard Stripe payments — you pay Stripe's processing fees, currently around 1.7% + A$0.30 for domestic cards and higher for international cards, per the published Stripe Australia pricing. Budget for the international rate if you sell to overseas buyers, and note that Stripe fees are not refunded when you refund a customer.

For GST, set up a 10% GST tax under the payments tax settings and apply it to your products or invoices. Decide deliberately whether prices are GST-inclusive or exclusive and keep it consistent — a registered business needs GST shown as a line for the invoice to function as a tax invoice. Confirm the sub-account currency is AUD before creating products; a product accidentally built in USD will charge Australian clients in US dollars and trigger conversion fees. Add your ABN and business address in invoice settings so tax invoices meet ATO formatting expectations.

Reconciling in the Stripe dashboard

GoHighLevel's Payments → Transactions view is fine for day-to-day visibility, but Stripe remains the source of truth for money. Reconcile in the Stripe dashboard: payouts show exactly which charges (net of fees) landed in your bank account and when — what your bookkeeper needs for Xero or MYOB matching. Check monthly that transaction counts roughly agree between the two systems; a mismatch usually means someone charged a card directly in Stripe, which means no tags, no workflow, no fulfilment trigger. Handle refunds and disputes in Stripe, then tidy the contact record in GoHighLevel. The official GoHighLevel help centre documents the current transaction sync behaviour if numbers ever drift.

Common mistakes to avoid

• Launching in test mode. The funnel “works”, the 4242 card is approved, and no real money moves. Always run one live $1 transaction before sending traffic, then refund it.
• Wrong currency on products. A USD product in an AUD sub-account charges the wrong currency silently. Set AUD before building anything.
• Duplicate products per sub-account. Rebuilding “the same” product for every funnel or after every snapshot import litters Stripe with duplicates and wrecks revenue reporting. One product, multiple prices, reused everywhere.
• No abandoned-checkout workflow on 2-step forms. If you built a 2-step order form but never wired the recovery sequence, you are paying for the friction without collecting the benefit.
• Ignoring GST setup. Invoices without an itemised 10% GST line and an ABN create BAS-time pain and are not valid tax invoices for registered businesses.
• Reconnecting Stripe carelessly. Disconnecting and reconnecting a different Stripe account can strand webhooks and existing subscriptions. If you must migrate Stripe accounts, plan it — do not just swap the connection on a live sub-account.

If you want your GoHighLevel payments stack — Stripe, order forms, invoices and payment automations — set up properly the first time, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Does GoHighLevel charge extra fees on top of Stripe?

No platform surcharge applies to standard Stripe payments through your own connected account — you pay Stripe's normal processing fees only (around 1.7% + A$0.30 for Australian domestic cards). The exception is SaaS Mode rebilling, where the agency configures its own markup on usage; that is a separate mechanism from your clients' customer payments.

Why is my order form not charging real cards?

Nine times out of ten the Stripe integration is still in test mode, so only test cards like 4242 4242 4242 4242 succeed. Check Settings → Payments → Integrations, switch to live mode, confirm the order form has a live product attached, and run a real $1 transaction to verify before launch.

Do I need a separate Stripe account for each sub-account?

Yes, in practice. Each client sub-account should connect the client's own Stripe account so funds settle directly to their bank and their name appears on card statements. Agencies running SaaS Mode use their agency-level Stripe for GoHighLevel subscription rebilling, which stays entirely separate from client transactions.

Can I collect GST on GoHighLevel invoices?

Yes. Create a 10% GST tax in the payments tax settings and apply it to products or individual invoice line items. Add your ABN and business details in invoice settings so the document functions as a valid tax invoice, and decide up front whether your listed prices are GST-inclusive or exclusive.

Can I use a payment provider other than Stripe?

GoHighLevel also supports PayPal, NMI, Authorize.net and others, but Stripe is the deepest integration — it powers subscriptions, Text2Pay, Tap to Pay, documents with payment and SaaS Mode rebilling. For Australian businesses I recommend Stripe as the primary provider and PayPal only as an optional secondary checkout button.