Keeping a Seasonal Merchant Account Alive in the Off-Season: Monthly Minimums, Dormancy Reviews, Close vs Suspend

A seasonal merchant may process heavily for a few weeks or months and then record little or no card volume for the rest of the year. The account may still generate fees, remain subject to PCI and contractual obligations, or undergo a fresh underwriting review before the next busy season.

That pattern is normal for fireworks retailers, holiday stores, fairs, festivals, vacation businesses, seasonal attractions, temporary retail locations, tourism operators, and many event-based sellers. 

What matters is whether the processor or acquiring bank understood that pattern when the merchant account was approved—and what the merchant agreement says should happen during periods of merchant account inactivity.

A seasonal merchant account should not simply be forgotten once the doors close. Zero sales do not necessarily mean zero costs, zero security responsibilities, or zero administrative work. 

Depending on the agreement, monthly account charges, gateway subscriptions, equipment expenses, PCI-related charges, minimum billing provisions, or other contractual fees may continue.

Inactivity also does not automatically mean an account has been closed. A processor may leave the account active, place restrictions on it, classify it internally as inactive, request updated information, suspend processing, or terminate the relationship according to its policies and contract. 

Card-network rules establish important responsibilities for acquirers and merchants, but they do not create one universal off-season dormancy schedule or one standard monthly minimum for every merchant. 

Visa’s current public rules, for example, place merchant oversight and merchant-agreement responsibilities on acquirers rather than establishing a single retail dormancy period that applies to everyone.

Good off-season merchant account management therefore starts with an intentional decision: keep the account active, use an available seasonal suspension or hold program, or close the account correctly.

The right answer depends on annual carrying costs, contract terms, future refund and chargeback needs, anticipated processing volume, equipment arrangements, the difficulty of underwriting a replacement account, and the operational risk of discovering a problem days before peak season.

What Is a Seasonal Merchant Account?

A seasonal merchant account is a payment-processing relationship established for a business whose card volume predictably rises and falls during the year. The merchant may generate a large percentage of annual sales during a short operating window and little or no revenue outside that period.

Typical examples include:

• fireworks stands and fireworks retailers;
• Christmas, Halloween, and other holiday stores;
• fairs, carnivals, festivals, and temporary events;
• beach, ski, lake, and other tourism businesses;
• seasonal attractions and recreational operators;
• farmers market and temporary retail vendors;
• pop-up stores;
• summer camps and seasonal programs; and
• ecommerce merchants centered on a particular holiday or annual event.

“Seasonal merchant account” is not necessarily the name of a standardized card-network product. In practice, it can describe an ordinary merchant account whose underwriting profile, expected annual volume, operating dates, or processor configuration reflects a seasonal business model. Provider terminology varies.

That distinction matters. A merchant should not assume that telling a salesperson “we are seasonal” automatically creates a special suspension program or eliminates off-season fees. The merchant agreement, pricing schedule, underwriting records, gateway agreement, equipment contract, and processor policies determine what actually applies.

For a fireworks seller, the processing profile can be especially concentrated. A business may operate several temporary locations around a major holiday, process substantial volume in a short period, close the locations, and reopen months later. 

Guidance on setting up a merchant account for a seasonal fireworks business illustrates why equipment, payment channels, security, and pre-opening preparation should be considered together rather than treating processing as a last-minute task.

The processor may underwrite a merchant using estimated annual card volume, peak monthly volume, average ticket, maximum ticket, product type, fulfillment method, processing channel, refund exposure, chargeback history, ownership information, banking details, and other risk factors. 

A seasonal business should describe those characteristics accurately rather than smoothing a highly concentrated sales pattern into an unrealistic year-round forecast.

Keeping a seasonal merchant account active works best when both sides understand that periods of legitimate inactivity are part of the business model rather than evidence that the company disappeared.

What Happens to a Merchant Account During the Off-Season?

There is no single outcome that applies whenever a seasonal business stops processing. Depending on the processor, acquirer, sponsor bank, merchant category, risk profile, and contract, the account may remain fully operational, remain open with no transaction volume, enter an internal inactive status, be suspended, undergo review, or eventually be closed.

Recurring charges can also continue. A merchant might still receive statements reflecting service fees, gateway charges, software subscriptions, equipment rentals, PCI-related charges, minimum-processing shortfalls, or another contractual expense even though no customers have used the account.

That is why the simplest rule of merchant account maintenance is worth remembering: zero transactions do not necessarily mean zero cost. Some merchant agreements also require merchants to keep material business information current. 

For example, Heartland’s published merchant terms require notification regarding specified business changes and contain continuing obligations involving settlement accounts, chargebacks, fees, and transactions. The exact provisions of another provider’s contract may be different.

A processor that sees months of merchant account inactivity may also want to confirm that the business still exists and that the processing profile it originally approved remains accurate. That does not mean every dormant merchant receives a formal investigation. It means inactivity can be one of several operational signals that lead to an account-status or underwriting check.

Merchant Account Dormancy Does Not Have One Universal Definition

A dormant merchant account generally refers to an account that has experienced little or no processing activity for some period, but the precise definition belongs to the relevant provider or contract. There is no universal card-industry dormancy period after which every U.S. merchant account automatically closes.

One processor might use inactivity as an internal review trigger. Another could maintain a seasonal account with no problem because its underwriting profile already reflects the operating schedule. A third may have contractual provisions addressing inactive services, minimum activity, suspension, or termination.

For that reason, merchants searching for an “account dormancy review processor rule” should distinguish card-network requirements from provider policies. 

Visa and Mastercard establish extensive rules governing acquirers, merchant agreements, acceptance, processing, monitoring, and compliance, but each merchant’s commercial pricing and account-management arrangement remains dependent on its actual processing relationship.

Do not rely on a generic claim that an account becomes dormant after a particular number of days. Ask the processor what its system considers inactive, what happens at that point, and whether an intentionally seasonal profile receives different treatment.

Monthly Minimum Processing Fees and Other Off-Season Charges

Merchant account monthly minimum fees are among the most misunderstood off-season costs. A monthly minimum, where included in a merchant agreement, generally means the merchant must generate a specified minimum amount of qualifying processing-related fees during the billing period.

It does not necessarily mean the merchant must process a specific dollar amount of sales. It also does not necessarily mean every fee appearing on the statement counts toward the minimum.

Suppose a hypothetical merchant agreement requires $25 in qualifying monthly processing fees. If transactions generate only $8 of fees that count toward the minimum, the processor might bill a $17 minimum shortfall:

$25 monthly minimum requirement − $8 qualifying processing fees = $17 possible shortfall

That example is only a calculation illustration. It is not a standard industry minimum. Actual monthly minimum merchant account provisions, qualifying charges, calculation methods, fee amounts, and billing practices vary by provider and contract, and many merchant accounts have no monthly minimum at all.

For a strongly seasonal business, the distinction can materially change annual merchant account costs. If a merchant processes nothing for several months but its contract contains a monthly minimum processing fee, those zero-volume months may still create minimum shortfalls.

Monthly Minimum vs. Monthly Account Fee

A monthly minimum and a fixed monthly service fee are different concepts.

A monthly minimum processing fee is generally tied to whether enough qualifying processing charges were generated. A monthly account or service fee is normally a recurring charge for maintaining or providing a service and may apply independently of transaction volume if the agreement says so.

Charge	What It Generally Means	Can Apply With Zero Processing?
Monthly minimum	A required minimum amount of qualifying processing fees, with a possible shortfall billed when qualifying fees fall below the requirement	Potentially, depending on the contract
Monthly account/service fee	A recurring account or service charge	Often possible
PCI fee	A charge associated with a provider’s PCI program, validation services, or related administration	Potentially
Gateway fee	Recurring access to an ecommerce gateway or virtual terminal	Potentially
Statement fee	Charge for statement delivery or account reporting where contracted	Potentially
Equipment/software fee	Rental, lease, licensing, connectivity, POS, or software cost	Potentially
Inactivity fee	A provider-specific charge associated with defined inactivity	Only if provided for under the applicable arrangement

None of these charges should be assumed to exist—or to disappear—without checking the merchant’s agreement and fee schedule.

Published processor contracts demonstrate why contract review matters. Providers can have separate terms for processing, gateways, equipment, hosted services, renewals, and termination. 

Elavon’s published gateway terms, for example, include fees, suspension provisions, term provisions, and termination obligations specific to the covered service.

Calculating the Annual Cost of Keeping the Account Open

A seasonal business can estimate its carrying cost with a straightforward framework:

