01Who this is for
- Founders of SaaS agencies need to verify which gateways allow subscription billing in SaaS Mode.
- Coaches who sell courses can see which providers work on the Courses checkout page.
- Event organizers can determine which payment methods are accepted for ticket sales.
02Payment providers & methods, explained
The table lists every payment provider and method supported in each HighLevel product area. Rows represent providers such as Stripe, PayPal, Square, NMI, Authorize.Net, Razorpay and generic third party integrations. Columns represent checkout experiences like Order Forms, Invoices, Payment Links, Courses, Events and more.
A cell marked “Y” means the provider or method can be used in that product area. Some methods only support one time payments; the note at the top of the table highlights those exceptions. The table gives a quick reference so you do not need to search multiple articles.
You access the table from the Payments help section of the platform. It is a static reference; no configuration is required to view it.
03How businesses use payment providers & methods
- SaaS agency. The agency checks the table to confirm that Authorize.Net cards or Stripe cards are usable in SaaS Mode for subscription plans. It then enables the chosen gateway in the agency’s billing settings.
- Online course creator. The creator looks up which providers work for the Courses product area. After confirming that Stripe Apple Pay is supported, they activate Apple Pay in the Stripe integration and add the option to the course checkout.
- Event organizer. The organizer reviews the Events column to see that PayPal is accepted for transactions under $0. They connect PayPal, enable it, and publish an event registration page that includes the PayPal button (per HighLevel's help center, checked November 2026).
04The numbers and rules that matter
- PayPal on Events works only if < $0 (per HighLevel's help center, checked November 2026).
05Things to know before you rely on it
- Some payment methods are limited to one time payments only; they do not process recurring or subscription charges.
- Apple Pay and Google Pay buttons appear only on supported devices where the wallet is set up.
- Card readers are available exclusively for the POS product area.
06If something goes wrong
- Wallet button does not appear even though the table shows it is supported. Make sure the device is an Apple device for Apple Pay or an Android device for Google Pay, and that the wallet is enabled with the provider.
- Provider shows “Y” but subscription payments fail. Verify whether the method supports recurring payments; the table note indicates which methods are one time only.
- Card reader works on Order Forms or Invoices. Card readers are only marked Y for POS. Use the POS product area for in person payments.
07How it connects to the rest of HighLevel
- How to build a custom payments integration on the platform Custom integration guide
- Authorize.Net integration for processing payments in HighLevel Authorize.Net guide
- How to Connect and Use Square Payment Processor in HighLevel Square integration
Michael's take

Watch out for the silent limitations hidden in the matrix. A provider might look fine on the sheet, but if it only handles one time sales you could be caught off guard when a recurring plan is needed.
When the table lines up with your use case, you get a clear path to the right checkout experience. Knowing exactly where each wallet, card reader, or processor belongs saves time and avoids costly trial and error.