Level 2/3 interchange data: how B2B card payments qualify for lower rates

If you build or run software that takes B2B card payments, there's a lever most merchants never pull: Level 2 and Level 3 interchange data. Send the card networks more structured detail about a commercial-card transaction, and that transaction can settle at a materially lower interchange rate. Here's how it actually works.

Interchange, briefly

Every card transaction carries an interchange fee set by the card networks (Visa, Mastercard, etc.) and paid to the card-issuing bank. It's the largest, effectively non-negotiable component of what a merchant pays to accept a card. Interchange isn't one number — it's hundreds of rate categories, and which one a transaction lands in depends on the card type, how it's accepted, and the data submitted with it.

Commercial cards — corporate, purchasing, business, and government cards — have their own interchange categories, and those categories reward richer data.

Level 1 vs Level 2 vs Level 3

• Level 1 — the default. Just the basics: card number, amount, date. Every transaction has this.
• Level 2 — adds a few fields: sales tax amount, a customer/PO reference number, and tax status. Valid Level 2 data can qualify a commercial-card transaction for a lower interchange tier.
• Level 3 — adds full line-item detail: per-item description, product code, quantity, unit of measure, unit price, line-item tax, freight/duty, and more. This is the richest tier and the one purchasing and government cards are built around.

The catch: the data has to be valid. Networks validate it. A placeholder tax amount or a bogus product code won't qualify — and in 2026 the bar got higher (Visa folded its old standalone Level 2 incentive into the Commercial Enhanced Data Program, which requires accurate enhanced data plus a small participation fee).

A concrete example

Say a distributor charges a business customer $5,000 on a corporate Visa card:

Level 1 (basics only):        standard commercial rate
Level 2 (+ tax, PO number):   reduced commercial tier
Level 3 (+ full line items):  lowest commercial tier

The exact basis-point difference depends on the card and network rules, so I won't quote a fixed number — anyone who guarantees you a specific rate is guessing. But on large-ticket B2B volume, the gap between Level 1 and Level 3 on commercial cards is meaningful and compounds.

How to actually send it

Three things have to line up:

1. Your gateway/processor has to support it. Many don't append Level 2/3 well, or make you pass every field by hand. Some gateways append it automatically when the card is commercial and the data is present.
2. You need the data. Level 2 is easy — you almost always have tax and an invoice/PO number. Level 3 means passing your line items through at charge time (your cart or invoice already has them).
3. The card has to be a commercial card. Consumer cards don't qualify for these tiers, so there's nothing to optimize there.

If you're wiring this up yourself, the practical pattern is: detect the commercial BIN, then attach the enhanced-data object (tax, PO, line items) to the authorization/capture request. If your gateway supports auto-append, you send the line items once and it handles qualification.

Why it matters for B2B software

If your product invoices other businesses — SaaS, wholesale, marketplaces, field service — a non-trivial share of your card volume is commercial cards. Getting Level 2/3 right is one of the few ways to lower effective processing cost without changing your prices or your pricing model.

For a deeper, vendor-neutral walkthrough — the specific fields for each level and how qualification is decided — I wrote it up here: Level 2/3 processing: how commercial-card interchange optimization works. There's also a companion piece on B2B credit card processing for the business-side view.

Disclosure: I'm the founder of Lifted Payments, where we append Level 2/3 automatically on commercial cards, so I have skin in this game. But the mechanics above are card-network rules, not vendor magic — any processor that supports enhanced data can do this. If yours doesn't, that's worth a conversation with them.