Revolut's Bank Charter Is an Interface Problem

Revolut has spent a decade teaching people that money is one number in one app. On September 3 a US regulator handed it a licence that makes that idea a lot harder to hold.

The Office of the Comptroller of the Currency gave Revolut preliminary conditional approval for a national bank charter, clearing the way to form Revolut Bank US, National Association. Nik Storonsky called it "an important first step towards establishing the proposed Revolut Bank US." Most of the coverage filed it under growth. We read it as a list of interface problems with a date attached.

Conditional is doing a lot of work in that sentence

Nothing has opened. Revolut still needs deposit insurance from the FDIC, approval from the Federal Reserve, and final authorisation from the OCC before a single US account exists. The company is aiming at a 2027 launch. The conditions are specific for something this early. Revolut has to pay in at least $95 million once organisational and pre-opening costs are covered, and hold a tier 1 leverage ratio of no less than 10% through the bank's first three years. Retail foreign exchange was left out of the approval. To offer it, Revolut has to come back to the OCC for a separate supervisory non-objection. That last condition is the one product teams tend to underestimate. A feature can be built, tested, translated and marketing-ready, and still be legally unreachable.

An app that has to say which dollars are insured

The proposed bank plans to offer FDIC-insured checking, deposits in more than 30 currencies, stock trading, crypto trading, stablecoin services, loans and credit cards, aimed first at people and businesses moving money across borders. Line those up on one balance screen and you have insured deposits, uninsured investments, a stablecoin the bank does not issue, and credit, all rendered in the same list, in the same typeface, with a single total at the top. The super-app pattern was built to flatten exactly that. One number, one card, one swipe between pots. It is a good pattern. It is also the reason Revolut has more than 70 million customers, a figure it passed in May 2026, and why it has committed $13 billion to global expansion with $500 million of that aimed at the US. A charter turns the flattening into a liability. Under a bank licence, the difference between a deposit and a balance that can go to zero stops being a footnote in the terms and becomes something the interface is responsible for saying out loud.

The signage rule is a design spec with a due date

This is not a hypothetical. The FDIC's Part 328 rules tell banks where the official digital sign has to appear: the initial page or homepage of the website or app, the login page, and the screen where a customer first starts opening a deposit account. Pages given over to non-deposit products need their own signage, displayed clearly, conspicuously and continuously. Before a customer reaches a third-party platform offering non-deposit products, once per session, the app has to tell them those products are not insured by the FDIC, are not deposits, and may lose value. The compliance date for the amended digital signage provisions is April 1, 2027. Those two dates sit almost on top of each other. Revolut wants to open in 2027. The signage rules bite on April 1 of that year. Whoever designs that app is not adding disclosures to a finished product. They are designing a product where the disclosure is load-bearing from the first wireframe. Most fintech teams we talk to still treat this as legal's problem, which in practice means a modal at the end of a flow and a footer nobody reads. That is how you get a compliance layer bolted onto a product designed to hide its own seams. It is also why we keep arguing, on nearly every fintech project we take, that the disclosure should be a component with states rather than a page somebody links to.

Regulatory status is now product status

Revolut is not alone here, and the pattern is about to get common. Over the past year the OCC has handed conditional approvals to Coinbase, Paxos, BitGo, Ripple and Circle. Since 2025 it has taken in 40 de novo charter applications, approved 21 and denied two. A lot of apps that currently present themselves as one seamless surface are about to inherit a regulator's vocabulary. That vocabulary needs somewhere to live in the UI. "Coming soon" is wrong, because the feature is finished. "Not available in your region" is wrong, because the region is fine. The honest state is closer to "this product is waiting on a specific approval from a specific regulator," and almost no design system has a component for it. Nobody writes that copy well the first time, and it usually gets written at 11pm the week before launch by whoever is still awake.

What we would build first

If we were briefed on this tomorrow, four things would come before any screens. An entity map. Every balance in the product tagged internally with the legal entity that holds it and the protection that applies. Not a Confluence page. A field that drives copy. Disclosure as a component. States for insured, uninsured, third party and pending, each with its own visual weight, each testable, none of them a modal you can dismiss and forget. An availability state machine keyed to approvals, not release trains, with real copy written for each state while people are calm. The FDIC digital sign treated as a design token in the header system. It sits near the bank's name, which means it is a layout constraint on your most crowded piece of real estate, on the smallest screen you support, in dark mode, forever. None of that is glamorous work. All of it decides whether the app still feels like one thing after the lawyers are done. The charter is the easy part to write about. The hard part is that Revolut's US app will have to tell the truth about several different kinds of money on one screen, in a few taps, to someone checking a balance on a train, and still feel like the app they already like. That is not a compliance workstream. That is the product.

Sources

1. Banking Dive, "Revolut nabs conditional OCC charter", September 4, 2026
2. PYMNTS, "Revolut Gets Conditional OCC OK for US Banking Charter", September 3, 2026
3. The Block, "Revolut takes 'important' step toward becoming a US bank with conditional OCC approval", September 3, 2026
4. FDIC, "Questions and Answers Related to the FDIC's Part 328 Final Rule", May 13, 2026
5. Tearsheet, "Revolut's US bet: A bank charter, a stablecoin pitch, and a graveyard of European challengers that tried before it", July 7, 2026