Merchant account frozen at peak season? Causes and how to avoid it

A merchant account frozen in December usually starts with something that looked like good news: more orders, bigger orders, all at once. Peak season doesn't invent new risks. It packs three classic freeze triggers into November and December (volume outside what you were underwritten for, fraud and card testing, and deliveries that slip), and then a fourth arrives in January, when holiday disputes land against a much smaller month of sales.

Many "freezes" are something narrower: a reserve working as written, a payout hold during a review, or a bank holiday.

Settlement missing today? Start with what to do right now. For year-round prevention, see how to keep your high-risk account from getting frozen.

Why merchant accounts get frozen at peak season

When a customer disputes a card payment, the cardholder's bank takes the money back through the card network from the acquirer (the bank that sponsors your card processing), and the acquirer recovers it from you. If you can't cover it, the acquirer takes the loss. Holds, reserves and freezes are how processors and acquirers manage that exposure, and merchant agreements commonly permit them.

Peak season raises the exposure in four ways:

1. Volume and tickets outside your normal. A week at three times your usual volume, or orders far above your usual ticket, can start a review even when every sale is real.
2. Fraud and card testing. Stolen cards hide in holiday traffic, and every fraud report counts against you later.
3. Slipping delivery. Carriers and warehouses fall behind, and "item not received" disputes follow.
4. The January arithmetic. Disputes count in the month they arrive, so holiday disputes land in January and February, when sales are lower.

The first three hit during the rush. The fourth is why a hold or a new reserve can arrive in February.

If your settlement is missing right now

The words get used interchangeably, but each ends differently.

Check the calendar first

Settlement is counted in business days, and Federal Reserve holidays aren't business days. This season the Federal Reserve observes Thanksgiving (Thursday, November 26, 2026), Christmas (Friday, December 25), New Year's Day (Friday, January 1, 2027) and Martin Luther King Jr. Day (Monday, January 18), according to its holiday schedule. On a one-business-day schedule, a batch closed on Thursday, December 24 can't arrive before Monday, December 28.

What to do today

1. Compare the missing amount with your reserve. If it matches your reserve percentage, the reserve is doing what the contract says. If the whole settlement is missing, a review is running.
2. Get the reason in writing. Ask what triggered the hold, which documents would close it, who is handling it and when to expect a decision.
3. Send documents the same day. Typical requests: supplier invoices, proof of inventory, tracking reports, your refund policy and recent bank statements.
4. Keep shipping and keep refunding. Pausing fulfillment to protect cash creates exactly the "not received" disputes that make a review go badly.
5. Read your merchant agreement. Hold and reserve periods come from the agreement, and vendor guides commonly mention up to 180 days or more. If the terms are unclear, ask your attorney.

More on reading reserve terms in the reserves and holds hub.

Trigger one: volume and tickets outside your underwritten normal

When you were approved, your processor recorded what your business looks like: expected monthly volume, average ticket, likely largest ticket, what you sell, how fast you deliver and how you handle refunds. Many agreements set ticket size and monthly volume limits, and going past them is a commonly cited hold trigger.

Risk monitoring typically compares you with your own profile, not with the season. The National Retail Federation forecasts November-December 2026 retail sales up 4.2% over 2025, to $1.013 trillion. A merchant whose volume triples in a week stands out against that, and against its own history.

New products do the same: gift cards, preorders or a holiday subscription box create a mismatch between what you were approved for and what is coming through.

Send a pre-peak note by Friday, November 20

Give your processor a plan to compare against:

Subject: Holiday volume plan for [business name], merchant ID [number]

We expect November card volume of about $[X] and December of about $[Y], against our usual $[Z] a month. Our average ticket should stay near $[A], and our largest orders will be around $[B] (gift sets and bundles). Promotions run from Black Friday, November 27, through Cyber Monday, November 30, with a second sale December 10-14. New this season: [gift cards / preorders / nothing]. Our last ship date for Christmas delivery is December [date]. Our refund policy is unchanged. [Name] is the contact for any questions, at [phone].

Then stick to the plan or update it. A note that says double and a month that does four times is a new conversation.

Trigger two: fraud and card testing during the rush

Every fraud report becomes part of the ratio the networks and your acquirer watch.

On Visa, that ratio belongs to the Visa Acquirer Monitoring Program (VAMP), which in 2025 absorbed Visa's separate fraud and dispute programs. It counts fraud reports (TC40) plus disputes (TC15) and divides by settled card-not-present transactions. That has consequences merchants often miss:

• Refunding a fraud order doesn't erase it. Processor guidance notes that issuers must report possible fraud on a captured payment even if it was refunded, and that Visa counts those reports whatever their outcome.
• One payment can count twice. By the same guidance, a fraudulent payment that is reported and then disputed appears in both TC40 and TC15, and Visa counts it twice.
• Winning doesn't remove the count. Mastercard counts a chargeback regardless of a refund, a 3DS liability shift or the outcome.
• 3-D Secure protects your margin more than your ratio. It shifts liability for eligible fraud chargebacks to the issuer, and on Visa a fully authenticated payment generally can't be disputed as fraud (outside some US high-risk categories), but the issuer still reports the fraud and Visa still counts that report.

Visa's fact sheet lists two exclusions: disputes resolved through pre-dispute services, and fraud reports that qualified for Compelling Evidence 3.0.

Card testing

Card testing is a burst of small authorization attempts that uses stolen card numbers to find the live ones. VAMP measures it separately, at an enumeration ratio of 20% of all authorizations together with at least 300,000 enumerated attempts in a month. Few small merchants reach that count, but a testing run still shows up as a spike in declines, and as fraud reports later if test charges are captured. Either can prompt a review.

The signs: bursts of $1 or $0 authorizations, a decline rate several times your normal, and many cards from one IP address or device. Before the rush, cap attempts per card, email address and IP address, block retries after a few declines, require CVV and address matches, and decide which orders get 3-D Secure or a manual look. Check your decline rate daily through December.

Trigger three: late deliveries and the FTC's 30-day rule

"Item not received" is the classic holiday dispute, and US federal law tells you what to do when orders slip. The FTC's Mail, Internet, or Telephone Order Merchandise Rule (16 CFR Part 435) covers merchandise (not services) ordered online, by mail or by phone, with a few exemptions such as C.O.D. orders.

• The ship-by rule. You need a reasonable basis to ship within the time you state, or within 30 days of a properly completed order if you state none (50 days if the buyer applies to you for credit to pay for it). The FTC's business guide asks whether, for promotions in busy sales seasons, your fulfillment can handle the total demand you expect.
• The delay notice. If you can't ship on time, you must tell the buyer by the promised ship date and offer a choice: accept the delay or cancel for a prompt refund, with a way to reply at your expense.
• Short and long delays. If your first delay notice gives a new date 30 days or less late and says silence means consent, the buyer's silence counts; any further delay needs express agreement. If the new date is more than 30 days late, or you can't give one, the order is cancelled automatically unless you ship within 30 days of the original date or the buyer expressly agrees to wait.
• Prompt refunds. For card payments, a prompt refund generally means sending the credit within seven working days of the buyer becoming entitled to it.

This is general information, not legal advice; ask your attorney how the rule applies to you.

Why it matters for disputes

A delay notice with a refund option turns a would-be dispute into a cancellation you control. Without one, the window is long. Under the current Visa Core Rules (October 2026 edition), a merchandise or services not received dispute (condition 13.1) can be filed up to 120 days after the processing date, or up to 120 days after the last date the cardholder expected delivery, but never more than 540 days after processing.

As arithmetic, not a rule: an order promised for December 22, 2026 could be disputed as not received until about April 21, 2027. Processor guidance adds the basics: show shipping times before checkout, ship with tracking, take a signature on high-value orders, and mark backordered items.

