Introduction
Level III processing on Clarity Payment Hub automatically enriches qualifying B2B and government P-card sales with the 20-plus Level 3 fields the networks require, including line detail, tax, freight, buyer code, destination ZIP, and unit of measure, pulled straight from the ERP invoice with no manual keying. The result is interchange cost reduction of roughly 0.3 to 1.0 percent on every qualifying corporate-card charge, recovered automatically rather than left on the table. The enrichment is invisible to the customer and to your staff, and every charge is reported so you can see exactly what Level 3 processing recovered.
Why Level 3 interchange savings exist at all
Interchange is the per-charge fee the card networks charge every merchant for every card payment. It is also the biggest single component of your merchant-statement cost, typically 80 to 90 percent of everything you pay on a card sale. Interchange rates are not one rate. Interchange rates run as hundreds of categories that shift based on card type, card-present versus card-not-present, and, critically for B2B and government, the quality of detail submitted with each charge.
These interchange rates reward enhanced detail, and Visa and Mastercard offer corporate-card programs (Corporate, Business, Purchasing, Fleet, Government, GSA) that carry reduced interchange on qualifying charges when the merchant submits enhanced transaction data, typically 20-plus fields covering line detail, unit of measure, product codes, tax breakdown, freight, destination ZIP, buyer code, and more. The networks want this data because corporate cards issuers and government purchasing-card programs need it for reporting, audit, and compliance. In exchange for the work of submitting it, they price your transaction at a lower tier.
The problem is that every merchant with a significant B2B or government P-card program is technically eligible for Level 3 pricing, but very few actually get it. The 20-plus fields are tedious to compile per charge, the gateway needs to support the full schema, and the data usually lives in an ERP that does not talk to the gateway. So most merchants accept Level 1 or Level 2 pricing on corporate cards and leave 0.3 to 1.0 percent on every charge on the table, year after year. That gap is the card processing cost most finance teams never see. Lower interchange fees mean lower processing fees overall, and the right credit card processing turns high interchange rates into lower fees on every corporate card. Credit card processing at the Level 3 tier is where the interchange fees fall, and the processing fees on your statement fall with them. Across every corporate card, Level 3 processing is the credit card processing tier, and credit card processing fees stay low because the Level 3 processing runs on every charge that keeps interchange fees and processing fees at the floor.
Level 1 vs Level 2 vs Level 3: what is in each, and what you pay
The three credit card processing levels correspond to progressively richer transaction data, and each card processing level changes the interchange rates you pay. Every card sale carries at least Level 1, the baseline. Level 2 is a modest step up, enough for business-purchasing reporting. Level 3 is the full enhanced-data envelope that unlocks the lowest corporate-card interchange and qualifies large-ticket purchases for additional rate-reduction programs.
Level 1 is the baseline: merchant account info, the tokenized card number, expiration date, authorization amount, currency, and transaction timestamp. Level 2 adds everything in Level 1 plus the tax amount, merchant tax ID, customer code or PO reference, invoice number, and tax-exempt status where applicable. Level 3 adds everything in Level 1 and Level 2 plus the full enhanced data: line detail up to the network maximum, item name, quantity, and unit of measure, unit cost, product code, and commodity code, line discount, line tax, and line total, freight, duty, discount, and destination ZIP, and order date and ship-from ZIP.
A Level 3 credit card transaction carries the Level III data the networks reward, and every Level 3 credit card submission includes the full Level 3 fields. The largest delta, and the one worth chasing, is Level 1 to Level 3 on corporate cards. For a merchant running substantial B2B or government card volume, this is ordinary-to-real money: on a $2,500 corporate-card invoice payment, the difference between Level 1 pricing at about 2.95 percent and qualifying Level 3 at about 1.95 percent is roughly $25 per charge. Across 4,000 qualifying charges a year, that is $100,000.
The 20-plus fields the networks require, and where Clarity gets each one
Level 3's field requirements differ slightly between Visa and Mastercard, but the core envelope is stable across card brands. Every field has a specific format, such as numeric, alphanumeric, ZIP length, or ISO country code, and a specific source. If any required field is missing, in the wrong format, or mismatched against a total, the charge downgrades to Level 2 or Level 1 and the rate gains evaporates.
Visa and Mastercard maintain the canonical field-list definitions, and exact required or optional status varies by card brand and by specific commercial program. Payment Hub maintains the current network specifications and submits the correct envelope for each card brand automatically.
Where Payment Hub cannot pull a field from the ERP because it is legitimately not captured in the source system, for example a missing ship-to ZIP on a counter walk-in, Payment Hub falls back to the best-available field or flags the charge for counter-staff review before authorization. Transactions with material data gaps submit at Level 2 with a reporting flag, so controllers see the downgrade rather than discovering it three months later in a rate review.
How Payment Hub enriches Level 3 automatically
Level 3 processing is the credit card processing that pulls the data and submits it. Eight capabilities run the Level 3 processing pipeline, the credit card processing steps that lower the interchange rates on corporate cards. Each one is work that most merchants do manually or skip entirely, and each one is required to actually be eligible for the lower interchange tier on a real-world corporate-card charge.
BIN lookup at authorization
Payment Hub identifies the card type at first authorization and determines Level 3 eligibility. consumer credit cards skip enrichment because there is no benefit. Visa and Mastercard Commercial, Corporate, Purchasing, Fleet, Government, and Business cards trigger enrichment, with no manual card-classification needed.
ERP invoice and line-item fetch
Clarity Connect pulls the underlying invoice or sales order from your ERP, including header fields (PO, order date, tax, freight), line detail (SKU, description, quantity, unit of measure, unit cost), and ship-to and ship-from ZIPs. It works with NetSuite, Acumatica, Dynamics 365 BC, F&O, and GP, Sage 100, 300, and Intacct, SAP, Epicor, Infor, SYSPRO, Workday, Oracle, and more.
Unit-of-measure normalization
the networks require unit-of-measure values from their standardized code list, such as EA, HR, LB, or GAL. Your ERP might store them as free text or a different code set. Clarity maps your ERP unit-of-measure catalog to the network's expected codes once at setup, so every line submits with a valid value automatically.
Commodity code mapping
Government card programs and some corporate cards require a UNSPSC or network-specific commodity code per line. Payment Hub maintains a rules engine that maps your ERP product categories to network commodity codes, configured once and applied to every charge without any per-order keying.
Header-to-line total reconciliation
Level 3 submission requires line totals to reconcile to header totals, where subtotal plus tax plus freight minus discount equals the header amount. Payment Hub runs this reconciliation before submission, and any mismatch triggers a data-quality flag before the charge submits, so staff can investigate rather than discover a silent downgrade later.
Per-gateway Level 3 envelope formatting
Each gateway (Fortis, PayTrace, Nuvei, Worldpay, PNC, Cybersource, Elavon, NMI, USAePay, Global Payments, Authorize.Net) has its own Level 3 API schema and field-packaging expectations. Payment Hub formats the correct envelope for your specific gateway without requiring gateway-specific configuration from your team.
Large-ticket program qualification
Visa Large Ticket (about $10,000 and up) and Mastercard Large Ticket (about $7,500 and up) are special Level 3-dependent programs with additional rate reductions on high-value purchasing transactions. Payment Hub submits qualifying charges with the full Level 3 envelope, and eligible transactions auto-qualify with no special handling.
recovery reporting and downgrade analytics
Every transaction is reported with its interchange category hit, the Level 3 fields submitted, and the recovery versus the Level 1 or Level 2 fallback. Controllers see where Level 3 worked, where data gaps caused a downgrade, and which upstream ERP fixes would recover more recovery, on an ongoing basis rather than just at go-live.
The Level 3 workflow: from card tap to interchange category
Here is what happens when a B2B customer pays a $12,400 invoice with a corporate P-card. The whole thing takes about two seconds end to end, and most of the enrichment work is invisible to everyone but the settlement report.
Customer initiates payment. The customer logs into the payment portal, or is at the counter, or is on a MOTO call, and selects invoice INV-48210 for $12,400 to pay. They enter their corporate purchasing card, a Visa Purchasing card issued by their bank.
Payment Hub does a BIN lookup. As the card is entered, Payment Hub identifies the BIN as Visa Purchasing, a commercial-card category that qualifies for Level 3 pricing, and flags enrichment on for this transaction. If the same customer had paid with a consumer Visa, Payment Hub would skip enrichment because it produces no rate benefit.
Clarity Connect fetches invoice and line data from the ERP. Clarity Connect to retrieve invoice INV-48210 from the ERP: header (PO number, order date, ship-from ZIP, destination ZIP, tax total, tax rate, freight, duty, currency), plus line detail (10 Widget Pro at $1,100 each, unit of measure EA, and 4 Installation service at $225 per hour, unit of measure HR). This takes about 200 milliseconds on a warm ERP connection.
Payment Hub normalizes unit of measure, maps commodity codes, and reconciles totals. Widget Pro's ERP unit of measure "Each" maps to network code EA, and Installation's "Hour" maps to HR. Commodity codes are pulled from the item-master mapping (UNSPSC 14-35-22-00 for the widget, 81-11-18-00 for the install service). The header total of $12,400 is verified against the line-item sum plus tax plus freight.
The Level 3 envelope is packaged for the gateway. Payment Hub formats the full Level 3 envelope in the exact schema the configured gateway expects, with header fields in the right order, line detail in the network's format, and field-level validation passed. The transaction is submitted for authorization with the card data and the Level 3 envelope attached.
The gateway authorizes and the card network categorizes. The gateway submits the authorization to Visa. Visa validates the Level III data envelope (all required fields present, formats valid, line totals reconcile), confirms the Visa Purchasing card's eligibility, and categorizes the charge at the lowest qualifying interchange tier, including large-ticket pricing since $12,400 exceeds the $10,000 Visa Large Ticket threshold.
The authorization is approved and payment flows back. The authorization response comes back approved at the lower interchange tier. Payment Hub returns a successful payment to the customer in under two seconds of total elapsed time. The customer has no idea that a Level 3 envelope with 20-plus fields was silently attached to their transaction.
The settlement report captures the recovery. Two days later, the charge settles on the merchant statement at the Level 3 large-ticket interchange tier of about 1.90 percent instead of the Level 1 commercial tier of about 2.95 percent. On a $12,400 charge, that is roughly $130 of direct interchange recovery versus the downgrade. Payment Hub's reconciliation report captures this delta alongside every other qualifying transaction, so the annual recovery total is visible in a dashboard rather than buried in statement line items.
Sample recovery calculation: distributor, $5M B2B card volume
Here is a realistic worked example using conservative interchange assumptions for a mid-sized industrial distributor accepting mixed commercial and consumer card volume. Your numbers will vary with your specific gateway pricing, your card mix, and your transaction sizes, but the methodology is the same across the industry.
The scenario assumes roughly half of B2B card volume falls on corporate cards, which is typical for distributors serving a mix of contractor, corporate, and municipal customers. A higher corporate-card mix, for government-heavy or fleet-heavy businesses, scales the recovery proportionally. Large-ticket transactions (over $7,500 on Mastercard, over $10,000 on Visa) typically yield higher per-charge recovery, and a single $28,000 transaction can recover $400 or more on its own.
For a larger B2G-focused business, such as a building-products distributor, an IT reseller to government, or a municipal-contract utility vendor, annual recovery can easily reach $60,000 to $200,000. For smaller businesses with $500,000 to $1,000,000 in B2B card volume, recovery is typically $1,500 to $7,500 a year. Payment Hub's recovery-per-charge reporting makes the actual delta visible on your own statement, so you can see what Level 3 processing recovered in any given month.
Industries where Level 3 optimization pays the most
Level 3 savings scale with the share of commercial and government card volume in your mix. Industries that sell to businesses, governments, and institutions tend to see the biggest gains. Industries that sell primarily to consumers see less, because consumer credit cards do not qualify for Level 3 pricing.
Wholesale and Industrial Distribution
Selling to contractors, plants, government fleets, and B2B accounts that pay on corporate, purchasing, and fleet cards, with typically a 50 to 65 percent corporate-card mix. Level 3 enrichment routinely recovers 0.6 to 0.9 percent across qualifying volume in PHCP distribution, electrical supply, industrial MRO, fleet service parts and maintenance, and contractor-facing building products.
Government and Public-Sector Suppliers
Selling to federal, state, municipal, and special-district agencies under government contracts that pay on GSA SmartPay, P-cards, and government corporate cards, across B2B and B2G, often an 80 percent or higher corporate-card mix, where large-ticket program eligibility is common. This covers GSA-scheduled vendors, state-contract suppliers, municipal utility and public-works vendors, and defense and federal IT resellers.
Manufacturing and Industrial
B2B manufacturing with corporate-card buyers paying for parts, supplies, and finished goods. Line-item data is usually already well-structured in the ERP, which makes Level 3 processing simple, and large-ticket pricing applies on bigger orders for industrial components, instruments, and tools, capital goods and equipment parts, and raw materials and commodity resale.
Professional Services B2B
Consulting firms, legal, engineering, and IT services billing corporate clients by card. Invoices tend to carry clean line-item detail (project, hours, rate, task) that maps naturally to the Level 3 line structure, and high-dollar engagements often hit large-ticket tiers, across IT services and managed hosting, engineering and architecture firms, and consulting, legal, and financial-advisory work.
Higher Education and Institutional
Universities, community colleges, and research institutions paying vendors with institutional procurement cards. This is a strong fit when the vendor is selling to the institution and less relevant for consumer-facing revenue such as student tuition and bookstore retail. It covers research-lab suppliers, campus-facilities and equipment vendors, and academic software and subscription resellers.
Healthcare (B2B Supply, Not Patient)
A strong fit on the B2B side of healthcare, such as a medical supply, device, or pharma reseller billing institutional buyers by purchasing card. It is a poor fit on patient-side card payments, since consumer HSA, FSA, and credit cards do not qualify. Clinics doing patient AR see minimal benefit, while B2B medical distributors, including medical-device suppliers to hospitals, pharmaceutical B2B distribution, and DME and surgical supply to clinics, see substantial benefit.
Consumer Retail and eCommerce
Direct-to-consumer eCommerce and retail see minimal Level 3 benefit because consumer cards do not qualify. Payment Hub still enables Level 3 on the subset of corporate cards that appear, such as small-business buyers and corporate-card users, but the impact is typically small. This is not a primary Level 3 use case, covering consumer-brand eCommerce, retail and DTC shipping, and subscription services to consumers.
Nonprofit and Foundation Donors
Foundations, government grant-makers, and corporate-giving programs issuing P-cards to nonprofit recipients for qualified program expenses. This is not huge volume at most nonprofits, but it is fully Level 3-eligible when it occurs, and is often worth the enrichment on single large grants, across corporate-giving platforms, foundation program-payment cards, and federal and state grant disbursements.
Frequently Asked Questions
What exactly is Level 3 processing, and how is it different from Level 1 and Level 2?
Level 1 is a standard retail-card sale with just the card data, authorization amount, and merchant info, the baseline every card sale has. Level 2 adds five or so fields commonly needed for business purchasing (sales tax amount, tax ID, customer code, invoice number). Level 3 adds fifteen or more, including itemized line detail (item description, quantity, unit of measure, unit cost, product code, commodity code, discount, line total), freight, duty, destination ZIP, order date, and ship-from ZIP. The card networks (Visa and Mastercard) charge lower interchange rates on qualifying commercial cards when all Level 3 fields are submitted correctly, because the enhanced data reduces fraud and supports B2B and B2G reporting. Typical savings are 0.3 to 1.0 percent per charge, sometimes higher on large-ticket purchases. Most merchants leave the savings on the table because the 20-plus fields are tedious to map manually and most gateways do not auto-pull them from the ERP.
Which card types qualify for Level 3 rates?
Level 3-eligible cards are the commercial BINs issued by Visa and Mastercard: Visa Corporate, Visa Business, Visa Purchasing, Visa Fleet, Visa GSA (government), and the equivalents on Mastercard (Corporate, Purchasing, Fleet, Business, Government). Consumer cards do not qualify, and they are priced at consumer tiers regardless of submitted data. American Express has a parallel program (AmEx Level 3 and OptBlue Level 2/III enhanced data) with similar line-item requirements and similar savings, and Discover also offers enhanced-data tiers. Payment Hub detects the BIN at authorization and only submits Level 3 fields to networks and cards where they produce a rate benefit, with no wasted overhead on consumer cards and no wasted envelope data when the gateway and card brand will not use it.
How much do we actually save with Level 3, in dollars?
Your credit card processing savings depend on three things: the mix of commercial versus consumer cards in your B2B card volume, the charge sizes, and the interchange category each charge currently falls under. As a rough guide, merchants who run B2B and B2G card volume see 0.3 to 1.0 percent savings per qualifying transaction when Level 3 submission is enabled correctly. A distributor running $5,000,000 a year in B2B card volume with roughly half of that on commercial cards typically recovers $15,000 to $50,000 annually in interchange. A larger B2G program running $20,000,000 or more can recover $60,000 to $200,000. Large-ticket purchasing transactions (over $7,500 on Mastercard, over $10,000 on Visa) can qualify for additional special-program rates if all Level 3 data is present, and these transactions often see the biggest single-charge savings. Payment Hub reports per-charge savings in the settlement reconciliation so you can see the actual delta on your own statement.
What fields does Level 3 require, and where does Payment Hub get them?
The Visa Level 3 program requires roughly 20-plus fields depending on the card brand and category. The fields split into header-level (invoice number, customer code, order date, ship-from ZIP, destination ZIP, duty amount, freight amount, discount amount, sales tax rate, sales tax amount, tax ID, currency) and line-item-level (item description, item quantity, unit of measure, unit cost, product code, commodity code, line discount, line tax, line total, per line item up to the network's maximum lines per charge). Payment Hub pulls these fields directly from the ERP invoice or sales order at the moment of payment, through Clarity Connect's integration with your ERP (NetSuite, Acumatica, Dynamics 365, Sage, SAP, Epicor, Infor, and others). The customer does not key anything extra, the counter staff does not key anything extra, and the AR user does not key anything extra. The enrichment is invisible and automatic.
Do we need to change gateways or merchant accounts to get Level 3 rates?
No. Payment Hub works with your existing gateway (Authorize.Net, Fortis, Nuvei, PayTrace, Worldpay, PNC, Cybersource, Elavon, NMI, USAePay, Global Payments, Adyen, Braintree, Stripe, Square, and more) and your existing merchant account and negotiated rates. Level 3 capability depends on the gateway, and the major B2B-focused gateways (Fortis, PayTrace, Nuvei, Worldpay, PNC, Cybersource, Elavon, NMI, USAePay, Global Payments, Authorize.Net) all support the full field set. Payment Hub's role is to enrich the charge with the right fields from the ERP and submit them in the format the gateway expects. If your current gateway does not support Level 3 submission and you run heavy B2B and B2G card volume, Clarity can help you migrate to one that does without replacing your merchant relationship, but migration is not required if your current gateway is Level 3-capable.
What happens to transactions where Level 3 data is missing or invalid?
The transaction still authorizes, because missing or invalid Level 3 data does not block the charge; the card brand just downgrades the interchange category to Level 2 or Level 1 for that specific transaction. Payment Hub detects data gaps before submission (missing ship-to ZIP, missing line items, line-total mismatch, invalid unit-of-measure code) and either fills them from the ERP record, flags them for counter-staff or AR review, or submits the charge at the best available tier with a reporting flag so controllers can see which transactions downgraded and why. The Payment Hub savings report surfaces downgrades so you can remediate the ERP data-quality issue that caused the gap, rather than silently losing the rate benefit indefinitely. Over time, the downgrade rate should approach zero as your ERP data quality improves under the visibility the report creates.
Does Payment Hub handle large-ticket programs for transactions over $7,500 or $10,000?
Yes. Visa Large Ticket (transactions typically $10,000 and up) and Mastercard Large Ticket ($7,500 and up) are special Level 3-dependent interchange programs the networks offer for high-value B2B transactions where all Level 3 data is present. Payment Hub submits transactions with full enrichment at every charge size, so large-ticket purchases automatically qualify when the underlying invoice carries the required data. For a municipal utility processing a $28,000 purchase-card sale, or a distributor processing a $14,000 order on a corporate card, the difference between Level 1 rates and qualifying large-ticket rates can be $400 or more on a single transaction. You do not need any special configuration to opt into large-ticket qualification; if the charge's data meets the criteria, it qualifies automatically.
Can we still use Level 3 optimization on consolidated or multi-invoice payments?
Yes, though the submission format differs. For consolidated payments where a customer pays one total across multiple invoices, Payment Hub can submit the charge with summary-level Level 3 data built from the consolidated invoice set, with combined line items rolled into the card network's allowed lines per charge, or as separate individual Level 3 transactions per invoice if the gateway and card network allow. The choice depends on transaction size: consolidated single submission is simpler operationally, but splitting can sometimes yield better per-line interchange when individual invoices fall into different interchange categories. Payment Hub uses whichever strategy produces the lowest total interchange for the customer's payment.