“Network Update” Fee Increase? How to Tell Real Card-Network Changes From Processor Markup

Why fee notices cluster around network update cycles

Card networks publish rule and fee changes on a recurring schedule, commonly in spring and fall. Many of those changes are targeted at specific fees, card categories, or transaction types rather than broad increases. Around each cycle, processors often send merchants notices that cite “card brand updates” or “network changes.”

A single notice can bundle two very different things: a real network change that passes through at cost, and a change to the processor’s own pricing. Both show up on the same statement, often in the same month. For a 20+ unit group with many merchant IDs (MIDs), the combined effect can be hard to see in a blended fleet rate.

This page covers one trigger event: a fee notice or an unexplained month-over-month jump. For the full portfolio method, use the multi-unit merchant statement audit checklist. For the program view, see the restaurant payment processing optimization hub.

Pass-through vs processor-set: who controls each line

Interchange: set by the card networks and paid to card issuers. It passes through at cost; what you pay within the schedule depends on how each transaction qualifies.

Assessments and network fees: set by the networks and passed through. These are the lines a genuine “network update” most often touches.

Markup, discount rate, and per-item fees: set by the processor under your contract. Changes here are a processor pricing decision.

Monthly, statement, PCI, gateway, and minimum fees: set by the processor (or a gateway provider) under your contract.

The merchant services fees guide explains these pass-through vs processor fee layers line by line.

The month-over-month check, per MID

Same-period effective rate. For each MID, divide total fees by card volume for the last full month before the change and the first full month after it. Sum fees and volume; do not average percentages. Then roll MIDs up to the location. The effective rate by MID method is in the statement audit checklist.

New or renamed line items. List every line that is new, renamed, or larger than before. For each one, record whether it is a network fee passed through or a fee the processor sets.

Markup and per-item changes. On interchange-plus pricing, markup and per-item fees appear on their own lines, so a change is visible directly. On tiered or flat pricing, request a breakdown by fee layer before drawing a conclusion.

Card-mix and channel shifts. Rule these out before blaming anyone. Seasonality, a rise in online or app ordering, or more rewards and commercial cards can move the effective rate with no price change at all. Qualification and downgrade causes are covered in the interchange optimization guide.

The notice itself. Check whether the notice names a specific network change and an effective date, or only refers to updates in general.

What to ask your processor in writing

Keep the requests neutral and documented. The goal is to separate the two kinds of change, not to start a dispute.

1. Which specific network change does the notice refer to, and what is its effective date?

2. Please show how that change passes through at cost on our statements, by MID.

3. Did the markup, discount rate, or any per-item, monthly, or ancillary fee change? If so, which ones and from when?

4. Which contract clause is the change made under, and what notice did that clause require?

5. Can you provide a fee-layer breakdown for MIDs on tiered or flat pricing?

For how rate-change and notice clauses typically appear in payment agreements, see the POS contract negotiation guide. Notice periods vary by contract; read your own.

Pricing model determines how much you can see

Interchange-plus pricing is the most auditable at multi-unit volume, because pass-through costs and the processor’s margin are listed separately. Tiered and bundled pricing put transactions into processor-defined buckets, so a network change can be absorbed, delayed, or amplified inside a bucket rate. Flat pricing hides both layers.

No model is automatically cheapest. The point is visibility: on a bundled model you may need a breakdown before you can answer whether a “network update” is really what moved.

A short checklist for every fee notice

1. Save the notice and note the effective date it gives.

2. Pull the statements for the month before and the month after, for every affected MID.

3. Calculate effective rate per MID for both months, summing fees and volume.

4. List new, renamed, or changed lines and classify each as pass-through or processor-set.

5. Rule out card-mix, channel, and seasonal shifts.

6. Send the written questions above and keep the replies.

7. Update your baseline so the next notice can be checked the same way.

What this does not change

This check sits entirely in statements and contracts. Guest checkout, menus, and store procedures stay the same. Surcharging or cash discounting is a separate, guest-facing decision, covered in the cash discount vs surcharging decision framework. And the pending card-network swipe-fee settlement is proposed, not in force, so it is not the cause of routine fee notices this fall.

Many groups resolve unexplained increases inside the existing processor relationship once each change is documented. Switching is a conclusion the analysis may reach, not a starting point.

Continue the review