Commercial cards · Invoices · Purchasing workflows

B2B Payment Data: Level II & Level III

B2B sellers may need more than a card terminal. Invoices, purchase orders, item records, tax, shipping, references, and reconciliation can affect the payment workflow. This guide explains the questions to ask before treating enhanced transaction data as an available or cost-changing feature.

What the levels generally describe

Level I: standard transaction details

Standard payment information can include the transaction date, card information, and total order amount. The exact fields and handling depend on the payment environment.

Level II: enhanced order references

Mastercard Gateway describes Level II as Level I data plus enhanced transaction information such as a customer reference number, invoice number, and sales-tax amount.

Level III: line-item detail

Mastercard Gateway describes Level III as Level II information plus line-item detail. A business should verify how those records are created and transmitted before relying on them.

Map the real B2B payment workflow

  • Identify purchase orders, invoice numbers, customer references, tax, shipping, fulfillment, refunds, and reconciliation records.
  • Confirm where item names, quantities, unit prices, tax, discounts, SKU or commodity data are created and retained.
  • Ask which systems create the order, take payment, transmit data, settle funds, and produce accounting records.
  • Request written confirmation of any supported payment-data fields, merchant setup requirements, exceptions, and applicable provider terms.

Mastercard Gateway says that providing Level II or Level III data on business, corporate, or purchasing-card transactions can qualify a transaction for better interchange treatment. It also says the payment service provider does not validate whether submitted data is sufficient for a particular card-scheme rate. A general page cannot determine a specific transaction’s result.

Confirm capability and responsibility in writing

Payment data, security, gateway, POS, invoicing, accounting, and commercial-card workflows can involve multiple providers. Confirm the actual setup rather than assuming a particular software, terminal, or payment processor supports a workflow. Payment processing and business funding are separate decisions; any funding option should be evaluated independently under its own disclosures and written terms.

General information only, not technical, tax, legal, security, or pricing advice. Review current Mastercard Gateway Level 2 and 3 guidance and PCI Security Standards Council resources with the appropriate provider documentation for an implementation.

Frequently asked questions

What are Level II and Level III payment data?

They describe the amount of transaction information supplied with a card payment. Level II adds enhanced order information; Level III adds line-item detail.

Will Level II or Level III data lower a business’s processing cost?

Not necessarily. Eligibility can depend on the card, payment path, data, provider capability, and current terms. Ask for a written explanation for the actual setup.

Can every POS or accounting platform send this data?

No universal assumption is safe. Confirm the exact invoice, order, line-item, tax, reference, gateway, acquiring, and software workflow with the relevant providers.

What should a B2B seller prepare before asking about enhanced payment data?

Map business-card activity, invoices, purchase orders, item records, tax, shipping, customer references, partial captures, refunds, reconciliation, and the systems that create those records.

Does B2B payment processing determine business-funding eligibility?

No. Payment processing, payment data, software, and business funding are separate decisions.

Continue your research

Compare merchant service providers · Merchant statement review · Payment-processing services · Equipment and POS guide · Local merchant-services guide · Meet Robert Staschak

View this page