What a “proof of operations” email means and how to answer it

Recognition: this is you if

The email arrived out of nowhere, and the subject line alone made your stomach drop. Every instinct says answer immediately, in whatever words come first, just to make it go away. Wise, Mercury, and Revolut have all sent this exact email before — to founders who wrote back fast, in a panic, and then watched the account close anyway.

The email is not the closure. It is a fork in the road, and the reply you send is what decides which branch you take. Which is why the worst thing you can do is treat it as an emergency to be resolved in the next five minutes with the first thing that comes to mind.

What the bank or fintech is actually asking for

Underneath the generic subject line, a proof-of-operations request is usually a substance ask: prove an address, show a transaction history, produce an invoice or contract, provide a document that demonstrates the business does what you said it does. Sometimes the document they want is itself gated behind another document you do not have yet, which is what makes these so stressful — the ask can be genuinely hard to satisfy even when nothing is wrong. The loudest current example is Mercury’s 2026 re-verification wave; what actually passes that review is its own playbook.

Read it for what it is: a request for evidence that your operations match what you declared at onboarding. It is not, by itself, a decision. The account is not closed. Someone, or something, has flagged that the picture is incomplete and wants it completed. That framing matters, because it tells you the goal of your reply — complete the picture with documents — rather than argue, explain, or defend.

What never to say or send

Do not take it public. An angry thread naming the institution does nothing to move the review and can actively harden it. Do not fire documents blindly at whatever inbox sent the email — the wrong document to the wrong department can create more questions than it answers. And above all, watch your phrasing. A defensive explanation that “admits” to whatever you assume they suspect, a casual line about clients or countries, an over-share meant to sound cooperative — any of these can read as confirming the exact risk the review is checking for.

The permanent-mark problem is real here. Anything that extends the review, or that reads badly in the file, can outlast this one episode independent of whether your underlying business is completely fine. You are not just trying to survive this email. You are trying not to leave a residue that makes the next application harder.

How to answer without extending the review

Preserve first, reply second. Before you write anything, gather the evidence: statements, invoices, prior correspondence, whatever demonstrates the operation is real. An answer built on documents is far stronger than an answer built on explanation, and assembling them first also slows you down enough to reply from a calm place instead of a panicked one. Then respond to exactly what was asked — the specific documents, cleanly labeled — and nothing you were not asked for.

If your reply then sits unanswered past a reasonable window, do not wait silently for a second email that may never come. Escalate through the institution’s own channels, in writing, referencing what you already sent and when. Silence is not resolution, and a review that stalls is a review you should be gently pushing along. If the email came from a fintech and you are staring at a “routine check” with no timeline, the fintech-specific version of this — including what to run in parallel — is covered in Revolut froze our account for 10 days.