Mercury Got Conditional OCC Approval for Mercury Bank, N.A. Here's the Five-Venture Banking Decision I'm Making — and the Three Things the Charter Doesn't Fix.

The OCC handed Mercury conditional approval on April 28. My five-venture banking stack does not move this month, and the reason is not the FDIC sign-off everyone keeps citing.

The April 28 conditional approval, in operator terms

The Office of the Comptroller of the Currency issued conditional approval for Utah-headquartered Mercury Bank, N.A. on April 28, 2026. Mercury filed the application in December 2025 – five months to conditional is fast for the OCC, and that route was open because the company already operated like a bank.

Here is the part most founders skip on the first read: conditional is not operational. The OCC letter is permission to organize Mercury Bank, N.A. as a national banking association. The FDIC still needs to clear deposit insurance separately. The Federal Reserve still needs to clear membership. Until both close, nothing in your Mercury account changes.

Today my Mercury balances ride Choice Financial Group's charter under Mercury's standard FDIC sweep program. The conversion to Mercury Bank, N.A. happens automatically for existing customers once FDIC and Fed sign off – and Mercury has not published a launch date, because nobody publishes a launch date on a conditional letter. The OCC sign-off is the easiest of the three. The FDIC and Fed take longer.

Translation for anyone running money through Mercury this quarter: the press cycle is loud, the operational change is zero. Treasury yields do not move. Wire fees do not move. Card limits do not move. What changes is what can be built on top of the charter, twelve to twenty-four months out, once the bank actually exists as a legal entity holding deposits directly.

That gap – between "OCC said yes" and "Mercury Bank, N.A. is on your statement" – is where the stack-rebuild work happens. Not in May. Not in June. But it gets planned now, because the second piece of news Mercury shipped this month matters more than the charter.

The three real gains for multi-entity operators

Strip the marketing and there are three things a national-bank charter actually changes for a founder running multiple US entities.

The first is Zelle for business, which sounds boring and is not. Partner-bank fintechs cannot reliably support Zelle for business accounts – the program rules are owned by Early Warning Services, the bank consortium that built Zelle, and consortium membership flows through chartered banks, not their fintech partners. Once Mercury operates its own charter, that pipe opens. For client invoicing under $10K, Zelle settles same day with no fee. For a services business sending fifteen to forty client invoices a month, that is real money and real days saved.

The second is direct access to payment rails. Today Mercury's wires and same-day ACH route through Choice Financial's correspondent relationships. That works, but it adds a hop, and it caps how aggressively Mercury can price the rails. A chartered Mercury can hold a Fed master account, originate ACH directly, and negotiate its own wire economics. Practically: faster wire confirmations, lower outgoing wire fees once Mercury chooses to compete on them, and same-day ACH at scale without the partner-bank ceiling.

The third is lending. Today, if I want venture debt or a working-capital line against my three US C-corps, I am bolting on Brex, Capchase, Pipe, or Arc as a separate underwriter who has never seen my deposits. One charter potentially collapses that. The same counterparty holding the cash sees the burn, sees the AR aging, sees the contractor spend – and writes a credit line against it. For a multi-entity operator, that is one underwriter looking at a consolidated balance sheet across three Delaware C-corps, not three separate Brex applications with three separate term sheets and three separate annual reviews.

Stack those three and the strategic shift is clear: Mercury moves from "great app sitting on top of a partner bank" to "Mercury is the underwriter." That is a different relationship. It is also the relationship that justifies a founder consolidating more of the financial stack into one counterparty – but only if the counterparty is actually operational, which is the FDIC/Fed timeline, not the OCC timeline.

The three things the charter does NOT fix

The charter is not a fix-all, and the consolidation play breaks in three specific places.

Non-resident account opening stays manual-review heavy. National-bank status does not relax Bank Secrecy Act or anti-money-laundering requirements – if anything, the OCC supervises BSA/AML more strictly than state regulators do. KYC for non-US founders remains a ticket, not an API. If you have a co-founder on a non-US passport opening a Delaware C-corp from outside the US, Mercury is no faster as a national bank than as a fintech. The bottleneck is regulation, not technology.

Multi-entity tax and accounting still require a QuickBooks, Xero, or Zoho hookup and an actual human controller. Mercury's native bookkeeping flow is convenient. It is not a controller. Once you cross three entities with intercompany expenses, transfer pricing, and consolidated reporting, you need real accounting software and a real human. The Central payroll bundle does not change this, even when it ships.

International payments are the third gap, and for me it is the load-bearing one. Mercury is not Wise. Mercury is not Airwallex. For DVNC.ae – my UAE Free Zone entity sending AED-denominated invoices to regional clients and receiving USD wires from US clients – Mercury is not in the conversation. The charter does not improve FX margins. The charter does not give Mercury a UAE banking license. The charter does not solve receiving AED, holding AED, or paying contractors in AED.

That last gap is why "consolidate everything on Mercury" is the wrong read for any founder operating across jurisdictions. The right read: Mercury is becoming the best US-domestic operating bank for tech founders. It is not becoming a global treasury. Those are different products, and confusing them is the most common framing mistake in the press cycle this week.

