Does FANF Stop When Your Seasonal Business Has No Card Volume? Month-by-Month Billing Mechanics

A seasonal business can go from a packed summer weekend to months with no Visa sales at all. That makes FANF seasonal business no volume months a practical budgeting question rather than an obscure card-network issue: if October through April have zero Visa activity, should the Visa Fixed Acquirer Network Fee disappear too?

For a true zero-Visa-volume month, the current FANF structure results in no FANF assessment for that zero-volume activity. Current processor documentation continues to show a zero FANF tier for very low monthly Visa volume, including $0. FANF is evaluated using monthly inputs, and card-present and card-not-present activity follow different tables.

That does not mean the merchant account becomes free. A processor may still charge a monthly minimum, statement fee, gateway subscription, PCI/security charge, software fee, equipment charge, or account-maintenance fee under the merchant agreement. Those charges are not FANF.

There is another complication: the month in which FANF appears on a statement may not always be the month that generated it. Some acquirers or processors invoice non-transactional scheme fees after the assessment period. 

For example, Adyen currently identifies U.S. Visa FANF as a monthly, volume-based non-transactional scheme fee and documents a one-month billing delay in its implementation. That timing is processor-specific rather than a universal rule for every merchant statement.

The correct seasonal workflow is therefore:

identify channel → identify locations and MIDs → measure each month’s Visa activity → determine that month’s FANF treatment → compare the result with the statement → separate FANF from processor fees → decide whether to keep, seasonally suspend, or close the account → forecast the year month by month.

FANF Seasonal Business No-Volume Months: What Actually Happens?

The most important distinction is between zero processing and zero merchant-account cost.

FANF itself is a Visa network assessment. Current first-party processor documentation describes the U.S. Fixed Acquirer Network Fee as a monthly scheme fee whose calculation takes into account monthly merchant sales volume and, depending on the FANF table, factors such as merchant locations and MCC. 

Adyen’s current documentation identifies three relevant FANF tables: customer-present high-volume MCCs, other customer-present merchants, and customer-not-present merchants.

Current processor FANF schedules also continue to identify a $0 FANF result for monthly Visa volume below the low-volume threshold, which necessarily includes a true $0 month.

FANF is a Visa network assessment, while the processor controls how that assessment is presented and how other contractual fees are billed. Visa’s current rules governing merchants and acquirers also make clear that merchants operate through their acquiring relationship and should review their acceptance agreement for account-specific requirements.

That gives a summer-only merchant an important starting point. If there are genuinely no qualifying Visa sales in November, December, January, and so on, those months should not simply be modeled as though the business were still operating at its July FANF level.

The analysis becomes more complicated when the business has:

• card-present and card-not-present activity;
• multiple physical locations;
• several MIDs;
• online sales that continue after stores close;
• refunds or adjustments after the season;
• a year-round location alongside seasonal locations; or
• processor billing that reports network fees later than the activity month.

The result can also change with monthly Visa volume, acceptance channel, MCC, and location structure, which is why a seasonal merchant should evaluate each activity month independently rather than carry one assumption across the entire year.

A merchant should therefore avoid two opposite assumptions: “FANF always continues while my merchant account is open” and “my processing statement must be zero because my Visa sales were zero.” Neither is a reliable way to reconcile the statement.

For a broader explanation of the inputs used in FANF calculations, how FANF fees are calculated from monthly volume, acceptance method, MCC, and locations provides useful background. This article focuses specifically on what changes when those monthly activity inputs fall to zero.

What counts as a true zero-volume month?

“Closed for the season” is not the same accounting concept as “zero Visa activity.”

Before treating October as a FANF zero volume month, verify whether the Visa activity report actually shows zero. A terminal sitting unplugged in a locked storefront does not prove that the merchant profile recorded no activity.

Check for:

• Visa sales settled after the final operating day;
• an end-of-season batch submitted after month-end;
• ecommerce orders still being accepted;
• recurring card-on-file transactions;
• activity on another MID;
• transactions from another location under the same business structure;
• late settlement or other residual processing entries; and
• refunds, credits, or adjustments that should be investigated.

