How interchange optimization actually works (and where SaaS leaves money on the table)

Interchange is the single largest line item in card processing cost. It is also the most opaque, the most negotiable in practice (despite the lore that it isn’t), and the most consistently mis-managed. On commercial card volume, the gap between “default behavior” and “optimized behavior” is regularly 30 to 80 basis points. On consumer volume, 10 to 35.

That gap is not a function of clever discounts. It is a function of paying attention to the data you already submit and the categories you already qualify for. Most SaaS platforms have never looked closely.

What interchange actually is

Interchange is a fee paid by the acquirer to the cardholder’s issuing bank on every transaction. The card networks (Visa, Mastercard, American Express, Discover) publish category-by-category interchange rates. There are hundreds of categories, and the one that applies to your transaction is determined by:

• The card type and issuing country.
• The merchant’s MCC (merchant category code).
• The data submitted with the transaction.
• The authentication and tokenization posture.
• The authorization-to-capture timing.
• The presence (or absence) of line-item detail.

You don’t negotiate interchange. You qualify into a category. The category determines the rate.

The misconception

Most platforms believe their processor handles this. The processor does, in a sense — but the processor’s incentive is to keep your business. They will not volunteer the categories you’re missing. They will not point out that your B2B transactions could be enriched to qualify for Level 2 or Level 3 interchange. They will not flag that your soft-descriptor strategy is causing avoidable downgrades.

The optimization is yours to find.

The practical levers

Level 2 / Level 3 enrichment for B2B

If you process commercial card volume — corporate cards, purchasing cards, government cards — you can submit additional data with each transaction. Tax amount, customer code, line-item detail, freight amount, ship-from / ship-to ZIP. The data is called Level 2 or Level 3 enrichment.

Each commercial card transaction that qualifies for Level 3 interchange instead of standard commercial pays roughly 50 to 100 basis points less. A SaaS platform with $20M in annual ARR billed to corporate cards is leaving $100,000 to $200,000 on the table by skipping enrichment.

Implementation is not free — it requires gateway support, integration work to capture the additional fields, and processor configuration. But it is bounded, and it pays for itself within the first quarter.

Network tokenization

Network tokens replace raw PAN data with a token issued by the card network. They reduce fraud, improve approval rates, and qualify some transaction types for lower interchange categories. Most processors have supported network tokens for years; most platforms have not turned them on.

Soft descriptors and MCC discipline

The merchant category code on each transaction is set when the merchant account is opened. Many platforms inherit a generic MCC and never revisit. The wrong MCC can cause systematic interchange downgrades — for example, if your platform is correctly classified as a SaaS provider rather than a generic professional service, certain card types qualify differently.

Soft descriptors (the merchant name shown on the cardholder’s statement) also matter. Recurring billing platforms with consistent, recognizable descriptors see fewer disputes, which feeds back into interchange-relevant fraud thresholds.

Authorization timing and refund handling

Auth-now-capture-later flows that exceed certain time thresholds can downgrade. Partial captures can downgrade. Refunds processed against the wrong original auth can downgrade. These are configuration choices in the gateway and processor, not negotiation items.

A simplified math

A B2B SaaS platform processes $25M annually on commercial cards. Default behavior puts most of that volume in standard commercial interchange, around 2.65%. With Level 2 / Level 3 enrichment, network tokenization, and disciplined MCC, the effective blended rate drops to roughly 2.10%.

That’s 55 basis points of recovery. On $25M, that’s $137,500 per year. Recurring. Compounding.

The implementation is meaningful — three to four weeks of engineering work, gateway configuration, processor coordination — but it is bounded. The recovered margin compounds for the life of the merchant account.

Where to start

If you have never had a structured interchange audit, the first step is a statement audit. Pull your last six months of processor settlement files and classify each transaction by interchange category. The gap between current state and target state will surface quickly.

The audit is the easy part. The discipline is everything.

---

This piece reflects engagements through Q1 2026. Specifics vary by processor, network, and geography. For a tailored view of your stack, schedule a strategy call.