The Central acquisition is where the real bundle math gets interesting

Three weeks before the OCC letter, Mercury closed a more strategically important deal. On April 2, 2026, Mercury acquired Central – an AI-native payroll, benefits, and compliance platform founded in 2023, backed by First Round Capital and Y Combinator. Central had roughly 500 startup customers and over $175M in payroll processed at acquisition.

The bundle is the play. Mercury banking plus Mercury payroll becomes a "do I still need this" question for Gusto, Rippling, and Justworks in the sub-50-FTE segment. Not a frontal attack – a sideways one. Founders already on Mercury get the second product at a bundled price, the way Brex once gave corporate cards away to anyone holding deposits.

For multi-entity operators, the math sharpens. Today I would pay Gusto a base fee per entity per month, plus per-employee fees, for each US entity running payroll. Three C-corps with payroll means three base fees and three separate logins, each with its own cap-table view that the others do not see. One payroll provider that already knows the banking side and sees the cap table across all entities collapses three base fees into one – and gives whoever underwrites the lending line a much cleaner view of headcount cost.

The timing also matters more than people noticed. Central is already live with customers. The Mercury-Central bundle can ship integrated long before Mercury Bank, N.A. is operational. Bank conversion is twelve to twenty-four months. The payroll bundle is quarters, not years. If you are deciding what to do about Mercury this year, the Central integration is the thing on the calendar – not the charter.

That is the framing flip. The OCC letter got the headlines. The Central acquisition is the move that changes my P&L first.

My five-venture decision tree as of May 2026

Here is the actual stack I am running and what changes for each entity.

Three US Delaware C-corps: DVNC.dev (services), imperfeqt.ai (product), CLVL.ai (product, waitlist). One US LLC: dvnc.cloud (solo, infrastructure layer for the services side). One UAE Free Zone entity: DVNC.ae (regional services). Different cash flows, different headcount profiles, different cross-border needs.

For the C-corps with payroll or near-payroll – DVNC.dev today, imperfeqt.ai once the first hire lands – the move is to bundle Mercury plus Central when the integration ships. That collapses banking, payroll, and benefits into one login, one underwriter, one cap-table view. The savings versus Gusto base fees plus a benefits broker plus separate logins are real once you cross two entities with W-2 staff. Pre-first-hire, Central does not pay back the migration friction; I keep contractors on 1099s through Mercury bill pay until there is actual payroll to move.

For dvnc.cloud, the LLC running solo with no payroll: keep Mercury IO plus Treasury as-is. Do not migrate, do not switch, do not optimize. The conversion to Mercury Bank, N.A. happens automatically when the FDIC and Fed sign off. There is no decision to make.

For DVNC.ae, the UAE Free Zone entity: Mercury is not on the table. The operating account stays with a regional bank – Emirates NBD or Mashreq Neo, depending on which Free Zone visa stack you are inside. Wise Business sits on top as the multi-currency overlay for USD invoicing to US clients. That stack is correct for cross-border and the charter does not change it. I am not migrating anything about the UAE entity because of news in the US press cycle. That decision is decoupled, and the UAE e-invoicing rollout in October 2026 is the actual forcing function for that side of the stack, not Mercury.

The numbers I am tracking before any migration: monthly banking-ops time across all five entities in hours, monthly all-in software cost across banking plus payroll plus benefits in dollars, total wire fees per quarter in dollars, and effective interest yield on idle balances in basis points. Without a real before-number for each line, the after-number after a bundle migration is not a savings claim – it is a vibes claim. The same discipline I applied when I declined the Codex two-free-months offer and the same line-by-line audit that produced the $387/month solopreneur stack applies here: write the spreadsheet first, decide second.

Migration order, when the time comes: payroll moves first (when Central ships its Mercury-native integration), bank conversion happens automatically and silently, lending consolidation comes last – and only when there is something to consolidate worth the underwriting reset.

What I am not doing this quarter: I am not pulling cards from Brex. Card programs are sticky. The credit-line history, the points economics, the spend controls already configured – none of that improves under a Mercury charter enough to justify the migration friction in 2026. Maybe in 2027, once the bank is operational and Mercury launches a real card program against its own balance sheet. Not now.

What I am actually doing this week

Wait on FDIC and Fed sign-offs before moving any Treasury balances. Partner-bank Mercury today is not meaningfully worse than national-charter Mercury tomorrow – the sweep program is already FDIC-insured up to the network maximum. The right move when the charter clears: consolidate banking and payroll first, renegotiate the lending line second, leave the UAE entity alone.

Conditional approval is permission to build the bank, not permission to bank with it. Plan accordingly.

When does Mercury Bank, N.A. actually go live?

Does the OCC approval change anything for my existing Mercury account today?

Should I switch from Brex or Ramp to Mercury because of the charter?

Will Mercury support non-US founders better as a national bank?

Is the reported $5B valuation relevant to my banking decision?