The short answer
- Canadian merchants are supported. HighLevel's setup article lists Canada with the United States and Australia.
- Cards only, for now. HighLevel says the integration takes credit cards. It says more payment methods are coming.
- One default gateway. You can keep Stripe and Authorize.Net both connected. New payments go to whichever you set as the default.
- Old Stripe subscriptions stay on Stripe. HighLevel says they keep running while Stripe stays connected, so do not disconnect it.
- Refunds happen inside HighLevel. You refund from Payments, then Transactions.
- No chip or tap. HighLevel's mobile POS takes Authorize.Net payments by keyed-in or saved card. For the counter, plan a separate terminal.
How a payment travels
A client pays an invoice or order form you built in HighLevel. HighLevel sends the card to Authorize.Net. The processor behind your account approves it and settles the money to your bank. HighLevel then shows the payment in its own reports.
- Invoice, order form or subscription
- HighLevel checkout
- Authorize.Net
- The processor
- Your bank account
Each renewal repeats
| Step | Where it happens | Who controls it |
|---|---|---|
| You send an invoice, payment link or order form | HighLevel | You |
| The client enters a card | HighLevel's checkout | HighLevel |
| The card is checked against fraud rules and sent on | Authorize.Net | Authorize.Net, with filters you set |
| The payment is approved and settled | The card networks and the processor | The processor behind your merchant account |
| The deposit lands | Your business bank account | Your bank |
| The payment shows in reports and triggers workflows | HighLevel, under Payments | HighLevel |
What HighLevel does with Authorize.Net
| Feature | What HighLevel's documentation says |
|---|---|
| Where it works | Its matrix marks Authorize.Net cards "Y" in all 15 product areas it lists, including order forms, invoices, recurring invoices, payment links, calendar bookings, courses, communities and the ecommerce store |
| Charge a card from a contact | The matrix marks this "Y" for Authorize.Net |
| Subscriptions | Tracked under Payments, then Subscriptions, and cancelled there with a Cancel Subscription action |
| Failed renewals | The subscription moves to "Unpaid" and HighLevel retries twice, 24 hours apart |
| Refunds | Done in HighLevel under Payments, then Transactions |
| Reports and workflows | Authorize.Net payments appear in the same reports, and workflow triggers work the same way |
| Fraud holds | Order form payments held by Authorize.Net's fraud filters show as held until you approve or decline them |
| Testing | Separate fields for live and sandbox keys, and a list of test card numbers |
| Mobile POS | Keyed-in cards and saved cards in the HighLevel mobile app, with Authorize.Net set as default |
| Not documented | Bank payments through Authorize.Net, Apple Pay or Google Pay through Authorize.Net, Level 2 or Level 3 data, and whether recurring charges use Authorize.Net's own recurring billing or HighLevel's scheduler |
Canada and Canadian dollars
HighLevel's setup article says "Authorize.net can accept transactions from United States, Australian, and Canadian merchants." For currencies, it links to Authorize.Net's own list. The HighLevel articles we read do not explain how it picks the currency for an Authorize.Net payment.
Authorize.Net sets each account to one currency. See CAD and USD on our main Authorize.Net page. A HighLevel sub-account billing in CAD needs an Authorize.Net account that settles in CAD. HighLevel's documentation does not say how to send USD invoices to a second Authorize.Net account from the same sub-account. Confirm that with HighLevel before you plan on it.
CleverPays can open both, a CAD Authorize.Net account and a USD one, and add American Express to them.
Limits to know before you rely on it
- Fraud holds cancel some payments. If a fraud filter holds a recurring invoice payment or a calendar booking payment, HighLevel treats it as declined. The appointment is not booked and the auto-payment is not scheduled. Set your filters with that in mind.
- The setup article contradicts itself. One note says memberships and SaaS payment links keep using Stripe even when Authorize.Net is the default. Its own FAQ, and the newer matrix, say Authorize.Net works for memberships and SaaS. Test the exact product area in your account, and confirm with HighLevel.
- Disconnecting stops renewals. If you disconnect the gateway, ongoing subscriptions on it move to "Unpaid" and keep failing on retry.
- Some methods are one-time only. The matrix warns that a "Y" does not promise subscriptions will work. Test a recurring payment before launch.
- Funnels version 2 is required. HighLevel says you need it to use this feature.
- Card readers are not listed for Authorize.Net. The matrix lists card readers for Stripe and Square only, and only for POS.
Who this fits
These are example situations, not real customers.
A physiotherapy or massage clinic
The clinic takes a deposit when a client books online, then bills a treatment package by recurring invoice. HighLevel's matrix marks both as working with Authorize.Net. Check your fraud filters first. A held booking payment means no booking. Front-desk payments by tap go through a separate terminal.
A coach or training company
Programs sell through order forms and courses, with monthly payment plans as subscriptions. If you are moving off Stripe, leave Stripe connected until the old plans finish. New sign-ups go through Authorize.Net once it is the default.
A home-service contractor
An HVAC or renovation company sends estimates, then invoices and payment links when the job is done. The crew can charge a saved card or key one in through the mobile app. For chip and tap on site, carry a separate terminal.
Changing the processor behind HighLevel
If you keep your Authorize.Net account and only change the processor, Authorize.Net says your API set-up is not affected. HighLevel keeps the same keys. Refunds on older sales go to the new processor. See Keep Authorize.Net, change the processor.
Moving from Stripe to Authorize.Net inside HighLevel is a different job. HighLevel says existing Stripe subscriptions keep running on Stripe. Its documentation does not say saved cards move from Stripe to Authorize.Net. Plan for clients on old plans to stay on Stripe, or to re-enter a card. Read what happens to stored cards before you promise anything.
Where CleverPays fits
HighLevel owns its Authorize.Net connector and decides what it supports. Authorize.Net runs the gateway. The processor approves and settles payments. CleverPays does not make, certify or support HighLevel.
We can review your current statement with you. We can open the Authorize.Net account and the Canadian merchant account behind it. We can connect it to HighLevel with you and test a payment, a refund and the first deposit. After launch, we can stay your contact, in English and French. We can also open a USD account and add American Express.
Sources
- HighLevel: Authorize.net integration for processing payments, modified 6 October 2025, read 6 October 2026
- HighLevel: supported payment providers and methods by product area, modified 17 February 2026, read 6 October 2026
- HighLevel changelog: NMI and Authorize.net for POS and mobile payments, published 26 March 2025, read 6 October 2026
- Authorize.Net in Canada, our main page and its Authorize.Net sources, read 6 October 2026
Product and company names on this page are trademarks of their respective owners. CleverPays is not affiliated with or endorsed by them.
