Skip to content
DT Nova
Software development

Banking software development for banks, credit unions and lenders

DT Nova does banking software development for the work around the core system: customer onboarding, loan origination, open banking interfaces, AML case handling, staff tools and reporting. Banks, credit unions, building societies and specialist lenders use us as a banking software development company that builds in fixed-price phases, signs contracts written for DORA, hosts in the EU and leaves the code in the bank's own account.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

Where banks need their own software

Most banks run a core banking system bought from a specialist vendor, and most should keep it. The core holds accounts, balances, interest and postings, and it is rarely where the daily friction sits. The friction sits around it: an application form that staff retype into three systems, a loan file assembled from email attachments, an AML alert queue in a spreadsheet, a branch tool that has not changed in ten years, a report the finance team rebuilds every month. Custom software pays back there, because the process is the bank's own.

AreaTypical problemWhat we build
OnboardingDocuments by email, checks done by hand, long time to account openingDigital onboarding with identity, beneficial owner and sanctions checks, and a case view for staff
LendingApplications retyped, credit files in shared foldersLoan origination: application, documents, decision rules, approval limits, contract and handover to the core
Open bankingInterfaces that third-party providers find unreliableAccount information and payment initiation interfaces with consent, monitoring and statistics
Financial crimeAlerts in a spreadsheet, reviews overdueAML case management, periodic review scheduling and audit trails
Staff and branchSeveral logins for one customer questionOne customer view for advisers, built on the systems the bank already has

What we build

Customer-facing mobile and web banking apps are covered on our fintech app development page, and software for finance teams, such as reconciliation and e-invoicing, on financial software development. Where a legacy system has no interface at all, RPA in banking can bridge the gap until one exists.

Core banking integration

Cores differ: some offer modern interfaces, some only batch files. We start by reading what the core actually exposes and how it behaves under load, then build an integration layer that hides those differences from the new software. Every message is validated, logged and retried, postings are idempotent so a repeated request never books twice, and failures appear in a queue staff can act on, with the original message and the reason. The new software then talks to the layer, not to the core, so a later core migration changes one place rather than every application.

Open banking and strong customer authentication

The Payment Services Directive (EU) 2015/2366, known as PSD2, gives payment service users the right to use payment initiation services (Article 66) and account information services (Article 67) where the account is accessible online, and it requires the bank, as the account servicing provider, to communicate securely with those providers and to treat their payment orders without discrimination other than for objective reasons. Article 97 requires strong customer authentication when a payer accesses an account online, initiates an electronic payment or acts through a remote channel that may imply a risk of fraud, and for remote payments the authentication must dynamically link the transaction to a specific amount and payee (Directive (EU) 2015/2366, read 12 November 2026 via the EU Publications Office).

In software terms that means an interface third parties can rely on, consent records that show what each provider may see and until when, authentication flows that work on every channel, and monitoring that proves availability. We build and test those parts.

Customer due diligence under the new AML Regulation

The EU Anti-Money Laundering Regulation, Regulation (EU) 2024/1624, applies from 10 July 2027 (Article 90). Article 20 lists the customer due diligence measures: identifying and verifying the customer, identifying beneficial owners and understanding the ownership and control structure, understanding the purpose of the relationship, checking targeted financial sanctions, assessing the nature of the customer's business, ongoing monitoring of transactions and determining whether a politically exposed person is involved. Article 26 sets the maximum period between updates of customer information: 1 year for higher risk customers under enhanced due diligence and 5 years for all other customers (read 12 November 2026).

Those periods are a scheduling problem as much as a compliance one. We build the review calendar into the customer record, so each customer's next review date follows from their risk level, overdue reviews are visible to managers, and every review leaves a record of what was checked and decided.

Working with a bank under DORA

The Digital Operational Resilience Act, Regulation (EU) 2022/2554, has applied since 17 January 2025. Article 30(2) lists what every contract for ICT services must contain, including a complete description of the services, the regions or countries where services are provided and data is processed with advance notice of any change, provisions on availability, integrity and confidentiality of data, access to and return of data on termination or insolvency, assistance in ICT incidents at no additional cost or at a cost fixed in advance, cooperation with competent and resolution authorities, and termination rights. For services that support critical or important functions, Article 30(3) adds full service levels, contingency plans, participation in threat-led penetration testing and exit strategies, and Article 28(8) requires the bank to have exit strategies for those services (read 12 November 2026).

