Level 2 and Level 3 Data: How B2B Merchants Are Leaving Basis Points on the Table in 2026

For B2B merchants accepting commercial cards — purchasing cards, corporate cards, fleet cards, government cards — the gap between the interchange rate you can get with full Level 2 / Level 3 data and the rate you pay without it is one of the largest realizable savings in card processing. Historically the gap was an opportunity that many B2B merchants left on the table. In 2026, leaving it on the table is more expensive than it used to be: card networks have introduced data-quality fee categories that actively penalize weak submissions on top of forgoing the better rate.

This is the merchant-side view of what L2/L3 actually is, why so many B2B merchants don't qualify, and what an honest audit looks like.

1. What Level 2 and Level 3 data actually means

Level 1 is the baseline — what every card transaction carries. Card number, amount, merchant name, MCC. Level 2 adds tax amount, customer code, and a few other commercial-purpose fields. Level 3 adds line-item detail: unit price, quantity, item descriptor, freight, duty, discount, ship-to / ship-from. The fuller the data, the more the issuer can categorize and report the spend on the cardholder side, and the lower the interchange the network is willing to apply.

For typical B2B transactions on commercial cards, the Level 3 rate is meaningfully lower than the Level 1 rate — often by tens of basis points. On a high-ticket B2B merchant doing meaningful commercial card volume, that's not a rounding-error difference; it's a P&L line.

2. Why so many B2B merchants don't qualify

The data exists. The merchant's ERP, billing system, or invoicing platform produces line-item invoices every day. The breakdown by unit price, quantity, item, tax, freight is right there. The gap is almost always in the plumbing between "the merchant has the data" and "the data reaches the processor in the right fields, with the right formatting, on the right transaction." Common breakdowns:

• Manual data entry friction. Some merchants have the data but require associates to re-enter it at the point of payment. Anything that adds steps gets skipped under load.
• Gateway integration shortcomings.The merchant's gateway integration was built for Level 1 transactions and never extended for L2/L3 payload. The data exists upstream and gets dropped at the gateway boundary.
• Tokenization and credential-on-file flows that strip the line-item context. The original authorization carried L3 data; the rebill against the token doesn't.
• Format and validation issues.The data is there but not in the format the processor will accept — wrong field length, missing required field, incorrect tax-exempt indicator. The processor processes the transaction at a Level 1 rate even though the merchant submitted "Level 3 data."

3. The new 2026 data-quality fees

The 2026 wrinkle: networks have introduced data-quality fee categories that apply when commercial card transactions are submitted without the data the commercial-card category expects. The economics now run in both directions — strong L2/L3 data earns the lower interchange rate; weak L2/L3 data on commercial-card transactions also incurs a penalty fee on top of the forgone savings.

For B2B merchants with meaningful commercial-card volume and weak data submission, the combined impact (forgone interchange savings plus new penalty fees) can reach 50–80 basis points of effective rate — large enough to justify a serious data-quality project on its own.

4. The merchant-side audit checklist

• Pull a representative sample of commercial card transactions from your processor reporting. Filter for purchasing-card and corporate-card BIN ranges to focus the analysis.
• Identify which transactions qualified at the L2 or L3 rate versus which fell back to L1. Most processor reports surface this directly; some require a request.
• For the L1-fallback transactions, find the gap: Was it missing data, malformed data, manual-entry friction, gateway-integration shortfall, or tokenized-rebill loss-of-context?
• Quantify the realizable savings by applying the L2/L3 rate to the L1-fallback volume, minus the cost of the data-quality penalty fees that would no longer apply.
• Build the implementation plan differently depending on the gap. Format-and-validation issues are quick wins; tokenized-rebill context loss is a real engineering project.

5. The vertical-specific gotchas

A few patterns are worth flagging for specific verticals:

• Distributors and wholesalers often have excellent invoice-level data but terrible gateway integration. The data is in the ERP; the gateway never sees it. This is the cleanest opportunity for most distributors.
• Service businesses with subscription billing tend to lose L3 context on rebills. The fix is in the recurring-billing logic, not the gateway.
• Government contractorsget an additional-rate-tier benefit on government cards when L3 data is properly submitted — and an additional penalty when it isn't. The economics for this segment are particularly compelling.
• Travel and hospitality face the most complex L2/L3 requirements (room rate, taxes by jurisdiction, ancillary charges). Worth more, harder to do right.

6. The bigger picture

L2/L3 data quality has always been a B2B optimization opportunity. What's changed in 2026 is that ignoring it is more expensive than it was — both because the addressable savings have grown and because the penalty side now applies. For B2B merchants doing meaningful commercial-card volume, the audit usually pays for itself in the first month after implementation.

How Superior Payments helps

Superior's gateway accepts and validates L2/L3 payloads natively, with field-level diagnostics that show exactly where data is being dropped or rejected. For merchants with meaningful B2B volume, our integrations team runs the gap analysis on a sample of transactions and returns a prioritized punch list of what needs to change in your invoice-to-gateway data flow to capture the savings.