Annual Carrying Cost = Monthly Fees + Minimum Shortfalls + Gateway/Software Fees + PCI/Compliance Fees + Equipment Costs + Other Contractual Charges

Assume, only for illustration, that a merchant expects several months without sales. The merchant should list every fixed or likely charge that continues through those months, then add costs that arise during the active season.

Do not stop at the processing statement. Review gateway invoices, POS subscriptions, terminal leases, wireless connectivity, chargeback-management tools, ecommerce applications, and other payment-related services that may be billed separately.

That number gives the merchant a useful baseline for comparing close vs suspend merchant account options.

Merchant Account Dormancy Reviews and Seasonal Underwriting

A payment processor dormancy review is an account-status or risk review that may occur after a period of low or no activity. There is no universal form, trigger, or information request used by every processor.

A review may be straightforward. The provider might simply confirm that the business plans to resume operations. In other cases, the processor or acquiring institution may ask for updated business records before restoring or allowing substantial processing.

Information that may be requested, depending on the circumstances, includes:

• legal business name and address;
• ownership or controlling-person information;
• current settlement bank details;
• current website or ecommerce information;
• applicable licenses;
• expected annual and peak-season volume;
• average or maximum ticket;
• product or service mix;
• in-person, ecommerce, mobile, or other processing channels;
• fulfillment or delivery arrangements;
• recent processing history; and
• PCI validation information.

A merchant should not assume every dormancy review requires all of these items. The scope is provider- and risk-specific.

Why Processors May Review Dormant Accounts

The basic concern is not merely that the merchant stopped processing. Time can change the facts on which the original approval was based.

Ownership can change. A storefront can move. A website can begin selling different products. The settlement bank account can change. Licenses can expire or be replaced. An in-person business can add ecommerce or delivery. Expected volume can rise sharply.

Acquirers also have broader responsibilities for the merchants they accept and monitor. Visa’s public rules include acquirer requirements and merchant-agreement requirements, while Mastercard’s current rules address acquirer responsibilities, merchant relationships, compliance, and maintaining information.

Fraud and dispute performance also matter. Visa’s current Acquirer Monitoring Program monitors specified fraud and dispute activity and places operational responsibilities on acquirers, illustrating why processors maintain risk controls rather than treating every previously approved merchant as permanently unchanged.

For the merchant, the lesson is practical: a previous approval does not guarantee that every future season can begin with no review.

Seasonal Merchant Underwriting and Volume Spikes

Seasonal businesses are often evaluated using annual activity and concentrated peak-season risk. A fireworks retailer that generates most of its annual volume during a short sales window looks very different from a year-round retailer producing the same total card volume evenly over twelve months.

An underwriter may consider expected peak volume, average and maximum ticket size, delivery timing, refund practices, dispute exposure, prior processing history, product type, regulatory considerations, and sales channel. Requirements vary and should not be treated as a universal checklist.

A legitimate sales surge can still generate risk alerts when actual behavior differs materially from the profile on file. For example, a merchant approved primarily for in-person sales may return next season with substantially higher volume, larger tickets, several new locations, and an ecommerce channel.

Those changes should be disclosed through authorized processor procedures. Trying to avoid review by underreporting expected volume creates a worse operational position, not a better one.

Special Considerations for Fireworks Merchants

Fireworks merchants combine seasonality with product-specific regulatory and underwriting issues. That makes account continuity particularly important for businesses that depend heavily on a short sales period.

Federal rules differ depending on the type of fireworks and business activity. The Bureau of Alcohol, Tobacco, Firearms and Explosives explains that display-fireworks activities can be subject to federal explosives licensing requirements, while completed consumer fireworks are regulated differently and can also be subject to state and local rules.

The Consumer Product Safety Commission separately regulates consumer-fireworks product requirements under federal consumer-product law and publishes fireworks business guidance.

For payment underwriting, this means a processor may want to understand exactly what products are being sold, where they are sold, how orders are fulfilled, and whether required business or product-related approvals remain current. A processor or sponsor bank can also maintain a risk policy that is more restrictive than what is merely legal to sell.

Consequently, fireworks merchant account availability can depend on current laws, licensing, product mix, sales channels, processor policy, acquiring relationships, sponsor-bank risk tolerance, and underwriting criteria. Approval one season should not be treated as an unconditional promise of approval forever.

