Mercury wants proof of US operations. What actually passes the review

Recognition: this is you if

The email said Mercury needs information to verify your account — something about a partner-bank transition — with a submission deadline attached. You uploaded what you had. Then a second letter arrived asking for proof of US business operations, with a sentence that reads like a verdict: “US operations are required to maintain your Mercury account.” And you are a non-resident founder whose whole structure is built on operating from outside the US.

You are not being singled out. This is a wave, and it is hitting legacy accounts in tranches while brand-new Mercury accounts continue to open normally. But the deadline is real, and the difference between passing and closing is mostly about which document you send — not how well you explain yourself.

Already rejected, or the deadline passed? The 72-hour playbook covers the sequence for a closing account — money out, records saved, and what never to write in a review thread. Start there, then come back for the fix.

Why this is happening now

Mercury is not a bank; it is software in front of partner banks that actually hold the deposits, and it has been migrating customers between those partners. A migration means every legacy account gets re-underwritten to the receiving bank’s standards — which is why founders who sailed through onboarding years ago are suddenly being asked to re-prove things nobody asked about at signup. The review is automated, batched, and impersonal. That is bad news for getting a human to sympathize, and good news in one narrow way: it means passing is about matching the checklist, not about your reputation.

The ladder: three letters, escalating

The wave runs in a recognizable sequence. First, a source-of-funds request: a non-Mercury bank statement, an invoice or contract, or a marketplace payout summary that explains where the money entering the account comes from. Second, the US-operations letter: documentation demonstrating current business activity in the United States. Third — if the reviewers reject what you sent — a stricter list: employment agreements with US-based staff, office leases, utility bills, or evidence of US customers, vendors, and suppliers.

Buried in the letters is the sentence that decides most outcomes: documentation “may need to be supported by corresponding transactional activity in your Mercury account.” The document alone is not the test. The reviewers cross-check it against the money actually moving through the account. A lease with no rent payments, a contractor agreement with no payouts, a customer contract with no matching deposits — each reads as paper produced for the review, and gets rejected as such.

What has been passing, and what keeps failing

The document with the best track record in this wave is a signed agreement with a US-based contractor whom you genuinely pay from the Mercury account — the contract and the payment history confirming each other. Records of sales to US customers help, but on their own they have been getting rejected far more often than founders expect. Office leases, co-working proof, photos of the space, and utility bills have mostly not been working, even when the lease is real.

That ranking is not arbitrary. A paid US contractor is recurring, verifiable activity inside the account itself. A lease is a document about a place the account never sees. If you are choosing what to build your response around, build it around the thing the account can corroborate — and if you engage a US contractor now, start the payments from Mercury before or with the submission, so the corroboration exists.

The tension nobody explains in the letter

Here is what makes this wave genuinely uncomfortable for non-resident founders: the structure most of you run — US LLC, all work performed outside the US — is built precisely on having no US presence, because presence is what creates US income-tax exposure. Mercury is now asking you to demonstrate the thing your structure is designed to avoid. The needle that threads this is the contractor-versus-employee distinction: an independent US contractor is the form of US activity that banks accept and that does not, by itself, convert your tax position the way US employees would. But this is exactly the kind of move to make deliberately, in the context of your whole structure — not improvised against a review deadline.

If the account closes anyway

Mercury closures in this wave have generally been orderly: the account closes and you are asked where to send the balance. The catastrophic version is not losing the account — it is having nowhere ready to receive payroll’s money when it happens. If you are inside the deadline window right now, opening the backup is more urgent than perfecting the appeal; the redundancy playbook covers what a real backup looks like, and the fintech-vs-real-bank data explains why the replacement for an operating buffer should be a chartered bank, not a third fintech.

And if this review has exposed that the structure itself was improvised — address from a formation package, no US activity the account can see, everything running through one fintech — that is a sequencing problem worth fixing once, properly. Mapping it to your situation is what the US banking for foreign founders page is for.