Skip to content

What building a fintech app in the UK requires

Moving, holding or advising on money is regulated activity, and the app is only one part of it. This page sets out the rules that shape a fintech build, how financial data has to be handled, and the questions we ask before we quote.

We reply within one working day. 020 7078 5151

The rules that shape the build

Most of these rules decide who is allowed to do what, long before they decide how the app looks. Your compliance adviser owns the regulatory position; we build so the position can be met and evidenced.

FCA authorisation
Payments, e-money, lending, investment and insurance distribution are regulated activities. The business needs FCA authorisation, registration, or an arrangement with an authorised firm (an appointed representative or a regulated partner that holds the money and the permissions). Which route you take shapes the whole product.
Payment Services and E-Money Regulations
The Payment Services Regulations 2017 and the Electronic Money Regulations 2011 govern payment accounts, wallets and stored value, including safeguarding of customer funds and strong customer authentication for payments and account access.
Money Laundering Regulations 2017
Know-your-customer checks, ongoing monitoring, suspicious activity reporting and record keeping for at least five years. In practice this means an identity verification provider, a sanctions and PEP screen, and transaction monitoring designed in from the start.
Consumer Duty
The FCA's Consumer Duty requires firms to deliver good outcomes for retail customers and to evidence it: clear communications, products that fit their customers, fair value and support. It touches copy, pricing screens, onboarding and the data you keep about outcomes.
Financial promotions
Marketing of financial products, including in-app screens and notifications, must be fair, clear and not misleading, and approved by an authorised firm where required. Cryptoasset promotions have their own FCA regime with risk warnings and cooling-off periods.
PCI DSS and Open Banking
Card data brings PCI DSS; the usual approach is to keep it out of your systems with a certified processor and tokenisation. Account data via Open Banking needs an FCA-registered provider or your own registration, and consent flows that follow the standard.
App Store and Google Play rules
Apple expects apps for trading, investing or money management to be submitted by the institution providing the service (Guideline 3.2.1), and both stores have specific rules for lending and cryptoasset apps. The account the app ships under matters.

How the data has to be handled

  1. 1

    Keep card numbers out of your systems. A certified payment processor and tokenisation keep PCI scope to a minimum and remove the most dangerous data from your estate.

  2. 2

    Secrets in the device's secure hardware (Secure Enclave and Keychain on iPhone, the Keystore on Android), never in the app binary or in logs.

  3. 3

    Biometric or strong authentication for access and for payments, with step-up checks for higher-risk actions, meeting strong customer authentication rules.

  4. 4

    Encryption in transit and at rest, certificate pinning where it is justified, and a clear separation between the app, the API and the ledger or partner that holds the money.

  5. 5

    An audit trail for every financial action and every change to customer data, kept for the periods the regulations require (five years for anti-money-laundering records).

  6. 6

    Monitoring for fraud and unusual activity, with the alerts and reports your compliance function needs to act on them.

  7. 7

    UK hosting with a provider that publishes its certifications, and a written data flow so the regulatory and privacy answers are true.

The questions we ask before we quote

Twenty minutes on these usually settles whether the project is sound, what it needs and roughly what it costs.

Book a 20-minute call with our team

We reply within one working day.

  1. 1

    Are you authorised by the FCA, applying, or working with an authorised partner? Who holds the customers' money?

  2. 2

    Which regulated activities does the product perform, and which does a partner perform on your behalf?

  3. 3

    Who are your identity verification, screening and payment providers, or do you need help choosing them?

  4. 4

    What has to happen in the app to meet strong customer authentication, and what step-up checks do you want?

  5. 5

    How will you evidence Consumer Duty outcomes, and who approves financial promotions?

  6. 6

    Will the app ship under your developer account or the authorised firm's, and who answers App Review?

  7. 7

    What is your incident, complaints and record-keeping plan, and what does the app need to support it?

Technologies we use

Swift and SwiftUI Kotlin React and Next.js Node.js PostgreSQL AWS and Google Cloud (UK regions) Stripe Open Banking APIs

After launch

Keep it working after launch

Websites and apps need looking after once they're live. App care is the plan most people choose after this, at £550 a month.

Already have an app or site that needs looking after?

Questions we get asked

Not before we start, but the route has to be decided: authorisation of your own, registration, or an arrangement with an authorised firm or regulated partner. Authorisation itself is between you, your compliance adviser and the FCA. We build so that whichever route you take, the app does what that route requires and the evidence exists.

Talk to us before you scope it.

Let's talk about your project and the best way to approach it. No commitment and no pressure, just a conversation about what's possible.