Why Visa FANF Can Change Even When Your Processor Pricing Does Not
Expert Verified & Fact-Checked
From the Desk of: Chris DuPont, founder of Merchant Statement Analysis, with 17+ years of merchant processing experience.
The Focus: Visa FANF can change even when processor pricing stays the same. Learn why volume, locations, acceptance channel, and account structure can affect this network fee
Our Approach: Separates the network fee basis, merchant volume/account structure, acceptance channel and locations, and processor markup shown separately so the reader can distinguish transaction or account changes from processor pricing changes without assuming that every unusual line item is an error.
A merchant compares two statements and notices that a Visa-related network charge changed.
The processor markup looks the same.
The sales volume is fairly close.
So why did the network fee move?
One possible reason is Visa's Fixed Acquirer Network Fee, commonly called FANF. FANF is a network-related fee whose amount can depend on characteristics of the merchant account rather than simply applying as one flat percentage to every transaction.
FANF Is Not Processor Markup
This distinction matters first.
FANF is not the processor's ordinary percentage markup.
If FANF changes, that does not automatically mean the processor changed the merchant's negotiated pricing.
Likewise, a stable processor markup does not guarantee every Visa-originated charge will stay exactly the same.
In merchant statement reviews, this is a good example of why "fees went up" and "my processor raised my price" are not always the same statement.
Why FANF Can Change
The exact current Visa rules should always be verified before relying on a specific fee amount, because network pricing changes over time.
Conceptually, FANF can vary based on characteristics such as merchant volume, acceptance environment, account structure, or number of locations.
That means two months can look different without the processor changing its markup schedule.
Acceptance Channel Can Matter
A physical storefront, ecommerce environment, and other acceptance setups can fall into different network-fee treatment.
That does not mean one is automatically better or worse.
It means the network recognizes that merchant accounts can have different operating profiles.
If a merchant changes how it accepts payments—or adds a new channel—the network-fee mix can change too.
Multiple Locations Can Change the Picture
A merchant with several locations may also have a different FANF profile than a single-location merchant.
This becomes particularly important when comparing:
- separate MIDs
- consolidated accounts
- newly added locations
- accounts that changed structure
A network fee that looks stable on one MID may behave differently once the business expands or restructures.
Why FANF May Be Hard to Spot
Processor statements do not all display network fees the same way.
One statement may name FANF directly.
Another may abbreviate it.
Another may group it with other Visa charges.
That is why identifying a network fee from the label alone can be difficult.
The processor's statement legend and current Visa documentation are useful reference points.
A Change Does Not Automatically Mean an Error
Suppose FANF rises this month.
That may be worth reviewing.
It is not, by itself, proof that:
- the processor padded the fee
- the processor changed markup
- the merchant was double-billed
- the statement is wrong
The right question is whether the amount is consistent with the account's current characteristics and the network's current rules.
Why Month-to-Month Comparison Needs More Than Sales Volume
Current Network Rules Matter
Network pricing and rules change. That makes old fee tables dangerous.
Why This Matters to an ISO or Agent
A proposal is strongest when the savings story can be explained in plain language.
When a Statement Review Helps
When those pieces do not line up, that is when a statement deserves closer review.
MSA can evaluate the account in context and show where the cost is actually coming from.
Publication note: Codex should verify current Visa FANF rules and any specific rate examples against current authoritative Visa/acquirer documentation before publication.
---
How to Read This Issue in Context
Published Visa interchange rates and related network resources can provide context, but network cost still needs to be separated from processor markup on the merchant’s statement. Start by comparing the network fee basis with merchant volume/account structure. Then review acceptance channel and locations and processor markup shown separately to determine whether the result is being driven by merchant activity, pass-through cost, processor pricing, or another service.
For Why Visa FANF Changes on Merchant Statements, a multi-period view is usually stronger than a one-month snapshot. If the statement shows a change in the network fee basis while there is no meaningful change in processor markup shown separately, the explanation points in a different direction than a month where the merchant’s activity is stable but the pricing line changes. That distinction keeps the review tied to evidence rather than to a quick assumption.
A Practical Statement Checklist
- For Why Visa FANF Changes on Merchant Statements, compare the network fee basis across the relevant statement periods.
- Separate merchant volume/account structure from charges that are billed on a different basis.
- Check whether acceptance channel and locations changed enough to explain the movement being reviewed.
- Identify the statement label and billing basis for processor markup shown separately, and confirm whether the statement provides enough detail to classify it confidently.
What This Does Not Prove
For Why Visa FANF Changes on Merchant Statements, a surprising number on one statement is a reason to investigate, not proof that the processor made an error or that the account is overpriced. Read the network fee basis, merchant volume/account structure, acceptance channel and locations, and processor markup shown separately together, then check the agreement, processor definitions, network rules, or operating details when the statement alone cannot answer the question.
A strong review of Why Visa FANF Changes on Merchant Statements makes its limits visible. Use the statement for conclusions it can support; where detail is missing, note the missing evidence and verify it before presenting the point as fact.
How This Affects a Quote or Review
The proposal test for Why Visa FANF Changes on Merchant Statements is whether the savings survives normalization. Account for changes in the network fee basis and acceptance channel and locations, then isolate processor markup shown separately from merchant volume/account structure. If the projected advantage disappears after those adjustments, the original comparison was measuring activity differences rather than processor pricing.
Use historical statement data—not a convenient snapshot—to support Why Visa FANF Changes on Merchant Statements, and make the assumptions and reconciliation visible before presenting the result as savings.
Primary Sources to Check
Rates, network rules, and compliance requirements can change. Verify the current primary documentation before publication and before relying on a specific rule or amount.