Our standard terms already point the same way: code in the bank's repository, hosting in the bank's own account in an EU data region, documentation written for handover, and an exit that does not depend on us. We add the DORA clauses to the contract and support your register of information with the details it needs.

AI in credit decisions

Annex III of the AI Act, Regulation (EU) 2024/1689, lists AI systems intended to evaluate the creditworthiness of natural persons or establish their credit score as high-risk, with an exception for systems used to detect financial fraud. The European Commission's AI Act page states that the rules for high-risk use cases in Annex III apply from 2 December 2027 (both read 12 November 2026). When a lending workflow uses a model to score consumers, we design for that classification from the start: documented data, logged decisions, explanations staff can read and a human who can override the result.

Ready-made banking software or custom?

Core banking platforms, digital onboarding suites, loan origination systems and AML monitoring products are mature markets, and for many banks a product is the right core. Custom work pays off around them: where the product does not fit the bank's own process, where several products must work as one for staff and customers, or where per-account licence fees grow faster than the business. A common pattern is a product at the core with custom onboarding, lending workflow and staff tools around it.

QuestionReady-made productCustom software
Standard process, standard dataUsually the better choiceRarely worth it
Process is how the bank competesConfigured as far as the product allowsBuilt around the bank's own rules
Several systems for one customer taskEach product has its own screenOne workflow across all of them
Exit and ownershipDepends on the vendor's contractCode and data in the bank's name

How we build it

  1. Process walk-through. We follow one process, such as a business loan from application to booking, through every system and team, and note each manual step, delay and risk.
  2. Scope and fixed price. A one-page scope with acceptance criteria, data locations and the DORA terms, priced firmly for the first phase and signed before work starts.
  3. Test version on realistic data. A separate environment with test data shaped like your own, connected to a test instance of the core.
  4. Security and acceptance testing. Your security team and auditors review the build; anything that does not meet a criterion is fixed within the fixed price, and the phase is accepted in writing.
  5. Controlled go-live and maintenance. A pilot group first, then the full roll-out, followed by a written maintenance plan for security updates, monitoring and changes.

You own it

The source code sits in a repository in the bank's account from the first day. Hosting, databases, keys and integration credentials are in the bank's name, in an EU data region, and personal data is processed under a written data processing agreement. You can keep us for maintenance, run it yourselves or hand it to another supplier.

Banking is one of several industries we build for; see the custom software development company page for how we work across all of them, and the industry pages for insurers and retailers. For the wider approach, read about our bespoke software development process, our API integration services and data migration. See prices. Send us a short brief describing the process you want to fix first.

Questions we get

Do you replace our core banking system?

Usually not. The core system holds accounts, balances and postings, and replacing it is a multi-year programme with its own specialist vendors. We build the software around it: onboarding, loan origination, case handling, open banking interfaces, reporting and staff tools, connected to the core through its interfaces or an integration layer.

Can you work with us under DORA?

Yes. The contract covers the elements DORA Article 30 lists, including the description of services, data locations, access and return of data, assistance in ICT incidents, cooperation with your competent authority and termination rights. For services that support critical or important functions, we add the extra terms in Article 30(3), such as exit strategies and participation in your testing.

Where is the data hosted?

In an EU data region, in a hosting account in the bank's own name, with every location written into the contract. If a location ever needed to change, you would be told in advance, as DORA requires.

Can you build our open banking interface?

Yes. We build dedicated interfaces for account information and payment initiation providers, consent handling, monitoring and the reporting around them, and connect them to your strong customer authentication. We also build the other side: products that use open banking data from other banks through licensed providers.

Do you build credit scoring models?

We build the decision engine and the workflow around credit decisions, with your rules, policy limits and full logging. Where a model scores natural persons, the AI Act lists creditworthiness evaluation as a high-risk use, so the design includes documentation, human oversight and the records that classification requires.

Who owns the software?

The bank. The source code sits in a repository in your own account from the first day, the documentation is written for your own engineers and auditors, and any competent team can continue the work.

How does a project start?

With the one process that costs the most time or risk today. We map it, agree a one-page scope with acceptance criteria and a fixed price, and build that first.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote