Level 3 Credit Card Processing

Level 3 processing for B2B and B2G merchants.

When a buyer pays with a corporate, purchasing or government card and the merchant submits Level 3 line-item data, interchange drops materially. We populate the data — your merchant does not have to.

Level 3 Processing is used in B2B (Business-to-Business) and B2G (Business-to-Government) transactions to secure lower interchange rates and capture additional reporting detail. It requires more line-item information than a standard sale; missing even one required field disqualifies the transaction from Level 3 rates.

Many gateways are not qualified for Level 3 — and even gateways that are often punt the data-population problem on to the merchant's checkout. We do not.

---

The interchange data tiers, plainly explained

Every card transaction carries a payload of data when it goes to the network. The richer that payload, the lower the interchange category the card networks assess. The reasoning is simple: more data means less dispute risk for the card issuer, so the issuer charges less for processing it.

Level 1 is the floor. Level 2 is enough for the corporate buyer to expense the purchase. Level 3 is enough for the buyer's procurement system to reconcile the invoice line-by-line — which is the bar that earns the lowest interchange tier.

---

The savings math

The exact basis points depend on the card type, the transaction size, the merchant category, and the processor relationship — there is no single answer. But the pattern holds across every schedule we have seen:

• Non-qualified commercial-card transactions can sit several hundred basis points above the optimal rate.
• Level 2 qualifying transactions typically save 30 to 60 basis points over non-qualified for the same card.
• Level 3 qualifying transactions typically save another 50 to 100 basis points over Level 2, depending on transaction size.

Worked example. A wholesale distributor takes a $5,000 commercial-card payment.

• At a non-qualified rate of 3.10%, the merchant pays $155 in interchange.
• At Level 2 at 2.65%, the merchant pays $132.50.
• At Level 3 at 1.95%, the merchant pays $97.50.

That is a $57.50 swing per transaction on the same sale, on the same card, without any change to the merchant's pricing or behaviour. For a portfolio running $500,000 a month in commercial-card volume, that delta scales into the low five figures monthly — recovered by sending data that exists in the merchant's system already.

The catch — and the reason most merchants leave this money on the table — is that one missing field disqualifies the entire transaction. Manual data entry at the speed and accuracy required is unsustainable. The only way Level 3 works in production is if the gateway populates the data.

---

Which industries benefit most

Level 3 is not a universal win; it is a vertical win. The merchants who care most are the ones with concentrated commercial-card volume.

Wholesale and distribution

The largest single use case. Buyers are businesses with corporate cards; transaction sizes are often four or five figures; line-item data already lives in the wholesaler's order system. Plumbing the data through to the gateway turns existing data into existing savings.

B2B SaaS and software

Subscription invoices paid by corporate card are textbook Level 3. The line items are the SaaS line items; the merchant's billing system already produces them. Wiring them into the payment request earns interchange the merchant can pass through to pricing.

Professional services

Law firms, consultancies, accounting practices, engineering firms. Invoice-based billing, corporate-card payments, transaction sizes in the thousands. Level 3 is interchange optimisation that requires zero behaviour change from the practice.

Government contracting (B2G)

Government purchase cards (GPC / GSA SmartPay) qualify for Level 3 and government buyers expect Level 3 detail in their reconciliations. For a contractor with federal, state or municipal volume, Level 3 capability is often a prerequisite to keep the relationship, not just an optimisation.

Healthcare B2B

Practice-to-supplier transactions, equipment sales, lab and imaging services between providers. Commercial cards are common; Level 3 is rarely set up correctly. It is a quiet margin opportunity.

Manufacturing

Industrial supply, equipment, MRO. Mid-five-figure transactions on corporate cards; line items already in the ERP. Same story as wholesale.

---

Auto-population — where most gateways fail

The single most common mistake we see is a gateway that supports Level 3 on paper but requires the merchant to populate fifteen fields per sale. That setup works for a software demo and breaks the moment a clerk has to clear a hundred sales a day.

We default what is defaultable.

