What to Do When Your US Business Bank Account Gets Shut Down (2026 Guide for Non-Resident Founders)

Comparison asset 4 of 4 · Cross-provider playbook for Mercury, Wise, Stripe, PayPal, and the MoRs

The short version: a freeze is a process, not a verdict. Most holds resolve; what determines yours is the evidence you can produce, the speed you produce it, and whether you built redundancy before you needed it. This guide covers the first 24 hours, the appeals playbook per provider type, routing revenue while frozen, and — most importantly — the prevention posture that makes the whole guide unnecessary.

One rule before anything: never lie in an appeal. Not about your location, your model, or your flows. A hold with honest answers usually ends; a hold that catches a misrepresentation becomes a permanent closure everywhere that provider's data reaches.

Seven providers, 1,692 complaints: what the public record shows

Most writing about fintech account closures runs on anecdote — a forum thread, a viral post, a friend of a friend. We pulled the public record instead.

The US Consumer Financial Protection Bureau publishes every complaint filed against a financial company, with the consumer's narrative and the company's response attached. We downloaded seven providers' complete records and filtered each for freeze, closure, hold, verification and business-account language, using the same filter on every one.

1,692 usable complaints. Here is what they show.

The headline table

Two things jump out.

Mercury has the highest closure share of any provider here by a wide margin. 55% of its filtered complaints concern account closure, against 38% at Relay and 14% at Wise. And 47 of Mercury's 116 — 40% of the whole set — are specifically about funds not returned after a closure.

Juno has almost none. Three closure complaints out of 118. Its record is overwhelmingly about deposits and withdrawals: 94 of 118 filings.

The patterns, side by side

We counted the same phrases across every provider's narratives.

Juno's profile is unusual and worth a note. 44 of 118 filings describe no reason being given — proportionally the highest here — while only 2 involve a document request. That combination suggests decisions communicated without explanation and without an opportunity to respond, rather than a review process the customer could engage with.

Current cites fraud or risk in 110 of 481 filings — proportionally the highest of the large sets.

What this tells you about choosing a provider

Closure risk and transaction risk are different problems, and providers specialise.

Mercury and Relay are US business banks operating through partner banks. Their complaint records are dominated by closures and by money not coming back. That is the risk profile of a bank that is making compliance decisions about whether you should be a customer at all.

Wise, Current and Revolut are payments businesses. Their records are dominated by transactions that failed, money that did not arrive when promised, and fraud. That is the risk profile of a rail rather than a vault.

Neither is safer. They fail differently, and the failure that matters depends on what you are using the account for. If you hold a balance, closure risk is what should worry you. If you move money, transaction risk is.

The one number that applies to all seven

Across 1,692 complaints, 1,562 were closed with an explanation — 92%. Money changed hands in 125 cases, roughly 7%.

Filing a complaint usually produces a reason, not a different outcome.

That is worth knowing before you plan around it. The CFPB complaint process is a good way to get a company to explain itself in writing. It is not a mechanism for getting your account back.

What to actually do

Every provider on this page has a complaint record. That is what a regulated financial business looks like from the outside, and a provider with no complaint record is usually one with no customers.

The response is the same regardless of which you pick.

Two rails, always. Not as a hedge against a bad provider — as a hedge against a compliance decision you cannot appeal. Configure the second account before you need it.

Two to four weeks of operating expenses maximum in any single fintech. Sweep the rest weekly. Mercury's 47 "funds not received" filings are the argument.

Be able to evidence any large inbound payment. Across the seven providers, 222 filings involve a document request. The contract, the invoice, the platform record.

Know how your money would come back. Ten Mercury filings and seven Novo filings mention a cheque being posted. If you have no US mailing address, that turns a closure into a much longer problem.

Where this data comes from, and its limits

The CFPB Consumer Complaint Database is a public record. Anyone can search it at consumerfinance.gov. Complaints are published with the consumer's narrative and the company's response, personal details redacted.

Four limits, and they matter for every number above.

Complaint data comes only from dissatisfied customers. Nobody files a complaint about an account that works. This measures what goes wrong, not how often it goes wrong.

