What Is Level 3 Credit Card Processing? When It Makes Sense for Your Business and When It Doesn’t

Many businesses first hear about Level 3 credit card processing after asking why they pay higher fees on commercial card transactions, or after a new customer requests support for purchasing cards. At that point, it’s common to assume Level 3 is a feature that any processor can simply switch on.

That’s rarely how it works.

During on-boarding, one of the first things we look at is how a business gets paid, not just how it accepts payments. Two merchants can process identical monthly card volume and only one turns out to be a real candidate for Level 3. The difference usually comes down to who their customers are, how invoices get created, and whether their payment systems can actually send the detailed transaction data the card networks require.

For most merchants, the real question isn’t “What is Level 3 processing?” It’s “Will it actually reduce my payment costs?” That depends on your customer base and your payment workflow, not on which processor you sign with.

Table of Contents: —

• Before Looking at Level 3, Start with One Question: —
• Why a Processor Asks About Your Invoicing Before Talking About Rates: —
• Level 3 Processing Isn't a Different Payment Method: —
• Where Businesses Usually Run Into Problems: —
• How We Decide Whether Level 3 Is Worth Implementing: —
• Which Businesses Usually Benefit from Level 3 Processing?
• Where the Required Information Actually Comes From: —
• Why Some Transactions Don't Qualify Even After Level 3 Is Enabled: —
• Signs Your Current Processor May Not Be Sending Level 3 Data: —
• Before You Change Processors: —
• Questions Your Payment Processor Will Probably Ask: —
• Common Mistakes That Increase Costs Instead of Reducing Them: —
• Who Should Be Involved: —
• Implementation Timeline Expectations: —
• A Merchant Readiness Checklist: —
• What a Processor Actually Looks for in Your Statement: —
• What to Prepare Before Contacting a Payment Processor: —
• Questions You Should Ask Before Choosing a Processor: —
• How This Connects to Your Merchant Account and Gateway Setup: —
• When Level 3 Processing May Not Be the Right Choice: —
• Frequently Asked Questions: —

Before Looking at Level 3, Start with One Question: —

Who is paying your business?

If most of your customers are individuals using personal credit cards, Level 3 won’t change how those transactions are priced. Personal cards don’t carry the interchange categories Level 3 data qualifies for, so there’s nothing for the enhanced fields to unlock.

If your customers are businesses, government agencies, universities, or hospitals that issue purchasing cards or commercial cards, the conversation changes.

We regularly see merchants spend weeks evaluating gateways or comparing processor rates before checking what share of their volume is even commercial-card eligible. A merchant with strong B2B revenue but a small share of commercial card usage is going to get a much smaller return than one where commercial cards make up most of the transaction mix. Pull a card-type breakdown from your last few statements before you do anything else. That breakdown tells you more about whether Level 3 is worth pursuing than any feature comparison between processors.

Before going further, determine:

1. What percentage of your revenue comes from B2B customers?
2. Do those customers regularly pay with purchasing cards or commercial credit cards?
3. Are you already collecting invoice-level information for every sale?

If the answer to most of these is no, Level 3 probably won’t provide enough value to justify the implementation work.

Why a Processor Asks About Your Invoicing Before Talking About Rates: —

Merchants are often caught off guard when a processor starts asking about invoicing and accounting software instead of card rates.

• How do you create invoices?

• Which accounting or ERP software do you use?

• Does every sale carry a purchase order number?

• Do you ship products, and how are freight charges recorded?

These aren’t underwriting formalities. They’re how we determine whether your business already produces the data Level 3 transactions need.

In practice, the data usually already exists somewhere in the business. The gap isn’t collecting it, it’s making sure it travels with the payment at the moment the transaction is processed. We’ve seen merchants switch processors expecting lower commercial card costs, only to find months later that their gateway was still transmitting only standard authorization data. Every field required for Level 3 was sitting in their invoicing system. None of it was reaching the card network. A new processor never had a chance to fix that, because the integration between the gateway and the accounting system was the actual bottleneck.

Level 3 Processing Isn’t a Different Payment Method: —

