Your processor is holding your money in a reserve or hold to cover the risk that a customer disputes a charge after you already have the funds, and it is generally legal because it is written into the terms you agreed to. Holds are triggered by things like a chargeback spike, a sudden jump in volume, suspected fraud, or a product the risk model flags, and aggregators apply them most aggressively because they never underwrote you up front.
The short answer first
Your processor is holding your money to protect itself against chargebacks and refunds that could land after you already have the cash, and it is generally legal because the right to hold funds is written into the terms you agreed to when you signed up. The hold is a risk tool, not a punishment, even though it rarely feels that way when payroll is due.
The reason it feels so arbitrary is timing. Aggregators like Stripe and Square apply holds most aggressively and with the least warning, because the hold is often the first underwriting they ever do on your account. A real merchant account answers the risk question up front, which is why this article ends with the version of payments where surprise holds are the exception, not the design.
What a reserve actually is
A reserve is a portion of your funds that the processor holds back to cover potential losses. When a customer disputes a charge, the issuing bank pulls that money back, and the processor is on the hook if your account cannot cover it. The reserve is their cushion against that scenario.
This matters because of how disputes work. A cardholder generally has 120 days from the transaction or expected delivery date to file a dispute, and certain reason codes can stretch all the way to 540 days. So a sale you made months ago can still come back as a chargeback, and the reserve is the processor's way of staying covered across that long tail of risk.
The three kinds of holds
A rolling reserve holds back a percentage of each day's sales and releases it on a set schedule, often after 90 to 180 days, so the reserve keeps rolling as new sales come in and old ones release. This is the most common structure for ongoing risk.
An upfront reserve is set aside at the start, before or as you begin processing, so the cushion exists from day one. A minimum or capped reserve holds funds up to a fixed ceiling and stops once that ceiling is reached. None of these are inherently unfair. The fairness lives entirely in whether the terms were disclosed and explained, or applied suddenly after a flag.
On an aggregator, you most often meet the reserve as a surprise: a sudden hold applied by a risk model with a vague reason and a term you never negotiated. On a true merchant account, a reserve, if one is needed at all, is set as part of underwriting with terms you can read and a person who can walk you through them.
Why the hold landed on you
Holds are triggered by a handful of risk signals: a chargeback ratio climbing toward the card networks' thresholds, a sudden spike in volume, suspected fraud, a prohibited or misrepresented business type, or simple underwriting gaps where the processor does not yet understand your business.
A volume spike is the one that catches honest merchants most often. A great sales week, a viral product, or a busy season can look identical to fraud from the outside, and an aggregator's model cannot tell the difference because it never underwrote you. That is why the freeze so often arrives at your best moment, which is also your most painful one.
How long it lasts and how to shorten it
Holds commonly run around 90 days and can reach 180, because that window matches the period during which most disputes can still arrive. There is generally no fixed legal cap shorter than that, which is why pinning down a committed release date in writing matters so much.
To shorten an active hold, respond to every verification request the same day, keep all communication in writing, send invoices, proof of delivery, your refund policy, and supplier records, and ask repeatedly for the specific reason and the exact release date while referencing your prior case numbers. Prompt, complete documentation is the most reliable lever you have.
The version where this does not happen
The durable fix is a merchant account underwritten to your business before you process, so the risk question is answered up front and there is no need for a surprise hold to undo a decision after the fact. You also get a human to call, which means a volume spike can be explained in a phone call instead of locked behind a template email.
Send me your last statement through my free statement review and I will tell you whether you are on an aggregator or a real account, and what a stable setup looks like for your volume, backed by North, a true processor serving more than 350,000 merchants since 1992. If a hold is active right now, my articles on recovering a Stripe freeze and on your options after a Square deactivation walk through the recovery steps, and the aggregator-versus-merchant comparison tool on my rates page shows the structural difference for your own numbers.
Want this read for your own statement?
Send your last processing statement and Alex will show you your true effective rate, what is interchange, and what is pure markup. It costs nothing either way.