Businesses reviewing their payment structure can also consult information about payment-processing challenges for fireworks retailers for additional context on concentrated seasonal volume, fraud, chargebacks, security, and processing infrastructure.

The critical compliance principle is transparency. Do not disguise regulated products, manipulate a merchant category deceptively, route another business’s transactions through the account, or misrepresent anticipated volume to make the account appear less risky.

Keep Active, Suspend, or Close the Merchant Account?

Seasonal merchants generally have three broad strategies: leave the account active, use a provider-supported seasonal hold or suspension if one exists, or close the account. The terminology and availability of each option vary significantly.

The best decision is not necessarily the choice with the smallest visible monthly fee. Reactivation workload, underwriting uncertainty, refund access, dispute management, equipment arrangements, and the consequences of failing to open on time can be just as important.

Option	Off-Season Cost	Reactivation Effort	Main Advantage	Main Risk
Keep active	Contract-dependent; recurring charges may continue	Usually lower if the account remains fully usable	Continuity	Paying for unused capacity and services
Suspend/seasonal hold	Provider-specific; some charges may continue	Low to substantial depending on provider	Potential cost reduction without complete termination	Assuming suspension preserves functionality that it does not
Close	May eliminate future recurring processing charges after proper termination, subject to other contracts and final obligations	Potentially high if full reboarding is required	Stops an unwanted processing relationship	Reapproval uncertainty and loss of immediate processing/refund capability

Option 1: Keep the Merchant Account Active

Keeping the account active can make sense when off-season carrying costs are reasonable and reopening would create substantial operational risk.

Advantages can include preserving established account credentials, maintaining access to reporting and dispute tools, simplifying legitimate pre-season testing, keeping settlement configuration in place, and avoiding a new application simply because the calendar changed.

The disadvantages are primarily cost and maintenance. Monthly account fees, gateway charges, minimum shortfalls, equipment expenses, PCI-related obligations, software subscriptions, or other contractual charges may continue.

An active account also needs attention. Statements should still be reviewed, contact and banking details kept current, dispute notifications monitored, credentials protected, and payment hardware stored securely.

For a seasonal business with a difficult underwriting profile, continuity itself can have financial value. Losing several peak sales days because a new account is still being reviewed may cost more than months of reasonable carrying charges.

Option 2: Suspend or Use a Seasonal Hold

Some providers may offer a seasonal suspension, seasonal closure, temporary hold, reduced-fee arrangement, or another inactive status. These terms are not interchangeable across the industry.

Before using such an option, ask exactly what it changes.

Can transactions still be processed? Can refunds still be issued? Which processing, gateway, software, PCI, and equipment charges continue? Will settlement credentials stay configured? Does reactivation require a new underwriting review? Is reactivation automatic after a specified request, or does someone need to approve it?

The merchant should also ask whether gateway and equipment services are separate contracts. A processor may be able to suspend one service while another company continues invoicing a terminal lease or ecommerce platform.

Finally, determine how reactivation is requested and how early the provider recommends beginning its own review. There is no responsible universal number of days because reactivation complexity differs by processor and account.

Option 3: Close the Merchant Account

Closing can be appropriate when the business will not return, the location is permanently gone, the merchant is changing processors, the business model has changed materially, or annual carrying costs no longer justify preserving the relationship.

Closure should be a controlled process, not simply a decision to stop processing.

Depending on the contract, the merchant may need to follow a notice procedure, pay final fees, return equipment, reconcile transactions, preserve settlement-account access, and address reserves or other surviving obligations. Provider contracts can specifically state that certain payment, chargeback, or other obligations survive termination.

Closing can also create a practical refund problem. If customers may legitimately seek refunds months later, determine how those credits will be handled after termination.

A merchant that returns the following season may have to complete full underwriting again, and approval is not guaranteed.

Break-Even Analysis: Keep vs. Reopen

Compare more than monthly fees:

Cost to Keep Account Open vs. Expected Reboarding/Reactivation Cost + Operational Risk of Opening a New Account

Suppose carrying the account for the off-season produces a hypothetical total of $300 in recurring costs. Assume closing eliminates those costs, but obtaining a replacement account could require new documentation, equipment setup, gateway configuration, staff retraining, and uncertain approval.

The merchant should ask whether the expected savings are worth the reboarding effort and the cost of even a short delay during peak season.

