Service · Software development

Custom core banking platform development.

Custom fintech software on top of a Banking-as-a-Service rail, or a specific module alongside your existing banking core: customer onboarding, KYC portal, loan application, payment app. We build the part your customers or employees actually work with, not the regulatory banking licence underneath it.

BaaS front endsFintech MVPPSD2 & DORAOpen Banking

We don't replace Temenos.

Let's be clear from the start: replacing a full core banking platform, the part that maintains accounts, posts ledger entries and talks to SWIFT, is the territory of Mambu, Thought Machine, Temenos and FinXact. That is a multi-year undertaking with a budget of many millions, and a dependency on decades-old legacy data models. We don't do that.

What we do: the layer on top. A BaaS rail from Solaris, Treezor or Currencycloud gives you accounts, cards and payments as a service. We build the customer-facing UI, the business logic and the compliance flows around it, so you can launch a fintech proposition under your own brand, or bring an existing banking product up to date.

We also build standalone modules alongside your existing core: a new customer portal, a digital mortgage application process, a KYC workflow, a treasury tool for SME customers. All of them add to what you already have rather than replacing it. Our sweet spot is precisely that outer layer: it's where the customer experience lives, where you differentiate, and where most of the regulation becomes truly visible to the end user.

We work for established banks that want to renew a specific module, for insurers with a banking licence that need to set up a digital channel, for fintech start-ups building their MVP or V2, for savings banks and cooperative banks that are digitalising, for BaaS resellers building a white-label layer for partners, and for crypto banks operating under MiCA. The common thread: you know the regulations and the product, and we deliver the software that makes it work.

What we build.

Three types of projects where we can put our experience with fintech software, regulated industries and BaaS integrations to work. In the first conversation we determine which path fits your situation.

BaaS front end · customer-facing application

Fintech app on Banking-as-a-Service

You have a proposition, such as a savings app for young people, a payment card for a community or a wallet for a specific industry, and you choose a BaaS provider for the rail. On top of that, we build the customer app, the onboarding flow, the transaction overviews and the business logic that sets your product apart. With BankID or iDIN for identification, push notifications for every payment, and integrations with your CRM so support and marketing work with the same data. Launch within one production-ready release, then keep building in the releases that follow.

iOS & AndroidiDIN / BankIDSolaris / TreezorCRM integration
Module · extension alongside your existing core

Specific banking module or customer portal

Your core system works fine; it's the customer-facing layer around it that feels twenty years old. We build the part your customers or staff use every day: a modern customer portal, a digital loan application, a KYC or AML compliance flow, or a digital mortgage application environment. With a clean API integration to your existing core, an anti-corruption layer wherever the legacy system misbehaves, and optionally a feature-flag system so you can run new flows alongside the old ones until you're certain the migration is going smoothly.

Customer portalKYC / AMLLoan originationMortgage flow
Fintech platform · scale-up or corporate

A complete custom fintech platform

For lending start-ups, wealth platforms, treasury tools and payments companies that need their MVP, V2 or platform layer. Open Banking APIs for PSD2, fraud detection with a rules engine plus, where useful, an ML model for anomalous patterns, real-time payment integration (SEPA Instant), and all DORA and GDPR requirements built in from the start. No rebuild in a few years' time, but a platform that scales with your growth, with audit trails that DNB or AFM supervisors are used to seeing, and an architecture that adapts when regulations change.

Open BankingPSD2 XS2ASEPA InstantFraud detection

What we do and don't deliver.

The financial sector draws a sharp line between building software and granting licences. We sit on the software side, and we're transparent about that.

For the regulatory side, such as a DNB or AFM licence, BIN sponsorship or SWIFT membership, you work with a specialist compliance adviser or a licensed BaaS provider. We connect to them technically.

  • Customer-facing applicationsThe web app, mobile app or customer portal your end users work with. Including design, onboarding flows and every interaction.
  • Business logic layerThe rules specific to your product: credit scoring, fee calculations, tier systems, loyalty, policy rules. Not a generic BaaS default, but your own.
  • Compliance flows in softwareKYC onboarding, AML screening, PSD2 SCA, audit trails, GDPR rights. We implement the processes your compliance team has defined.
  • Integrations with a BaaS rail or bank coreIntegrations with Solaris, Treezor, Currencycloud, or your own mainframe via REST, SOAP or file-based interfaces. Open Banking integrations via PSD2 / eIDAS certificates.
  • What we do NOT deliverNo replacement of your core ledger (Temenos / Mambu / FinXact territory). No BIN sponsorship or regulatory licence. No SWIFT membership or cash clearing. For those, you already know where to go.

Tech stack & security.

Banking software needs a stack that will still hold up in ten years, using patterns that supervisors recognise. For back-end work we rely on Java with Spring Boot, the workhorse of enterprise banking, with mature libraries for security, transactional work and messaging. For modern high-throughput services and payment engines we use Go, and for data pipelines and fraud models Python. On the front end, React or Vue for web, and native (Swift / Kotlin) or React Native for mobile, depending on what the product needs.

For the layer in between: Kong or Tyk as the API gateway, a service mesh where microservices are genuinely justified, and Kafka or RabbitMQ for event streams between bounded contexts. Secrets and cryptographic keys live in an HSM or a cloud equivalent (AWS CloudHSM, Azure Key Vault Managed HSM), with automatic rotation. Observability via Prometheus, Grafana and structured logging, not because it looks good, but because DORA explicitly requires demonstrable incident detection.

Layered security: encryption in transit and at rest, secret scanning in the CI pipeline, dependency scanning for CVEs, a pen test before go-live, and periodic pen tests afterwards. For regulated workloads, often a dedicated tenant or your own VPC, so the separation of data between customers and environments is demonstrable. We document the controls in a way your compliance or internal audit team can reuse directly for DNB or AFM reporting.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When an engagement with us is a good fit.

