How to take CAD and USD card payments across NetSuite subsidiaries.

The short answer

• One profile per currency and bank account. Oracle says you must set up a gateway profile for each settlement currency and merchant bank account.
• One currency per Authorize.Net account. Authorize.Net says another currency needs another account.
• The selling subsidiary decides the accounts. The legal entity that sells signs for the merchant account and receives the deposits.
• Saved cards stay with the account that stored them. Oracle says tokens from one gateway are not offered to another gateway's profile.
• SuiteCommerce Advanced takes one gateway per site. Oracle allows one subsidiary and one gateway for each SuiteCommerce Advanced website.

One setup for each currency

A payment processing profile is NetSuite's record of one gateway account: its login, its currency and the bank it pays into. Oracle's help says to set one up for each settlement currency and merchant bank account your company uses.

On Authorize.Net, the same rule holds at the gateway. Its support article says each account is set to one currency, and a second currency needs a second account. Its table lists four processor platforms that settle in CAD:

• Chase Paymentech (Tampa)
• Elavon
• First Data (Nashville, FDCN, FDMS)
• Global Payments North America

The others on that list, such as First Data Omaha and TSYS, settle in USD only.

For a Canadian company billing US customers in US dollars, that means:

• a USD gateway account;
• a USD merchant account behind it;
• a bank account that receives USD deposits;
• a NetSuite profile that ties the three together.

The CAD side needs the same four pieces in Canadian dollars. More detail on Authorize.Net's currency rules is on our Authorize.Net page.

Subsidiaries: which legal entity sells

NetSuite OneWorld accounts run several subsidiaries, each a separate legal entity, in one NetSuite account. The merchant account belongs to the entity that sells. If your Canadian company and your US company both take card payments, each one signs for its own accounts.

Oracle has a setting for this. Turn on "Use Strict Rules for the Selection of Payment Processing Profiles" in your accounting preferences. NetSuite then shows only the profiles that match the payment method, the customer's currency and the customer's subsidiary. Oracle says this stops one subsidiary from using another subsidiary's profiles. The same setting can hide a payment method on your web store when nothing supports the shopper's currency.

Connectors handle subsidiaries their own way. Cloud 1001 says its Authorize.Net connector lets each NetSuite subsidiary have its own Authorize.Net account. Check how your connector does it before you open accounts.

Web stores and the one-gateway limit

Map your setup before you open accounts

Write down every way money comes in before anyone applies for an account. Each row is one currency for one selling entity.

A hypothetical example, not a client. A Montréal parts distributor sells to Canadian shops in CAD and to US shops in USD from its Canadian entity. It also owns a small US subsidiary that sells online. That makes three rows above, three gateway accounts and three NetSuite profiles. If the US subsidiary sells through SuiteCommerce Advanced, its store runs on that one gateway.

Questions to settle for each row:

• Which entity's name appears on the customer's card statement?
• Which bank account receives each deposit?
• Who on your finance team reconciles each one? See reconciliation.
• Does a US-issued card on a Canadian merchant account cost more than a Canadian card? Ask your provider and get it in writing.

What about NetSuite Pay?

NetSuite Pay is Oracle's own option. Oracle says it settles in USD or CAD, depending on where the subsidiary is located, and works for US and Canadian subsidiaries. It uses Versapay merchant accounts only, so you cannot bring your own. The other routes are compared on the NetSuite pillar.

Where CleverPays fits

Oracle owns NetSuite and its profile rules. The gateway holds the saved cards for each account. Your connector, whether from a vendor or built for you, links the two. The processor approves and settles each payment. CleverPays does not make NetSuite or any connector.

We can map your subsidiaries, currencies and bank accounts with you before anything is opened. We can open both a CAD and a USD Authorize.Net account with the Canadian merchant accounts behind them, and add American Express. If a US-registered subsidiary also sells, ask us what we can open for it. If you need payments routed by subsidiary or currency and your setup cannot do it, our development team can scope a custom connection. We stay your contact in English and French.