Nonfinancial considerations belong in the calculation too: preserving refund capability, retaining historical records, keeping hardware configured, maintaining ecommerce integrations, and reducing the number of operational dependencies immediately before opening.

Off-Season Merchant Account Maintenance

Keeping a seasonal merchant account active is not the same as ignoring it until the next season. Good off-season processing strategy focuses on preserving access, security, contract awareness, and accurate business information.

At minimum:

• review processor and gateway statements;
• keep business and authorized-contact information current;
• update settlement-account changes through approved procedures;
• maintain required PCI activities;
• retain administrative credentials securely;
• monitor refund and dispute activity;
• maintain applicable licensing and business records;
• review renewal and termination provisions;
• confirm ownership and location information;
• inventory payment equipment;
• secure unused terminals;
• disable unnecessary staff access; and
• document the pre-season reactivation process.

A shared annual operations calendar can help. Assign responsibility for reviewing statements, PCI notifications, contract renewal dates, equipment storage, licensing, and the date when the processor should be contacted about the next season.

Do Not Manufacture Transactions to Make the Account Look Active

A seasonal merchant should not create artificial, self-funded, fabricated, or unrelated transactions merely to make the account appear active.

Do not charge your own card simply to create processing history. Do not run fake purchases. Do not process transactions belonging to another business or unrelated activity. Do not disguise a product or change transaction descriptions deceptively to avoid an inactivity review.

Merchant agreements and card-network rules require transactions to represent authorized activity within the approved merchant relationship. American Express terms published through Heartland, for example, describe charges as bona fide sales and prohibit merchants from submitting transactions on behalf of unrelated parties except as expressly permitted.

If the processor wants to verify the terminal before opening, ask for its approved testing procedure. Genuine authorized customer sales and provider-approved technical tests are different from fabricated commerce intended to manipulate account status.

Refunds, Chargebacks, and Reserves Continue to Matter

Customers do not necessarily stop needing support because the store has closed for the season. A customer may discover a billing problem later, seek an eligible refund, or initiate a payment dispute after peak operations end.

Before suspending or closing the account, ask whether refunds can still be processed and how they are funded. Do not assume another merchant account can simply refund a transaction that belongs to the old one.

Chargeback management is equally important. Merchants should retain receipts, order details, policies, fulfillment records, communications, and other evidence relevant to their transactions. They should also maintain access to whatever portal or notification channel their processor uses for disputes.

For a fireworks-specific overview, see this guide to chargebacks for fireworks retailers.

Reserves may also remain relevant after processing slows or ends. A processor can use rolling reserves, fixed reserves, delayed funding, or other risk arrangements where permitted by the merchant agreement. Release timing and conditions vary by contract and risk profile; closing the account should not be assumed to create immediate reserve release.

PCI Compliance and Security Do Not Take a Vacation

Simply stopping sales does not automatically remove every PCI responsibility while the merchant relationship and payment environment remain in place.

The PCI Security Standards Council states that PCI DSS applies to entities involved in cardholder-data environments and that even merchants outsourcing all payment processing retain responsibilities for understanding and validating the applicable compliance arrangement. 

Merchants should confirm their specific validation requirements with the organization managing their compliance program.

Fireworks retailers can also review this overview of PCI compliance for fireworks businesses.

During the off-season:

• physically secure payment terminals;
• keep an equipment inventory;
• protect devices from tampering;
• restrict access to authorized personnel;
• disable accounts belonging to departed or seasonal employees;
• use multifactor authentication where supported;
• maintain necessary software and security updates;
• avoid unnecessary storage of card data; and
• keep administrative credentials protected.

Do not open secure terminal hardware, attempt to inspect cryptographic components, or manipulate keys. If a terminal appears damaged or tampered with, stop using it and follow the processor’s or equipment provider’s support procedure.

Gateway and virtual-terminal accounts need similar care. Seasonal employees who no longer require access should not remain active indefinitely, and merchants should periodically review administrator privileges and continuing gateway billing.

Preparing for Merchant Account Reactivation Before Peak Season

Do not make opening day the first time anyone logs into the gateway, powers on a stored terminal, or checks the merchant account status.

A seasonal business should begin reactivation sufficiently early to accommodate the processor’s required review, document requests, equipment replacement, software updates, bank verification, licensing questions, or underwriting changes. The correct lead time is provider-specific, so ask rather than relying on a universal deadline.

