Why payment processors freeze your account

Why processors freeze instead of just terminating

A processor freezes your funds when it thinks future chargebacks might exceed what you have on deposit. If they terminate you and pay out your balance, and disputes roll in for the next six months, they eat those losses. So they hold your money as insurance. That's the whole logic. It's not personal and it's not punishment. It's their risk team protecting their balance sheet with your working capital.

The problem is the timeline. A typical hold runs 90 to 180 days, because that's how long a cardholder has to file a dispute. For a business doing real volume, that's a quarter of revenue locked up while your ads, staff, and suppliers still need paying.

Reason one: your chargeback ratio moved

This is the most common trigger. Card networks put merchants into monitoring programs when disputes pass roughly 0.9% of transactions. Your processor gets fined when you cross that line, so they act before you reach it. In high-risk verticals the baseline dispute rate is already close to the threshold. A gambling operator gets disputes from losing players. A forex broker gets them from traders who blew up an account. One bad week of disputes can move a monthly ratio enough to trip an automated hold.

Note that winning disputes doesn't help here. The ratio counts filed disputes, not outcomes. You can win 90% of them and still get frozen.

Reason two: your volume spiked

You were approved at a stated monthly volume. Then a campaign worked, or a market moved, and you did triple that. To a risk system, a volume spike looks identical to a merchant about to take the money and run. Sudden growth is one of the fastest ways to get flagged, and it always happens at the worst possible time, because the frozen balance is your biggest month ever.

Reason three: underwriting caught up with you

Stripe and PayPal approve first and review later. Plenty of CBD and gaming merchants process for months before a human looks at the account, sees the category, and applies the policy that existed all along. The approval was never a decision to accept your business. It was a decision to defer looking at it. We cover the full termination pattern in why high-risk merchants get dropped.

Reason four: something looked like fraud

Mismatched billing descriptors, a burst of foreign cards, average tickets that jump from $50 to $500, refunds issued to cards that never bought anything. Any of these can trip a model. Most of the time you have an innocent explanation. You rarely get asked for it before the hold lands.

What to look for in a processor that won't pull this

First, real underwriting up front. A processor that asks hard questions before approving you has already priced in your category. It won't be surprised by you later. Instant approval is a warning sign, not a convenience.

Second, reserve terms in writing. Ask what triggers a hold, how large a reserve can get, and how release timing works. If the answer is a vague pointer to the terms of service, the answer is that they can hold whatever they want for as long as they want.

Third, a named human. When a hold happens, an account manager who knows your business can resolve in days what a ticket queue resolves in months.

Fourth, evidence they know your vertical. A processor that already serves exchanges, brokers, gambling operators, or CBD brands has seen your dispute patterns before. Your normal won't look like their emergency.

Fifth, settlement speed. The shorter the gap between a customer paying and money reaching an account you control, the less there is to freeze. This is where crypto settlement changes the math entirely: funds that are final on-chain in minutes can't sit in someone's reserve for six months.

The short version

Freezes come from chargeback math, growth that looks like risk, and underwriting that happens after approval instead of before. You can't remove those mechanics from card processing. You can pick processors that underwrite honestly, and you can keep part of your volume on rails where holds aren't possible.

We built Flint to solve this problem.