Skip to content

Industry · Financial services

Fintech, Banking and Insurance Software Solutions

Fintech covers payments, lending, wallets and wealth products sold by firms that are not traditional banks. This page sets out how those businesses make money, which licences and partners they depend on, and what the software underneath has to get right.

Ledger-first architecture

Licence and partner-bank aware

Reconciliation built in from day one

Operating models

Operating models in fintech.

01Model

Payment facilitation and acquiring

Revenue comes from a margin on each card or account-to-account transaction. The product onboards merchants, routes payments through an acquirer or scheme, and carries chargeback and settlement risk for the merchants it signs.

02Model

Digital lending

Consumer, SME or point-of-sale credit funded from the balance sheet, a warehouse facility or a lending partner. Income is interest and fees, and the whole business rises or falls on underwriting and collections quality.

03Model

Stored-value wallets and e-money

Customers hold balances for spending, sending or saving. The operator earns interchange, FX spread or float income and must safeguard client funds separately from its own money.

04Model

Wealth and investment platforms

Robo-advice, share dealing, pensions or fractional assets. Revenue is platform fees, spreads or payment for order flow where permitted, with custody usually held by a regulated third party.

Rules and constraints

Rules that shape fintech software.

01Constraint

Licensing or a regulated partner

Holding money, lending or arranging investments normally needs authorisation, such as an e-money or payment institution licence, a consumer credit permission or a broker-dealer registration. Many start-ups operate under a partner’s licence instead, and which route applies depends on jurisdiction and product.

02Constraint

Card data and PCI DSS

Any system that stores, processes or transmits cardholder data falls within PCI DSS scope. Most fintechs shrink that scope with hosted fields and tokenisation so raw card numbers never touch their own servers.

03Constraint

KYC, AML and sanctions screening

Customers and merchants must be identified, risk-rated, screened against sanctions lists and monitored for suspicious activity. The thresholds and reporting duties vary by country and by licence type.

04Constraint

Safeguarding and client money

E-money and payment firms in many regimes must keep customer funds in segregated or insured accounts and reconcile them daily. Software has to prove, at any moment, that customer balances are fully covered.

05Constraint

Open banking and strong customer authentication

Under PSD2 in the EU and comparable UK rules, account access runs through regulated APIs and most electronic payments need two-factor authentication. Other markets have their own open-finance schemes with different consent models.

Core systems

Systems a fintech product needs.

01System

Double-entry ledger

An immutable, append-only ledger that records every movement as balanced debits and credits. Balances are derived from it, never edited directly, which is what makes audits and disputes answerable.

02System

Payment orchestration

Routing across acquirers, local payment methods and bank rails, with retries, idempotency keys and webhook handling so a payment is never charged twice or silently dropped.

03System

Onboarding and identity verification

Document and biometric checks, business verification for merchants, sanctions and PEP screening, and a case queue where compliance staff review the edge cases.

04System

Risk and fraud engine

Rules plus scoring on device, velocity and behaviour signals, applied before money moves, with clear reason codes so analysts can explain each decision.

05System

Reconciliation and finance reporting

Automated matching of ledger entries against bank statements, scheme settlement files and partner reports, with breaks surfaced to an operations team the same day.

Failure points

Where fintech software projects go wrong.

01Watch for

Balances stored as editable fields

Teams that keep a mutable balance column instead of a ledger cannot explain how a customer reached a number. The first audit or dispute turns into weeks of forensic work.

02Watch for

Partner bank dependency discovered late

Sponsor banks and BaaS providers set their own onboarding, monitoring and reporting requirements. Products designed before reading those contracts often need rework before launch is approved.

03Watch for

Webhooks treated as reliable

Payment providers send events out of order, twice or not at all. Systems that do not poll, deduplicate and reconcile end up with orphaned transactions and support tickets.

04Watch for

Compliance bolted on after growth

Monitoring, case management and audit trails added late are costly, and regulators judge the controls in place when the volume arrived, not the ones planned for next quarter.

Start with the money flow, not the screens

Before any design work, draw where funds sit at each step: whose account, under which licence, with which settlement timing. That diagram decides your partners, your ledger accounts and much of your compliance scope.

A wallet that pays merchants on the next business day needs a very different treasury setup from a lender that disburses instantly and collects monthly.

Choose partners for their operations, not only their price

Sponsor banks, card issuers and payment processors differ in API quality, sandbox realism, reporting files and how quickly they answer an incident. Ask for their settlement file formats and dispute workflows before you sign.

Switching a core partner after launch is one of the most expensive migrations a fintech can face, so plan for an abstraction layer that keeps a second option open.

Treat compliance tooling as product

Compliance analysts are daily users. Case queues, evidence capture, screening hit review and audit exports deserve the same design care as the customer app, because slow reviews mean slow onboarding and lost revenue.

Plan reconciliation and support from the first release

Every day, your ledger should agree with what banks and processors say happened. Build automated matching and a breaks dashboard before you scale, and give support staff a read-only view of each customer’s transaction history.

Firms that skip this tend to find out through customer complaints rather than through their own controls.

FAQ

Questions to resolve before the build.

01Do we need our own licence to launch a fintech product?

Not always. Many firms launch under a regulated partner such as a sponsor bank, e-money institution or broker, then apply for their own authorisation once volumes justify it. The right path depends on the product, the countries you serve and the partner’s terms, so take specialist legal advice early.

02Why does a fintech product need a double-entry ledger?

Because every balance must be explainable. A ledger records each movement as matching entries, so you can rebuild any balance at any point in time, reconcile against banks and answer auditors without guesswork.

03How do fintechs reduce PCI DSS scope?

By using a provider’s hosted payment fields or SDK so card numbers go straight to a tokenisation service. The fintech stores tokens instead of card data, which narrows the systems an assessor needs to examine.

04What usually delays a fintech launch?

Partner due diligence, compliance sign-off and reconciliation testing take longer than building screens. Planning for those workstreams from the first sprint shortens the path to live money.

Primary sources

References behind this page

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

  1. 01
    Financial Conduct Authority

    UK regulator for payment, e-money, lending and investment firms.

  2. 02
    PCI Security Standards Council

    Publisher of the PCI Data Security Standard for card data.

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.