A practical pre-season workflow is:

1. Contact the processor or acquirer: Confirm that the account is open and determine whether it is active, restricted, suspended, or awaiting review.
2. Confirm the reactivation procedure: Ask what must occur before normal processing resumes.
3. Verify business and licensing information: Provide current documents where requested.
4. Confirm the settlement bank account: Use the provider’s authorized verification process.
5. Review processing parameters: Discuss relevant limits or risk controls that could affect peak operations.
6. Verify gateway and equipment access: Confirm that terminals, virtual terminals, integrations, and credentials work.
7. Complete required PCI activities: Confirm the applicable validation status and outstanding actions.
8. Update expected volume and ticket size: Disclose material changes from the prior profile.
9. Follow approved testing procedures: Use only legitimate and processor-authorized testing methods.
10. Verify settlement: Confirm that approved transactions settle to the intended bank account.
11. Train returning and new staff: Review terminal use, refund controls, security, and escalation procedures.
12. Confirm support contacts: Know whom to contact during nights, weekends, or the highest-volume operating periods.

Testing deserves particular attention. A processor or equipment provider may have an authorized procedure for confirming that a terminal, gateway, integration, and settlement path function correctly. Follow that procedure rather than inventing self-funded sales to mimic customer activity.

Volume forecasting also deserves a deliberate review. Tell the processor if the new season is expected to involve significantly higher volume, materially larger tickets, a new ecommerce channel, new locations, changed products, or a different fulfillment model.

Seasonal transaction volume is not suspicious merely because it is concentrated. The problem arises when the activity arriving at the processor differs substantially from what the relationship was approved to handle or otherwise triggers risk controls.

Bank changes are another common source of avoidable opening-day problems. If a business changed banks during the off-season, update settlement instructions through authorized procedures in advance. Do not wait for the first major batch to discover that the account still points to obsolete banking information.

Pro Tip: A successful authorization is only part of pre-season verification. Confirm settlement and reporting as well, because a terminal that approves a transaction is not proof that every downstream funding or account configuration is correct.

Closing a Seasonal Merchant Account Correctly

If closing is the best financial and operational decision, use the procedure specified in the merchant agreement rather than merely unplugging equipment or emptying the settlement account.

A disciplined closure process is:

1. Review the merchant agreement, pricing schedule, equipment agreement, gateway terms, and related services.
2. Confirm required notice procedures and the effective closure date.
3. Settle all legitimate open batches.
4. Determine how pending and future refunds will be handled.
5. Continue monitoring outstanding disputes and processor communications.
6. Download statements, transaction histories, tax records, and other records the business needs to retain.
7. Confirm reserve balances and applicable release terms.
8. Return leased, rented, loaned, or provider-owned equipment when required and keep shipping or delivery evidence.
9. Obtain written confirmation that the merchant account has been closed.
10. Review final statements and bank activity for remaining authorized adjustments or charges.

Termination provisions vary considerably. Some processor agreements expressly preserve obligations relating to fees, disputes, credits, equipment, or reserves after termination, which is why the merchant’s own documents—not generic online advice—must control the closure process.

Do not close the settlement bank account solely because card sales have stopped without understanding contractual obligations. Depending on the agreement, processors may still need to settle credits, collect valid chargebacks, release reserves, or make other permitted adjustments.

Similarly, do not assume a verbal conversation with a sales representative is sufficient notice. If the contract requires a particular cancellation method or written notice, follow it and retain proof.

Common Seasonal Merchant Account Mistakes and Off-Season Health Check

The biggest off-season mistakes are often administrative rather than technical.

One is assuming no sales means no bill. Another is ignoring statements because the business is closed. Merchants also create problems by letting contact information expire, missing PCI notices, forgetting gateway subscriptions, failing to monitor disputes, leaving old employees with system access, or storing terminals without basic inventory controls.

Another mistake is closing the account before considering refunds and chargebacks. What looks like a clean cost-saving measure can create customer-service and accounting problems if post-season transactions still need attention.

Waiting until the busiest week to request merchant account reactivation is equally risky. An account may need updated documents, new equipment, software configuration, or additional review.

Finally, merchants should never hide material changes in seasonal business payment processing. A new website, additional location, substantially different volume, or changed product mix can affect the account’s risk profile.