Level 3 is not another way to accept payments. Customers still pay with the same commercial or purchasing card they always have. What changes is how much transaction data travels with that payment.

A standard consumer purchase typically includes only the amount and basic authorization details. A qualifying Level 3 transaction also carries line-item detail, invoice and purchase order numbers, tax and freight amounts, and customer reference information (the full field-by-field breakdown, and where each one typically comes from, is in the table below).

This detail helps the buyer’s procurement team reconcile the purchase against their own records, and it allows the transaction to be evaluated under interchange categories that require that level of data. Submitting more information does not guarantee a lower rate. It only makes a transaction eligible to qualify, provided the card type, transaction details, and data format all line up. That’s the distinction most merchants miss when they assume “enabling Level 3” automatically lowers every commercial card fee.

Where Businesses Usually Run Into Problems: —

The issue almost never starts with the processor. It starts earlier, and by the time it surfaces, the merchant usually assumes the processor is at fault.

What the Business Believes	What Actually Happens
“Our invoices already contain all the required information.”	The payment gateway only transmits basic authorization data.
“Our processor supports Level 3.”	The current software integration doesn’t send the required fields.
“We upgraded our gateway.”	The ERP and gateway were never configured to exchange enhanced transaction data.
“Every commercial card should qualify.”	Many transactions don’t meet the card network’s qualification requirements.
“We’re paying high fees because of our processor.”	The issue is incomplete transaction data, not processor pricing.

We treat this table as a diagnostic starting point during a Level 3 review: if a merchant’s actual situation matches the right-hand column, the fix is almost always in the invoicing-to-gateway connection, not in the processor relationship. Before comparing rates or negotiating with a new provider, confirm that your invoicing system, ERP, gateway, and processor are actually configured to pass the same data to each other. Changing one piece without reviewing the rest tends to create a second problem instead of solving the first.

How We Decide Whether Level 3 Is Worth Implementing: —

We don’t start with rates. We start with how payment moves through the business.

Take two companies that both accept commercial cards. One supplies equipment to government agencies, so every order already comes with a purchase order, invoice number, product description, and shipping detail, because the customer requires all of that before they’ll approve payment. The other sells industrial tools through a standard online checkout, and while many of its customers are businesses too, very little invoice-level detail is attached to any given transaction.

Both accept commercial cards. Only one is naturally set up for Level 3, and the difference has nothing to do with volume. It’s the quality of the transaction data already built into how each business operates.

That’s why the intake conversation focuses on invoicing, accounting software, ERP, and order management before it ever gets to implementation.

One of the first documents we ask for is a recent merchant statement. Not to compare rates against another provider, but to see the actual mix of consumer, commercial, and purchasing card volume already coming through the account. That single document usually answers the implementation question before any technical discussion has even started.

Which Businesses Usually Benefit from Level 3 Processing?

The better fit depends more on your customers than your industry. Businesses that routinely receive a purchase order before payment tend to be better candidates than businesses processing immediate retail-style sales, for example:

• Wholesale distributors

• Manufacturers

• Government contractors

• Medical equipment suppliers

• Laboratory suppliers

• Educational vendors

• Commercial equipment providers

• Technology hardware suppliers

• Industrial product distributors

One pattern we see during on-boarding: businesses that receive a purchase order before payment tend to have a noticeably smoother Level 3 implementation than businesses that don’t. The procurement process already forces the invoice number, line-item detail, freight information, and customer reference to exist before anyone on either side has thought about how the payment will be processed. That means the implementation work turns into a data-mapping project, connecting records that already exist to the fields the transaction needs, rather than a data-collection project where someone has to start capturing new information from scratch.

Compare that to a restaurant, salon, grocery store, or local service business. Those transactions generally don’t carry purchasing information at all, and building a Level 3 workflow on top of them tends to add operational complexity for very little return.

A practical gut check: pull your last few months of transactions and count how many were paid with purchasing or commercial cards versus personal cards. If that number is small, you’re usually better off putting the effort into tightening your existing payment workflow than building out Level 3 data mapping.

