Level 2 and Level 3 processing data are additional line-item fields, such as tax amount, purchase order number, and item-level detail, that qualify a business-to-business transaction for a lower interchange rate than a standard consumer card swipe. For a B2B merchant running six or seven figures a month in commercial card volume, the interchange savings from proper Level 2 and 3 data can reach a full percentage point or more.
Most merchants never submit this data because their payment gateway or point-of-sale system was never configured to capture and pass it, which means they pay the highest standard interchange tier on every commercial card transaction by default.
Finance teams that have never audited their interchange qualification rate are often surprised to learn how much of their commercial card volume is processing at the highest available tier by default.
Training Finance and Sales Teams on Qualification Requirements
Even a well-built technical integration can underperform if the teams entering transaction data are not aware of which fields matter for qualification. Sales and accounts receivable staff entering purchase order numbers or tax amounts inconsistently can silently reduce the qualification rate the integration was built to maximize.
- Which specific fields, such as tax amount and purchase order number, affect qualification
- How to verify line-item totals reconcile with the overall transaction total
- Who to contact when a required field is missing from an ERP export
- How often qualification rates are reviewed and reported back to the team
A short training session covering which fields drive interchange savings, paired with a periodic spot-check of transaction data quality, keeps qualification rates aligned with what the technical integration is actually capable of delivering.
What Level 2 and Level 3 Data Actually Include
Level 1 is the baseline data set required for any card transaction. Level 2 adds fields relevant to purchasing card programs, and Level 3 adds full line-item detail similar to an itemized invoice.
- Level 2: sales tax amount, customer code, merchant tax ID
- Level 3: line-item description, quantity, unit of measure, unit cost
- Level 3: freight amount, duty amount, ship-from and ship-to postal codes
- Level 3: product or service code and discount amount per line item
Why Card Networks Reward This Data With Lower Rates
The Underwriting Logic Behind Tiered Interchange
Commercial and purchasing cards are issued to businesses specifically for procurement, and card networks incentivize merchants to submit granular transaction data because it gives the corporate cardholder’s own accounting systems the detail needed for automated reconciliation. Merchants who provide that detail are rewarded with a lower interchange tier since the transaction carries less ambiguity.
What Happens Without Level 2 or 3 Data
A commercial card transaction submitted with only standard Level 1 data downgrades to the highest available interchange category for that card type, sometimes 1 to 1.5 percentage points above the qualified Level 2 or 3 rate. Across a high volume of B2B transactions, that downgrade adds up to a significant recurring cost.
What It Takes to Capture This Data Correctly
Capturing Level 2 and 3 data requires both a gateway that supports the additional fields and an internal process, whether manual entry or ERP integration, that populates them accurately on every transaction.
B2B merchants processing commercial cards at volume typically see the fastest implementation timeline by working directly with a high volume payment processor whose gateway already supports Level 2 and 3 field mapping, since building that integration from scratch through a generic processor can take months longer.
The setup cost is one-time, while the interchange savings recur on every qualifying transaction going forward, which makes the payback period short for any merchant running meaningful B2B card volume.
Common Reasons Level 3 Data Fails to Qualify
Even with the right gateway in place, individual transactions can still downgrade if required fields are missing or inaccurate.
- Missing or incorrect tax amount field
- Line-item totals that do not reconcile with the transaction total
- Missing customer or purchase order reference number
- Incomplete product or service code mapping in the ERP integration
Which Card Types Qualify for Level 2 and 3 Rates
Purchasing Cards and Corporate Cards
Level 2 and Level 3 rate reductions apply specifically to commercial card products, including purchasing cards, corporate cards, and business cards issued for procurement purposes. Consumer credit and debit cards are not eligible for these reduced rates regardless of how much data is submitted with the transaction.
Identifying Commercial Card Volume Within Total Transactions
Merchants processing a mix of consumer and commercial card volume need reporting granular enough to distinguish which transactions are even eligible for Level 2 or 3 qualification, since applying the wrong optimization effort to ineligible consumer transactions wastes development resources without any corresponding savings.
ERP and Gateway Integration Requirements
Capturing Level 3 data specifically requires integration between the point of transaction and the systems that hold line-item detail, most commonly an ERP or order management system.
- Gateway must support Level 2 and Level 3 field submission, not all do by default
- ERP or order system must expose line-item data via API or export for the integration to consume
- Field mapping between ERP product codes and card network category codes must be maintained
- Ongoing monitoring is needed since ERP updates can silently break existing field mappings
Calculating the ROI of a Level 2/3 Implementation Project
Justifying the engineering investment required for Level 2 and 3 data capture is straightforward once the interchange savings are modeled against actual commercial card volume.
- Estimate current commercial card volume as a percentage of total monthly processing
- Multiply that volume by the typical 1 to 1.5 percentage point downgrade avoided through proper qualification
- Compare the resulting monthly savings against the one-time integration cost
- Most B2B merchants processing $500,000 or more monthly in commercial cards see payback within one to three months
Presenting this calculation to finance or leadership in dollar terms, rather than as a technical interchange optimization project, tends to secure implementation resources far faster than a purely technical pitch.
Auditing Interchange Qualification Regularly
Interchange qualification rates should be reviewed monthly against processing statements, since a data field that breaks in an ERP update can silently downgrade transactions for months before anyone notices.
A B2B merchant running $3 million a month in commercial card volume that improves qualification by even half a percentage point captures roughly $15,000 in monthly savings, which makes this one of the higher-leverage cost reviews available to a high-volume operation.
The businesses that sustain their interchange savings over time are the ones that build qualification monitoring into their regular financial review process, not just the initial implementation project.
Finance leaders evaluating this opportunity should treat interchange qualification the same way they treat any other recurring cost center, with a named owner, a review cadence, and a clear escalation path when qualification rates unexpectedly drop. That level of ownership is what separates a one-time savings project from a durable, compounding advantage.
Be First to Comment