Four recognisable patterns in which we often get involved. If one sounds familiar, we'd be happy to talk further.

BaaS launch

You're building a fintech proposition

You have the market, you've chosen a BaaS partner, and now the end-user application needs to be built. The BaaS rail gives you accounts and cards, but you have to build the UI, branding, onboarding and all the distinctive features yourself. That's the difference between a generic savings pot and a product people keep coming back to. That's exactly where we come in.

Modernisation

Your customer portal feels outdated

The core system works fine, but the layer your customers use hasn't been touched in years. A new customer portal or a modernised onboarding flow alongside your existing core, without touching it. We build modularly so that any later migration of the core won't break through your new layer.

Compliance module

A specific flow needs to improve

The KYC flow had too many drop-offs. The DORA deadline is approaching and your incident management tooling is a spreadsheet. A mortgage application takes too long because data has to move back and forth between four systems. Digitising or rebuilding one specific module, modularly alongside what's already there, with demonstrable audit trails for your auditor.

MVP or V2

Your fintech is ready to mature

The prototype is running and the first customers are on board, but the stack was put together with scarce resources and won't scale to 10× the volume or a second country. We rebuild it with an architecture that is production- and audit-ready, with multi-tenancy or multi-region where needed, without starting over on the feature set that already works.

How an engagement works.

1

Introduction & scope

A conversation in which we understand which proposition you're bringing to market, which BaaS provider or core bank is in the picture, which regulations apply and what your own team can already carry. By the end, we have a shared view of the scope.

2

Architecture and compliance mapping

A workshop with your tech and compliance team. We map the regulatory requirements (PSD2, DORA, GDPR, and possibly MiFID II or the Wft) to concrete software controls. This results in an architecture document and a first screen flow.

3

Building in sprints

A working build every two weeks. We work in a feature-flagged staging environment so that compliance and security reviews can run in parallel. The pen test is scheduled early, not only at the end.

4

Production and ongoing management

A phased go-live, with a controlled rollout to an initial customer group. After that, ongoing management: monitoring, security patches, changing regulations (PSD3 is on its way), and further development based on what customers actually use.

Frequently asked questions.

The questions we get most often before an engagement begins.

Do you replace our core banking system (Temenos / Mambu)?
No, and we're clear about that. Replacing a full core banking system is work for specialised vendors such as Mambu, Thought Machine, Temenos or FinXact, and is usually a multi-year, multi-million-euro programme with dozens of people working on it. We build the layers around it: customer applications, modules and compliance flows that talk to your existing or new core. That's where our added value lies too, in the layer your customer sees and that shapes your brand.
What exactly is a BaaS front end?
Banking-as-a-Service providers such as Solaris, Treezor or Currencycloud supply the regulatory and technical rails (accounts, cards, payments) under their own licence. We build your customer-facing application on top: the mobile app, the web portal, the business logic and the specific features that set your product apart. For the end user it feels like one coherent product, and for the regulator it is clear which party carries which part of the liability.
Which compliance frameworks do you build in?
The usual set for digital financial services: PSD2 (and soon PSD3), DORA for ICT resilience (see our page on DORA compliance software), GDPR, Wft and MiFID II controls where relevant, and AFM or DNB reporting flows. For crypto propositions, MiCA applies as well. We build the controls into the software rather than as a separate procedural layer, so they automatically apply to every transaction.
Do you help with the DNB or AFM licence application?
No. Licensing is work for specialised compliance lawyers and consultants who know the legal side of the Wft, BRRD or MiCA in detail. We align technically with the requirements that come out of that process and make sure the software demonstrably delivers the required controls. For the application file itself, you work with a Wft specialist or a consultancy that specialises in this.
Which tech stack do you use for banking software?
Java with Spring Boot for those following enterprise banking traditions, Go for modern high-throughput services, and Python where data and ML play a role. For the API gateway we use Kong or Tyk, HSM integration for secrets and keys where needed, and Prometheus and Grafana for observability. For mobile we use native (Swift / Kotlin) or React Native, depending on the use case. We are pragmatic: no dogma about a single stack if another fits better with what you already run.
Can you integrate with our existing core or legacy systems?
Yes. We have experience with REST APIs from modern cores and BaaS providers, but also with SOAP, ISO 20022 messages, batch files and even message queues on mainframes. Where needed, we build an anti-corruption layer so your new application doesn't inherit the quirks of the legacy system, and so that a later core replacement doesn't break through the new layer.
What about Open Banking and PSD2 integrations?
For consumer or SME applications that need access to accounts at third-party banks, we build PSD2 XS2A integrations, including eIDAS certificates and the correct SCA flow with a re-authentication cycle. You can do this yourself as a TPP (licence holder), or via an aggregator such as Tink or Yapily. We advise which route fits your scope and time-to-market.
What determines the lead time and costs?
Scope is by far the biggest factor: a standalone module alongside an existing core is a different project from a full fintech application with onboarding, transactions and KYC. Beyond that, the number of integrations, the complexity of the business logic, how much compliance evidence is required, and whether you serve one or multiple countries or brands all play a role. After an initial workshop, we give you a concrete estimate with several scope variants so you can choose based on risk and investment.

Talk to us about your banking platform.

A no-obligation, half-hour introduction. Tell us about your proposition, your BaaS partner or core vendor, and which regulations apply. We'll give you useful direction, even if you ultimately go with someone else. For larger fintech or compliance challenges, we also work together with our enterprise software team and colleagues who build insurance software.

Edit content