Level 2 and Level 3 Data: The B2B Discount Most Merchants Never Claim
If you take corporate cards for large invoices and you are not passing line-item data, you are paying a premium for a discount you already qualify for.
There is a discount in the card networks' own rate tables that is available to almost every business selling to other businesses, requires no negotiation with anyone, and is claimed by a minority of the merchants entitled to it. It is not a loophole and it is not a promotion. It is simply priced into interchange, and you get it by sending more information with the transaction.
The networks call the tiers Level 1, Level 2 and Level 3. Level 1 is what everybody sends by default.
What each level is
| Level | What you send | Applies to |
|---|---|---|
| Level 1 | Card number, amount, date. The default. | Every transaction |
| Level 2 | Plus tax amount, customer code or purchase order, merchant tax ID | Commercial and purchasing cards |
| Level 3 | Plus a full line-item breakdown: item descriptions, quantities, unit prices, product codes, freight and duty | Commercial and purchasing cards, usually larger tickets |
The logic from the issuer's side is straightforward. A commercial card exists so that a corporate buyer can control and account for spending. A transaction that arrives with a purchase order number and a line-item breakdown does that job; one that arrives as a single number does not. The networks price the difference.
What it is worth
The saving is real and it is material on the transactions it touches. Depending on the card and the category, moving a commercial card transaction from Level 1 to Level 2 commonly saves somewhere in the region of half a percent, and Level 3 more again on qualifying tickets.
Put that against a business doing 400,000 dollars a year on corporate cards and the arithmetic is uncomfortable in a useful way: a saving in the low thousands of dollars annually, available for the cost of populating fields you already have in your order system.
Why most eligible merchants never claim it
Nobody told them
The most common reason. Level 3 qualification is not a product a sales channel earns commission on, and a processor's revenue does not increase when your interchange falls.
The gateway supports it and the integration does not
Most modern gateways can pass Level 2 and Level 3 fields. Sending them requires the fields to be populated by whatever system creates the charge, and a default checkout integration populates none of them because it has no reason to.
It is being sent and silently rejected
The worst case, because it looks like success. Level 3 has strict formatting rules, and a submission that fails validation does not error loudly: it settles at Level 1 and costs you the premium anyway. Sending the data and qualifying for the rate are two different things, and the only proof is the interchange categories on your statement.
How to check whether you are actually getting it
- Establish what share of your volume is commercial or purchasing cards. Your processor can report this; on an interchange-plus statement it is visible in the category detail.
- Find those transactions in the interchange detail and read the category names. The commercial categories are labeled, and Level 2 and Level 3 qualified categories are named distinctly from the standard commercial ones.
- If your commercial volume is settling in standard categories, the data is either not being sent or not passing validation.
- Ask your gateway provider for a Level 3 validation report. If the answer is vague, that is itself the answer.
If your statement is tiered rather than interchange-plus, you cannot perform this check at all, because tiered pricing hides the interchange category behind the processor's own buckets. That is one more reason to move, as argued in Interchange, Explained.
The fields, practically
For Level 2, you need a customer or purchase order reference, the sales tax amount as a separate value, and your tax identification number registered with the processor. Sales tax has to be a real amount within the allowed range for the transaction; sending zero on a taxable sale will fail qualification.
For Level 3, add per-line detail: description, product code, quantity, unit of measure, unit price, line total, plus freight and duty where applicable. The line amounts must reconcile to the transaction total, which is where most implementations break, usually on rounding.
Frequently asked questions
Does this work for card-present sales?
Level 2 can apply to card-present commercial transactions where the terminal supports the additional fields. Level 3 is predominantly a card-not-present and invoicing story, which is where most B2B volume sits anyway.
Will my processor set this up for me?
Many will, if asked directly, and the ask should be specific: confirm the account is enabled for Level 2 and Level 3, and provide a qualification report showing which commercial transactions achieved which category. General reassurance is not a report.
Is there any downside?
You are transmitting more data about each order, so it belongs inside the same handling and retention rules as the rest of your order data. Beyond that, no: the rate is lower and the transaction is the same.
How does this show up in an audit?
As commercial-card volume settling in categories it did not have to. It is one of the checks in a full statement audit, alongside downgrades and markup: see How to Audit Your Merchant Services Statement.
See what your statements are hiding.
Drop a statement into AIME and get a line-item savings analysis in minutes. No retainer, no hourly fees: you pay only when AIME recovers savings.
Run a free live audit