Do not automatically assume that a refund or credit by itself creates the same FANF result as new Visa sales. FANF calculation uses specific network/acquirer reporting fields, so where an off-season month contains only credits or unusual adjustments, the processor should identify the volume it used in its FANF calculation.

Worldpay’s FANF reporting documentation is useful operational evidence because its merchant FANF report includes the merchant ID, monthly Visa settled sales volume, the FANF tier description, and the assessed fee. That demonstrates why reconciliation should be performed against the actual activity month rather than merely against a calendar marked “closed.”

How Card-Present FANF Works Month by Month

Card-present seasonal merchants should evaluate FANF at the location and monthly-activity level rather than assuming every licensed store creates the same fee every month.

Under the current FANF framework documented by processors, customer-present merchants use location-based FANF tables once the merchant is above the applicable low-volume treatment. The table used can also depend on the merchant category.

For seasonal planning, the important fact is not the exact per-location rate. It is that monthly Visa activity matters before the ordinary per-location calculation is applied.

That means a retail location that is active in July and completely inactive in January should not be forecast as though the same card-present location charge automatically applies during both months.

Per-Location FANF and Zero-Activity Months

Consider a boardwalk retailer that operates May through September.

Its owner might look at a five-month operating season and assume that because the merchant account remains technically open all year, the FANF card present location month charge must continue for all 12 months. That is not the correct forecasting method.

Instead, test every month against the current Visa/FANF activity rules before applying the applicable location table.

Table 1: Card-Present Seasonal Month

Month	Location Status	Visa Activity	FANF Treatment	Other Fees
April	Closed	$0	Zero-volume FANF treatment; verify statement timing	Possible
May	Open	Hypothetical active volume	Apply current CP rule for that activity month	Possible
June	Open	Hypothetical active volume	Apply current CP rule for that activity month	Possible
October	Closed	$0	Zero-volume FANF treatment; verify residual activity	Possible

The “Other Fees” column is deliberately separate. An April FANF of zero does not tell you whether April’s processor invoice will also be zero.

A merchant may still see gateway access, account maintenance, PCI-related charges, software subscriptions, statement charges, minimums, or equipment obligations.

If you operate several storefronts, location and merchant-profile issues for multi-site FANF calculations should also be considered when reconciling a card-present seasonal portfolio. The homepage currently lists the dedicated multi-location FANF analysis, although the exact article URL should be confirmed in the CMS before publication.

Multi-location seasonal merchant

Now consider a retailer with two stores:

• a beach location that closes October through April; and
• a downtown location that operates all year.

In that situation, merchant IDs, location counts, and multi-site FANF reporting become important because one inactive storefront does not necessarily make the entire merchant relationship inactive. 

It would be a mistake to label the whole company “dormant” during winter. The downtown operation still generates Visa activity.

The business should map monthly activity at the relevant TIN, merchant-account, location, and channel structure used by its acquirer. The seasonal beach site’s zero activity does not erase activity at the year-round location.

Likewise, having two MIDs does not necessarily mean Visa FANF should be reconstructed by independently applying a retail rate to whatever appears on each statement page. FANF reporting and aggregation can depend on how the acquirer has structured merchant identifiers, locations, taxpayer IDs, and channels.

For that reason, ask the processor exactly which Visa activity and locations were included in its calculation.

How Card-Not-Present FANF Tiers Change With Seasonal Volume

A seasonal ecommerce business needs a different forecast from a storefront.

Card-not-present FANF is tied to monthly CNP Visa sales volume. Current processor documentation describes the customer-not-present table as a monthly tier structure, and Worldpay’s FANF report explicitly identifies monthly Visa settled sales and the applicable CNP FANF tier.

That makes the seasonal merchant FANF tier inherently sensitive to peaks and valleys.

Suppose an ecommerce company sells holiday gifts. October may be quiet, November busy, December extremely busy, and January completely inactive.

Those four months should not be assigned the same FANF simply because annual Visa volume divided by 12 produces one convenient average.

Month-by-month versus annualized assumptions

For CNP merchants, the useful budgeting unit is the month.

Imagine this hypothetical pattern:

