Contents
- Visa CEDP, Product 3, and Mastercard Enhanced Data: What Government Agencies, Insurers, Property Managers, and Nonprofits Must Do Now
- What Changed and Why the Old Approach No Longer Works
- Visa CEDP and Product 3: How the Program Works
- Verified vs. Non-Verified Status
- What Visa Flags as Junk Data
- The CEDP Participation Fee
- Mastercard Enhanced Data: A Separate Program
- Program Comparison: Where Things Stand Now
- How This Plays Out in Your Vertical
- Government Agencies (MCC 9311 and Related)
- Property Management (MCC 6513 and Related)
- Insurance (MCC 6300 and Related)
- Nonprofits (MCC 8398 and Related)
- Product 3 Data Fields: What Must Be Submitted
- The 45-Day Clawback Rule
- Five Steps to Get This Right
- Frequently Asked Questions
- Not Sure If Your Commercial Transactions Are Qualifying?
- Sources and References
- Related Reading
Visa CEDP, Product 3, and Mastercard Enhanced Data: What Government Agencies, Insurers, Property Managers, and Nonprofits Must Do Now
⚡ Quick Answer
- Visa Level 2 is gone. It sunset in April 2026. Transactions on commercial cards either qualify for Product 3 under CEDP or they pay base interchange, which can exceed 3% all-in.
- Level 3 is now Product 3. Under Visa's Commercial Enhanced Data Program (CEDP), every line-item field is validated in real time. Merchants with clean data get Verified status and lower rates. Everyone else pays base.
- Mastercard is a separate program. Mastercard has not adopted CEDP. Its Level 2 and Level 3 programs are still active under their own rules.
- Government agencies, insurers, property managers, and nonprofits are all exposed. Each of these verticals accepts meaningful commercial, corporate, and purchasing card volume. Without compliant data passing through your processor and gateway, those transactions are downgrading every billing cycle.
- Visa can claw back interchange savings up to 45 days after settlement if submitted data turns out to be inaccurate or static.
If you run billing for a government agency, an insurance operation, a property management portfolio, or a nonprofit, you accepted commercial credit cards this year. Some of those cards were corporate cards. Some were purchasing cards. Some were government cards issued to businesses and contractors making payments on behalf of their organizations.
If your payment stack was not sending clean, invoice-level line-item data on every one of those transactions, you were paying more than you needed to. And you probably did not know it. Here is what changed, what it means for your organization specifically, and what you need to do about it.
The utility CEDP picture is covered separately in our MCC 4900 utility guide. The full Product 3 technical reference is in our complete Product 3 merchant guide. This article focuses on the verticals those guides do not cover.
What Changed and Why the Old Approach No Longer Works
For roughly two decades, Visa and Mastercard ran enhanced data programs known as Level 1, Level 2, and Level 3. The deal was simple: submit more transaction data on commercial card payments, qualify for lower interchange rates. Level 2 required a sales tax amount and a customer code. Level 3 required full line-item detail including item descriptions, quantities, unit prices, commodity codes, and ship-to information.
The problem was that enforcement was weak. Many processors learned that submitting static or low-quality data would still qualify for the reduced rates. Zero tax amounts where tax applied, generic product codes, identical line descriptions repeated across thousands of transactions. Visa decided to fix that.
CEDP changes the enforcement mechanism entirely. Visa now validates data in real time using AI-based monitoring before assigning interchange rates. Two dates matter:
- October 17, 2025. CEDP enforcement went live. Level 3 was replaced by Product 3. Visa began validating line-item data quality in real time. A 5-basis-point CEDP participation fee now applies to all qualifying program transactions.
- April 18, 2026. Visa Level 2 sunset. The Small Business and Commercial Level 2 interchange programs are retired. Product 3 is now the only route to below-base interchange on Visa commercial cards.
🚨 Both milestones have passed. If your processor has not confirmed CEDP compliance and Product 3 data submission for your commercial card volume, your transactions are currently routing to base interchange rates. Every billing cycle without action is a billing cycle where you are overpaying.
Visa CEDP and Product 3: How the Program Works
CEDP is not simply a rename of Level 3. It adds a data quality validation layer that did not exist before. Understanding how Visa evaluates your transactions determines whether your setup will actually qualify.
Verified vs. Non-Verified Status
Visa classifies participating merchants as either Verified or Non-Verified based on the quality and consistency of the data they submit.
- Verified. You consistently submit complete, accurate, non-static line-item data meeting all Product 3 field requirements. You qualify for reduced Product 3 interchange rates on eligible commercial card transactions.
- Non-Verified. Your data is incomplete, inaccurate, or fails Visa's quality checks. Transactions route to base interchange. That said, even Non-Verified merchants can receive Product 3 rates on individual transactions if that specific transaction passes validation. Visa evaluates each transaction separately.
Achieving Verified status takes time. Visa typically requires about 30 days of consistent, high-quality data submission before granting Verified classification.
What Visa Flags as Junk Data
Visa's AI monitoring flags several patterns as data quality failures. If your processor or billing system is generating any of these, you will not qualify for Product 3 rates:
- Sales tax reported as zero when the transaction involves a taxable sale in a taxable jurisdiction
- Item descriptions that match the merchant name. For example, every line item described as "City Water Department" or "ABC Insurance"
- Product codes or commodity codes that are generic placeholders like "0000" or "MISC"
- Identical unit prices and quantities across every transaction in a portfolio, indicating static data rather than real line items
- Ship-to postal codes that are always identical to the merchant postal code regardless of customer location
⚠️ Important for government agencies and nonprofits. Many government agencies and nonprofits have genuinely zero-tax transactions. That is legitimate. However, zero tax must be formatted correctly in the appropriate CEDP fields with proper indicators, not left blank or null. Ask your processor specifically how they handle tax-exempt transactions under CEDP. A vague answer is a problem.
The CEDP Participation Fee
All transactions submitted under CEDP incur a 5-basis-point (0.05%) participation fee from Visa. This applies to both Verified and Non-Verified merchants submitting Product 3 data. For Verified merchants, the net savings, the Product 3 rate discount minus the participation fee, is typically in the range of 10 to 15 basis points on corporate and purchasing cards, and meaningfully higher on large-ticket transactions.
Mastercard Enhanced Data: A Separate Program
Mastercard has not adopted CEDP and has not announced plans to do so. Its enhanced data programs, internally called Data Rate II and Data Rate III but commonly referred to as Level 2 and Level 3, remain active under Mastercard's own rules as of this writing.
ℹ️ Note on Mastercard. Your processor needs to handle Visa CEDP and Mastercard enhanced data correctly and separately. A gateway that updated for CEDP compliance may or may not have simultaneously updated its Mastercard enhanced data submission. These are different technical implementations. Confirm both explicitly with your processor.
For Mastercard commercial, corporate, and purchasing card transactions, Level 2 data includes the sales tax amount, customer code or purchase order number, and merchant postal code. The tax amount must be between 0.1% and 22% of the transaction total to qualify, or properly indicated as zero for exempt transactions. Level 3 requires all Level 2 fields plus full line-item detail per Mastercard's specifications. As of October 2025, Mastercard also tightened its unit-of-measure field requirements. If your system previously submitted a generic unit, your processor should now be populating a compliant value.
Program Comparison: Where Things Stand Now
| Program | Network | Status (June 2026) | Savings vs. Base | Line Items Required |
|---|---|---|---|---|
| Level 2 | Visa | Retired April 2026 | N/A | N/A |
| Product 3 (CEDP) | Visa | Active, Verified status required | ~10 to 15 bps; more on large tickets | Yes, AI-validated |
| Level 2 | Mastercard | Active, unchanged | ~75 bps on eligible cards | No |
| Level 3 (Data Rate III) | Mastercard | Active, unchanged | Up to ~100 bps | Yes, per MC specs |
How This Plays Out in Your Vertical
The exposure to commercial card interchange is not the same across every industry. Here is what CEDP and Mastercard enhanced data actually look like for each of IntelliPay's non-utility verticals.
Government Agencies (MCC 9311 and Related)
Government agencies, county treasurers, municipal offices, courts, and licensing departments, accept payment for taxes, fees, licenses, permits, and fines. A significant and growing share of those payments arrive via corporate purchasing cards and government cards issued to businesses, law firms, and contractors paying on behalf of their organizations.
The practical reality for most agencies: a property tax payment or permit fee is a single-line transaction. It is conceptually simple. But the Product 3 field requirements still apply to the card type. Your processor needs to populate all required fields correctly even when the transaction has only one line item. Item description should reflect the actual payment type, for example "Property Tax, Parcel 12-345-678, 2026 Q1," not a generic agency name. Work with IntelliPay to confirm how your MCC 9311 transactions are being structured under CEDP.
Property Management (MCC 6513 and Related)
Property management companies and HOA billing operations regularly receive commercial card payments from business tenants, corporate property owners, and commercial lessees paying dues and assessments. These are exactly the card types CEDP targets.
Property management has an added complexity. Billing typically runs through property management software that integrates to a payment gateway via API. That integration, not just the gateway, needs to pass Product 3 fields through the full stack. If the property management software is not populating item description, unit number, lease charge type, and amount breakdown, the gateway has nothing to forward to Visa. This is a software configuration issue, not just a processor issue.
Insurance (MCC 6300 and Related)
Insurance premium payments via commercial cards represent meaningful volume at mid-size and regional carriers. An employer paying group health or liability premiums on a corporate card, a business owner paying commercial lines via purchasing card. These are Product 3 eligible transactions. Without compliant data submission, they route to base commercial interchange.
Insurance billing systems frequently operate on legacy platforms or third-party policy administration software that was not built with enhanced payment data in mind. The integration point between policy billing and payment processing is where Product 3 data often breaks down. If your payment processor receives only a lump-sum authorization with no line-item context, it cannot generate compliant CEDP submissions downstream.
Nonprofits (MCC 8398 and Related)
Nonprofits collect membership dues, event registrations, sponsorships, and program fees. Corporations sponsoring events and paying dues often do so with corporate cards. Foundations making payments may use purchasing cards with line-item reporting requirements built into their internal approval workflows.
Most nonprofits assume their card volume is predominantly consumer. It often is not, especially for organizations with corporate membership tiers or sponsorship programs. Pull a card-type breakdown from your processor to see what share of your volume runs on commercial, corporate, or purchasing cards. That share is your CEDP and Mastercard enhanced data exposure. Many organizations are surprised by the number.
Product 3 Data Fields: What Must Be Submitted
To qualify for Visa's Product 3 interchange under CEDP, the following fields must be submitted with every eligible commercial card transaction. All fields are required. There is no partial credit. Visa validates each field for accuracy, not just presence.
| Field | Notes |
|---|---|
| Invoice / Order Number | Must be unique and meaningful, not auto-generated sequential numbers that suggest no real reference |
| Customer Code / PO Number | The buyer's internal reference for the purchase |
| Sales Tax Amount | Actual amount; exempt transactions must use correct exempt indicators, not null or blank |
| Ship-to Postal Code | Actual customer location, must not default to merchant ZIP on every transaction |
| Item Description | Descriptive and specific; cannot match the merchant name or be a generic placeholder |
| Item Quantity | Actual unit count per line item |
| Unit of Measure | Specific (e.g., EA, HR, MO). Mastercard also tightened this in October 2025 |
| Unit Price | Per-unit cost for each line item |
| Item Commodity Code | A real commodity code. Generic codes like 0000 will flag as junk data |
| Total Item Amount | Quantity x Unit Price, matching the line-item total |
| Discount Amount | Required if a discount was applied; cannot be omitted |
| Freight / Shipping Amount | Required if applicable; zero is acceptable if no freight was charged |
The 45-Day Clawback Rule
This catches organizations by surprise, so it deserves a clear explanation. Under CEDP, Visa's AI monitoring does not only evaluate transactions at authorization. Visa continues reviewing submitted data after settlement. If Visa determines, within 45 days of settlement, that data used to qualify a transaction for Product 3 rates was inaccurate or static, it can reclassify those transactions and issue a debit against your settlement account for the difference.
What that means in practice: even if your transactions are currently clearing at Product 3 rates, you are not protected if the data behind those rates is low quality. A month of incorrectly qualified transactions can become a surprise charge two billing cycles later.
Clawback risk is highest when billing systems auto-populate static or template-style data across large volumes. Which is exactly how most government billing, property management, insurance, and nonprofit payment systems operate. Have your processor audit a sample of actual submitted data fields, not just confirm that fields are present.
Five Steps to Get This Right
- 1Pull your commercial card volume
Ask your processor for a statement breakdown showing transaction count and volume by card type. Specifically separate business, corporate, purchasing, and government cards from consumer cards. This tells you your actual CEDP exposure. If your processor cannot provide this breakdown, that is a red flag.
- 2Confirm Product 3 field submission with actual data, not a yes or no
Ask your processor to pull a sample of actual transaction data submitted on recent commercial card transactions and show you the specific Product 3 fields as submitted. Confirm they contain real, transaction-specific data, not placeholders. Ask whether your CEDP submissions have Verified or Non-Verified status.
- 3Audit the integration between your billing software and your gateway
Line-item data originates in your billing system, not in your payment processor. If your invoicing, property management, policy administration, or accounting software is not passing item description, quantity, unit price, and commodity code to your gateway, the gateway cannot forward it to Visa. This is a software configuration issue that needs both your software vendor and your processor involved.
- 4Establish a policy for tax-exempt transactions
If a significant share of your transactions are legitimately tax-exempt, common in government and nonprofit contexts, you need a defined approach for how those are handled under CEDP. Zero tax submitted without correct exempt indicators reads as a data quality failure. Ask your processor how they document and handle this scenario specifically.
- 5Confirm Mastercard Level 2 and Level 3 separately
CEDP compliance and Mastercard enhanced data compliance are separate technical implementations. Ask specifically about Mastercard Data Rate II and Data Rate III submission, and the October 2025 unit-of-measure requirement. Your Mastercard commercial card volume is likely leaving the same savings gap if this has not been addressed independently of CEDP.
Frequently Asked Questions
My organization mostly processes consumer cards. Do we need to worry about CEDP?
It depends on your card mix, and organizations are often surprised when they pull a card-type report from their processor. Corporate cards and purchasing cards are issued to individuals who use them for organizational expenses. An employee paying a permit fee for their employer, a property manager paying HOA dues for a corporate owner, a nonprofit sponsor charging a sponsorship fee on a company card. These look like individual transactions but they are commercial card transactions subject to CEDP. Pull the breakdown before assuming your exposure is low.
What is the actual difference between the old Level 3 and Visa's Product 3 under CEDP?
Level 3 required submitting specific line-item fields, but enforcement of data quality was minimal. Processors could pass static or low-quality data and still qualify for lower rates. Product 3 under CEDP requires the same fields but adds Visa's AI-based data quality validation. Data is evaluated for accuracy, not just presence, before the reduced rate is applied. Merchants with poor-quality data receive Non-Verified status and do not qualify for Product 3 rates. Visa also now charges a 5-basis-point CEDP participation fee on all qualifying program transactions, which did not exist under the old Level 3 structure.
We process government payments under MCC 9311. Are we eligible for Product 3?
Yes, MCC 9311 is eligible for CEDP and Product 3 rates on commercial card types including corporate, purchasing, and business cards. The challenge is that government payment transactions are often single-line, one payment for a specific tax bill or fee. You still need to populate all Product 3 fields correctly for that single line. Item description should reflect the actual payment type, for example "Property Tax, Parcel 12-345-678, 2026 Q1," not a generic agency name. IntelliPay can help confirm how your MCC 9311 transactions are being structured and submitted.
Can Visa really claw back interchange savings after we have already settled?
Yes. Under CEDP, Visa reserves the right to reclassify transactions and debit your settlement account for the interchange difference if it determines, within 45 days of settlement, that submitted data did not meet quality standards. This is an active enforcement mechanism. It is particularly relevant for organizations whose billing systems auto-populate static or template-style data across large volumes. The way to avoid it is ensuring submitted data is genuinely transaction-specific and accurate, not just technically present in the right fields.
Has Mastercard announced any changes to match Visa's CEDP?
As of June 2026, Mastercard has made no announced changes to align with Visa's CEDP framework. Mastercard's Level 2 and Level 3 (Data Rate II and Data Rate III) programs remain active under their own specifications. Mastercard did tighten its unit-of-measure field requirement in October 2025, but this was a refinement to its existing program, not a structural overhaul comparable to CEDP. Monitor Mastercard's April and October interchange update announcements for any future changes.
Our nonprofit is tax-exempt. Does that disqualify us from Product 3 rates?
No. Tax-exempt status does not disqualify you from Product 3 rates. But transactions with zero tax must be formatted correctly in the data submission. Leaving the tax field null or blank is not the same as properly populating an exempt indicator. Visa's data quality checks can flag zero-tax transactions as suspicious if the surrounding data context does not support the exemption. Ask your processor how they handle tax-exempt transactions specifically under CEDP. IntelliPay has developed protocols for nonprofit and government exempt-transaction handling under the new program.
We use a third-party property management platform connected to our processor via API. Who is responsible for Product 3 compliance?
Both parties share responsibility, but the data originates with your property management software. Your processor cannot submit Product 3 fields it has not received. If your software is only sending a transaction total and card credentials, without item description, quantity, unit price, and other Product 3 fields, your gateway cannot generate compliant CEDP submissions regardless of its own capabilities. You need your software vendor to confirm their API passes all required Product 3 fields. Your processor then confirms they are forwarding those fields correctly to Visa. IntelliPay can help identify where the breakdown is occurring.
Not Sure If Your Commercial Transactions Are Qualifying?
IntelliPay audits your processing statement, identifies your commercial card volume, and shows you exactly what Product 3 and Mastercard enhanced data savings you are or are not capturing. No obligation.
Talk to a Consultantintellipay.com · 855-872-6632 · sales@intelliPay.com
PCI DSS Level 1 Certified · Processing since 2004
Sources and References
- Visa. Commercial Enhanced Data Program (CEDP) Overview and Technical Specifications. Visa Merchant Resource Library. usa.visa.com/support/merchant/library.html
- Visa. Interchange Reimbursement Fees, U.S. Domestic Interchange April 2026. usa.visa.com, Merchant Resources
- Mastercard. U.S. Interchange Rate Programs. Mastercard Merchant Resource Center. mastercard.us
- NMI. Everything You Need to Know About Visa CEDP (updated February 2026). nmi.com
- Wind River Payments. Big Changes to Visa's Level 2 and Level 3 Incentive Program (October 2025). windriverpayments.com
- IntelliPay. Visa CEDP & Product 3 Explained: The Complete Merchant Guide (2026). intellipay.com/visa-cedp-product-3-explained/
- IntelliPay. Visa CEDP & Service Fees: MCC 4900 Utility Guide (updated April 2026). intellipay.com/visa-cedp-utilities-mcc-4900/