Merchant-side defaults. Postal code, ship-from postal code, commodity code, units of measure, tax identification — these rarely vary per sale and are set once per merchant at boarding. Auto-applied on every transaction.

Vertical-aware defaults. A wholesaler ships product; a professional-services firm ships nothing. The default field set adjusts so a services merchant is not asked for freight amounts they do not have.

Customer-aware defaults. When a sale comes from a saved customer in the Customer Vault, ship-to and customer codes flow from the saved record rather than being re-keyed.

Catalog-aware line items. If the merchant runs a product catalog in the gateway, item descriptions, product codes and unit prices flow from the catalog onto the transaction in one click.

The only fields the merchant actively enters are the ones that genuinely vary per sale. That is the difference between Level 3 being a feature people use and a feature that exists in the documentation.

---

Automatic BIN lookup

The first six to eight digits of every card number — the BIN — identify the issuer and the card product. Real-time BIN lookup tells us whether a card is a consumer credit card, a debit card, a corporate card, a purchasing card, a fleet card, or a government card before the auth request even fires.

We use that information two ways.

To decide whether Level 3 is worth attempting. Consumer cards do not qualify; sending Level 3 data on a consumer card adds payload for no benefit. Corporate, purchasing, fleet and government cards do qualify; on those we always attempt the Level 3 submission.

To avoid downgrades. A bad Level 3 submission — missing fields, malformed data — can downgrade the transaction below where it would have qualified at Level 1 alone. We validate the payload against the network's published requirements before submission, and if a required field cannot be populated, we drop to Level 2 cleanly rather than risk a downgrade.

The merchant does not remember which cards qualify. Neither does the customer. The gateway handles it.

---

Integration requirements

For partners boarding Level 3-eligible merchants and software vendors integrating against the Fluid Pay API, the practical requirements are short.

Required from the integrator: line items (description, quantity, unit price, product code where you have one), ship-to postal code (varies per sale), and tax amount on the transaction.

Provided by Fluid Pay: BIN-based qualification check, auto-population of merchant defaults, payload validation, fallback to Level 2 if a required field cannot be populated, network submission, response handling.

Provided by the merchant once at boarding: merchant postal code, ship-from postal code, commodity code, units of measure, tax identification, vertical preset.

This is materially less work than other gateways require. The intent is that an integrator with line-item data already in their checkout — which is most of them — gets Level 3 by populating two extra fields, not fifteen.

---

Cross-channel coverage

Level 3 is not a feature of one screen — it runs across every Fluid Pay channel a merchant might transact on.

• Virtual Terminal: Level 3 fields on the same form as the rest of the transaction, with the merchant's defaults pre-applied.
• Recurring Billing: subscription transactions on commercial cards carry Level 3 payloads from the saved plan and customer record.
• E-Invoicing: invoices generated in the gateway carry line items, and when the customer pays the invoice the line items flow into the auth request automatically.
• Hosted payment pages: the page captures Level 3 detail from the cart or invoice without requiring the merchant to re-implement the fields.
• API: every Level 3 field is exposed in the REST API for integrators who build their own checkout.

Same data, same auto-population, every channel.

---

Pair Level 3 with the rest of the B2B stack

Level 3 is the headline optimisation, but B2B portfolios benefit from a wider set of payment features that are often missing from gateways aimed at retail.

• The Customer Vault for repeat corporate buyers — line-item defaults plus payment-method tokenisation in one record.
• Recurring Billing for B2B subscription and retainer models.
• Automatic Account Updater so corporate card refreshes do not break recurring B2B revenue.
• Surcharging and Dual Pricing for portfolios that pass card-acceptance costs to commercial buyers — often more palatable in B2B than retail.

These four products together make up the bulk of what a B2B-heavy portfolio actually needs from a gateway. Level 3 is the entry point.

---

What to do next

If you are a partner with B2B-heavy merchants in your portfolio, talk to us about boarding them onto the Level 3 flow. Most of the savings is recoverable from existing transactions without rewriting any merchant integration.

If you are an integrator wiring Level 3 into your own product, the developer documentation covers the field-by-field API surface.