Skip to content

Industry · Banks and credit unions

Banking App Development

Banks and credit unions build digital channels on top of a core system they rarely control, under supervisors who expect resilience, security and clear accountability. This page explains how those institutions run their technology and where digital banking projects stall.

Core banking integration experience

Resilience and audit trails by design

Retail, business and member channels

Operating models

Operating models in banking.

01Model

Retail and community banks

Deposit-funded institutions earning net interest margin plus fees. Digital channels must cover current accounts, savings, cards and loans while keeping branch and contact-centre staff in the same picture.

02Model

Credit unions and mutuals

Member-owned lenders with a common bond and often a smaller IT team. They depend heavily on shared service providers and need apps that feel modern without replacing their core.

03Model

Business and commercial banking

Multi-user access, payment approvals, bulk files and cash management for companies. Entitlements and dual control matter more here than consumer-style design polish.

04Model

Digital-only and challenger banks

Chartered institutions without branches that compete on onboarding speed and app experience. They usually run a modern cloud core yet carry the same prudential and conduct obligations as incumbents.

Rules and constraints

Rules that shape banking software.

01Constraint

Prudential supervision and operational resilience

Supervisors expect banks to identify important business services, set impact tolerances and prove they can recover from outages. Regimes such as the EU’s DORA and the UK’s operational resilience rules differ in detail by jurisdiction.

02Constraint

Third-party and outsourcing risk

Using a cloud host, core vendor or app developer does not move accountability away from the bank. Contracts need audit rights, exit plans and incident notification, and many regulators expect a register of critical providers.

03Constraint

Authentication and payment security

Strong customer authentication, device binding and transaction signing are expected for login and payments in most markets, alongside card network rules for any card features.

04Constraint

Deposit protection and disclosures

Customers must be told which entity holds their money and whether a deposit guarantee scheme applies. Product terms, rate changes and fees have disclosure rules that the app has to present correctly.

05Constraint

Data protection and retention

Banking data is covered by privacy laws such as GDPR plus banking secrecy and record-keeping duties, which set how long data is kept and who may see it.

Core systems

Systems a banking product needs.

01System

Core banking integration layer

An API or middleware layer that shields digital channels from the core’s batch windows, legacy formats and rate limits, with caching for balances and a queue for postings.

02System

Digital onboarding and account opening

Identity checks, credit and fraud bureau calls, product selection and e-signature, ending with the account actually created in the core rather than a pending spreadsheet.

03System

Payments hub

Domestic faster payments, wires, direct debits and card controls, with limits, cut-off times, beneficiary management and confirmation-of-payee checks where they exist.

04System

Entitlements and approvals

Role-based permissions, maker-checker workflows and delegated access for business customers, joint accounts and powers of attorney.

05System

Observability and incident response

End-to-end tracing from app tap to core posting, synthetic monitoring of key journeys and runbooks that support the bank’s resilience testing.

Failure points

Where banking software projects go wrong.

01Watch for

Underestimating the core

Cores impose batch cut-offs, field limits and slow change processes. Apps designed as if the core were a real-time modern API end up showing stale balances or failing during end-of-day runs.

02Watch for

Vendor due diligence left to the end

Procurement, information security reviews and outsourcing notifications can take months. Starting them after development finishes pushes go-live back even when the code is ready.

03Watch for

Ignoring branch and contact-centre staff

If staff cannot see what a customer did in the app, every call becomes a guess. Digital programmes that leave out colleague tooling create service failures and complaints.

04Watch for

Big-bang launches

Switching every member to a new app overnight concentrates risk. Phased rollouts by segment, with the old channel still available, catch defects before they reach everyone.

Map the core before you design the channel

List which core functions are available in real time, which run in batch and which need manual staff action. That inventory tells you what the app can promise customers and where you need queues or messages such as pending status.

It also shows where the integration layer has to absorb load so a busy payday does not overwhelm the core.

Bring risk, security and procurement in early

Banking programmes are gated by internal approvals as much as by engineering. Share architecture, data flows and vendor details with risk and information security teams at the start so their reviews run alongside development.

Design for colleagues as well as customers

Branch teams, call handlers and operations staff need a view of digital activity, the ability to reset access safely and clear notes on what the customer saw. Without that, adoption falls and complaints rise.

Treat colleague tooling as part of the same release, not a later phase.

Prove resilience before scale

Run failure tests on the integration layer, rehearse incident communication and check recovery times against the bank’s tolerances. Supervisors increasingly ask for evidence of this testing, not just a written plan.

FAQ

Questions to resolve before the build.

01Can a new banking app work with our existing core system?

Usually yes. Most projects add an integration layer between the app and the core, which handles batch windows, caching and translation. Replacing the core is a separate, much larger decision.

02What do supervisors expect when a bank outsources app development?

Expectations vary by country, but typically include due diligence on the provider, contracts with audit and exit rights, security assurance and clear ownership of the service inside the bank. The bank stays accountable for the outcome.

03How do credit unions differ from banks for app projects?

Credit unions often share cores and service providers, have smaller in-house teams and serve a defined membership. Projects need to fit their provider’s integration options and keep running costs proportionate.

04Should business banking be a separate app?

Often it is a separate experience even if the platform is shared, because business users need multiple logins, approval chains, bulk payments and accounting exports that would clutter a personal banking app.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    Basel Committee on Banking Supervision

    International standards body for prudential bank regulation.

  2. 02
    FFIEC IT Examination Handbook

    US interagency guidance on how examiners assess bank technology.

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.