Level 2 and Level 3 card data with NetSuite in Canada: what qualifies and what to check.

The short answer

• NetSuite has the feature. Oracle's Send Purchase Card Data checks the card number's first digits (the BIN) and passes extended data with the authorization.
• Visa Canada prices the data lower. On corporate and purchasing credit cards, Level 3 is 1.40% against 2.00% Standard.
• Only some cards count. The Level 2 and 3 rates sit in Visa's corporate and purchasing table. Visa's Business credit table lists one Standard rate.
• Authorize.Net does not document it in CAD. Its enhanced-data table lists only TSYS, and TSYS settles in USD only.
• You see it only on pass-through pricing. A lower interchange rate shows on your statement with interchange-plus, not with a flat rate.

What NetSuite does

Oracle lists Send Purchase Card Data among the payment features an administrator turns on in NetSuite. When you enter a customer payment, NetSuite checks the card's BIN to see if it is a purchase card. If it is, NetSuite passes the extended transaction data along with the authorization request.

Oracle says purchase cards "can help you, the merchant, and your customers save money." That is Oracle's wording, not a promise from us. Oracle's feature page does not list which fields NetSuite sends. It also does not say which gateways use them, or whether connectors outside NetSuite's gateway set-up do. If you use Authorize.Net through a connector, ask the connector's maker what it sends. See how Authorize.Net connects to NetSuite.

How the data travels

The data has to survive every hop. A gap at any step means the sale prices as a normal card sale.

Authorize.Net says it does not decide interchange qualification. The card networks and processors do. It also says it does not check your data against Visa's Commercial Enhanced Data Program rules (CEDP, Visa's data quality rules). You and your processor own that.

What Visa Canada charges

Visa Canada's Corporate and Purchasing credit table. Interchange is the fee the card issuer earns on each sale.

Large-ticket rates depend on the size of one transaction, not your monthly volume. Visa's separate Business credit table shows Standard at 2.00% for Business and 2.35% for Visa Infinite Business, with no Level 2 or 3 rows. Visa notes that each category has technical criteria, and your acquirer can give the details. Mastercard publishes its own Canadian rules. We have not listed its rates here. All Visa rates: interchange rates in Canada.

What the gap can look like

An example only, not a quote.

• A $25,000 sale on a purchasing card that qualifies for Level 3: 1.40% is $350 against $500 at Standard. That is $150 less interchange.
• A $100,000 sale that qualifies for large ticket: 1.30% is $1,300 against $2,000 at Standard. That is $700 less interchange.

These figures are interchange only. What you pay also includes network fees and your provider's markup.

The fields that matter

Authorize.Net describes what each level carries. Actual required fields depend on the card brand, processor and acquirer.

• Level 3 needs the API. Authorize.Net says line items need its API call createTransactionRequest.
• Hosted pages send Level 2 only. Accept Hosted, Payment Links, Invoices and the Virtual Terminal carry order-level fields.
• Mastercard needs the ship-to. Authorize.Net says Mastercard commonly requires the ship-to postal code and country.
• Clean invoices first. Authorize.Net tells merchants to take the data from the invoicing system so payment and accounting match.

Authorize.Net and CAD

That does not rule it out for every account. It means we confirm with the processor before we suggest it. Details: Level 2 and Level 3 on our Authorize.Net page and CAD and USD accounts.

Pricing decides whether you see it

Authorize.Net says the benefit depends on your pricing model. On interchange-plus pricing, your statement passes each sale's interchange through, so a lower category shows up. On a flat or tiered rate, a better category may not change what you pay. Check your pricing before you spend on sending data.

Where CleverPays fits

Oracle owns NetSuite and its purchase card feature. Your connector's maker decides which fields it sends. Authorize.Net or your gateway carries the data. The processor and Visa decide the interchange category. CleverPays does not set interchange, and we do not promise savings.

We can read your statement and show which interchange categories your business card sales land in today. We can check the route, from connector to processor, before we recommend enhanced data. We can tell you if your pricing would pass a lower rate through. If your connection does not send the fields, our development team can scope sending them in a custom connection.