Choose your country or region

What a bank mobile app really costs.

The cost drivers behind a bank mobile app, how vendors usually price it, and the questions to ask before you sign.

By Everbranch team · Published · Updated · 4 min read

Ask five people what a bank mobile app costs and you'll get five numbers, none of them useful. The honest answer is that the price depends on a handful of drivers, and most of them have little to do with the screens your customers see.

This guide walks through those drivers, how vendors usually structure their pricing, and the questions that turn a vague proposal into one you can compare. We don't quote market prices here: they vary too much by country, core and scope to mean anything without your details.

People are the biggest line

Whether you build or buy, someone has to design, build, test and run the app. Building in-house means hiring for each of these roles and keeping them for as long as the app exists:

  • Product and design: someone who decides what the app does and makes it easy to use.
  • Mobile engineers for iOS and Android, and web engineers for online banking.
  • Backend and integration engineers who connect the app to your core and providers.
  • Security engineers and testers, plus someone who handles app store releases.

In many of the markets we work in – East and West Africa, Iraq, Sudan, Indonesia – these skills are scarce, and the people who have them are courted by fintechs and telecoms. Retention is a cost too. Our comparison of building in-house goes through the trade-offs in more detail.

Your core decides more than you think

The app is only as useful as its connection to your core banking system. A modern core with a documented API is the simplest case. An older core that only exchanges files, or exposes a database, takes more work – and that work is often the largest single item in an implementation.

Ask early how the app will reach your core. Common routes are a direct API, standard ISO 20022 files over SFTP or S3, read-only database views, or a message queue. The same applies to your identity checks, sanctions screening, payment schemes and mobile money partners. Each connection is a line in the budget, so list them before you ask for a quote. Our integrations page shows the kinds of systems a bank typically connects.

Security and compliance work

A banking app carries controls most apps don't: two-step sign-in for staff, step-up checks before sensitive payments, two-person approvals, audit trails, encryption of documents and secrets, and a separate environment for each bank's data. Building these from scratch is a project of its own. Buying them still means review time from your security team.

Budget for your own side as well. Your compliance team will set the onboarding policy, your risk team will review the vendor, and many banks commission a penetration test before launch. Our security page lists the controls we build in and what is still open, so you can see what your team would review.

App stores, hosting and upkeep

Some costs are small but fixed. Publishing on iPhone needs an Apple Developer Program membership, listed at $99 a year (opens in a new tab). Publishing on Android needs a Google Play developer account, which has a US$25 one-time registration fee (opens in a new tab). Apple's review guidelines (opens in a new tab) ask that apps in highly regulated fields such as banking be submitted by the legal entity that provides the service, so these accounts are usually your bank's own.

Hosting depends on where your data must live and how isolated it must be. A shared environment costs less; a dedicated one for your bank alone costs more. Then there is upkeep: every new version of iOS and Android, every security fix, every change in a payment scheme or a regulator's rules needs someone to update, test and release the app. This is the cost people forget, and it never stops.

How vendors usually structure pricing

Most vendors of banking apps combine some of these elements. Knowing which ones a proposal uses makes it much easier to compare.

Common pricing elements for a bank mobile app
ElementWhat it usually coversWhat to check
Annual subscriptionThe platform, hosting in a shared environment, updates and supportWhat is included, and what counts as an extra
One-off implementation feeConnecting your core and providers, designing and building your app, testingWhich connections and custom work are in scope
Usage-based feesCharges per active customer, per account or per transactionHow the fee grows as you grow, and whether there is a cap
Change requestsNew features or screens after launchWhether improvements to the shared product reach you at no charge
Dedicated hostingAn environment or cloud account for your bank aloneWho pays the cloud bill, and how it is shown

A low headline price can hide a large change-request budget. A high one may include years of upkeep. Compare total cost over the life of the contract, not the first invoice.

Watch the currency too. A bank in Iraq, Sudan or Nigeria earns in its own currency, while most software is priced in dollars or euros. Ask whether the price is fixed for the contract, how it changes with exchange rates, and whether hosting is billed separately in another currency. A predictable yearly figure is often worth more than a lower one that moves.

How Everbranch prices it

Our model is simple: an annual subscription for the platform, plus a one-off implementation fee to connect your systems and build your app. Both are quoted per bank, because no two banks have the same core, providers and products. Custom components built for your bank are part of the implementation fee, and every product update reaches your app as part of the subscription.

For the first banks we run a pilot programme, with terms agreed before the pilot starts. You can see the options on our pricing page, and how an implementation runs in how it works.

Questions to ask any vendor

  1. Which of our systems are connected in the quote, and how – API, files, database or message queue?
  2. Who designs the app, and how far can we change screens, flows and words?
  3. Is online account opening included, or priced separately?
  4. Who keeps the app current with new iOS and Android versions, and at what cost?
  5. What happens to price as our customer numbers grow?
  6. Whose developer accounts publish the app, and who owns the listing?
  7. What security controls are built in, and what will our team still need to review?

If you are weighing a ready-made template against a fully customised app, our comparison with white-label app vendors covers the differences that affect cost later.

Pilot programme

Want a real number?

Tell us your products, customers and core banking system, and we’ll send a clear proposal.

  • Your name and colours in the demo
  • Straight answers for risk, compliance and IT
  • No commitment