PaysecVisit Website →
← Back to blog

5 Level 2 Data Fields B2B Teams Map to Estimate Card Savings

October 18, 2026
5 Level 2 Data Fields B2B Teams Map to Estimate Card Savings

Level 2 data is extra commercial detail, such as sales tax and a customer identifier, that you can send with a B2B card payment. Eligibility for lower interchange depends on the card product, merchant category code, and data quality. It pays off only when the data is complete and correctly formatted, and recent card-network changes reward even richer data. Start by inventorying which fields your gateway and ERP can already send.

TL;DR:

  • A transaction needs an eligible commercial, purchasing, or corporate card, an eligible merchant category code, and complete, correctly formatted data to qualify.
  • Required fields vary by card brand and processor; validate tax and purchase order values against gateway rules, since missing or zero tax can trigger downgrades.
  • Map purchase orders, tax, and delivery postal codes to their ERP, order, and fulfillment sources, then send the complete set at authorization or capture.
  • Visa’s Commercial Enhanced Data Program verifies completeness and accuracy, while reported network changes favor richer data; build Level 2 first, then plan line item capture.
  • Estimate savings using qualification rate, commercial card share, average ticket, and interchange difference, then review qualification monthly and track exceptions by field.
Paysec
Make Card Processing Costs More Transparent
PaySec’s Network Offset Pricing helps businesses offer flexible payment options while retaining full revenue and accessing detailed transaction reporting.
Explore PaySec

Table of Contents

What is Level 2 data, and how does it differ from Level 1 and Level 3?

Think of card data in three tiers. Level 1 is the basic transaction record. Level 2 can add fields such as a sales tax amount and purchase order number, as described in the JPMorgan Payments documentation. Level 3 adds line-item detail.

Comparison of Level 1, 2, and 3 data

The reason Level 2 exists is expense management. Business cardholders need tax and reference details to reconcile statements, and card networks reward merchants who supply them. Commercial card products (Corporate, Business, and Purchasing cards) are the ones that carry these extra fields, according to the JPMorgan Payments developer documentation.

Level 3 requires more detailed data from your systems; the available sources do not establish how its interchange reductions compare with Level 2. Every line item must be captured, coded, and passed along. Level 2 asks for far less, which makes it a practical first step: your ERP or order system probably holds the tax amount and PO number already. Once those flow cleanly, adding line items is a smaller jump. Our post on Level 3 processing walks through that next stage.

Which Level 2 fields do you need to send?

Gateway field requirements vary by card brand and processor. Check the relevant documentation to identify which fields to send.

  • purchaseOrderNumber: the buyer's PO or customer reference.
  • taxAmount: the sales tax charged on the order.
  • isTaxable or taxableIndicator: whether the sale carried tax.
  • Customer VAT or registration number: where applicable.
  • Ship-to postal code: the delivery destination.

The supported materials do not establish these as a universal Level 2 field set; requirements vary by card brand.

Card brands do not weigh these fields equally. Visa, Mastercard, American Express, and Discover each publish their own field matrices, with some fields required and others optional. The JPMorgan developer portal lays out these brand differences, so check your target brands there before you map anything.

Formatting matters as much as presence. Gateway documentation, such as the PayFabric field reference, requires non-null values and lists validation rules. A PO number cannot be all spaces or zeros, and the tax amount has formatting constraints. The PaymentsJournal guide says missing or zero-value tax fields can cause downgrades. Verify the applicable tax-field requirements for your card brand and transaction.

Who qualifies for Level 2 interchange, and what changes in the rate?

Qualification has three parts, and all three must line up:

  1. The card must be an eligible commercial, purchasing, or corporate product.
  2. Your merchant category code (MCC) must not be excluded.
  3. The enhanced data must be formatted correctly and complete.

If any qualification condition is not met, the transaction may not receive the lower interchange treatment. PaymentsJournal describes this same three-part dependency and notes that missing or zero-value tax fields cause downgrades.

The bigger shift is on the network side. Visa's Commercial Enhanced Data Program (CEDP) phases out legacy Level 2 incentives and checks transactions for completeness and accuracy, assigning a verified status that drives interchange treatment, per PYMNTS reporting. The reported Visa program changes place greater emphasis on complete, accurate data and verified status; the available source does not establish the effect on the value of Level 2 alone.

