Mercury Fintech Bank Charter: OCC Approval, BaaS, and What Comes Next

Immad Akhund of Mercury shared on LinkedIn this morning that Mercury just cleared one of the hardest regulatory hurdles in fintech: conditional approval from the Office of the Comptroller of the Currency to establish Mercury Bank, N.A. If you've been watching the startup banking space, you know this has been in motion since December 2025, when Mercury filed its OCC application alongside an FDIC deposit insurance application and announced plans to apply to the Fed to become a financial holding company. Now the OCC has said yes, conditionally.

This matters. But it's also worth being precise about what it means and what it doesn't.

What Mercury Is Today

To understand why this is significant, you have to understand how Mercury actually works right now.

Mercury is not a bank. It's a fintech platform: a software layer that plugs into partner banks to deliver financial services. Its banking services currently run through Choice Financial Group and Column N.A. Its IO Card is issued through Patriot Bank. The "Mercury account" you open is real and FDIC insured, but the underlying infrastructure is a BaaS (Banking-as-a-Service) model. Mercury is the front end; regulated banks hold the deposits and carry the charter risk.

This is a model that's actually served Mercury very well. They've built an impressive business on top of it: over 200,000 business customers, $650M in annualized revenue, and three years of GAAP profitability. Roughly one in three U.S. startups banks with Mercury. That's a remarkable market position for a company that, legally speaking, isn't a bank.

But the BaaS model has real structural limits, and Mercury's charter pursuit is a direct response to them.

The Problem with Banking Through Partners

The Synapse collapse in 2024 was a stress test the whole industry failed. Synapse was the middleware layer sitting between fintechs and their bank partners, and when it imploded, customers couldn't access their funds. The failure exposed a fundamental fragility in how BaaS dependent fintechs operate: when your infrastructure is owned by someone else, your operational continuity depends on their stability.

Mercury felt this acutely. In its own regulatory commentary to the Fed, Mercury acknowledged it launched using an intermediate platform provider, found the model unworkable at scale, and transitioned to direct bank partner relationships by 2021. That was a meaningful upgrade, but it still leaves Mercury dependent on third parties for the most critical parts of its stack: deposit holding, payment rail access, and regulatory charter coverage.

A national bank charter changes that equation fundamentally. Mercury would hold deposits directly. It would have its own FDIC insurance relationship. It would access payment rails (like ACH, Fedwire, and potentially Zelle) under its own authority, not through a partner's sponsorship. Immad Akhund said as much in his LinkedIn post announcing the conditional approval: the charter enables faster money movement, expanded lending, and payment infrastructure Mercury actually controls.

Control of infrastructure is not a vanity metric. It's the difference between a fintech and a financial institution.

Why This Approval Is Harder to Get Than It Looks

The regulatory environment for fintech bank charter applications has historically been brutal. The OCC's "fintech charter" initiative from 2017 spent years in litigation and died without producing a single approved charter. SoFi's national bank charter application (the one that Jon Auxier, Mercury's newly appointed Chief Banking Officer, helped navigate) took years of regulatory work and faced its own headwinds.

What's different now is context. The OCC has been in a more approvals friendly posture in 2025–2026, evidenced by a wave of conditional approvals for crypto adjacent entities (Circle, BitGo, Paxos, Bridge/Stripe's stablecoin subsidiary) and Mercury. The regulatory climate shifted, and Mercury was positioned to take advantage of it: profitable, scaled, with a clean compliance record and a management team that includes real banking operators.

Mercury hired Jon Auxier specifically for this moment : he held senior roles at SoFi Bank, Green Dot, and Goldman Sachs. The SoFi parallel is instructive. SoFi went through a multi year bank charter process, and what it unlocked was the ability to offer products at margins that a BaaS dependent model can't match: direct deposit relationships, better yield on held deposits, and lending products without a bank partner taking a cut.

I imagine Mercury is pursuing the same playbook.

What "Conditional" Actually Means

It's worth being clear that conditional approval is not final approval. Mercury still needs to satisfy the OCC's remaining requirements, complete the FDIC deposit insurance process, and get Federal Reserve approval to operate as a financial holding company, with Mercury Technologies, Inc. as the holding company and Mercury Bank, N.A. as its wholly owned subsidiary. The bank will be headquartered in Utah, which has become a hub for digital forward banking entities.

None of that is guaranteed, and none of it is quick. The gap between conditional approval and a fully operational chartered bank can span years. Mercury has been explicit with customers: nothing changes today.

But conditional approval is the hardest gate to clear. The OCC doesn't grant it lightly. It signals that regulators have reviewed Mercury's business model, financial health, and compliance posture and found them credible enough to proceed. That's not nothing.

What It Means for the Payments Ecosystem

Here's where I'd focus attention if I'm watching this space professionally.

For Mercury customers, the near term impact is minimal. The more interesting question is what Mercury builds once the charter is fully operational: whether they expand into more sophisticated lending products, whether they offer Zelle directly rather than through partners, and how they use deposit economics to fund competitive yield products. The charter turns Mercury from an account provider into something with actual bank economics.

For the BaaS model broadly, Mercury's charter pursuit is a signal that the most successful fintechs are aging out of BaaS dependency. The model was a brilliant GTM shortcut: get to market fast, let the banks carry the regulatory weight. But it caps your margin and your control. The natural end state for a fintech that reaches Mercury's scale is direct access to the infrastructure, which means either acquiring a bank, partnering deeply enough that you effectively become one, or doing what Mercury is doing: getting a charter from scratch.

For traditional banks, a chartered Mercury is a more formidable competitive threat than the current Mercury. Right now, Mercury competes on UX and integrations, not on balance sheet. A Mercury with a charter can compete on deposit rates, lending products, and payment rails: aka the core economics of banking.

For payments infrastructure, direct FedWire and ACH access under Mercury's own charter means potentially faster, cheaper money movement for their customers. The correspondent banking layer, where Mercury currently relies on partners to access rails, gets eliminated. That's a meaningful reduction in operational complexity and cost.

The Bigger Pattern

Mercury's approval is happening in a broader wave of fintech charter activity. The OCC approved a cluster of crypto focused trust bank charters in early 2026. PayPal filed for an industrial loan company in Utah around the same time Mercury filed its application. The regulatory posture toward technology native financial institutions is more permissive than it's been at any point in the past decade.

In my opinion this isn't just a Mercury story, it's a structural shift in how financial infrastructure gets built and who gets to build it. The fintechs that built durable, profitable businesses during the BaaS era are now using that foundation to pursue the real prize: owning the charter, the deposits, and the rails.

Mercury earned the right to make this move. Now we'll see if they can execute it, and who follows suit.