• October: modest Visa CNP volume;
• November: substantially higher volume;
• December: the annual peak;
• January: zero Visa CNP sales.

The applicable CNP tier should be determined from the current structure for each month. The merchant should not calculate total annual Visa CNP volume, divide it by 12, and assume the resulting average is the Visa volume that governed every month.

That shortcut can distort the forecast in both directions.

High-volume December activity can push December into a different tier from October. A true $0 January has a different result again.

Table 2: Seasonal Ecommerce CNP Example

Month	Visa CNP Volume	Applicable Tier	FANF
October	Hypothetical low-season volume	Determine from current monthly table	Current applicable amount
November	Hypothetical higher volume	Determine from November volume	Current applicable amount
December	Hypothetical peak volume	Determine from December volume	Current applicable amount
January	$0	Zero-volume treatment	$0 FANF for zero volume

This is why peak-month FANF × 12 is usually a poor estimate for a highly seasonal CNP merchant.

It is equally dangerous to use annual Visa sales ÷ 12 and assume that average sets every month’s CNP tier.

For background on how ecommerce volume moves through the CNP structure, the site’s existing coverage of card-not-present profiles is listed in the current article library. The publication URL should be verified in the CMS before adding that internal link rather than fabricating a slug.

Holiday-only merchant example

Consider a merchant that accepts orders only during November and December.

Its annual Visa volume might look meaningful when spread across 12 months, but ten months could have no Visa sales at all. Dividing annual volume by 12 creates an artificial “average month” that never actually occurs.

A better model has twelve rows.

November receives the FANF treatment associated with November’s Visa CNP volume. December receives the treatment associated with December’s Visa CNP volume. A genuinely inactive January receives the zero-volume treatment.

That approach also makes year-end reconciliation easier. Instead of asking why an annual average failed, finance can compare each processor assessment with the month’s actual Visa activity.

What an Off-Season Processing Statement Should Show

A zero-volume month should trigger an audit, not an assumption that the statement must have a $0 balance.

The first task is to identify FANF itself. Because processors can label network charges differently, it helps to understand where FANF can appear on a merchant processing statement before deciding whether an off-season charge is actually FANF, a monthly minimum, or another fixed fee.

Then separate that charge from everything else.

Table 3: Off-Season Statement Audit

Charge	Network or Processor	Expected at $0 Visa Volume?	What to Check
Visa FANF	Visa network assessment	Zero-volume month should produce zero activity-month FANF	Confirm activity month and billing lag
Visa transaction assessments	Network	Usually activity-dependent	Check residual transactions
Monthly minimum	Processor/acquirer agreement	Can potentially continue	Contract and pricing schedule
Statement fee	Processor	Can potentially continue	Merchant agreement
Gateway fee	Gateway/processor	Can potentially continue	Subscription terms
PCI/security fee	Processor/service provider	Can potentially continue	Contract and compliance program
Account-maintenance fee	Processor	Can potentially continue	Pricing schedule
Batch fees	Processor/network depending on fee	Activity-dependent	Determine whether a batch actually occurred
Adjustment	Processor/network	Possible	Identify originating activity month

First-party acquiring documentation also identifies FANF as a Visa fee reported through monthly processor billing, which is why the FANF line should be reconciled separately from processor-created account fees.

A nonzero statement therefore does not prove that FANF itself continued.

For example, suppose November has:

• $0 Visa sales;
• $0 applicable activity-month FANF;
• a monthly minimum under the processor contract;
• an active gateway subscription; and
• a statement fee.

The business can receive a bill even though FANF for November is zero.

Processor billing lag

A fee appearing after the business closes for the season may also relate to a prior month.

Processor implementations differ. Adyen, for example, currently documents FANF as monthly but shows a one-month billing delay for its non-transactional scheme-fee service.

Do not convert that example into a universal statement such as “FANF is always billed one month late.” Ask your own processor:

Which activity month generated this FANF charge?

If the processor says the November statement contains October’s FANF, retain that explanation with the reconciliation workbook.

FANF vs Monthly Minimums and Other Fixed Merchant Fees

