The payment is taken in a virtual terminal
A standalone terminal has no access to your invoice lines, so it physically cannot send Level 3 data. This is the single most common cause and it is invisible on a tiered statement.
Level 3 is not a product anyone sells you. It is a data standard your transactions either meet or fail, silently, on every commercial card payment you take.
Level 3 processing is the transmission of detailed line-item data alongside a commercial card transaction so it qualifies for the lowest interchange rate the card networks make available. Level 2 requires a small set of additional fields, principally sales tax and a customer or purchase order reference. Level 3 requires all of Level 2 plus per-line-item detail: product codes, item descriptions, quantities, unit prices, freight and duty amounts.
It applies only to commercial, corporate and purchasing cards - consumer cards do not have Level 3 interchange categories. Published card-network and industry figures put the difference between a non-qualified commercial card transaction and a properly qualified Level 3 one at roughly 50 to 150 basis points. On a $5,000 invoice that is $25 to $75 per transaction. The most common reason a business fails to qualify is that its accounts receivable team keys card numbers into a standalone virtual terminal, which cannot transmit the required fields at all.
The data already exists on your invoice. The work is getting it to travel with the payment.
| Level | Required data | Where it lives |
|---|---|---|
| Level 1 | Card number, expiry, amount | Any terminal. This is the default, and the most expensive. |
| Level 2 | Sales tax amount, customer code or PO number, merchant postal code, tax-exempt status | Order header in your ERP |
| Level 3 | All of Level 2, plus item description, product code, quantity, unit of measure, unit price, line-item total, discount, freight and duty | Invoice lines in your ERP |
A single missing required field drops the whole transaction to the next level down. This is why qualification needs monitoring rather than a one-time setup.
A standalone terminal has no access to your invoice lines, so it physically cannot send Level 3 data. This is the single most common cause and it is invisible on a tiered statement.
Freight is a required Level 3 field. Billing delivery on its own ticket removes it from the transaction and fails the whole record.
Transactions must settle within a window, typically the next day. Batching late downgrades otherwise-perfect data.
Common on milestone and progress billing. If the milestone invoice has no line detail of its own, there is nothing to transmit.
A zero-tax transaction must be marked tax-exempt rather than simply left blank, or it reads as missing data.
The honest calculation is: your commercial card volume, multiplied by the share currently downgrading, multiplied by the basis-point gap. Only the last figure is general knowledge; the first two come from your statements.
Be sceptical of anyone who quotes you a savings number before seeing them.
What percentage of your card volume is business, corporate or purchasing cards. Consumer cards are irrelevant to Level 3.
On interchange-plus, read it off the statement. On tiered pricing it is hidden, which is itself a finding.
Published ranges put non-qualified against Level 3 at roughly 50 to 150 basis points on a commercial card.
Some volume will never qualify - consumer cards, card-present retail sales, customers whose data you cannot obtain. A credible projection excludes these.
There are three ways, and only one of them scales.
A payment connector reads the invoice from NetSuite, Sage, QuickBooks, Acumatica, Epicor or SAP Business One and transmits the fields automatically. This is the durable answer.
Some gateways let a user type line items into a payment screen. It works and it qualifies, but it doubles data entry and degrades the moment someone is busy.
Direct integration against the gateway API. Worth it for high volume or an unusual system, overkill for most.
Where you are today
Not processing yet. We map which payment methods your card mix and products can realistically support, what each costs, and what your application file needs before you open.
Plan your payment setupAlready processing but paying too much, funding too slowly, or working around a system that does not fit. Send statements and we return a line-by-line read plus alternatives.
Review my current setupAccount terminated, frozen, capped or moved to reserve. We help you interpret the notice, pursue held funds, and rebuild with fewer single points of failure.
Get help with a complex accountTurned down on application. We read the decline reason, identify what was missing or mismatched in the file — licence, ownership, product mix, banking — and rebuild the submission before it goes back out.
Review a declined applicationNo. Level 3 interchange categories exist only for commercial, corporate, purchasing and government cards. Sending line-item data on a consumer card transaction does not reduce its cost.
Generally no. A standalone virtual terminal has no connection to your invoice lines. Some gateways offer an enhanced-data entry screen, but that requires someone to retype line items for every payment.
On interchange-plus pricing, interchange is itemized on your statement and qualification is readable. On tiered or flat-rate pricing it is deliberately not visible, which is one of the strongest arguments for changing pricing model.
Indirectly, yes. The same line-item detail that qualifies a transaction is also compelling evidence in a dispute, because it documents exactly what was sold.
Sometimes. The requirements are that the processor supports Level 3 pass-through and that your ERP can feed it. Both need confirming - ask your current provider directly what percentage of your commercial card volume qualified last month, and see whether they can answer.
The line-item data standard that qualifies a commercial card transaction for the lowest available interchange. These pages sit under this guide and link back to it.
Send three months of merchant statements and one representative invoice. You get back a line-item breakdown of what is downgrading, what it costs annually, and what could realistically be recovered. No obligation, and the analysis is yours either way.
Interchange qualification depends on your card mix, the data your systems can transmit, your settlement timing, and card-brand rules that change twice a year. Nothing on this page is a quoted rate, a guarantee of savings, or a promise of approval. Figures shown are illustrative ranges drawn from published card-network and industry sources, not an offer. What you would actually save is whatever a review of your own statements shows, which is why we start there.