Mercury rejected you. Here is the math behind it, and what to do next

The email arrives. "Mercury will not be able to support your business at this time. We will not be able to provide additional details about this decision." You spend the next two weeks building an appeal: residence permit, business plan, tax registration, customer contracts, the whole file. You attach a polite cover letter explaining that you are not in Russia, not a sanctioned individual, fully compliant. Mercury either does not respond or sends the same boilerplate back. By week three you have decided you did something wrong, that your business is somehow tainted, that you will never get a US bank account.

None of that is true. The reject was a system response, and once you can see the arithmetic driving it, the next move gets obvious and the spiral stops.

The math behind an auto-decline

OFAC violation penalties start at roughly $1 million per transaction. The annual revenue from a single diaspora-founder account at Mercury sits somewhere between $50 and $500. On top of that sits reputational risk: one Bloomberg story about "the fintech serving sanctioned Russians" damages the next funding round, strains banking partner relationships, and invites regulatory attention.

Run those numbers and an auto-decline on an RU or BY passport signal becomes the rational move for the fintech, even when the overwhelming majority of flagged applications are perfectly legal. The downside of a single miss outweighs the upside of correctly clearing every legal applicant. What you are looking at is a company optimising against an asymmetry: maximum downside, minimal upside, per application. There is no judgement of you anywhere in that calculation.

How the decline actually happens

A KYC submission includes a passport scan, residence permit, and business documents. The decisioning system flags an RU or BY passport regardless of where you live, how the company is structured, or where the revenue comes from. Human review exists, but it triggers only when the signal-to-noise ratio is exceptionally clean, and most diaspora-founder profiles never escalate that far. The signal stays on the passport.

Why appeals do not work

When you appeal, your file lands with a human reviewer working inside the same policy framework as the algorithm. The reviewer is not asking whether you are legal. They are asking one question: can I defend this decision in a single sentence if a regulator calls. Your residence permit, your contracts and your tax records do not answer that question, so the system risk stays exactly where it was. The reviewer rejects again, usually faster than the first decision, because they are not rerunning the evaluation. They are confirming the flag was applied correctly.

That is why founders who have appealed three times keep getting the same email. Better writing will not move it. The framework has no path to yes for the profile.

What works instead

Three options, in the order most founders should think about them.

1. Use a second passport, if you have one

Israeli, Armenian, Georgian, Kazakh, Ukrainian (still workable on some applications), or any non-RU/BY document. Submit that one as your primary KYC. A lot of diaspora founders picked up a second citizenship over the past five years, and this is the moment it pays for itself.

2. Skip Mercury

For US LLC banking in 2026, Relay Financial is the most active replacement. It accepts most non-US founders, including a meaningful share of RU and BY passport holders with non-sanctioned residence. Novo is the bootstrapped option: free tier, about a week to set up. Bluevine works if you have an SSN or ITIN. (The earlier piece on Stripe Atlas vs Firstbase vs doola covers the incorporation side.) The Mercury-shaped hole in your stack has working alternatives that skip the appeal dance entirely.

3. Ask whether you need a US LLC at all

If you live in Tbilisi, Yerevan or Belgrade and are not raising US VC in the next 18 months, Georgian Small Business Status, the Armenian 1% IT turnover tax or the Serbian paušal will almost certainly serve you better than any Delaware structure. (The earlier piece on local sole-proprietor regimes has the comparison.) Plenty of founders only worked this out after spending $400 on Firstbase and three weeks on a doomed application, with the local option sitting there the whole time.

The seven days after the email

Day 1: do not appeal, and do not write the perfect cover letter. From Mercury's policy standpoint the reject was correct, and your time is worth more elsewhere.

Day 2: work out whether your actual business needs a US LLC, or whether local incorporation solves the same problem with a fraction of the friction.

Days 3 to 5: if you need the US LLC, apply to Relay or Novo with realistic expectations and clean documentation. If you do not, plan the local setup instead.

Days 6 and 7: if you have decided against the US LLC and already formed one through Firstbase or Stripe Atlas, contact them about closing it out. Both have refund or pro-rata mechanisms in the first 30 days for most situations.

This is structural

Fintechs are doing the arithmetic their compliance teams force on them. The email reads impersonal because the decision was impersonal: OFAC penalties dwarf the revenue from a founder account, and the policy math has no yes-path for your profile. Nothing about your business is tainted and nothing about your profile is broken. You do not owe proof of legitimacy to a system that never asked for it. Plan around the math.