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
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
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
Biometric or strong authentication for access and for payments, with step-up checks for higher-risk actions, meeting strong customer authentication rules.
- 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
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
Monitoring for fraud and unusual activity, with the alerts and reports your compliance function needs to act on them.
- 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.
We reply within one working day.
- 1
Are you authorised by the FCA, applying, or working with an authorised partner? Who holds the customers' money?
- 2
Which regulated activities does the product perform, and which does a partner perform on your behalf?
- 3
Who are your identity verification, screening and payment providers, or do you need help choosing them?
- 4
What has to happen in the app to meet strong customer authentication, and what step-up checks do you want?
- 5
How will you evidence Consumer Duty outcomes, and who approves financial promotions?
- 6
Will the app ship under your developer account or the authorised firm's, and who answers App Review?
- 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?Up to 4 hours of changes a monthFits after this
App care
£550 a month
We keep your app working on each new iOS or Android, passing App Review or Play policy and looking current in the store, with time each month for changes.
What's coveredin App careUp to 1 hour of small edits a month
Website care
£95 a month
We keep your website online, up to date and secure, and make the small changes you need each month.
What's coveredin Website careUp to 3 hours of changes a month
Website care Plus
£195 a month
Everything in Website care, with three hours of changes a month for sites that need new pages, offers or content most months.
What's coveredin Website care Plus2 reserved build days a month, more if you need them
Ongoing development
From £1,500 a month
From £1,500 a month for 2 reserved build days to keep improving your app or web product, with a backlog we prioritise together and a release each month.
What's coveredin Ongoing development
Month to month, billed in advance. Cancel with 30 days' notice. Pay yearly for two months free. No VAT is added.
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.
By keeping the most sensitive data out of our systems where we can (a certified payment processor, tokenisation), and protecting what remains: secrets in secure hardware on the device, strong authentication with step-up for risky actions, encryption in transit and at rest, audit trails, and independent penetration testing before launch. We write the controls down so your compliance function can evidence them.
Yes, through an FCA-registered Open Banking provider or, if you hold the registration, directly with the banks' APIs. Account information and payment initiation each need consent flows that follow the standard, and we build those as part of the work.
A payment or money-management app typically takes 12 to 18 weeks to build once the regulatory route is settled. Partner onboarding, testing with payment rails and compliance sign-off often set the pace, and we plan around them rather than pretending they won't happen.
A straightforward payment or money-management app starts around £30,000. A product with several payment rails, KYC and AML tooling, Open Banking and both mobile platforms usually ranges from £60,000 to £150,000, before partner and licence fees. We give a fixed price after scoping, once the questions above have answers.
Cryptoasset promotions in the UK fall under the FCA's financial promotions regime, and both app stores have specific rules for crypto apps. If your product includes them, we scope that work separately and only once the compliance position is clear.
Where to go next
- Fixed-price offers
- Our own work
- Guides
- Plan your budget
Related services
SaaS MVP Development
Read about SaaS MVP DevelopmentA first version of your software product with sign-in, billing and the one workflow customers will pay for. You get a live product to test with real users, and code that can grow into the full version.
API integration services
Read about API integration servicesWe connect the systems your business already runs on, such as your CRM, payment provider, booking tool, accounting software and couriers, so data moves between them on its own instead of being copied by hand. A single integration is a fixed price from £3,500 and takes 2 to 4 weeks; a platform that joins several systems starts at £12,000.
Blockchain and Web3 development
Read about Blockchain and Web3 developmentSolidity smart contracts on Ethereum and EVM chains, wallet connection and sign-in, tokens and NFTs inside a web or mobile app, and dashboards built on on-chain data. Everything is tested, built on audited libraries and deployed to a testnet first. And if you don't need a blockchain at all, we'll say so.
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.
We reply within one working day. Or call 020 7078 5151