Use this off-season account health checklist:

Area	What to Verify
Account status	Active, suspended, restricted, dormant, or closed status
Monthly minimum	Whether one applies and what charges count toward it
Monthly fees	Which recurring charges continue
Gateway fees	Whether billing continues while unused
PCI status	Current validation requirements and outstanding actions
Refund access	Whether legitimate credits remain available
Chargeback access	Portal, notifications, records, and authorized contacts
Bank information	Correct settlement account and authorized ownership
Business/licensing records	Current information where applicable
Terminal security	Inventory, physical security, condition, and tamper check
User access	Current administrators and removal of unnecessary users
Reactivation process	Required steps and provider-specific lead time
Peak-season volume profile	Current forecast, ticket size, channels, and locations

A short quarterly review during the inactive period is often easier than reconstructing everything just before reopening. The purpose is not to create unnecessary work; it is to prevent small administrative changes from becoming sales-blocking problems.

Questions to Ask Your Processor Before the Off-Season

A processor should be able to explain how its specific contract and policies apply to the merchant’s seasonal pattern. Get important answers in writing where practical, especially when they affect billing, closure, suspension, or reactivation.

Ask:

• Does this merchant account have a monthly minimum?
• Which fees continue when processing volume is zero?
• Is there an inactivity or dormancy fee?
• What does your organization consider an inactive or dormant account?
• What can trigger a dormancy or underwriting review?
• Is a seasonal suspension or reduced-fee status available?
• What functionality remains available during suspension?
• Can refunds still be processed?
• How are open chargebacks handled?
• Does gateway, POS, equipment, or software billing continue?
• What is required to reactivate the account?
• Can reactivation involve underwriting again?
• How early should we begin your reactivation process?
• What documentation might be requested?
• Are reserves affected by inactivity or closure?
• What should we do if projected peak-season volume is materially higher?
• What should we report if locations, products, ownership, or sales channels change?
• What notice and equipment-return requirements apply to permanent closure?

The answers should drive the merchant’s keep, suspend, or close decision. A generic recommendation cannot substitute for those account-specific details because monthly minimums, inactivity fees, dormancy policies, suspension options, account closure fees, equipment obligations, merchant account underwriting reviews, reactivation procedures, reserve policies, and notice periods vary by processor, acquirer, sponsor bank, merchant category, risk profile, and contract.

Frequently Asked Questions

Conclusion

A seasonal merchant account deserves active management even when the business is not actively selling.

The core decision is whether the account should remain active, move into an available processor-supported seasonal status, or close completely. Each option can be reasonable, but each carries different costs, operational requirements, and reactivation consequences.

Start with the merchant agreement and current fee schedule. Determine whether a monthly minimum processing fee exists, identify fixed monthly charges, check gateway and equipment contracts, confirm PCI responsibilities, understand refund and chargeback procedures, and ask what the processor considers account dormancy.

Then calculate the true annual carrying cost instead of looking at one monthly statement:

Annual Carrying Cost = Monthly Fees + Minimum Shortfalls + Gateway/Software Fees + PCI/Compliance Fees + Equipment Costs + Other Contractual Charges

Compare that figure with the cost and risk of suspension or full reboarding. For businesses with brief but intense peak seasons, continuity and reliable opening-day processing may be worth more than the apparent savings from cancelling everything during the quiet months.

Most importantly, manage the account transparently. Accurately disclose seasonal transaction volume and material business changes. Do not generate artificial transactions, disguise products, process unrelated activity, or misrepresent expected sales merely to avoid a dormancy review.

A well-managed off-season should end with no surprises: the processor knows what the business does, the merchant understands its costs, payment systems remain secure, refunds and disputes are covered, and reactivation begins early enough to address legitimate account or underwriting requirements.

Informational disclaimer: This guide provides general educational information about seasonal payment processing and merchant account operations. It is not legal, financial, compliance, underwriting, or contract advice. 

Monthly minimums, inactivity fees, dormancy policies, suspension programs, closure procedures, equipment obligations, reactivation requirements, account closure fees, reserve arrangements, notice periods, and underwriting decisions vary by processor, acquirer, sponsor bank, merchant category, jurisdiction, risk profile, and individual agreement. 

Fireworks businesses should also verify applicable federal, state, and local requirements and current processor or sponsor-bank policies for their specific products, locations, and sales channels.