Most banking infrastructure in the UK is decades old, built on mainframe systems from an era before "API-first" meant anything. ClearBank is the first genuinely new entrant into the UK's core clearing infrastructure in roughly 250 years, and it's one of the quieter stories in UK tech news worth knowing about, since it got there by betting entirely on cloud-native architecture in an industry that historically treated "cloud" and "critical financial infrastructure" as incompatible ideas.
That bet is worth unpacking if you've ever wondered how you get a regulator to trust software running on someone else's servers with the plumbing of a national payments system.
What ClearBank actually does
ClearBank isn't a bank in the way Monzo or Starling are. Founded in 2015 by Nick Ogden (who also founded WorldPay), it doesn't offer consumer accounts, loans, or mortgages. Instead, it provides the underlying rails: real-time clearing, embedded banking, and direct access to the UK's payment infrastructure, exposed through a single API that other regulated fintechs and financial institutions build on top of.
Tide runs on it. So does Coinbase's UK clearing. It functions less like a retail bank and more like a banking-as-a-service layer that other companies plug into instead of building their own connection to national clearing systems from scratch.
Why "cloud-native clearing bank" was considered impossible
Getting there wasn't a matter of writing code. ClearBank had to work with dozens of separate regulatory stakeholders, spanning the FCA and the Bank of England, to get approval for something that had genuinely never existed before: a cloud based system sitting inside the UK's critical payments infrastructure.
Financial regulators are conservative for good reason, core clearing systems can't have downtime, can't lose transaction integrity, and can't be treated like a typical SaaS product where "we'll patch it in the next sprint" is an acceptable answer to a bug.
Getting a regulator comfortable with cloud infrastructure sitting at that layer of the stack, when the entire industry's mental model still assumed dedicated, on premise mainframes, was as much a trust-building exercise as an engineering one.
The architectural distinction that actually matters
The interesting technical detail here is what ClearBank chose not to build. It doesn't do lending, doesn't hold retail deposits in the traditional sense, and doesn't compete with the businesses that plug into it. That's a deliberate constraint, not a limitation.
By staying narrowly focused on clearing and settlement infrastructure, exposed through one API, it avoids the conflict of interest that comes from being both the rails provider and a competitor to the companies running on those rails.
Compare that to a vertically integrated bank trying to offer infrastructure services on the side, the incentive structures pull in different directions, and it shows up eventually in how a platform prioritizes its own roadmap versus a client's.
Interest income as the quiet backbone of the model
Money moves through the system via account fees and per transaction charges, but there's a third, less obvious revenue stream: client funds get held at the central bank at a 1:1 ratio, rather than being lent out the way a traditional bank would.
Interest earned on those overnight deposits gets partially returned to clients. It's a conservative structure, holding cash 1:1 instead of fractional-reserve lending is a deliberate trade off that sacrifices lending margin for the kind of stability and transparency that lets regulated institutions comfortably build critical infrastructure on top of you.
The lesson for anyone building infrastructure others depend on
Strip away the banking specifics and the pattern generalizes well beyond fintech: if you're building infrastructure other companies will depend on for something mission critical, the technology is frequently the easier half of the problem.
The harder half is building enough operational trust, through conservative design choices, regulatory transparency, and a narrow, well-defined scope, that a risk-averse institution is willing to bet its own uptime on your system instead of building the equivalent in-house.
ClearBank didn't win by being the flashiest fintech in the room. It won by being the first company in two and a half centuries that regulators, and by extension the institutions plugging into its rails, actually trusted to run cloud infrastructure at the core of a national payments system.
Top comments (0)