How Level 2 / Level 3 Processing Works
When a cardholder pays with a commercial card, the transaction carries a structured data payload from the merchant's system to the card network. Standard Level 1 transactions include only basic fields: card number, expiration date, billing zip code, and transaction amount. Level 2 and Level 3 processing extend this payload with additional structured fields that card networks use to qualify transactions for preferential interchange fee tiers—reducing the cost per transaction for merchants who submit the required data correctly.
Customer Initiates a Commercial Card Payment
The buyer uses a purchasing card, corporate card, or government payment card at checkout—online, in person, or via an invoice-based payment flow. The merchant's system must recognize the commercial card BIN to trigger enhanced data capture. Most modern gateways identify qualifying BINs automatically, but the downstream data enrichment still depends on merchant configuration.
Payment System Collects Enhanced Data Fields
The gateway or ERP integration pulls Level 2 fields—sales tax amount, customer code or purchase order number, and merchant tax ID—from the order record. For Level 3 qualification, the system additionally collects line-item detail for each product in the order: product codes, descriptions, quantities, unit prices, and unit of measure. This data must be structured and available at the moment of authorization, not after the fact.
Authorization Request Carries the Full Data Payload
The enhanced data fields are submitted alongside the authorization request over the card network rails. Visa uses its VPAS (Visa Purchasing and Accounts Payable Solution) field format; Mastercard uses its own commercial data field conventions. Both networks validate the payload structure and completeness at this stage. Field naming, character limits, and decimal precision differ between networks, requiring network-specific handling in the integration layer.
Card Network Qualifies the Transaction
The network evaluates whether the submitted data meets the criteria for Level 2 or Level 3 qualification. Transactions with complete and valid Level 3 data qualify for the lowest available interchange tier. Incomplete or invalid submissions fall back to Level 2 or Level 1 rates automatically—this is called a downgrade. The downgrade decision is made in real time and is reflected in the interchange rate applied at settlement.
Interchange Rate Is Applied at Settlement
At settlement, the interchange rate corresponding to the qualified data tier is applied to the transaction. The difference between the qualified rate and the non-qualified rate represents the savings passed on to the merchant, net of any enhanced data processing fees charged by the gateway or processor. These savings compound across every qualifying transaction in the settlement batch.
Why Level 2 / Level 3 Processing Matters
The financial impact of enhanced data submission is substantial and well-documented across the payments industry. For merchants with meaningful B2B card volume, the difference between submitting Level 1 versus Level 3 data on the same transactions can represent hundreds of thousands of dollars in annual processing cost. Combined with a deliberate interchange optimization strategy, Level 2/Level 3 processing is one of the highest-ROI levers available to commercial merchants—with no change to the buyer experience required.
Three statistics anchor the opportunity:
- Up to 100 basis points in interchange savings: Visa and Mastercard both publish rate tables showing Level 3 qualifying rates for purchasing and corporate cards that are 70–100 bps lower than standard commercial card non-qualified rates. On a $10 million B2B card portfolio, that difference is $70,000–$100,000 per year in reduced interchange alone.
- $27 trillion+ in global B2B payment volume: According to McKinsey's Global Payments Report, business-to-business transactions represent the largest segment of global payment flows. The share of that volume running on commercial cards eligible for Level 2 and Level 3 interchange programs is growing year over year as purchasing card adoption expands in enterprise procurement.
- 40–60% of B2B card transactions are downgraded: Data from payment processors and industry analysts indicates that a significant portion of commercial card transactions submitted by merchants fail to qualify for enhanced data rates due to missing fields, gateway misconfigurations, or insufficient merchant awareness—leaving substantial savings uncaptured across the portfolio.
The merchant discount rate a business pays is heavily influenced by interchange, which typically constitutes 70–90% of the total processing fee. Reducing interchange through Level 2/Level 3 data directly lowers the effective cost of card acceptance without requiring processor renegotiation or volume commitments.
Who Benefits Most
Merchants selling to government agencies, healthcare systems, manufacturers, and enterprise procurement teams see the largest impact. These buyers typically pay with purchasing cards specifically designed for enhanced data programs, and some—particularly federal agencies—require line-item detail for procurement compliance independently of interchange savings.
Level 2 / Level 3 Processing vs. Level 1 (Standard Processing)
Level 2 and Level 3 are not separate products—they are tiers of a single enhanced data framework layered on top of standard card processing. Understanding what changes at each tier clarifies what investment is required and what savings are achievable before committing to an integration project.
| Dimension | Level 1 (Standard) | Level 2 | Level 3 |
|---|---|---|---|
| Required data fields | Card number, amount, billing zip | + Tax amount, customer/PO code, merchant tax ID | + Line-item detail: product code, description, quantity, unit price, UOM per line |
| Eligible card types | All consumer and commercial cards | Corporate, purchasing, government cards | Corporate, purchasing, government cards |
| Typical Visa interchange (U.S. B2B) | ~2.65–2.70% | ~2.40–2.50% | ~1.90–2.20% |
| Integration complexity | None | Low–Medium (gateway configuration) | Medium–High (ERP or order system integration required) |
| Best fit | Consumer retail, low B2B card mix | Mid-market B2B with moderate commercial card volume | High-volume B2B, government contractors, distributors, SaaS billing |
| Downgrade risk | None | Low | Higher—more required fields, more potential failure points |
Interchange rates shown are approximate U.S. illustrative benchmarks; actual rates vary by card product, transaction type, and network pricing tables in effect.
Types of Level 2 / Level 3 Processing
The enhanced data framework spans multiple card networks and card product categories, each with distinct requirements. Understanding the variations is necessary for building a compliant and complete integration.
Visa Level 2 and Level 3: Visa's commercial card enhanced data program covers its full suite of business payment products, including Visa Purchasing Card, Visa Corporate, and Visa Business cards. Visa publishes specific field requirements and rate tables for both U.S. and international markets, with distinct qualification criteria for card-present and card-not-present environments. Visa's Level 3 format uses the VPAS field structure and requires commodity codes alongside unit-level pricing.
Mastercard Level 2 and Level 3: Mastercard's equivalent program applies to its Purchasing, Corporate, and World Elite Business card products. The required data fields are largely similar to Visa's but differ in field naming conventions, character limits, and validation rules—meaning gateway integrations must handle network-specific formatting logic separately rather than using a single unified payload.
Government Card Programs: U.S. government purchasing cards under the GSA SmartPay program and similar federal procurement instruments are a special category. Federal agencies frequently require line-item detail for procurement compliance and audit purposes independently of interchange incentives. For merchants with federal government customers, Level 3 data submission is often both a cost-reduction measure and a contractual buyer requirement.
ERP-Driven vs. Gateway-Driven Enrichment: Some payment platforms automatically enrich transactions with available Level 2 data—tax rate, merchant tax ID—at the gateway level without requiring changes to the merchant's checkout flow. True Level 3 qualification, however, requires line-item data that must flow from the merchant's order management or ERP system at the time of payment, making it an integration-layer concern rather than a gateway-configuration concern.
Best Practices
Implementing Level 2 and Level 3 processing correctly requires coordination between business operations, payment configuration, and software engineering. Requirements differ depending on whether you are approaching this as a merchant or building the capability into a payment platform.
For Merchants
Audit your B2B card volume first. Pull a report of card transactions segmented by BIN range or card product type to identify what share of your volume runs on purchasing cards, corporate cards, or government cards. This establishes the addressable opportunity and the expected savings before investing in integration work.
Confirm gateway support for Level 3 specifically. Not all payment gateways support Level 3 submission reliably. Verify that your gateway explicitly supports Level 3 data fields for both Visa and Mastercard, and ask for documentation of the required field format and any enhanced data processing fees. Some gateways support Level 2 only and will silently drop Level 3 fields.
Capture PO numbers and tax breakdowns at checkout. For B2B ecommerce or invoicing workflows, add a purchase order number field to the checkout or invoice form and ensure your tax calculation engine passes actual tax amounts at the line-item level. These two additions alone can unlock Level 2 qualification for the majority of commercial card transactions.
Monitor qualification rates monthly. Your processor or gateway should provide reporting showing what percentage of commercial card transactions qualified at each data level. Track this metric and investigate drops, which typically indicate a data pipeline issue rather than a volume change.
Map product codes across your catalog. Level 3 requires commodity codes—often UNSPSC or custom codes—per line item. Build a mapping at the product or category level before going live with Level 3, and include code validation in your order management system to prevent blank or placeholder values from triggering downgrades.
For Developers
Handle network-specific field formatting separately. Visa and Mastercard have different API field specifications for enhanced data. Confirm which network conventions your gateway expects, validate field lengths, decimal precision for unit prices, and the distinction between required and optional fields before going to production.
Validate tax amount logic before submission. A tax amount of zero on a taxable transaction is the single most common Level 2 downgrade trigger. Build validation rules that flag transactions where a non-zero tax rate is expected but the submitted tax amount is zero or null.
Serialize line-item loops correctly. Level 3 data includes a repeating structure for each line item in the order. Ensure your integration correctly handles multi-line orders, edge cases like discounts or shipping charges as separate line items, and any maximum line-item count enforced by the gateway or network.
Log the full payload per transaction. Store the exact Level 2 and Level 3 payload submitted with each transaction ID. When a downgrade occurs, this log is essential for identifying which field was missing or invalid without relying on incomplete processor dispute data.
Test with commercial card BINs in sandbox. Use test card numbers that simulate purchasing card BINs and submit transactions with both complete and incomplete Level 3 payloads to confirm that your qualification logic, downgrade handling, and reporting all function correctly before processing live volume.
Common Mistakes
Level 2 and Level 3 processing has a higher operational failure rate than standard card processing because there are more required fields, each one a potential failure point. These are the most frequently encountered errors in production environments.
Submitting zero or null for sales tax on taxable transactions. If your system does not pass a tax amount and the transaction is taxable, the card network rejects the Level 2 qualification and downgrades the interchange. This is the most common failure for merchants activating Level 2 for the first time, and it is often caused by a tax calculation engine that returns the tax amount too late in the checkout flow to be included in the payment authorization payload.
Omitting the customer code or purchase order number. Many merchants do not surface a PO number field in their B2B checkout or invoicing flow. Without a customer reference code, Level 2 qualification typically fails. Adding this field to the B2B checkout experience is a low-effort, high-ROI fix that often unlocks savings within days of deployment.
Using a gateway that does not fully support Level 3. Some gateways advertise "Level 2/Level 3 support" but only implement Level 2 reliably—Level 3 fields are either silently dropped or submitted in an incorrectly formatted structure. Always verify with a test transaction and check the settlement report for actual interchange qualification codes, not just the authorization response code.
Failing to map product or commodity codes. Level 3 requires structured product codes per line item. Merchants without a maintained product catalog often submit placeholder values or leave the field blank, which invalidates the Level 3 submission. Building a proper code mapping at the product or category level is a prerequisite, not an afterthought.
Not auditing interchange qualification rates after go-live. Many merchants configure enhanced data submission once and never audit the results. Software updates, gateway version changes, or new card products introduced by issuers can silently break data pipelines and cause downgrade rates to spike. A monthly review of commercial card interchange qualification by data tier is the minimum required to maintain savings over time.
Level 2 / Level 3 Processing and Tagada
Tagada operates as a payment orchestration layer, routing transactions across processors and gateways based on cost, performance, and compliance criteria. For merchants with B2B card volume, this creates a direct opportunity to improve Level 2 and Level 3 qualification rates systemically rather than through point-by-point gateway configuration.
Tagada and Enhanced Data Routing
Tagada can route commercial card transactions to the processor or gateway in your stack that offers the strongest Level 3 support and the lowest enhanced data fees. Rather than being locked to a single gateway's Level 3 capabilities, orchestration lets you direct purchasing card and government card transactions to the path most likely to qualify at the lowest interchange tier—while falling back automatically when a processor cannot accept or validate the full Level 3 payload.
By centralizing payment routing logic, Tagada also provides a single point for injecting enhanced data enrichment, ensuring that Level 2 fields like tax amounts and customer codes are appended consistently across all downstream processors without requiring each individual gateway integration to implement the enrichment logic independently. This is particularly valuable for merchants managing multiple processors across different geographies or business units, where inconsistent enhanced data handling across integrations would otherwise create unpredictable interchange qualification results.