Stripe put my account "under review" and froze ~$14k (June 2026) - what actually works?

I publish illustrative scenarios prepared by my practice. All participants and conversations are fictional. The fictional posts are not posts by real users, accounts of client experiences, or reports of actual results.
Illustrative scenario prepared by my practice.
This discussion reflects member experiences as of 2026 and is general information, not legal advice. Verify current terms and consult a licensed attorney for your situation.

Key Takeaways

Dealing with Stripe reserve holds? I handle qualifying payment-processor disputes through the Demand Package, starting at $2,500.
Hypothetical question

Two weeks ago I got the dreaded email: account placed "under review," payouts paused, and there's about $14k sitting in my Stripe balance I can't touch. I run a small B2B SaaS, mostly monthly subscriptions, and I've been on Stripe for almost three years with basically no chargebacks. No warning, no specific reason given beyond the generic risk language.

I uploaded everything they asked for in the dashboard form (business details, recent invoices, a couple customer contracts) and now I'm just... waiting. Support keeps replying with the same canned message that the review can take up to 90 days.

I'm trying to figure out what actually moves the needle here vs. what's a waste of energy. Has anyone gotten funds released faster by sending a specific kind of documentation? Did a demand letter or a lawyer letter help, or did it just annoy them? And what's the deal with the 90-180 day reserve I keep reading about? Any real experiences appreciated.

Illustrative response

Been there last year. The single biggest thing that helped me was sending proof that I actually deliver the service, not just that the business exists. They're mostly worried you'll take the money and disappear and they'll eat the refunds/chargebacks.

What I uploaded: signed customer agreements, screenshots of active accounts/logins for those customers, fulfillment timestamps, and a short written explanation of my refund policy and churn. The narrative mattered as much as the docs.

Illustrative response

Clarifying question because it changes the advice a lot: did they say the account is being closed/terminated, or just "under review" with funds held? Those are different situations. A review can resolve in your favor with funds released. A closure usually triggers the reserve/hold-period language.

Also do you have any recent spike in volume, new product, or a batch of annual prepays? That's often what trips the automated risk flag, and explaining the spike directly tends to help.

Illustrative response

Good question. The email says "under review," not closed. And yes, now that you mention it, I switched on annual billing in April and had three customers prepay a full year right before this happened. That probably looks like a volume spike to their model.

I'll write up a short explanation of the annual-prepay change and attach those three contracts specifically. Hadn't thought to call it out directly.

Illustrative response

The annual prepay thing is almost certainly it. Processors hate prepaid future-delivery revenue because if you fold, every one of those customers can dispute and they're on the hook.

When this happened to me I sent a delivery schedule showing exactly what each prepaid customer gets and when, plus the fact that my churn is low and refunds are rare. Framing it as "this is recurring delivered software, not a future promise" is the move.

Illustrative response

One practical thing nobody mentions: keep all your communication inside the official support channels and in writing. If you call and get a verbal "it'll be fine," follow up with an email summarizing what they said. You want a paper trail if this drags on.

Also screenshot your dashboard balance and the review notice now, with dates. If the number changes or the notice disappears later you'll want the record.

Illustrative response

And to OP's likely next question, if it converts to a reserve, watch whether it's "rolling" or "fixed." In my case it released automatically but "the end" was a moving target because each day's batch had its own 120-day clock, so money trickled out rather than one big release.

Read your notice carefully for those two words. Totally different cash-flow situation and people confuse them all the time.

Illustrative response

On the arbitration point since OP mentioned it: the Stripe Services Agreement has historically included an arbitration clause and a class-action waiver for US users, with some carve-outs. Worth actually opening the current version and finding that section rather than relying on what people remember, because they update the terms.

Practically, arbitration is a real lever but it's slow and has its own fees, so most people treat it as the last resort after the documentation route and a formal written demand have failed.

Illustrative response

Timeline as requested. SaaS, ~$22k held, "under review" on May 5. Uploaded: incorporation docs, last 6 months of invoices, three signed customer MSAs, a one-page churn/refund summary, and a written explanation of a usage spike. Resubmitted the same day they asked a second time.

Funds released June 9, so about 35 days. No reserve imposed in the end. Honestly I think the churn/refund summary did the heavy lifting because it directly answered their actual fear.

Illustrative response

Counterpoint so OP has the full picture: not every story ends well. Mine got reviewed, then they decided to close the account and held the balance under the reserve language for the full period for potential chargebacks. I got it eventually but it was painful and there wasn't really a button to push to speed it up.

What I wish I'd done earlier: had a backup processor already set up (not started mid-review, set up before any trouble) so the business kept running while the money was stuck. The cash being frozen hurt less than not being able to bill at all.

Illustrative response

Something nobody told me: even with payouts paused, double-check what's happening with your in-flight subscriptions and refunds. I had refunds I needed to issue and the held balance complicated it. Sort out how you'll handle customer refunds during the freeze so you don't generate chargebacks, which is the exact thing that makes them extend a hold.

Proactively refunding anyone who's unhappy (out of band if you have to) keeps your dispute rate down while you're under the microscope.

Illustrative response

Day 33 update. They finally responded, but not with a release: it's a reserve offer, 50% rolling for 6 months. That math genuinely doesn't work for us, we'd be floating half of every payout for half a year.

For anyone who's been through this: do you just accept it to get moving, or is countering a real option that doesn't restart the whole review?

Illustrative response

We countered ours in May. They opened at 50/180 like yours, we replied in the dashboard thread with three months of refund and chargeback data and proposed 25% for 90 days, and they accepted the counter about a week later. One data point, not a promise, but no, countering did not restart anything for us. It stayed with the same reviewer as far as I could tell.

Make the counter about numbers, not fairness. Show the dispute rate.

Illustrative response

Just take the offer man, it doesn't matter anyway because legally they can only hold funds 90 days max, it's a payment processing regulation. After 90 days they have to release everything no matter what the agreement says, so the 6 month reserve is unenforceable.

Illustrative response

I need to flag that because people make real decisions off comments like this: there is no universal rule capping processor holds at 90 days. General info, not legal advice. The operative document is the services agreement you accepted, and processor agreements typically permit reserves and extended holds tied to risk findings, chargeback windows, and liability exposure, which can lawfully run longer than 90 days. People repeat the 90-day number because some holds and internal policies use that window, but it is not a legal ceiling someone can wave at a risk team.

The counter route described above is the sane one: respond in writing, with data, inside the same thread. A reserve negotiation is a business conversation supported by your numbers. If what comes back is unworkable and funds sit with no findings, that's when it's worth having the agreement and the correspondence reviewed properly.

Illustrative response

Countered this morning: 25% for 90 days, attached a 12-month chargeback report (0.3%) and refund rate. Politely declined the 50/180 in the same dashboard thread. Watch this space, and thanks Marge, the "numbers not fairness" framing is how I wrote the whole thing.