Level 3 processing data requirements is the most powerful interchange optimization tool available to B2B merchants — but it only works if every required data field is submitted correctly, completely, and in the right format. Visa’s CEDP program does not award partial credit. A transaction either passes the full data review and qualifies for the lowest interchange rate, or it fails and you pay the standard rate. For merchants processing significant B2B or government card volume, the difference can run into thousands of dollars per month. This guide breaks down every mandatory field, the arithmetic that must balance, and the exact errors that silently disqualify transactions you think are already optimized.
Why Level 3 Processing Data Requirements Must Be Met Exactly
Since November 2025, Visa paused adding new merchants to the CEDP verified merchant list while it refines its adjudication processes. During this pause, all transactions submitted for CEDP go through a post-settlement lagged review — meaning Visa grades your data after the transaction settles, typically issuing a credit 10 to 15 days later if the transaction qualifies.
This makes the quality of your Level 3 data submission more consequential than ever. Under the lagged process, there is no upfront adjustment. If your data passes, you get the credit. If it fails — for any reason, including a single misconfigured field — you get nothing. The review is binary.
⚠ Critical Point
Many merchants assume their processor is handling Level 3 “automatically.” What that often means is that some fields are being passed — not necessarily all of them, and not necessarily correctly. The CEDP lagged review will tell you the truth. If you’re not seeing “Visa CEDP Verified” credits on your statements 10–15 days after settlement, your data has gaps.
Every Mandatory Level 3 Processing Data Requirement by Field
The following fields are required for a transaction to qualify for Level 3 interchange under Visa’s CEDP program. These requirements come directly from Visa’s qualification standards. Every field marked Mandatory must be present and valid — missing or blank values are an automatic disqualification.
Line Item — Required for Every Item on the Transaction
| Field | Status | Requirement |
|---|---|---|
| Item Commodity CodeCategory code for the goods or service — must be meaningful and traceable | Mandatory | Must be meaningful based on the item description. Cannot be blank or spaces. Not based on any ISO standard — use your own categorization system. |
| Item DescriptionPlain language description of goods or services provided | Mandatory | Must be meaningful and based on goods or services supplied. Cannot be spaces or a single character. A generic placeholder like “ITEM” or “PRODUCT” will fail the review. |
| Product CodeYour internal SKU, part number, or service code | Mandatory | Must be meaningful and based on the item or service. Cannot be spaces or the Card Product ID. Must be something the merchant can track internally. |
| QuantityNumber of units purchased | Mandatory | Must be greater than zero. A quantity of 0 or a blank value disqualifies the line item. |
| Unit of MeasureEA, HR, LB, etc. | Mandatory | Must not be spaces. Must reflect the actual unit being sold — each, hour, pound, gallon, etc. |
| Unit CostPrice per unit before discounts and tax | Mandatory | Must be greater than zero. This is the per-unit price, not the line total. |
| Tax RateApplicable tax rate for this line item | Mandatory | Must be a numeric value. For tax-exempt transactions, submit 0 — do not leave blank. |
| Line Item DiscountAny discount applied to this line item | Mandatory | Must be a numeric value. If no discount applies, submit 0 — do not leave blank. |
| Tax AmountDollar amount of tax for this line item | Conditional | Required if Tax Treatment is 0 or 2 (line-item level tax). Must not be used simultaneously with Invoice Tax Amount — choose one approach and apply it consistently. |
| Line Item TotalCalculated total for this line — must match the formula exactly | Mandatory | Must equal: Quantity × Unit Cost − Discount + Line Item Tax Amount. If this calculation does not balance, the transaction fails. See arithmetic section below. |
| Line Item Discount Treatment Code | Optional | Must be a numeric value if submitted. |
Invoice Level — Required for the Overall Transaction
| Field | Status | Requirement |
|---|---|---|
| Customer CodePurchase order number or customer reference — required for Level 2 and Level 3 | Mandatory | Must not be spaces. This is the single most commonly missing field in failed Level 3 submissions. For government transactions, this is typically the PO number or contract number. |
| Invoice Tax AmountTotal tax applied at the invoice level | Mandatory | Must be numeric. If greater than zero, must be between 0.1% and 22% of the transaction amount for Visa. Do not use simultaneously with line-item Tax Amount. |
| Invoice Discount AmountAny discount applied at the invoice level | Mandatory | Must be numeric. Submit 0 if no invoice-level discount applies. |
| Invoice ShippingFreight or shipping charges | Mandatory | Must be numeric. Submit 0 if no shipping charges apply. |
| Invoice DutyImport duty or customs charges | Mandatory | Must be numeric. Submit 0 if no duty applies. |
| Invoice Tax TreatmentCode indicating how tax is being applied | Mandatory | Must be one of the following values: SPACE or 4 — No tax applies 0 or 2 — Tax entered at the line-item level 1 or 3 — Tax entered at the invoice level This field controls which tax fields are required. Mismatching this code with your actual tax submission is a common disqualification error. |
Important: You must choose either invoice-level tax (Invoice Tax Amount) OR line-item level tax (Tax Amount per line) — not both. Similarly, choose either Invoice Discount Amount OR Line Item Discount per line. Mixing both levels for the same field type will cause the transaction to fail validation.
The Arithmetic That Must Balance
Level 3 qualification is not just about having the right fields — it requires the numbers to reconcile mathematically. Visa validates that your line-item calculations and your invoice total are internally consistent. If the math does not balance, the transaction fails regardless of how well-populated your data fields are.
There are two formulas that must hold:
Formula 1 — Line Item Total
Quantity × Unit Cost − Discount + Line Item Tax Amount = Line Item Total
Example
| Qty | Unit Cost | Discount | Tax Amt | Line Total |
|---|---|---|---|---|
| 1 | $5.00 | $1.00 | $0.00 | $4.00 |
Formula 2 — Transaction Total
All Line Item Totals + Invoice Tax Amount − Invoice Discount + Shipping + Duty = Transaction Amount
Example
| Line Totals | Invoice Tax | Invoice Disc | Shipping | Duty | Txn Amount |
|---|---|---|---|---|---|
| $4.00 | $1.00 | $0.34 | $0.25 | $0.00 | $4.91 |
Both formulas must balance exactly. A rounding discrepancy of even one cent between your calculated line item total and the submitted Line Item Total field will fail validation. This is a common source of disqualification in automated systems that round differently at the line level versus the invoice level.
The Most Common Reasons Transactions Fail
These are the field-level errors that most frequently cause Level 3 transactions to fail the CEDP review. Most of them are configuration issues in the payment gateway or ERP integration — not errors a business owner would ever see unless they know what to look for.
Blank or Placeholder Descriptions
Item Description and Product Code submitted as “ITEM”, “PRODUCT”, “N/A”, or a single character. Visa requires meaningful descriptions that reflect the actual goods or services. Generic placeholders fail immediately.
Missing Customer Code
The Customer Code field — typically the PO number or contract reference — is left blank. This is required for both Level 2 and Level 3 qualification and is the single most commonly missing field in failed submissions.
Tax Treatment Code Mismatch
The Invoice Tax Treatment code doesn’t match where the tax is actually being submitted. For example, setting Treatment to “SPACE” (no tax) while simultaneously submitting a tax amount will fail validation.
Mixing Tax Levels
Submitting tax at both the invoice level and the line-item level simultaneously. Visa requires one or the other — not both. Many gateway integrations default to submitting both, causing silent disqualification.
Arithmetic That Doesn’t Balance
Rounding differences between the line item calculated total and the submitted Line Item Total field. Even a $0.01 discrepancy causes the transaction to fail the mathematical validation check.
Zero or Blank Quantity / Unit Cost
These fields must be greater than zero. Service-based businesses sometimes submit quantity as 0 or leave unit cost blank for subscription or retainer transactions, which disqualifies the line item entirely.
Getting every field right is not a one-time setup task — it requires ongoing validation. Card network requirements evolve, gateway configurations drift, and ERP integrations introduce new edge cases with every update. The lagged interchange credit on your statement is your only real-time signal that the data is still qualifying.If you stop seeing those credits, something changed — and you’re paying for it on every transaction.
How to Confirm Your Level 3 Processing Data Requirements Are Passing
The most reliable way to confirm your Level 3 processing data requirements is qualifying under the current CEDP lagged review is to check your statements line by line. Under pass-through or interchange-plus pricing, qualifying transactions generate a separate credit line labeled “Visa CEDP Verified” approximately 10 to 15 days after the original settlement date.
If you are submitting Level 3 processing data requirements data and not seeing those credits consistently, the field-level issues above are the most likely cause. A full data audit — comparing your actual submitted field values against the requirements in this guide — will identify precisely where the gaps are.
For businesses that want expert help diagnosing their setup, Revolution Payments specializes in Level 3 processing data requirements for B2B merchants and can review your statements to show you exactly what’s qualifying and what isn’t.
Is Your Level 3 Data Passing the CEDP Review?
We audit B2B merchant statements and identify exactly which fields are causing transactions to fail — and what it’s costing you per month.Get a Free Data AuditNo obligation · Results within 48 hours · B2B specialists