01 / The quick answer
What is Level 3 credit card processing?
Level 3 credit card processing sends itemized purchase information with eligible commercial-card payments. Instead of transmitting only the payment total, the transaction carries details about what was purchased. That information can support buyer reconciliation and qualification for a different interchange category. The benefit depends on the card, transaction, data quality, processing route and your pricing agreement. [1]
Think of it as connecting the invoice to the payment. A wholesaler already knows which parts a customer ordered. The opportunity is to carry those details through the payment system accurately, then verify what changed on the processing statement.
For a business comparing providers, the useful question is not simply “Do you support Level 3?” Ask: Which of our transactions can qualify, how will our actual invoice data reach the network, and where will we see the financial result?
This guide focuses on U.S. commercial-card acceptance. For the full cost structure around it, start with our credit card processing fees guide.
02 / Read the data, not the label
Level 1, Level 2 and Level 3: what actually changes?
The levels describe increasingly detailed transaction information. Level 1 is the basic payment record. Level 2 adds purchasing and tax context. Level 3 adds item-level detail. A higher data level is not a higher credit limit, a faster payout promise or a merchant approval category. [9]
The payment.
The basic transaction: amount, currency, and the information needed to process it.
The starting point.
The purchase.
Additional purchase context, such as tax and a customer or purchase-order reference.
More transaction context.
The line items.
Invoice-level detail: what was sold, how many units, at what price, and how totals reconcile.
A more complete data record.
A traditional data taxonomy, not a universal pricing ladder. Current network programs, card eligibility, and processor requirements determine qualification.
The terminology can be confusing because a network's current interchange program and a gateway's feature name may differ. NMI, for example, still calls its service Level III Advantage while explaining Visa's move to Product 3. Ask for the current network program behind the product label. [8]
Keep one other distinction clear: a card's marketing tier is not its transaction-data level. Mastercard's rate schedule uses Level 1–5 column headings for small-business card products, separately from its Data Rate I and II rows. A “Level 3” column does not mean that every payment in that column is a Level 3 enhanced-data transaction. [5]
03 / The 2026 reality
Visa CEDP and Mastercard Level 3 follow different rules
An older article that presents one permanent Visa-and-Mastercard Level 2/3 rate chart can send you in the wrong direction. Treat the two networks separately and date every rate comparison.
Visa: understand Commercial Enhanced Data Program and Product 3
Visa introduced CEDP in stages. April 2025 brought a new program fee; October 2025 replaced the legacy Level 3 program with Product 3; January 2026 changed business-credit pricing; April 2026 ended the ordinary Level 2 incentive program. [3]
There is an important exception: Visa's current U.S. schedule still lists Commercial Level II–Fuel. It also distinguishes Commercial Product 3 from Business Product 3. Do not turn “Visa retired Level 2” into a claim that every fuel-related program disappeared, or confuse the separate Business Product 2 row with the retired Level 2 enhanced-data incentive. [4]
Merchant verification also needs current evidence. Stripe's CEDP guidance says Visa paused verifying new businesses as of November 2025 while allowing transaction-level qualification to continue. Avoid assuming that an old “verified merchant” diagram describes every current processing arrangement. Ask your acquirer how qualification and any later adjustment work for your account today. [3]
Mastercard: keep Data Rate II and III distinct
Mastercard's April 2026 U.S. table continues to show both Data Rate II and Data Rate III. Its large-market-credit column includes Data Rate III, while the commercial-debit and commercial-prepaid columns show that row as not applicable. Small-business credit has a separate table. Visa's CEDP transition does not rewrite those Mastercard categories. [5]
Practical takeaway: request a network-by-network explanation for your actual card mix. A single “commercial card rate” hides too much to support a useful buying decision.
04 / Find the addressable opportunity
Which businesses and cards can qualify?
Start with the payment mix, not the company name. A B2B seller may still receive consumer cards; a consumer-facing company may occasionally receive purchasing cards. Stripe's current documentation identifies purchasing, corporate and business cards for Visa Product 3, but purchasing and corporate cards for Mastercard Level 3. It also lists merchant-category exclusions and geographic limits. These are not universal benefits for every card bearing a business name. [2]
| Review question | Evidence to request |
|---|---|
| Which cards do customers use? | A report separating network, commercial product and consumer-card volume. |
| Where is the transaction acquired? | The merchant and card-issuer countries, with confirmation of the applicable domestic or cross-border program. |
| Is our business category eligible? | The assigned merchant category code and the current program exclusions. |
| Does this payment flow carry the data? | Confirmation for your exact gateway, processor, ERP connector and capture method. |
| Does our contract pass through the benefit? | A written explanation of pricing, extra fees and any later credits. |
Wholesalers, distributors, manufacturers and professional-service businesses with detailed invoices are sensible places to investigate. That is a workflow fit, not a statement that every merchant in those industries qualifies. Gather a representative month and isolate plausible candidates before estimating savings.
Mastercard notes that qualification can depend on merchant category, timing between authorization and clearing, enhanced data and other conditions. Complete line items alone do not override the rest of the program. [12]
For a larger account, connect this review to your high-volume payment processing plan. The best project may be improving an existing integration, rather than changing the whole payment stack.
05 / Build an invoice the payment can carry
What Level 3 data fields do you need?
Expect purchase references, truthful tax information and a record for each item. Typical item details include a description, product or commodity code, quantity, unit of measure, price and relevant discounts. Freight, duty and shipping information may also be required. The precise fields and formats depend on the provider and transaction. [9]
| Data group | Where to look in your business | Question to resolve |
|---|---|---|
| Invoice or order reference | Sales order, invoice or customer purchase order | Can finance trace the payment back to one purchase? |
| Item identity | Product catalog or service catalog | Does the description identify what was sold? |
| Quantity and unit | Fulfillment or billing record | Does “2” mean two units, cases or hours? |
| Price and adjustments | Invoice calculation | Do discounts and extensions reflect the actual sale? |
| Tax and delivery | Tax engine, invoice and shipment | Are these real amounts and the appropriate locations? |
Accurate is more important than merely populated
Adyen's current guide rejects generic Visa item descriptions such as “product” or “service.” It also requires invoice arithmetic to agree: line totals reflect quantity, price and discounts; the capture total reconciles with the lines, freight and tax. [6]
Same payment. A more detailed record.
Make the invoice
part of the payment.
Item descriptions, quantities, and unit costs give the transaction more context. The line items, tax, freight, and adjustments need to reconcile to the amount captured.
This simplified example illustrates data depth. It is not a complete gateway payload or a qualification test.
All details are fictional. $1,200 in items + $84 tax + $16 freight = $1,300. Selecting a level highlights that layer; it does not submit a payment or predict interchange.
Switch between the traditional data levels to see how an itemized invoice adds context to a payment. This fictional $1,300 purchase combines valve kits, inspection hours, tax and freight. The explorer illustrates the information; it does not validate a payload or establish network qualification.
For an internal audit, pull one ordinary invoice, one discounted order and one partially fulfilled order. Give each to finance and the integration owner. Ask both teams to calculate the captured amount independently. Any disagreement belongs on the mapping worklist before launch.
Do not invent sales tax or commodity codes to make a record look complete. If tax is genuinely zero, report it accurately and confirm the applicable requirements. Stripe's Product 3/Level 3 guidance allows zero tax where no tax was collected. [2]
06 / Follow the information
How Level 3 processing connects your ERP, gateway and acquirer
A useful implementation has an accountable path from the original invoice to the final statement. Treat these as four handoffs, with an owner for each:
- Source the real purchase. Your accounting system, ERP, storefront or billing platform supplies the invoice and item records. Decide which system owns changes after the original order.
- Map and validate. The integration converts those records into the gateway's fields. Resolve currency units, rounding, discount allocation and product identifiers before transmission.
- Submit through a supported route. The gateway and processor must support the selected program on your account. NMI specifically directs partners to check the processor matrix and enable the relevant service. [8]
- Reconcile the result. Match the data status and eventual interchange category to the original payment. Keep an exception list for eligible transactions that missed the intended outcome.
The risky shortcut is to stop at “payment successful.” Cybersource documents cases where a payment processes even when required enhanced fields are omitted, or where Level 3 transmission is disabled after a batching problem. It also describes its data service as pass-through: partial captures and credits may require the information again. [1]
Ask for separate visibility into data received and data submitted. Adyen exposes that distinction along with refusal or warning reasons. A payment log that contains line items is weaker evidence than confirmation that the provider transmitted them. [6]
Expect the cost result to have its own timing
PayPal describes a CEDP process in which qualifying transactions can receive an interchange adjustment after a review 10–15 days following settlement. That is provider-described review timing, not a universal promise that your deposit takes that long or that every account receives a credit on that schedule. Ask where the adjustment will appear. [7]
07 / Turn the rate into a business case
How much can Level 3 processing save?
The honest answer comes from eligible transactions and your agreement. Interchange is a network-defined transfer between financial institutions. Your business pays its negotiated merchant price, which includes other services and costs. A lower interchange category therefore is not automatically the same amount of savings on your invoice. [10]
Published interchange is context, not a processing quote
| Published category | Interchange row | Important boundary |
|---|---|---|
| Visa Commercial Product 3 | 1.75% + $0.10 | Corporate/purchasing schedule; not every business card. [4] |
| Visa Business Product 3, Tier I | 2.40% + $0.10 | One business-credit tier; other tiers differ. [4] |
| Mastercard Data Rate III | 1.90% + $0.10 | Large-market credit column; not commercial debit/prepaid. [5] |
These rows exclude your processor's markup and other charges. Visa's cited schedule is effective April 18, 2026; Mastercard's is effective April 17, 2026. Use the live network documents and a written account-specific quote when making a decision.
Model net benefit, including the transactions that miss
For planning, calculate gross improvement only on the volume that actually qualifies. Then subtract incremental program, gateway and service fees. PayPal documents a five-basis-point CEDP program fee on applicable reviewed transactions. Confirm the fee base and pass-through terms rather than subtracting it only from transactions that earned a benefit. [7]
A lower rate is only half the math.
Start with the card volume that may qualify. Then account for actual qualification and the extra fees. This comparison isolates the change; it is not a quote or your total processing bill.
Modeled monthly cost reduction
$3,688.80 less per year at the same monthly activity
After $52.60 in added monthly fees.
- Gross modeled interchange difference
- $360.00
- Incremental program + transaction fees
- $52.60
- Break-even rate improvement percentage points on qualifying volume
- 0.0438 pp
Assumes unchanged activity for 12 months and the same average ticket for qualifying volume. Existing fees common to both scenarios cancel out. Nonqualifying volume gets no modeled interchange reduction. Results do not guarantee eligibility, qualification, pass-through pricing, or savings.
Runs in this page. Inputs are not sent or saved.
A basis point is one hundredth of a percentage point. An illustrative 50-basis-point improvement on $80,000 is $400 before additional costs. It is a calculation, not a claim that your cards will improve by 50 basis points.
Build a conservative case first. Use a smaller eligible share, allow for data failures and include the real monthly software bill. Then compare the result with setup time and ongoing reconciliation work. If the project works only when every submitted dollar qualifies, its business case needs more evidence.
Use the credit card processing fee calculator for the wider account comparison. A change that saves money on one category can still cost more overall if other charges rise.
Reviewing your commercial-card costs? Discuss your processing setup with NUMUS
08 / Make the rollout measurable
A practical Level 3 implementation checklist
Assign finance to the numbers, operations to the invoice process and your integration owner to the data path. Give the provider one shared review packet so each team works from the same assumptions.
Your enhanced-data readiness checklist.
Map the open questions before changing your setup. This is a conversation guide—not an approval score or a determination that your transactions qualify.
0 of 8 questions reviewed. Start with card eligibility.
Separate networks, commercial card types, transaction types, and regional requirements. Do not assume every business card qualifies.
Confirm the Visa CEDP / Product 3 path and Mastercard Data Rate III support where relevant; an old “Level 3” feature label is not enough.
Check product descriptions, quantities, unit prices, item codes, tax, and other fields your specific integration requires.
Validate quantities, prices, discounts, tax, and freight. Use legitimate transaction data; do not fill gaps with invented values.
Confirm the ERP, gateway, processor, authorization / capture flow, and settlement records support the fields and timing required.
Ask for the applicable interchange categories, added program fees, transaction fees, and contract terms in writing.
Ask for settlement-level reporting, the reason a transaction misses the intended category, and a named owner for corrections.
Compare similar card mixes and transaction sizes after implementation. Check realized interchange differences against every incremental fee.
Selections stay in this page and reset on reload. No contact information is needed.
Open printable worksheetBuild a small but representative test pack
Include a single-item sale, a multi-item invoice, a discount, freight, a legitimate zero-tax example and a partial capture. Add a credit or refund where the provider's workflow supports it. Test in the provider's approved environment before involving real customers.
For each scenario, record the expected invoice total, data payload, accepted payment result and enhanced-data status. Then separately record the settlement category when a controlled production check is appropriate. A sandbox result can demonstrate the mapping; it cannot prove a future interchange charge.
BlueSnap's published CEDP error reference includes mismatches between the source amount and aggregated line, tax, shipping and discount values. Use feedback like that to identify a specific mapping defect instead of retrying the same bad record. [11]
Keep the first-month report simple
Track candidate volume, submitted volume, qualified volume, additional fees and realized net change. Keep those denominators separate. If submission coverage improves while qualification stays flat, inspect the data and eligibility rules before congratulating the team on the integration.
Compare similar card products and transaction types across periods. A lower account-wide effective rate may result from a changing card mix; it does not, by itself, prove that Level 3 caused the improvement. Our merchant processing statement guide helps organize that review.
09 / Have a better provider conversation
What to ask a Level 3 payment processing provider
Request answers in the context of your software and customers. A product brochure can explain a feature; it cannot confirm your merchant setup or commercial terms.
- Which exact card products and categories qualify? Ask for separate Visa and Mastercard answers, including exclusions.
- Is our existing processor route supported? Identify the account feature, connector version and any configuration work.
- Where does each invoice field come from? Ask how corrections, service items, partial captures and refunds are handled.
- Which fields are enriched automatically? Require the enrichment to reflect actual purchases, with a way to inspect the submitted result.
- What happens when enhanced data fails? Ask whether the payment still settles, who receives the warning and who fixes it.
- How do we verify the financial benefit? Request an example statement or transaction report showing the category, fees and later adjustments.
- What will implementation and ongoing service cost? Include setup, per-transaction, percentage, monthly and support charges.
- What will success look like after the pilot? Agree on an evidence-based comparison before expanding the rollout.
Prepare representative statements, redacted invoices, your software list and the card-mix report. The merchant account application checklist provides broader account-preparation context. Share sensitive records only through the provider's agreed secure process.
10 / Common questions
Level 3 credit card processing FAQ
Is Level 3 the same as Visa Product 3?
Level 3 describes detailed transaction data and remains common provider terminology. Product 3 is Visa's current U.S. commercial interchange program under CEDP. They are closely related, but using a feature named Level 3 does not itself establish Product 3 qualification. [3]
Does Level 3 work on every business credit card?
No. Network, product, merchant category and geography matter. Current Stripe guidance distinguishes Visa Product 3 eligibility from Mastercard Level 3 eligibility. Ask your provider to classify actual transactions before applying an estimated savings rate to them. [2]
Can we qualify when the invoice has no sales tax?
A truthful zero-tax transaction can be compatible with Level 3/Product 3 requirements. Do not manufacture tax to pursue a discount. Confirm the specific network and provider rules for your transaction, including any other required fields. [6]
Can service businesses use Level 3 data?
Potentially. The review turns on the transaction and supported program, not simply whether you ship a physical product. A service invoice still needs meaningful descriptions, quantities or units, and accurate amounts. Confirm how your provider maps your actual services and business category. [9]
Does a successful payment mean the enhanced data qualified?
No. Cybersource explicitly describes successful payment processing despite missing enhanced fields. Look for transmission and qualification evidence, followed by the relevant settlement or billing result. The authorization message answers a different question. [1]
Will Level 3 automatically reduce our flat processing rate?
Not necessarily. Your agreed merchant price determines what you pay. Ask whether an interchange reduction passes through, changes a later credit or leaves your contracted flat price unchanged. Compare the full written terms, not just a network table. [10]
Do we have to replace our ERP or gateway?
Not automatically. First identify the missing step: source data, mapping, account configuration, processor support or reporting. A targeted connector or configuration change may be enough. Require confirmation for your precise setup before purchasing a replacement. [8]
What is the best way to verify real savings?
Run a defined pilot. Match the same types of transactions, inspect qualification outcomes and include every incremental cost. Reconcile later credits to the original period, then compare realized net cost with the agreed baseline. Keep estimated savings separate from money actually reflected on your statement.
Primary-source references
Sources and current-rule context
Checked September 26, 2026. Network documents establish the cited U.S. rate context. Provider documentation illustrates specific implementations; it does not establish NUMUS capabilities or universal requirements. Current network rules and your agreement control.
- Cybersource — Level II and Level III Processing. Data purpose, account configuration, pass-through handling and payment success versus data transmission.
- Stripe — Payment line items. Current card and geographic eligibility, tax treatment and Visa Product 3 context.
- Stripe — Understand Visa's Commercial Enhanced Data Program. Transition dates and the published verification-status update.
- Visa — USA Interchange Reimbursement Fees, April 18, 2026. Corporate/purchasing and business-credit schedules; Fuel Level II exception.
- Mastercard — U.S. Region Interchange Programs and Rates, April 17, 2026. Small-business and large-market commercial tables.
- Adyen — Level 2/3 data. Field validation, invoice arithmetic and received-versus-submitted data status.
- PayPal — Visa's Commercial Enhanced Data Program. CEDP flag, participation fee and lagged interchange review; published February 17, 2026.
- NMI — Understanding Visa's CEDP Program. Processor support, account enablement and provider feature terminology.
- PayPal Developer — Level 2/Level 3 processing. Data levels and example order/item fields; updated July 24, 2026.
- Visa — The Visa System: Rates, Fees and Rules. Interchange versus the merchant's negotiated processing price.
- BlueSnap — Visa CEDP requirements and error codes. Error feedback for source-amount and invoice-component mismatches.
- Mastercard — Interchange rates and fees. Acquirer pricing and the multiple criteria underlying qualification.