Business-to-business (B2B) sales often carry hidden payment processing costs. Small manufacturers, distributors, professional firms, and even SaaS companies frequently pay high interchange fees simply by submitting minimal transaction data. Credit card networks, however, offer Level 2 and Level 3 processing options that can drastically lower costs.
By gaining an understanding of and utilizing credit card processing levels, B2B merchants in the U.S. can save hundreds or thousands of dollars per year. This guide explains how Level 2 and Level 3 processing work, what additional data is required, and how to qualify and implement them to enhance your margins.
All credit card transactions are categorized into three data levels. Level 1 is the standard, bare-bones transaction data (typical for consumer sales). Level 2 and Level 3 progressively add more detail. Each step up requires submitting additional information, but rewards the merchant with lower interchange rates.
To put in perspective, basic retail sales use Level 1. B2B and government purchases, which are usually larger and more complex, can qualify for Level 2 or Level 3 by providing extra data. The more detail provided, the lower the merchant’s rate. In other words, Level 1 carries the highest rates, Level 2 moderate rates, and Level 3 the lowest.
Credit card processing levels differ by the amount of transaction data passed. Level 1 is minimal, Level 2 adds business-specific fields (such as tax and PO), and Level 3 adds full line-item detail. Each level lowers interchange fees.
Level 1 is the default for most transactions. It requires only the essentials: card data (number, expiration, and CVV), the total amount, date, merchant name, and category code, as well as sometimes basic billing information.
No extra fields are needed. This simplicity makes authorization fast, but issuers assume more risk, so Level 1 rates are the highest of all tiers. Consumer credit cards and typical in-person sales fall under Level 1.
Level 2 targets business and government transactions. It includes all Level 1 data, plus additional fields that provide more detailed descriptions of the purchase. Required Level 2 fields typically include:
Depending on the card network, Level 2 may also utilize optional fields, such as line-item counts or customer codes. For example, Visa’s Level 2 processing expects a separate sales tax line and may require the seller’s Tax ID.
Each network (Visa, Mastercard, Amex) has its list, but generally, you must at least send the tax details and a customer reference. Providing this data qualifies the transaction for lower rates than Level 1. American Express supports Level 2 data (but not Level 3).
Level 3 is the most detailed tier and is aimed at the largest B2B or B2G transactions. It includes everything from Levels 1 and 2, plus a detailed itemization of the sale. In practice, this means submitting a breakdown of each product or service purchased. Required Level 3 fields include:
In other words, Level 3 turns your payment message into an invoice. It answers “what exactly did you buy?” down to line-item detail. By providing the issuer with maximum transparency, Level 3 transactions receive the lowest interchange rates.
For example, a company that buys office equipment can list each item’s code, quantity, and unit cost. Government contracts often require Level 3 data; for commercial customers, offering Level 3 can provide a competitive edge through cost savings.
To clarify, here’s a breakdown of typical data fields needed for each level (beyond the basic card and amount):
Cardholder name, card number, expiration, transaction amount, date, merchant name/DBA, and merchant category code.
Apart from all the fields of Level 1 and Level 2, here are the additions:
For example, PayPal’s developer documentation lists Level 2 fields (card, address, invoice, customer code, and tax) and Level 3 fields (unit price, quantity, commodity code, freight, duty, etc.). Essentially, Level 3 must include all the invoice details the issuer would need to reconcile the purchase.
Collecting and passing this extra data may seem complex, but many billing or payment systems can capture it if your sales process already handles invoicing. The key is to ensure your payment gateway or processor is set up to transmit these fields in the authorization or settlement request. Without the complete L2/L3 data, transactions will default to Level 1 rates.
Why go to the trouble of Level 2 or 3? The payoff comes in the form of interchange fee savings. Card networks reward lower fraud risk and better transparency by lowering the fee rates. In practical terms:
Across many transactions, this adds up. For a small business processing $100,000/month in B2B card sales, shaving just 0.5–1.0% means saving $500–$1,000 per month (or $6,000–$12,000 per year). Level 3 interchange reductions can be roughly double those at Level 2.
Passing Level 2 data can save about $0.50–$0.75 on a $100 transaction, and adding Level 3 detail can save up to about $0.80. In competitive B2B markets, keeping this extra 1% means either boosting profit margins or having the flexibility to lower prices. It’s often said, “interchange is 80–90% of processing fees”.
So any percentage drop in interchange yields nearly proportional savings overall. Because B2B purchases are typically larger, even small rate discounts yield significant dollar savings. Thus, the “hidden” savings in Level 2/3 processing can impact your bottom line. In practice, merchants report improved margins and increased pricing flexibility by reducing card costs this way.
Not every merchant or transaction automatically qualifies for Level 2 or Level 3 pricing. To capture the savings, you must meet specific criteria:
Only corporate, purchasing, or government cards are eligible for Level 2/3 benefits. Personal or consumer credit cards are always Level 1. Visa and Mastercard corporate credit (and in Mastercard’s case, commercial debit/prepaid) support Levels 2 and 3. (American Express offers a Level 2 program on corporate cards but has no Level 3.)
Debit cards and consumer cards do not qualify beyond Level 1. Always check that your B2B customers are using eligible commercial credit cards.
U.S. merchants need a Federal Tax ID (EIN) on file to include tax information. You should also verify that your Merchant Category Code (MCC) allows for Level 2 or Level 3 rates. Some MCCs (like airlines, lodging, or utilities) may be excluded.
If using a gateway like Braintree or PayPal, ensure your account displays the correct business tax identifier and MCC to enable Level 2 or 3 processing.
Level 2 generally requires a taxable sale. If no sales tax is charged on the invoice, Level 2 rates won’t apply. In other words, there must be a nonzero tax line item to claim L2 savings. (If your business doesn’t charge sales tax on a particular transaction, you may still send “0” tax, but some networks might not grant the lower rate.)
Level 3 also requires a valid invoice context. One best practice is always to include a unique invoice or order number, allowing issuers to match the details.
Some networks impose compliance checks. For example, Visa’s Commercial Level II program may require annual PCI SAQs, an Attestation of Compliance, and quarterly network scans for larger merchants.
American Express Level 2 processing typically requires merchant pre-approval and submission of documentation. In practice, discuss Level 2/3 setup with your acquiring bank or ISO: they may need to opt you into the program.
Note: Transactions meeting all criteria will be routed at the special rates. If even one required field is missing or the card is ineligible, the transaction will default to a higher Level 1 rate, resulting in lost savings.
Successfully taking advantage of these savings requires your technology and processes to capture and send the extra data. Here are practical tips:
Not all payment gateways or merchant accounts automatically handle L2/3 fields. Start by checking with your processor or ISO. Many modern gateways (e.g., Stripe, PayPal/Braintree, Authorize.Net, etc.) support passing Level 2/3 data via their APIs or virtual terminals.
Some payment providers even advertise “Level 2/3 processing” or “L3 optimization” features. Ensure your account is enabled for these; you may need a special merchant profile or a settings change.
If you send invoices or use accounting software, use it. For example, QuickBooks Online or other billing platforms can integrate with payment processing so that when a customer pays an invoice by credit card, the invoice number, item details, tax, and shipping are automatically included.
This bridges the gap between your invoice system and the payment gateway. Many ERP or invoicing systems (SAP, Oracle, Zuora, etc.) have payment modules designed to transmit Level 3 data to approved gateways.
If processing cards manually (via phone or key entry), use a system that allows you to enter tax and invoice information. Many merchant portals have fields for Sales Tax, PO#, etc. Fill every relevant field on each transaction. Don’t just enter a lump sum – include shipping and tax as separate lines if possible.
Work with your developers or payment integrator to map your order system’s data fields to the gateway’s Level 2 and Level 3 parameters. For instance, ensure that the tax amount field in your checkout goes to the gateway’s “taxAmount” parameter. When using APIs, include the line item array that contains product code, quantity, and price.
Configure your accounting software to capture the additional details for reconciliation. Many integrated systems will automatically tag payments as Level 3 if they see full line items. This not only gets you the rate break, but also makes audits and reporting easier.
After implementation, review your merchant statements or use analytics tools to confirm Level 2/3 rates are being applied. Gateways often label the level of data used in each transaction. If some eligible sales are still processing at Level 1 rates, check which fields were omitted.
Over time, strive to establish a consistent process so that all qualifying B2B transactions include the additional data.
Integrating your systems (billing software, e-commerce platform, or POS) with your payment gateway automates the collection of Level 2 and Level 3 data. This not only reduces errors but also helps you avoid the need to enter line items manually. The goal is that whenever a corporate card is used, your system seamlessly passes the full invoice detail. Doing so not only saves money but also improves reporting, as you’ll have precise audit trails for large sales.
Lower interchange fees translate directly into higher profit margins. In tight-margin industries like manufacturing or wholesale, saving even 0.5–1% per transaction is significant. For example, a parts supplier running 10% net margins gains a whole percentage point back by implementing Level 3 – effectively boosting margin by 10%. You can reinvest this saved money in discounts, customer loyalty, or competitive bids. In negotiated contracts, knowing that your processing costs are lower also gives you the flexibility to absorb or pass on costs to buyers.
Additionally, submitting detailed invoices fosters trust with clients, as they see the exact breakdown you send to banks. This transparency can enhance client satisfaction and reduce the likelihood of disputes. And because the savings occur at the network level, you could even offer a small “card payment rebate” to customers (if permitted by law in your industry) and still come out ahead.
Over time, these savings compound, giving B2B sellers greater freedom in pricing and budgeting. Merchants who provide full details can save roughly 1% of each sale. That extra percentage can be the difference between a break-even bid and a profitable order.
Implementing Level 2 and Level 3 credit card processing can transform your B2B payment operations from a necessary cost center into a strategic tool for generating savings. By supplying enhanced transaction data, ranging from simple tax and invoice details at Level 2 to complete line-item breakdowns at Level 3, small businesses unlock interchange fee discounts of approximately 0.45–0.90% and around 1.0%, respectively.
Over time, these savings compound, enabling you to strengthen profit margins, offer more competitive pricing, and develop customer trust through transparent invoicing. To realize these benefits, ensure you accept eligible corporate or government cards, work with a processor or gateway that supports enhanced data fields, and integrate your invoicing or POS systems to capture and transmit the necessary information automatically. The upfront effort to gather and map Level 2/3 data pays off quickly in reduced processing costs and improved financial visibility.
Level 1 includes basic information, such as the card number and amount. Level 2 adds tax, invoice, and customer details. Level 3 includes complete item-level data, such as product names, prices, quantities, shipping costs, and discounts.
Level 2 needs tax amount, merchant tax ID, invoice or PO number, customer code, and ZIP code. Some card networks may also ask for shipping address information.
Along with Level 2 fields, Level 3 requires item descriptions, SKUs, unit prices, quantities, line totals, shipping/duty fees, unit of measure, discounts, and destination ZIP codes and country names.
You must accept business, government, or purchasing cards, not personal ones, and use a processor that supports Level 2 or Level 3. Also, meet transaction volume targets and connect your invoicing or ERP system to pass required data.
Level 2 may cut fees by 0.45–0.90%, and Level 3 by about 1%. On $100,000 in B2B payments, even a 0.5% reduction saves $6,000 annually, making a noticeable impact on profits.