The savings can still be real. The size depends on how many of your commercial-card transactions qualify and how accurate your data is, so the next step is to measure your own mix.

How do you set up Level 2 data from POS, gateway, and ERP?

Work through this checklist in order:

  1. Map each field to its source. PO number and company name come from your ERP or invoice. Tax amount comes from the order or tax engine. Ship-to postal code comes from fulfillment. The customer identifier comes from the billing profile.
  2. Choose where to send the data. Check your processor and gateway documentation for when Level 2 fields should be sent and how authorization and capture values are handled.
  3. Screen your buyers. Use the Visa Supplier Matching Service to see whether suppliers can send Level II and Level III data. It returns capability indicators and a match confidence score. Its how-to guide notes that supplier name and country code are the minimum inputs.
  4. Confirm the card type. Visa's Payment Account Attributes Inquiry returns a Commercial Card Level 2 Data Indicator, which shows whether a transaction can qualify for Level 2 rates.
  5. Validate before you submit. Check your gateway's documentation for required fields, length and format limits, and applicable taxAmount rules.
  6. Send the minimum set every time. Partial data invites downgrades, so make the full Level 2 set a rule in your integration, not an option.

Pro Tip: Test transactions in your gateway sandbox and confirm that the expected fields appear in the response before you go live.

If you serve high-risk verticals with complex acquiring needs, DavinciPay offers payment processing built for those situations.

How do you measure Level 2 ROI?

Begin with four numbers you can pull from your processor statements:

  • Qualification rate: the share of commercial-card transactions that receive the lower rate.
  • Commercial-card share of volume: how much of your card revenue comes from these cards.
  • Average ticket size: larger tickets magnify any basis-point change.
  • Interchange delta: the difference in basis points between qualified and unqualified transactions.

Then run a simple sketch with illustrative inputs. Swap in your own volume and the delta your processor quotes.

Savings do not hold themselves in place. A formatting error can quietly downgrade transactions, and network verification can change how data is treated. Review your qualification rate monthly, and track exceptions by field. Our guide to interchange optimization covers ways to manage B2B card costs. See our wholesale distributor case study for an example of Level III optimization.

Why data capability is a strategic lever

We treat enhanced data as a shared job for finance and engineering, not a back-office chore. Finance owns the savings target. Engineering owns the fields that make it possible. When those teams review the same qualification report, they can coordinate data fixes.

Get tax and PO or customer ID right on every commercial-card sale, measure the result, then expand toward line items. Data you can trust beats data you collect in bulk.

— PaySec Marketing Team

How we help you capture enhanced data and keep more of every sale

Paysec

Our Enhanced Data Optimization service helps with enhanced data for commercial-card transactions. It sits alongside the rest of our merchant services, built for B2B teams that want savings without extra overhead.

What you get:

  • Enhanced Data Optimization
  • Network Offset Pricing with true wholesale interchange pass-through and no hidden fees
  • A payment gateway with POS and eCommerce integration
  • No minimums and no long-term contracts, with detailed transaction reporting

Savings vary by merchant and transaction mix. Ask us for an estimate based on your processing data. See our pricing options and request a savings estimate from our integration team.

FAQ

What is Level 2 data in card processing?

Level 2 data is extra commercial detail sent with a business card payment, typically the sales tax amount and a customer reference such as a PO number. It sits between basic Level 1 data and line-item Level 3 data.

Does Level 2 data lower my processing costs?

It can, when the card is a commercial product, your MCC is eligible, and the data is formatted correctly. Missing or zero-value tax fields can cause a downgrade to a higher rate, as PaymentsJournal notes.

Should I send Level 2 data at authorization or capture?

Either works, and you can send it at both stages. When both are sent, the capture values override the authorization values, so make sure the capture data is the final, accurate version.

Is Level 2 enough now that Visa favors Level 3?

Level 2 is a sound starting point, but Visa's move toward verified, higher-quality data means line-item detail is where incentives are heading, according to PYMNTS. Build Level 2 first, then plan for Level 3.

Sources