Complaint counts are not comparable across providers without customer numbers, and we do not have them. Wise has 734 filings and Found has 30. That difference is mostly the difference in customer base. This is why we have shown the shape of each record — closure share, pattern counts — rather than ranking providers by volume.

Some proportion of any complaint set involves accounts closed for genuine cause. We cannot distinguish those and have not tried.

And the CFPB is a US consumer protection body. Most of the people reading this live outside the United States, are less likely to know it exists, and may not believe they can file. This record under-represents our own readers, and probably substantially.

Seven providers, 1,692 filtered complaints, data current to August 2026. Next review: February 2027.

Part 1 — The first 24 hours

1. Read the notice precisely. "Payouts paused pending review" ≠ "account closed" ≠ "funds held 60/180 days." Each has a different playbook. Screenshot everything, note timestamps, and start a written log — appeals are won on documentation discipline.

2. Diagnose the trigger before responding. Almost every freeze traces to one of six causes: an inflow spike, a chargeback/dispute cluster, a KYC mismatch (name, address, document expiry), a location/IP signal, a category concern, or an unanswered verification request. Look at what changed in the 30 days before the freeze — that's usually the answer, and your response should address that, not a generic plea.

3. Do not do these things:

• Don't spray reapplications from the same entity — auto-rejections harden the record (documented pattern at Mercury and Stripe).
• Don't open a "fresh" account with altered details to dodge the freeze — that converts a compliance review into a misrepresentation finding.
• Don't threaten or escalate emotionally in the first message. The person reading it processes hundreds of these; be the file that's easy to approve.
• Don't move money in ways that look like evasion — rapid transfers out of connected accounts during a review extend reviews.

4. Respond same-day with a complete evidence pack (Part 2). Speed matters: reviews resolve in the order files become complete, and founders who respond in hours consistently report shorter holds than founders who respond in days.

Part 2 — The evidence pack

Build this before any freeze; keep it in one folder, current, because during a freeze you assemble it under pressure.

Identity & entity: passport; formation documents; EIN letter (CP-575 or 147C); operating agreement; a Certificate of Good Standing (order fresh — an administratively dissolved entity mid-review is fatal and fixable in advance).

Business reality: live website with policy pages; invoices and signed contracts behind your largest recent payments; supplier agreements; platform statements (Upwork/Amazon/Stripe) showing income provenance.

Delivery proof (processors especially): tracking and delivery confirmations for physical goods; usage logs/access records for SaaS; deliverable sign-offs for services. This is the deciding evidence at Stripe and PayPal — funds are refunded to customers when delivery can't be shown, and released when it can.

Money-flow coherence: bank statements for the accounts feeding and receiving; a one-paragraph plain-English explanation of your flow of funds that matches what onboarding was told. If a spike triggered the review, the contract or campaign behind the spike is the single document that ends it.

Part 3 — The playbook by provider type

Fintech banks (Mercury, Relay, Bluevine, Slash): email-queue processes with no phone line; expect days per round-trip, so make the first reply complete. Mercury's known endgame if offboarded: ~60-day hold, funds by paper check — if it reaches that, immediately confirm a mailing address where a US check can land and ask (politely, in writing) about wire/ACH disbursement alternatives. [VERIFY: disbursement flexibility is inconsistently reported.] Fintech offboarding decisions rarely reverse; the realistic goal is fast, complete fund return, not reinstatement. Direct energy accordingly.

EMIs (Wise, Payoneer): document-driven and comparatively mechanical — the named triggers (spikes, mismatches, restricted-term references in payment descriptions) map to named fixes. Typical clean-case resolution: 3–7 business days, longer when source-of-funds is disputed. Provide the invoice + contract + platform record for the exact flagged transfers, fix the underlying mismatch (name spelling, expired document), and answer only what's asked, completely.

