Skip to content
BritonOne Technology
Software DevelopmentBanking

Core-banking platform build for a challenger bank

Ledger, accounts, and payment rails delivered to an FCA launch milestone in 9 months.

9 months
GoPostgreSQLKafkaKubernetesAWS
Core-banking platform build for a challenger bank
IndustryBanking
DisciplineCustom Software
CountryUnited Kingdom
Headline result9 months
The story

Problem, approach, and the outcome

About the client

The client is a UK challenger bank building from a clean sheet towards an FCA authorisation milestone. As a new entrant, their entire launch, and the investor confidence behind it, hinged on hitting a fixed regulatory date with a platform that could withstand scrutiny.

They had capital, a licence application in flight, and a small senior team, but no core banking estate: everything had to be built, proven, and evidenced from scratch.

The challenge

The licence deadline was fixed and immovable, the estate was entirely greenfield, and every component had to be defensible to the regulator from day one. A challenger bank cannot slip its launch without burning investor confidence and runway.

That put brutal pressure on scope: the team had to build the right things, prove them, and leave nothing that could not withstand assurance. Ambition had to be disciplined by what could actually be evidenced in time.

On top of the deadline, a core banking platform is unforgiving: a ledger that cannot be audited to the penny, or payment rails that behave unpredictably, are not launch blockers so much as existential risks. Correctness was non-negotiable.

Our approach

We built an event-sourced ledger and account core with the payment-rail integrations a live bank needs, delivered in bounded increments against the launch milestone. Event sourcing gave us a ledger auditable to the individual transaction, which the regulator's assurance process demanded.

Crucially, we assembled the evidence pack as we went rather than reconstructing it at the end. Treating assurance as a continuous by-product of delivery, not a final scramble, is what let the team hit a hard date without cutting corners.

We sequenced the build so the highest-risk, longest-lead components were proven early, retiring the biggest unknowns first. That ordering meant no nasty surprises surfaced late, when there would have been no time to absorb them.

Results
  • MVP to launch in 9 months to a hard regulatory date
  • Event-sourced ledger auditable to the transaction
  • Zero critical findings at pre-launch assurance
  • Assurance evidence assembled continuously, not retrofitted
Next step

Get a senior architect on the call, first time, every time.

No SDR gauntlet. 30 minutes with an engineer who can scope the problem, name the risks, and give you an honest feasibility call.