Where the Required Information Actually Comes From: —

During implementation calls, merchants often assume someone on their accounting team is going to end up manually typing this information into every transaction. That’s rarely the goal, and for any business processing real commercial volume it isn’t realistic either. If your accounting software, ERP, inventory system, and gateway are properly connected, most of these fields should already move with the transaction automatically. When they don’t, the problem is almost always the integration between those systems, not the payment processor.

Level 3 Data	Usually Comes From
Invoice Number	Accounting or invoicing software
Purchase Order Number	Customer purchase order
Product Description	ERP or inventory system
Quantity	Inventory or order management system
Unit Price	Product catalog or ERP
Tax Amount	Accounting software or tax engine
Freight Charges	Shipping software
Customer Reference	Customer record or CRM
Ship-To Information	Order management system

The implementation work isn’t collecting this data, it’s confirming these systems actually pass it to your gateway, and that the gateway transmits it correctly to your processor. We’ve walked into implementations where every required field existed cleanly inside the ERP, but the payment integration had only ever been configured to send the transaction amount and authorization request. Payments still processed without errors, so nothing looked broken from the merchant’s side. From the card network’s side, the transaction looked identical to a standard commercial card payment, because the enhanced data never arrived.

Why Some Transactions Don’t Qualify Even After Level 3 Is Enabled: —

This is one of the most common questions we get after a merchant has already gone live: “We enabled Level 3. Why didn’t our fees change?” The answer is usually in the transaction detail, not the pricing schedule.

• The card wasn’t eligible. Level 3 applies to eligible purchasing cards, commercial cards, and government-issued cards. A standard consumer credit card won’t qualify for enhanced categories no matter how much data you attach to it.

• A required field was missing. One missing field, a purchase order reference or a tax line, is enough to keep an otherwise complete transaction out of the intended interchange category. The transaction still gets approved. It just doesn’t qualify at the rate the merchant expected.

• The gateway isn’t actually sending the enhanced data. This is the most common gap we see. A gateway can advertise Level 3 support in general and still not transmit the required fields for a specific merchant’s integration. Before switching processors over pricing, confirm your current gateway is actually sending Level 3 fields today, not just that it’s technically capable of it.

• Systems aren’t connected properly. Moving to a new processor doesn’t automatically fix interchange qualification, because the processor can only work with the data your systems send it. If the ERP, invoicing platform, shopping cart, and gateway aren’t wired together correctly, a new processor relationship won’t change the outcome.

• Nobody tested the transactions first. Before moving all commercial card volume onto a new workflow, run a small batch of test transactions and review the settlement reports with your processor. This confirms the required fields are actually transmitting, transactions are qualifying as expected, and your accounting team is getting the reporting detail it needs. Catching a mapping error in a test batch is a five-minute fix. Catching it after three months of live volume means going back through every affected transaction.

Signs Your Current Processor May Not Be Sending Level 3 Data: —

This is the situation we get called in on most often: a merchant who was told Level 3 is “enabled” but has no way to confirm it’s actually working. A few signs it’s worth checking:

• Your processor confirms Level 3 is turned on, but can’t point to a single settled transaction that actually qualified at a Level 3 rate.

• Your settlement or batch reports don’t show the enhanced fields (invoice number, PO number, line-item detail) anywhere, even though your team is entering them somewhere upstream.

• Commercial card fees look identical to what they were before implementation, month over month.

• Your ERP or invoicing system clearly has the required data on file, but the payment reports coming back from the processor don’t reflect any of it.

Any one of these on its own is worth a call. If more than one is true, the enhanced data almost certainly isn’t reaching the card network, regardless of what the processor’s marketing page says the gateway supports.

Before You Change Processors: —

If your current gateway isn’t transmitting enhanced data, moving the merchant account to a new processor can produce the exact same result, because a new processor still only receives what your systems send it. Before signing anything, get specific about where in the chain the data is actually getting dropped: is it never leaving your ERP, is the gateway not passing it through, or is the processor receiving it and not applying it correctly? Each of those has a different fix, and only one of them is actually solved by switching providers.

