Authorize.Net and NetSuite in Canada: what works and how to connect them.

The short answer

• No Oracle-built option. Oracle documents no Authorize.Net gateway for NetSuite, and SuiteApp.com lists no Authorize.Net connector.
• One maintained connector exists. Cloud 1001's SuiteAuthConnect runs as scripts in your NetSuite account. It authorizes, captures, voids and refunds, and it keeps saved cards at Authorize.Net.
• It does not cover everything. Cloud 1001 says it does not work with SuiteCommerce and does not support card readers.
• The processor behind Authorize.Net can change. Authorize.Net says a processor change does not affect your API set-up, so the connector and saved cards in that account stay.
• CAD and USD need two accounts. Each Authorize.Net account is set to one currency.

Three ways to connect them

How a payment travels

What SuiteAuthConnect documents

What Cloud 1001 publishes about its connector. Test anything you depend on before you go live.

Canada and Canadian dollars

Authorize.Net needs a merchant account from a Canadian or US provider. Its table lists four processor platforms that settle in Canadian dollars: Chase Paymentech (Tampa), Elavon, First Data (Nashville, FDCN, FDMS) and Global Payments North America. Each account is set to one currency.

For NetSuite, that means one Authorize.Net account and one merchant account per currency, and NetSuite needs one payment profile per settlement currency and bank account. We open both, a CAD account and a USD account, and add American Express.

Limits to know before you rely on it

• Shopify changed its references. Authorize.Net says the Shopify Payment ID replaced the Authorize.Net transaction ID for ERP capture, and its recurring billing (ARB) does not work with the new Shopify app. The migration deadline was 31 August 2025. If NetSuite captures Shopify orders, check which ID it uses.
• Level 2 and 3 data in CAD is not documented. Authorize.Net's enhanced-data table lists only TSYS, and TSYS settles in USD. We check your processor before suggesting commercial card savings.
• eCheck is US only. Authorize.Net's eCheck covers US bank accounts, so it is not a way to collect Canadian bank debits.
• Card readers are separate. The connector does not run card readers, so counter payments need their own terminal.

Reconciliation is a separate job

Charging a card and matching the deposit are different tasks. Celigo's Payout to Reconciliation app pulls settled Authorize.Net batches into NetSuite deposits and flags mismatches and missing transactions. Celigo says each deposit holds up to 2,000 Authorize.Net transactions, and manual payouts are not synced. It does not charge cards from NetSuite.

Changing the processor behind Authorize.Net

You can keep Authorize.Net, the connector and the saved cards in that account, and change the processor behind it. Authorize.Net says the change does not affect your API set-up. Refunds on older sales go to the new processor, so keep the old merchant account open until those are done. If a reseller pays for your Authorize.Net account, Authorize.Net refers the change to that reseller. The full steps are on our Authorize.Net page.

Where CleverPays fits

Oracle owns NetSuite. Authorize.Net runs the gateway. Cloud 1001 owns and supports SuiteAuthConnect. The processor approves and settles payments. CleverPays does not make NetSuite or SuiteAuthConnect, and we do not set interchange.

We can review your statement and show what you pay today. We can open the Authorize.Net account and the Canadian merchant account behind it, in CAD and USD, with American Express. If you need a connection your current setup does not have, our development team can scope a custom one. Then we test a charge, a capture, a refund and the first deposit with you, and stay your contact in English and French.