You can connect a payment gateway to GoHighLevel in a few minutes. You link Stripe in the settings, add it to an order form, and the money starts coming in. The trouble comes later: a customer asks whether they can pay through GoPay (a Czech payment gateway), and your accountant asks where the invoice with the variable symbol (the Czech payment reference) is. The American platform has no answer to either question on its own.
In accounts I take over from others, I keep seeing the same picture. A course instructor has a finished course, a sales page, welcome emails, and Stripe connected. Then one of her customers writes that she doesn’t want to pay by card, and the accountant sends the document back because half the details are missing. The gateway worked flawlessly the whole time. What didn’t fit was everything around it.
Which payment gateways does GoHighLevel support on its own?
Five, natively: Stripe, PayPal, Square, NMI, and Authorize.net. You connect them in the Payments section, on the Integrations tab, and the platform then uses them in order forms, invoices, and the booking calendar.
The customer pays in a few seconds. You live with the invoice for that payment for years.
For a Czech business, that leaves Stripe in practice. It handles Czech crowns, and Apple Pay and Google Pay work through it. NMI, Authorize.net, and Square mainly target US merchants, and PayPal works as an add-on for customers abroad. I always try each gateway first in the test mode GoHighLevel offers for payments, and I switch to live mode only after a test order.
Payment gateway
A service that takes the customer’s card or bank details, verifies the payment, and sends the money to your account. GoHighLevel doesn’t hold the money itself: it just asks the gateway whether the payment went through and, depending on the answer, lets the rest of the automation run.
GoPay and Comgate: why you won’t find them in the list
GoHighLevel is an American platform, and it builds its gateway lineup for the US market. It does have a framework that lets a developer connect other gateways as a marketplace app. But as of October 8, 2026, I hadn’t found a verified, ready-made app for either GoPay or Comgate.
Even if one showed up, the same would apply to it as to any third-party add-on. Another link gets added to the chain your money travels through, and someone you don’t know is responsible for it. With payments, I want the chain as short as possible. And Czech businesses aren’t alone in this. In GoHighLevel user discussions on Reddit, people from across Europe are working out how to get a document out of Stripe in GoHighLevel that holds up under EU VAT rules.
Two routes that work for Czech businesses
Either the customer pays directly in GoHighLevel through Stripe and the invoice is issued elsewhere, or they pay in FAPI (a Czech invoicing and payments tool) and GoHighLevel just learns about the payment. Both routes make sense, each for a different kind of seller.
Stripe in GoHighLevel, invoice in FAPI. The order goes through on a page built in GoHighLevel. A workflow catches it and sends it to FAPI, which issues a Czech invoice. The whole purchase happens under your brand on one page, and the customer goes straight into the course.
Payment and invoice both in FAPI. According to its own overview, FAPI supports GoPay, ThePay, Comgate, Pays, Stripe, and GP webpay. The customer fills out the order in FAPI, pays through the gateway they’re used to, and the invoice is created right away. GoHighLevel then gets notified of the payment and triggers the rest: it adds a tag, unlocks the course, and sends a welcome email.
Payment anchor
The system where the payment actually originates and where all the others learn about it from. In the first route, the anchor is GoHighLevel. In the second, it’s FAPI. There should only ever be one anchor. When a payment is recorded in two places independently, sooner or later the two records will drift apart.
Three questions for your accountant
Before you connect a gateway, find out three things from your accountant. First, whether they need an invoice at the moment of payment or a monthly summary is enough. Second, whether they want website sales in their own number series. And third, which system they’ll pull the records from. Based on the answers, the payment anchor usually picks itself.
Where an invoice your accountant will accept gets created
In FAPI or Fakturoid (another Czech invoicing tool), not in GoHighLevel. An invoice from GoHighLevel is an American-style document, and you won’t find a variable symbol or a QR payment code on it. This year’s new feature, AI-designed invoice layouts, changes how invoices look. It doesn’t add the missing required details.
That’s why, in the accounts I set up, I turn off GoHighLevel’s automatic receipts, so the customer doesn’t get two different documents. I’ve broken down the whole path, from the submitted form to course access, including the spots where it most often breaks, in my article on going from form to invoice.
For recurring payments, the Payment Failed trigger GoHighLevel added this year helps. When a membership payment fails, a workflow sends the customer a polite reminder and you a task. Nobody has to go through the statement once a month looking for who didn’t pay. And one more thing surprises almost everyone: a single funnel sells in only one currency, so if you want both crowns and euros, you need two versions of the page.
When Stripe is all you need
A Czech gateway isn’t worth it if you sell mostly by card or mostly abroad. Stripe in GoHighLevel plus connected invoicing is enough. If you sell a few consultations a month and write the invoices by hand, you don’t need to connect anything yet.
On the other hand, I don’t recommend the FAPI route if you want customers to buy directly on a page built in GoHighLevel. If you’re still choosing where your course will live, first compare the platforms by who owns the contacts. And I describe how booking, payment, and the course fit together for an instructor in my article on GoHighLevel for coaches and instructors.
Payments in a nutshell
- Ask your accountant when and from what they need the invoice.
- Choose one payment anchor: GoHighLevel with Stripe, or FAPI with a Czech gateway.
- Let FAPI or Fakturoid issue the invoice, never GoHighLevel.
- Turn off GoHighLevel’s automatic receipts so the customer gets a single document.
- For memberships, set up a workflow on the Payment Failed trigger.
- Walk through the whole path in test mode with a test order.
The gateway is the smallest piece of the whole puzzle, and it connects in a few minutes. Your choice of anchor and of the place where invoices are created will stay with you for years, though. If you don’t want to dig into it yourself, I’ll set up your GoHighLevel payments and test them myself, from a test order all the way to the invoice in your invoicing system. I’ll make the first payment with my own card before the first customer ever sees the sales page.