Processors (Stripe, PayPal): the stakes are different — closure can mean customer refunds (Stripe, ~5 days post-closure) and liability that survives closure (both). Priorities: (1) delivery evidence on every disputed/flagged charge, same day; (2) chargeback ratio math — show it below 1% or show the concrete fix (descriptor clarity, refund policy, fulfilment change); (3) if a reserve is imposed rather than closure, treat it as a win and operate through it — reserves release with clean months. PayPal-specific: upload tracking on everything immediately; its own release mechanics reward delivery confirmation. If closure stands, funds typically release at the stated horizon (up to 180 days) less disputes — calendar it, keep the entity alive and mail monitored until then.

MoRs (Paddle, Lemon Squeezy, Polar, Dodo): the platform is the seller, so their exposure is direct and their appeals narrow. Cite their own Merchant Acceptance Policy clause-by-clause in your response — the closure notice usually names a violation; rebut it specifically or accept it and negotiate fund release. Expect the 120–180-day hold horizon regardless of outcome; the appeal shortens it only when the violation claim is factually wrong and you can show it.

Traditional banks (Chase, BofA): usually a mailed KYC-refresh you never saw. Call the branch, ask exactly what's outstanding, supply it — human escalation exists here and works. Prevention is a monitored mail address; cure is a phone call. This tier is the easiest to fix and the easiest to have prevented.

Part 4 — Operating while frozen

Revenue rerouting, by what froze:

• Bank frozen → repoint Stripe/marketplace payouts to your second rail (this is why it exists). New payout accounts verify in days — start immediately.
• Stripe frozen → activate the dormant backup: PayPal for card capture short-term, an MoR for digital goods (onboarding in days, no LLC needed), the high-risk tier if category was the cause and you hold an ITIN.
• PayPal frozen → it was your trust layer, not your treasury (if you followed the reviews) — card volume continues on Stripe.
• MoR frozen → a second MoR onboards fastest; longer-term, this is the push to the US-LLC + Stripe migration.

Cash triage: the freeze locks a balance, not your obligations. Sequence: payroll/contractors → suppliers keeping revenue moving → everything else negotiated. A two-line note to affected counterparties ("payment provider compliance review, funds expected by X, here's our revised date") preserves more relationships than silence.

Legal escalation — when and what: for large balances past stated horizons, or non-response measured in weeks: (US providers) a written complaint to the CFPB produces a tracked, deadline-bound response and is free; formal demand letters from US counsel move some files; arbitration per the provider's terms is the endgame for large sums. Escalate in that order — regulator complaint first, it's the best effort-to-effect ratio. [VERIFY: CFPB coverage varies by product type; EMI complaints may route to state regulators or the provider's home regulator.]

Part 5 — Prevention (the part that matters)

Everything above is triage. This is the architecture:

1. Two rails from day one — operating fintech + second rail live and tested, traditional-bank vault when travel allows.
2. Sweep weekly — 2–4 weeks of operating cash in any single fintech, maximum. Money withdrawn cannot be held.
3. Dormant backup processor — a configured MoR account (free to hold) turns a Stripe closure from catastrophe into a bad week.
4. Evidence folder, always current — Part 2, maintained monthly, not assembled mid-crisis.
5. Consistency discipline — same name spelling, same address, same business description everywhere; update providers when anything changes before their systems notice.
6. Warn before spikes — a launch, a big contract, a flash sale: tell your processor in advance. A predicted spike is growth; a surprise spike is a fraud signal.
7. Watch the 1% chargeback line monthly — it's the tripwire for every card rail you use.
8. Monitored US mail — the traditional-bank killer is the unseen KYC letter; the fintech-offboarding killer is the unreceivable paper check. One monitored address solves both.
9. Answer every verification request the day it arrives — non-response is the one trigger with no defence.
10. Never let one provider hold a month of runway — the concentration test that decides whether a freeze is an inconvenience or an extinction event.

[CLIENT STORY PLACEHOLDER: a founder who survived a freeze cleanly *because* the second rail and evidence folder existed — the before/after of prevention. And one who learned it the hard way first. The pair makes the argument better than either alone.]

This guide reflects provider terms and consistently reported founder experiences as of July 2026. Hold durations, appeal channels, and disbursement practices vary by provider and case — items marked [VERIFY] need confirmation, and nothing here is legal advice; for large frozen balances consult a US attorney. Individual reported cases represent one party's account. We are not affiliated with any provider named.