This is the distinction that causes the most off-season confusion.

FANF is not the monthly minimum.

Visa FANF is a network assessment. A processor monthly minimum arises from the commercial relationship described in the merchant agreement or pricing schedule.

A monthly minimum may therefore remain even in a month when there is no applicable FANF.

The same principle applies to a gateway subscription, statement fee, software subscription, security service, equipment rental, or account-maintenance charge.

Table 4: FANF vs Other Monthly Fees

Fee	Who Charges It	Trigger/Basis	Can It Continue at $0 Visa Volume?
FANF	Visa through acquirer/processor	Current FANF activity rules	$0 Visa volume produces zero activity-month FANF
Processor markup	Processor/acquirer	Contract/pricing model	Possibly
Monthly minimum	Processor/acquirer	Contractual minimum	Yes, if agreement says so
Statement fee	Processor	Account/reporting service	Possibly
Gateway fee	Gateway/processor	Gateway subscription	Possibly
PCI/security fee	Processor/service provider	Compliance/security program	Possibly
Account maintenance	Processor	Account contract	Possibly
POS/software subscription	Software provider/processor	Subscription	Possibly

The practical accounting rule is to put these items in separate ledger categories.

Do not post everything labeled “Visa,” “merchant services,” or “processing fees” into a single seasonal variance bucket and then try to infer whether FANF continued.

FANF pass-through versus processor markup

There are three different questions:

1. What did Visa assess?
2. What amount did the processor pass through?
3. Did the processor charge anything additional?

Those figures are not automatically identical.

A processor can present network costs in different ways depending on the pricing agreement. FANF may appear as a discrete line, within a network-fee category, or within a broader bundled price.

That is why an unexpected off-season fee should be described initially as an unexplained variance, not “processor padding.”

Ask for the calculation.

Useful questions include:

• Is this line the exact Visa FANF assessment?
• Is any processor markup included?
• What Visa activity month generated it?
• Which MID, locations, or taxpayer-ID grouping was used?
• Which FANF table or category was applied?
• Is the network assessment passed through at cost?
• Does the statement show network cost and markup separately?
• Is billing delayed from the previous cycle?

Get the answers in writing.

Does Dormant or Seasonal Account Status Change FANF?

“Dormant” is commonly an account-management term, but it should not be treated as though Visa has created a universal FANF dormant merchant account category that overrides the ordinary FANF calculation.

The current Visa public rules define merchant/acquirer relationships and explain that some proprietary and competitive network details are omitted from the public rules. Merchants are directed to their acquirers for implementation questions.

For seasonal merchants, the safer model is:

Visa FANF treatment follows the applicable network calculation. Seasonal or dormant status follows the processor’s account terms.

A processor may have a seasonal program, temporary suspension procedure, dormant-account configuration, or reduced off-season pricing. Another processor may have no equivalent feature.

Do not assume that placing the merchant account into “seasonal mode” automatically modifies Visa’s FANF rules.

What seasonal status can potentially change is the processor-created portion of the bill.

For example, a processor may agree contractually to alter an account fee or service configuration while a merchant is closed. But that must be verified from the processor’s current documentation or a written amendment applicable to the merchant.

Monthly minimums deserve special attention

A seasonal merchant can have:

• $0 Visa volume;
• $0 activity-month FANF;
• and a monthly minimum that remains due.

That is not inherently contradictory.

The minimum exists because of the processor agreement, not because Visa transformed FANF into a minimum charge.

When evaluating a seasonal or dormant arrangement, ask explicitly whether the monthly minimum:

• remains unchanged;
• is reduced;
• is suspended;
• resumes automatically;
• requires advance notice; or
• changes under a seasonal pricing schedule.

Never rely on “we can put you on seasonal status” without asking what that phrase changes financially.

Should You Close the Merchant Account During the Off-Season?

From a pure network-fee perspective, closing an account solely to avoid FANF may produce less benefit than expected when the merchant would already have zero Visa activity in the off-season.

The larger potential savings may come from processor-created fixed charges.

That changes the keep-versus-close decision.

Table 5: Keep Open vs Close