The January arithmetic: why ratios peak after the season

Visa and Mastercard both assign a dispute to the month they receive it, not the month of the sale. Visa divides by the same month's transactions, Mastercard by the previous month's. Either way, disputes on December's sales land in January and February, when sales have dropped.

The thresholds in force this season

Visa figures are from Visa's fact sheet, where the merchant line applies only while the acquirer's portfolio isn't flagged; Mastercard figures are as reported by processors. All are as of November 2026, so confirm yours with your acquirer.

Visa's US merchant line dropped from 2.2% to 1.5% on April 1, 2026; the 0.9% figure many articles still quote belongs to the retired Visa Dispute Monitoring Program. Visa also judges the acquirer's whole portfolio at 0.5% and 0.7%. Our reading: an acquirer watching its book at those levels has reason to act on a merchant long before 1.5%, and staying under 1,500 a month isn't a safe harbor, since that line depends on the acquirer's portfolio and processor documentation lists a lower 0.5% merchant tier. For most small merchants, the acquirer's limit is the one that bites.

A worked example (hypothetical)

Say a merchant's Mastercard numbers are 6,000 transactions in November, 9,000 in December, 3,000 in January and 2,500 in February, with 20 chargebacks received in December, 45 in January and 60 in February.

The business did nothing differently, yet its Mastercard-style ratio in February is six times December's. With 60 chargebacks it is under the ECM count of 100, so Mastercard's monitoring program doesn't flag it. But at an assumed $95 average, February's chargebacks total $5,700, which with a 2.4% same-month ratio meets the MATCH reason code 04 criteria, the ones that count if the acquirer terminates the account. A MATCH listing stays visible to other acquirers for five years, and later wins don't change it.

Run your own figures in the chargeback ratio calculator, which shows both denominators side by side, and see the chargebacks hub for the fixes that bring a ratio down.

A dated checklist for the 2026 season

Before Thanksgiving (by November 20)

• Send the pre-peak note and ask who your contact is if a review starts.
• Read your agreement for reserve terms, volume and ticket limits, and how holds are communicated.
• Put the usual review documents in one folder.
• Make sure customers will recognize your statement descriptor, the name on their card statement.
• Set fraud rules and attempt limits, and decide where 3-D Secure runs.
• Put realistic ship dates on product pages and set a last order date for Christmas delivery.

Black Friday (November 27) to Christmas

• Compare daily volume and tickets with your plan, and warn your processor early if you'll exceed it.
• Send delay notices before promised ship dates, with a cancel-and-refund option.
• Refund quickly when customers ask, before they go to their bank.
• Answer document requests the same day.

January through April

• Track disputes weekly against both denominators, not once a month.
• Expect holiday disputes to keep arriving: by the 120-day arithmetic, until about the end of April for orders due in late December.
• Respond to every dispute and process returns promptly.
• Keep part of December's revenue as a cash buffer in case a reserve is added in February.

How Flux approaches peak-season risk

Flux won't promise that an account is never held. Flux has acquirer and card-network obligations, so there are situations where it has to ask for documents or hold funds while a review runs. What it commits to is how that goes.

• A person who knows your normal. Every business gets its own merchant account, and a person reviews every application. When something looks unusual, the commitment is "a question before you get an action, whenever the choice is ours." Send your peak plan ahead.
• Fraud rules you control. Flux fraud detection scores each transaction as it comes in and flags or blocks the risky ones before they settle, using rules you set.
• 3-D Secure where you want it. Flux supports it on hosted checkout (hosted fields), payment links and invoices, and you choose every card payment or only riskier ones. The liability shift covers eligible fraud chargebacks only.
• Visibility. Webhooks send real-time notifications for every payment, refund, dispute and settlement, and the dashboard shows payments as they happen. Card payments typically settle within 1-2 business days.

Planning a big season? Email sales@fluxpayments.com or call (813) 402-8244.