Add commercial transaction detail
Eligible commercial-card transactions may require additional fields such as customer code and tax information beyond ordinary retail payment data.
B2B & Commercial Card Processing
Level II & Level III data can turn commercial-card processing into a qualification strategy.
Selective Pay helps B2B and B2G merchants review the processor, gateway, ERP or POS workflow and transaction data required to improve commercial-card qualification where supported. The objective is simple: transmit the right data, through the right payment path, and verify how the transaction actually settles.
- Level II and Level III transaction-data review
- Gateway, processor and ERP compatibility analysis
- Settlement and qualification validation
Transmit line-item detail
Product, quantity, unit cost, tax, commodity and shipping data can be required for the highest commercial-card qualification levels where supported.
Confirm settlement qualification
Sending fields is not enough. We review how eligible transactions actually qualify after settlement and where missing or malformed data may be creating avoidable cost.
Why Commercial Cards Are Different
A B2B card transaction may carry more information—and more opportunity—than a retail sale.
Commercial cards are often used for purchasing, accounts payable, business travel, procurement and government spending. Depending on the card program and processing path, those transactions may qualify differently when the merchant submits the additional data expected for a commercial payment.
The opportunity is not simply “turn on Level III.” The merchant must confirm that the card is eligible, the gateway captures the correct fields, the processor transmits them correctly, the ERP or POS supplies usable values and the transaction ultimately settles into the intended qualification category.
Commercial cards can qualify differently
Corporate, purchasing and other commercial card products may use qualification categories and data requirements that differ from ordinary consumer-card transactions.
The data path matters
A merchant may collect the right information in an ERP or invoice system but lose it before settlement if the gateway or processor does not support the required fields.
Settlement tells the truth
Authorization success does not prove optimal qualification. Transaction-level settlement and interchange detail are the best way to verify the final result.
Level II vs. Level III
The difference is the depth of commercial transaction data.
Exact required fields vary by network, card product and processing environment, but the general concept is straightforward: Level II adds commercial transaction detail, while Level III extends that data to the line-item level.
Level II commercial card data
Level II commonly adds business transaction information beyond standard authorization data.
- Customer code or purchase reference
- Tax amount or tax-exempt indicator
- Invoice or order reference
- Transaction and merchant information required by the supported program
Level III line-item data
Level III can add detailed product and fulfillment information for eligible commercial card transactions.
- Product or commodity code and description
- Quantity, unit of measure and unit cost
- Extended line-item amount and item-level tax
- Ship-to ZIP or country and other required commercial fields
Commercial Card Workflow
Optimization requires the entire transaction path to work together.
Selective Pay reviews where the commercial data originates, how it is mapped, which systems touch the transaction and how the processor reports the final qualification.
Identify eligible commercial-card volume
Review card mix, transaction types and current statements to determine how much B2B or B2G volume may be affected by commercial-card qualification.
Map the required transaction data
Determine which customer, tax, invoice, order and line-item fields are available from the ERP, POS, ecommerce or accounts-receivable workflow.
Confirm gateway and processor support
Verify the certified processor, gateway, transaction type, devices and commercial-data fields rather than assuming every integration supports Level II or Level III.
Test the transaction lifecycle
Validate authorization, capture, partial payment, refund and settlement workflows to make sure commercial data remains attached to the final transaction.
Review actual qualification results
Use transaction-level interchange or qualification reporting to identify downgrades, missing data and transactions that did not achieve the expected commercial qualification.
Where Level II & III Matter
Commercial-card optimization is most valuable where B2B and government payments are material.
The strongest opportunities are typically merchants with meaningful corporate, purchasing-card or government-card volume and enough transaction detail to support the required data fields.
Distribution and building materials
Invoice-driven transactions, repeat business customers and detailed product data can create strong commercial-card optimization opportunities.
Industrial and commercial suppliers
ERP-based orders often contain invoice, customer, tax and line-item detail that may be useful for eligible commercial-card transactions.
Contractors and commercial services
Large invoices and business-card payments can make qualification analysis especially relevant when commercial data is available.
B2G and purchasing-card acceptance
Government and procurement payments may involve purchasing-card programs where commercial transaction data and qualification rules are important.
What We Review
A Level II/III review looks beyond the headline processing rate.
We evaluate how the merchant is currently processing commercial cards, whether the required data is available, whether the payment technology can transmit it and whether the processor's settlement reporting proves the expected qualification.
Statement and card-mix analysis
Commercial-card volume, effective cost, qualification categories and patterns that suggest avoidable interchange or downgrade expense.
Gateway and processor capability
Supported Level II/III fields, processor routes, transaction types, devices, APIs and any limitations that affect commercial-data transmission.
ERP, POS and ecommerce data
Invoice, customer, purchase-order, tax, product, quantity, unit-of-measure, price and shipping information available at the point of payment.
Capture and settlement behavior
Partial captures, delayed capture, refunds, card-on-file and other workflows that can alter the final amount or affect the transaction data sent at settlement.
Transaction-level qualification
Actual interchange and downgrade results by transaction, not just blended monthly averages or assumptions based on the gateway settings.
Operational ownership
Which party owns the data mapping, gateway configuration, processor setup, development, testing and ongoing support when something changes.
Qualification note: Level II or Level III fields do not guarantee a lower interchange category. Results depend on the card product, network rules, transaction type, merchant setup, processor, gateway and whether required data is complete and accepted at settlement.
Real-World Lesson
The difficult part is often not collecting the data—it is preserving it through settlement.
In complex B2B environments, a merchant may already have invoice and line-item data inside the operating system. The optimization opportunity depends on whether that data survives the complete payment workflow, including authorization, capture and any adjustments before settlement.
The source system can have everything needed
ERP or business software may already contain customer codes, invoice numbers, tax, product descriptions, quantities, unit costs and other commercial fields.
- Map the source fields correctly
- Confirm the gateway receives them
- Validate the processor supports them
- Retain them through the final capture
Settlement reporting verifies the outcome
The most useful test is whether the final settled transaction receives the intended commercial qualification—not simply whether a gateway screen shows Level III fields.
- Review transaction-level interchange detail
- Identify downgrade reasons
- Compare expected vs. actual qualification
- Correct mapping or workflow issues and retest
Integration Matters
Level III only works when the payment connection supports the required data.
A gateway can be excellent for one merchant and unsuitable for another if it does not support the processor route, line-item fields, capture workflow or software integration required for commercial-card optimization.
Confirm the supported processor route
The same gateway may support different features depending on processor, platform, integration method and transaction type.
Test data after capture changes
If an authorized amount is later reduced or partially captured, the line-item and tax data should still reconcile to the final settled amount.
Keep the ERP and gateway aligned
Field names alone do not prove the data is usable. Values, formats, totals and mappings must satisfy the supported payment path.
Frequently Asked Questions
Level II and Level III commercial-card processing questions.
What is Level II credit card processing?
Level II processing adds commercial transaction data such as customer code, tax amount and other required fields to eligible business-card transactions. Exact requirements depend on the card type, network, processor and processing environment.
What is Level III credit card processing?
Level III processing can include detailed line-item information such as product description, quantity, unit cost, commodity code, tax and shipping data for eligible commercial card transactions.
Does sending Level III data guarantee lower interchange?
No. Better qualification depends on the card product, transaction type, processor, gateway, merchant category, required data and how the transaction ultimately qualifies at settlement.
Can Level II and Level III work with ERP or ecommerce payments?
Yes, when the ERP, ecommerce platform, gateway and processor support the required fields and transaction workflow. The supported integration path should be confirmed before relying on commercial-card optimization.
Why would a commercial transaction still downgrade?
Possible causes include missing or invalid required fields, unsupported gateway or processor paths, timing or capture issues, mismatched totals, card-product eligibility or other qualification requirements. Transaction-level reporting is needed to identify the actual reason.
What do you need for a commercial-card review?
We typically start with recent processing statements, monthly volume, card mix, average ticket, ERP or POS information, current gateway and processor, transaction workflow and any available interchange or qualification detail.
Review Your Commercial Card Costs
Find out whether your B2B card transactions are qualifying the way they should.
Selective Pay can review your statements, commercial-card mix, gateway, processor, transaction data and ERP or POS workflow to identify Level II and Level III opportunities and the issues preventing better qualification.