Option	Potential Savings	Risks	Questions
Keep account open	Avoids reopening/setup disruption	Fixed account fees may continue	Which fees remain during zero volume?
Seasonal/dormant status	May reduce certain processor costs if offered	Terms vary; FANF rules still need separate analysis	Which charges are suspended in writing?
Close and reopen	May eliminate some account-level fees after closure	Reapplication, repricing, setup, operational delay	Will a new application and MID be required?

Keeping the merchant account open

Keeping the account open can preserve operational continuity.

Potential advantages include:

• no fresh application purely because the season restarts;
• retention of an existing merchant relationship;
• preserved terminal or gateway configuration;
• fewer deployment steps before opening day;
• continuity for stored operational settings; and
• less risk of discovering in April that the account cannot be activated under the old arrangement.

The disadvantage is obvious: processor-created fixed fees may continue even while sales are zero.

A merchant should total those costs over the actual off-season rather than making the decision from FANF alone.

Closing and reopening

Closing may eliminate certain continuing account charges once the account is properly terminated, but closure should not be equated with guaranteed savings.

Possible consequences include:

• a fresh merchant application;
• new underwriting;
• different pricing;
• a new MID;
• updated gateway configuration;
• equipment provisioning;
• revised contract terms; and
• an approval process before processing resumes.

The merchant must also identify any final-cycle charges that can legitimately arrive after closure.

If a processor invoices network assessments or other costs after the activity period, a final statement can remain nonzero even after the account has stopped processing.

Re-underwriting and repricing risk

A merchant account is an underwriting relationship.

If the old account is closed rather than merely kept inactive, the business should not assume it has a permanent right to reopen under the same terms.

On a future application, the acquirer may review current information such as:

• business ownership;
• products or services;
• MCC;
• expected processing volume;
• average or high tickets;
• refund policy;
• fulfillment timing;
• card-present versus CNP mix;
• chargeback history; and
• financial or risk information requested by the provider.

Risk policies can also change between seasons.

That does not mean the merchant will encounter a problem. It means reopening risk belongs in the financial model.

Keep-vs-close break-even framework

Use this equation conceptually:

Expected off-season fixed fees avoided

minus

expected reopening/setup costs + contract costs + operational friction + value assigned to re-underwriting/repricing risk

The result is more useful than asking, “Can I save FANF by closing?”

For a business with a true zero-Visa-volume winter, activity-month FANF may already fall to zero. The decision may therefore turn principally on processor and technology costs.

Do not insert assumed dollar values. Use your own merchant agreement and written processor quote.

How to Forecast Annual FANF for a Seasonal Merchant

The correct annual FANF forecast is:

Annual estimated FANF = January applicable FANF + February applicable FANF + … + December applicable FANF

It is not automatically:

peak-month FANF × 12

and it is not:

annual Visa volume ÷ 12 → one tier × 12

Seasonality means each month’s inputs can be different.

Summer-only merchant example

Consider a physical merchant operating from May through September.

The forecast should show the operating period and closed period explicitly.

Table 6: Month-by-Month Seasonal FANF Forecast

Month	Channel / Status	Visa Volume	FANF Rule	Estimated FANF	Separate Fixed Fees
January	CP / closed	$0	Zero-volume treatment	$0 activity-month FANF	Contract-specific
February	CP / closed	$0	Zero-volume treatment	$0 activity-month FANF	Contract-specific
March	CP / closed	$0	Zero-volume treatment	$0 activity-month FANF	Contract-specific
April	CP / closed/pre-opening	$0 or actual	Evaluate actual activity	Current applicable result	Contract-specific
May	CP / open	Hypothetical	Current CP rule	Calculate monthly	Contract-specific
June	CP / open	Hypothetical	Current CP rule	Calculate monthly	Contract-specific
July	CP / open	Hypothetical peak	Current CP rule	Calculate monthly	Contract-specific
August	CP / open	Hypothetical	Current CP rule	Calculate monthly	Contract-specific
September	CP / open	Hypothetical	Current CP rule	Calculate monthly	Contract-specific
October	CP / closed	$0 if truly inactive	Zero-volume treatment	$0 activity-month FANF	Contract-specific
November	CP / closed	$0	Zero-volume treatment	$0 activity-month FANF	Contract-specific
December	CP / closed	$0	Zero-volume treatment	$0 activity-month FANF	Contract-specific

