اختر بلدك أو منطقتك

Launching a mobile banking app, step by step.

From the first workshop to the app stores: the steps a small bank goes through to launch its own mobile banking app.

By Everbranch team · Published · Updated · 5 min read

Launching a mobile banking app is less about writing code than about making decisions in the right order. Which customers come first, which systems the app must reach, who approves what, and when real customers see it.

This guide follows the steps a small bank goes through, whether it builds alone or with a partner. We use the same order in our own implementation programme: discovery, connecting your core and tools, designing the experience, testing on your sandbox, a pilot, then launch.

1. Decide what launches first

Don't start with a feature list. Start with the customers you want to serve and the journey that fails them today. A bank in Lagos may want salary customers to open an account without a branch visit. A bank in Erbil may want traders to pay suppliers instantly. A bank in Jakarta may want customers to send money by mobile number.

Write down the first release in a few lines: personal or business customers, which accounts, which payments, which languages. Everything else becomes the next release. A focused first launch is easier to test, easier to explain and much easier to get right.

Name a sponsor and a small group who decide: someone each from operations, compliance and IT. Most delays in a launch come from decisions waiting for an owner, not from code. Agree now who signs off the design, the words, the risk policy and the day you open the doors.

2. Map your core and every tool around it

List every system the app must touch, with a name and a contact for each:

  • Your core banking system, its version and how it can be reached: API, files, database or message queue.
  • Identity checks and sanctions screening providers, if you already have them.
  • Payment schemes and wallets: an instant payment system such as BI-FAST or Aani, and mobile money partners such as M-Pesa or MTN MoMo.
  • Cards processor, SMS or messaging provider, and your staff directory for sign-in.

Note which systems have a test environment. You will need them later. Older cores are not a blocker: many exchange standard ISO 20022 files, and a new app can work through those. We explain the options in adding a new banking app on top of an existing core.

3. Set your rules and who decides

Before anyone designs a screen, agree the rules the app will enforce. Your compliance team sets the onboarding policy: which checks run, how applicants are scored, which ones are approved automatically and which go to a person. Your operations team sets payment limits and when a payment needs a second approver.

Name the people who will decide applications, review payments and answer customers. High-risk decisions should need two people, never the same one twice. If you want to see how explained scoring works, read risk scoring in digital account opening or the risk and compliance page.

4. Connect your systems and design the experience

These two run side by side. One team builds each connection to your core and providers and tests it against their test systems. Another designs the app: colours, type, screens, flows and words, in each language your customers use. Arabic needs right-to-left layouts; French and Bahasa Indonesia need copy written for those customers, not translated at the last minute.

Design for real conditions. Customers may be on a slow connection, on an older Android phone, or opening the app in a market stall. Every journey should survive a dropped connection and pick up where it stopped. With us, your app is built from one shared product and your own design package, so you get your own screens and flows without forking the code.

5. Test on your sandbox, then run a pilot

Every connection and every journey should run against your own test systems before a real customer sees it. Open an account, make a payment, freeze a card, send a support message, approve a high-risk application with two people. Your staff should run these journeys themselves, in the operations portal they will use every day.

Then run a pilot with a small group of real customers your team picks – often staff and their families first. Watch every case. Fix what confuses people. Only open the doors when your team is confident, not when a date on a slide says so.

Keep a short launch checklist and tick it from facts, not feelings: the core connection tested, every provider tested, the design and words signed off, the risk policy published, staff accounts set up with two-step sign-in, support and complaint rules agreed by your bank, and runbooks for incidents read by the people on call.

6. Publish in your bank's name

Your app should be published under your bank's own developer accounts. Apple's App Store 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, not by an individual developer. An Apple Developer Program membership is listed at $99 a year (opens in a new tab); a Google Play developer account has a US$25 one-time registration fee (opens in a new tab). Opening these accounts can take time for an organisation, so start early.

Prepare the store listing, screenshots and privacy details, and check the review rules that apply to banking. One example: Apple's guidelines say an app that lets people create an account must also let them delete it from inside the app. Our apps include a way for customers to ask to close their login or their accounts, which your staff complete with two people.

7. After launch: keep it current

Launch is the start. New iOS and Android versions arrive every year, payment schemes change their rules, and customers ask for new things. Plan who keeps the app current and how often you release. On a shared platform, improvements reach every bank's app; on an in-house build, your own team carries all of it. Our build-in-house comparison sets out what that means for your team.

Ask your security team what evidence they want before and after launch, and keep the audit trail switched on from the first day. Our security page lists the controls built into the platform and what is still in progress.

Pilot programme

Start with a call, not a contract.

Tell us your core and your first customers, and we’ll walk you through what your launch would take.

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