Questions Your Payment Processor Will Probably Ask: —

Most of these have very little to do with accepting credit cards and everything to do with whether your existing workflow can support enhanced data. Each one is checking something specific:

• Which accounting or ERP software do you use? Determines where the line-item data (product detail, quantity, unit price) actually originates.

• How are invoices created? Shows whether an invoice number and structured line items exist before payment, or get created after the fact.

• Do customers issue purchase orders before payment? Indicates whether procurement data already exists upstream, which is usually the strongest signal for Level 3 fit.

• Which payment gateway processes your transactions? Determines whether the gateway is even capable of transmitting enhanced fields to the processor, separate from whether it’s configured to.

• Are freight charges recorded separately? A missing freight or tax line is one of the more common reasons an otherwise complete transaction fails to qualify.
• Does your inventory system store detailed line-item information? Confirms whether product description and quantity data exists in a structured, exportable form.

• Will payments run through an online checkout, virtual terminal, or integrated software? Determines whether operators are keying transactions manually, and if so, whether the virtual terminal in use can capture enhanced fields at the point of entry.

• Have you previously attempted Level 2 or Level 3 processing? Tells the processor whether they’re troubleshooting an existing broken integration or building one from zero.

Having these answers ready before the first call is the single biggest thing that shortens implementation. It’s also the fastest way for a processor to tell you honestly whether Level 3 is worth pursuing before you’ve invested time in it.

Common Mistakes That Increase Costs Instead of Reducing Them: —

Level 3 is often treated as a pricing decision. It’s really a process decision, and in most failed implementations, the technology worked fine but the business process around it didn’t.

A common pattern: a company accepts commercial card payments through its ERP, but the accounting team edits invoices after the payment has already been authorized. Those edits never make it into the data submitted to the card network, so the accounting record and the payment record drift apart. That mismatch doesn’t just cost interchange savings, it makes reconciliation harder every single month.

This is why implementation shouldn’t sit only with the finance team. Operations, accounting, IT, and whoever owns the payment systems all need to understand how transaction data moves from the original order to final settlement.

The mistakes we see most often:

1. Choosing a new processor before reviewing the current payment workflow
2. Assuming every commercial card automatically qualifies for Level 3
3. Skipping test transactions before processing live customer payments
4. Expecting accounting software and payment gateways to sync data on their own
5. Focusing only on processing costs instead of the operational lift required
6. Treating Level 3 as a processor feature instead of a business process
7. Waiting until after implementation to loop in the accounting team

That last one is more common than it should be. A lot of Level 3 projects stall or under-perform simply because accounting, operations, and IT were never in the same conversation before the first live transaction went through.

Who Should Be Involved: —

Level 3 implementation touches more of the business than most merchants expect going in. A short list of who typically needs a seat at the table, and why:

• Accounts receivable — owns invoice creation and is usually the source of the fields Level 3 needs.

• Operations — knows how orders actually move from purchase order to fulfillment to invoice in practice, not just on paper.

• IT or whoever manages the ERP — controls whether the ERP can export or transmit line-item data to the gateway at all.

• The gateway provider — confirms which fields their integration actually supports for your specific setup.

• The payment processor — verifies the data reaches the card network and settles under the right interchange category.

Skipping any one of these tends to be where implementations stall, since the fix usually sits with whichever team wasn’t in the room.

Implementation Timeline Expectations: —

Merchants often assume implementation is finished once the first transaction authorizes successfully. In practice, it moves through a few distinct stages, and skipping ahead is where most of the problems in this article start:

• Payment workflow review — mapping how invoicing, ERP, gateway, and processor currently connect.

• Software compatibility check — confirming the ERP and gateway can actually exchange the required fields.

• Gateway verification — confirming the gateway is configured to transmit enhanced data, not just capable of it in theory.

• Test transactions — running a small batch and reviewing settlement reports before going live.

• Live roll-out — moving real commercial card volume onto the new workflow.

• Settlement validation — confirming, after live transactions settle, that they actually qualified as expected.