Then create separate annual totals for:

• FANF;
• monthly minimum;
• statement/account fees;
• gateway fees;
• PCI/security charges;
• equipment costs;
• POS/software subscriptions; and
• other fixed merchant-services expenses.

This prevents a misleading “annual processing cost” figure from obscuring what can actually be eliminated during the off-season.

Why annual averages can be misleading

There are at least three reasons.

First, CNP merchants may move through multiple volume tiers during the year.

Second, a zero-volume month does not resemble an average active month.

Third, a card-present merchant’s operating locations can change seasonally.

An amusement business, resort operator, festival merchant, or coastal retailer may therefore have fundamentally different network-fee inputs in January and July.

Forecast multiple MIDs separately before reconciling

If a business has several merchant IDs, list them before building the annual budget.

For each MID record:

• merchant ID;
• location;
• channel;
• active months;
• expected Visa volume;
• related gateway;
• processor pricing schedule; and
• whether the processor says FANF is calculated or allocated at another aggregation level.

Do not automatically sum independently calculated MID estimates unless that matches the processor’s documented FANF treatment.

The processor should tell you how the Visa assessment maps to its merchant hierarchy.

What to Ask Your Processor Before the Season Ends

Do not wait until January’s statement arrives to learn what “seasonal account” meant.

About four to six weeks before the operating season ends—or whatever lead time your processor requires—request a written explanation of off-season treatment.

Ask:

1. Will FANF be charged for an activity month with zero Visa volume?
2. How will FANF appear on my statement or invoice?
3. Is the line the exact Visa assessment or an allocated processor amount?
4. Is any processor markup added to FANF or network fees?
5. Which fees continue when Visa volume is $0?
6. Does my monthly minimum continue during inactive months?
7. Do you offer a seasonal, dormant, or temporary-suspension status?
8. If so, exactly which fees change under that status?
9. Does gateway billing continue?
10. Are there contractual reactivation, setup, or other restart charges?
11. If I close the account, must I submit a new merchant application?
12. Would reopening create a new MID or merchant profile?
13. Could my pricing or other contract terms change when I reapply?
14. Does FANF or another network charge appear one or more billing cycles after its activity month?
15. Which locations, MIDs, TINs, and channels are included in your FANF calculation?
16. How are off-season refunds or adjustments treated in the FANF reporting you receive?

Ask the representative to answer by email or provide the applicable contract/documentation.

Verbal explanations can help operationally, but they are poor reconciliation evidence six months later when staff changes and nobody remembers exactly what was promised.

Common Seasonal FANF Billing Mistakes

Most seasonal FANF problems are not complicated mathematical errors. They are classification and timing errors.

A merchant sees a nonzero November statement and concludes that Visa continued FANF. Or finance annualizes July’s CNP tier over 12 months even though the business operates for four.

Another common problem is leaving a second MID out of the analysis.

Table 7: Common Seasonal FANF Mistakes

Mistake	Risk	Better Approach
Assuming $0 processing means a $0 merchant statement	Fixed processor fees are overlooked	Reconcile FANF separately
Assuming an open MID always creates FANF	Seasonal forecast may overstate network cost	Use actual monthly Visa activity
Confusing monthly minimum with FANF	Network and processor costs become mixed	Match each fee to its source
Annualizing the peak season	Annual FANF can be overstated	Calculate each month
Averaging annual CNP volume	Monthly tier changes disappear	Use monthly Visa CNP volume
Ignoring CP/CNP differences	Wrong FANF methodology	Separate channels
Overlooking a second MID	“Zero-volume” month may not be zero	Inventory all MIDs
Ignoring a year-round location	Seasonal company status is overstated	Map each location
Ignoring residual activity	Statement appears inexplicable	Check settlement and adjustments
Calling an unexplained charge “padding” immediately	Conclusion may be unsupported	Request fee calculation first
Closing solely to eliminate FANF	Re-underwriting cost may exceed savings	Model total fixed costs
Relying on verbal seasonal terms	Difficult to enforce or reconcile later	Get terms in writing
Stopping statement reviews in winter	Errors or continuing charges go unnoticed	Audit every billing cycle

