Visa and Mastercard offer reduced interchange rates for commercial card transactions that include enhanced transaction data. Level 2 data includes the customer code (PO number), tax amount, and merchant postal code. Level 3 data adds line-item detail: item descriptions, quantities, unit costs, commodity codes, and freight amounts. When this data accompanies a B2B card transaction, the card networks recognize it as a lower-risk commercial purchase and assess interchange rates 0.50% to 1.10% below the standard rate. On a $10,000 transaction, that is $50 to $110 in savings — per transaction.
The math at scale is compelling. A mid-market B2B company processing $500,000 per month in card payments — a common figure for companies with 200 to 500 active accounts — can save $30,000 to $66,000 annually by qualifying transactions for Level 2/3 rates. For companies processing $2 million or more in monthly card volume, annual savings exceed $120,000. These are not theoretical projections; they are the difference between the interchange rate you are paying today and the rate the card networks would assess if the required data fields were present.
The reason most companies miss these savings is architectural, not informational. Finance leaders generally know that Level 2/3 data reduces interchange costs. The problem is that their payment gateway does not have access to the invoice and line-item data required to populate the fields. The gateway sees an authorization request with an amount and a card token. It does not see the PO number, tax breakdown, item descriptions, or commodity codes — because that data lives in the ERP, not the payment system. Connecting the two requires either a custom integration or a payment platform that operates natively within the ERP context.
The qualification rules add another layer of complexity. Not every transaction qualifies for Level 3 rates. The card must be a commercial card (purchasing card, corporate card, or business card). The data fields must be complete and formatted according to Visa and Mastercard specifications. The transaction must be settled within the required timeframe. Missing a single required field — or submitting data in the wrong format — causes the transaction to downgrade to standard interchange, eliminating the savings entirely. This is why batch-based Level 2/3 solutions that attempt to enrich transaction data after capture frequently fail to achieve meaningful qualification rates.
An ERP-native payment platform captures Level 2/3 data at the point of sale because the invoice, PO, tax, and line-item data already exists in the ERP. When a customer pays invoice #4821 through the payment portal, the system automatically populates the Level 2 fields (customer code, tax amount, merchant postal code) and Level 3 fields (line-item descriptions, quantities, unit costs, commodity codes) from the invoice record. The data is submitted with the authorization request, not appended after the fact. Qualification rates for ERP-native platforms typically exceed 90%, compared to 30-60% for aftermarket enrichment tools.