That last stage is the one merchants skip most often, and it’s the only stage that actually confirms whether the whole project worked.

A Merchant Readiness Checklist: —

Question	Yes	No
Most of our customers are businesses or government organizations.	☐	☐
Commercial or purchasing cards are commonly used for payment.	☐	☐
Every order has an invoice number.	☐	☐
Customers often provide purchase order numbers.	☐	☐
Our ERP or accounting software stores line-item details.	☐	☐
Taxes and freight charges are recorded separately.	☐	☐
We know which payment gateway processes our transactions.	☐	☐
Our payment workflow is documented.	☐	☐

Mostly “No” answers mean your time is better spent tightening payment operations first. Mostly “Yes” answers mean it’s worth a compatibility conversation with your processor.

What a Processor Actually Looks for in Your Statement: —

When we review a merchant statement for Level 3 fit, rate isn’t the first thing we’re reading for. We’re looking at:

• The split between consumer, commercial, and purchasing card volume

• Card-present versus card-not-present mix, since that affects which interchange categories are even in play

• Which gateway is listed as processing the transactions

• How settlement timing lines up with when invoices are actually generated

That review usually tells us more about whether Level 3 is worth pursuing than a conversation about your invoicing process would on its own, because it shows what’s actually happening on every transaction rather than what should be happening in theory.

What to Prepare Before Contacting a Payment Processor: —

A processor can give you a faster, more accurate answer when you walk in with this ready:

• A recent processing statement (one of the first things most processors will ask to review)

• Your current payment processor

• The payment gateway you use

• Your accounting or ERP software

• Your monthly commercial card volume, if known

• A sample customer invoice

• A sample purchase order, if customers issue them

• A description of how payments are currently accepted (online checkout, integrated software, virtual terminal, or another method)

Gathering this before the first conversation is what separates a same-call compatibility answer from a multi-week back-and-forth.

Questions You Should Ask Before Choosing a Processor: —

Skip “Do you support Level 3 processing?” Every processor will say yes. Ask questions that reveal how the implementation actually works:

• Which gateways have been certified for Level 3 processing?

• Can you review whether our current payment workflow supports Level 3 qualification?

• Will our ERP or accounting software require additional integration?

• How do you confirm that enhanced transaction data is submitted successfully?

• Can you help test transactions before we begin processing live payments?

• What reporting will we receive after implementation?

• If we change gateways in the future, will we need to reconfigure Level 3 data mapping?

These answers tell you more about how implementation will actually go than any rate comparison will.

How This Connects to Your Merchant Account and Gateway Setup: —

Level 3 eligibility isn’t decided in isolation. It’s decided by three things working together: your merchant account setup, the payment gateway processing the transaction, and (for businesses invoicing customers rather than running a checkout page) whether a virtual terminal is involved in how those payments get keyed in.

If your merchant account was set up around retail or card-present transactions, the account itself may need to be reconfigured for card-not-present commercial and purchasing card volume before Level 3 data has anywhere to go. If invoices are paid by phone or manually keyed rather than through an online checkout, that’s a virtual terminal conversation, since not every virtual terminal is built to capture and transmit line-item detail. And if a business is weighing card acceptance against ACH for its B2B customers, that’s worth a separate conversation entirely: buyers with strong purchasing-card programs are Level 3 candidates, but buyers who’d rather push large invoices through ACH may be better served by ACH payment processing than by chasing card interchange savings at all.

When Level 3 Processing May Not Be the Right Choice: —

Not every payment improvement creates business value. If your customers mostly pay with personal credit cards, adding Level 3 creates operational work without reducing your overall cost of acceptance.

The same is true if your business doesn’t issue invoices, rarely sees purchase orders, or can’t reliably capture detailed transaction information at the point of sale. In those cases, reviewing processor pricing directly, tightening reconciliation, reducing failed payments, or upgrading your gateway is likely to deliver a better return than a Level 3 build-out.

The goal isn’t to qualify for Level 3. It’s to build a payment process that fits how your business actually operates.

Frequently Asked Questions: —