Seasonal FANF Audit Checklist

A reliable seasonal review should be repeatable by the bookkeeper, controller, or merchant-account administrator without relying on memory.

Use this checklist for every off-season month:

• Confirm whether the business was operational.
• Confirm every active merchant ID.
• Confirm every physical location.
• Separate card-present and card-not-present activity.
• Pull the current FANF rules or processor-supported Visa fee schedule.
• Verify actual monthly Visa sales rather than total card volume.
• Confirm whether Visa activity was truly zero.
• Check residual settlements or late batches.
• Review refunds or adjustments that require explanation.
• Identify the FANF/network line on the statement.
• Identify the activity month that generated the assessment.
• Separate FANF from the monthly minimum.
• Separate FANF from statement charges.
• Separate FANF from gateway charges.
• Separate FANF from PCI/security charges.
• Separate FANF from account-maintenance charges.
• Check whether the processor has added or allocated any network-fee amount.
• Verify seasonal/dormant status terms.
• Compare keep-open cost with close/reopen economics.
• Include underwriting and repricing risk.
• Save the processor’s explanation in writing.
• Update the annual month-by-month forecast.
• Compare the actual statement against the forecast.

Practical Seasonal FANF Workflow

A controller responsible for a seasonal merchant portfolio can turn the checklist into a 16-step operating procedure.

1. List the active months. Record the expected opening and closing month for every seasonal operation.
2. Identify CP versus CNP channels. A store that closes physically but leaves its website running is not fully inactive.
3. List every location and MID. Do not assume one legal business equals one merchant account.
4. Confirm the current FANF structure. Network fees can change, so do not roll last year’s worksheet forward without checking it.
5. Record monthly Visa activity. Use Visa activity rather than total card-brand sales.
6. Evaluate each month separately. Apply the current monthly rule rather than annualizing.
7. Identify true zero-volume months. A calendar closure date is not sufficient evidence.
8. Review statements for FANF. Locate the Visa FANF or relevant network-fee entry.
9. Identify the assessment period. Determine whether the charge belongs to the same month or a prior cycle.
10. Separate fixed processor charges. Pull monthly minimums, gateway fees, statement charges, PCI/security fees, maintenance charges, and software costs into separate rows.
11. Ask whether seasonal or dormant treatment is available. Do not assume it exists.
12. Model keep-open versus close/reopen. Focus on actual avoidable costs, not FANF alone.
13. Include re-underwriting risk. Reopening later may involve a new review or new commercial terms.
14. Get treatment in writing. Save the response with the merchant agreement and seasonal worksheet.
15. Forecast annual FANF month by month. Sum monthly FANF results.
16. Resolve unexplained variances. Ask the processor to identify the Visa activity, FANF category, and billing period behind the difference.

Frequently Asked Questions

Conclusion

Seasonal FANF should be analyzed month by month, not by assuming that an active merchant account produces the same Visa network fee throughout the year.

Card-present and card-not-present businesses also require different analysis. Physical merchants need to account for their location structure and monthly activity, while ecommerce and other CNP merchants need to model the applicable monthly volume tier.

A true $0 Visa-volume month can produce $0 activity-month FANF, but that is not the same as a $0 merchant-services bill. Monthly minimums, gateway subscriptions, statement fees, PCI/security charges, software costs, and account-maintenance fees can remain under the merchant agreement.

Similarly, a processor’s “seasonal” or “dormant” designation should not be treated as a substitute for the Visa FANF calculation.

Closing the account can reduce some contractual off-season costs, but it can also introduce new underwriting, repricing, MID, gateway, and setup considerations.

For budgeting, use one durable formula: calculate the applicable FANF for each month and add the monthly results together. That gives a seasonal merchant a much more defensible annual forecast than multiplying the peak month by 12 or averaging annual Visa volume across months that never looked alike.