A mobile banking app doesn't forgive mistakes. Incorrect balance display, completed transfer without confirmation, session loss during a transaction — each of these costs user trust and potentially money. Architectural decisions here are driven by security, not development convenience. We have been developing mobile banking apps for over 5 years, delivered 15+ projects for European and Asian banks. Each project undergoes security architecture review and load testing. We offer turnkey development: from analysis to store publication and support. Estimate your project in 2 business days — contact us.
Key Challenges in Mobile Banking App Development
A mobile bank must work flawlessly under loads up to 10,000 transactions per minute while remaining unbreakable. We have encountered cases where lack of idempotency caused users to lose money and banks to lose reputation. On one project, implementing certificate pinning prevented an MITM attack when a CA was compromised. That's why every project starts with threat modeling and security architecture review.
Authentication and Biometrics
Let's start with what happens on every app launch. Classic approach: JWT in Keychain (iOS, .whenUnlockedThisDeviceOnly) / EncryptedSharedPreferences via Android Keystore. On launch — BiometricPrompt (Android) / LAContext.evaluatePolicy(.deviceOwnerAuthenticationWithBiometrics) (iOS).
Biometrics unlock an encryption key that protects the refresh token — not the token itself. If an encrypted blob is stolen from Keychain without the private key from Secure Enclave, decryption is impossible. This is critical for bank certification requirements.
PIN as fallback: store a hash of the PIN in Keychain. Never store the actual PIN. Never send the PIN to the server. Server authentication uses tokens; biometrics and PIN are only for local session unlocking.
Jailbreak/Root detection is a requirement for most banks. iOS: check for cydia://, mobile substrate, write access to /, successful fork(). Android: RootBeer library or SafetyNet Attestation API / Play Integrity API (current). If root is detected, the app either refuses to launch or runs in restricted mode.
Why Idempotency Matters for Transfers
The transfer form is technically simple but UX-critical. After entering the amount and recipient, a confirmation screen shows full details before submission. The confirm button has an artificial 1–2 second delay (prevents accidental double-tap). For large amounts, re-authentication via biometrics or PIN is required.
Idempotency for transfers: each transfer request contains a unique idempotency_key (UUID generated on the client). If the network is lost and the request is retried, the server returns the result of the first request without creating a duplicate. This is critical — without idempotency, a user with unstable internet could send the transfer twice. Thanks to this mechanism, we reduced duplicate transactions to 0.01%.
Transaction history: paginated list, cursor-based. Grouped by date. Search by description, amount, recipient. Detailed transaction page: all details, status, receipt in PDF (server-generated, downloadable on device).
How to Ensure Data Protection in Mobile Banking
A mobile banking app never stores PAN card numbers in plain text anywhere. Even masked numbers (**** 1234) are only for display, not for logging. Firebase Crashlytics and Analytics must have PII collection disabled: FirebaseCrashlytics.crashlytics().setCrashlyticsCollectionEnabled(false) until explicit user consent.
Network traffic — Certificate Pinning. On iOS: NSURLSession with URLSessionDelegate.urlSession(_:didReceive:completionHandler:), comparing the SHA256 of the certificate's public key. On Android: OkHttp CertificatePinner. This protects against MITM attacks even with a compromised CA.
We update SSL pinning when certificates rotate via OTA configuration updates (Firebase Remote Config or own endpoint) — not through store updates. Otherwise, all old app versions would stop working after certificate expiration.
Transaction Notifications
Push for every operation is standard. Requirements: delivery within seconds, not minutes. FCM with priority: high for Android, APNs with apns-priority: 10 for iOS. Critical: if a push is not delivered (device offline), on next app open — sync unconfirmed transactions.
Rich push notification: amount, operation type, last 4 card digits. On iOS — UNNotificationServiceExtension to decrypt end-to-end encrypted push payloads (banks often encrypt sensitive data in push). Push response time — under 500 ms.
Accounts and Cards
Main dashboard screen: list of accounts with balances. Card widget (physical or visual representation). Card management: blocking, limits, view details (CVV only after biometrics, not stored in memory longer than 30 seconds).
Apple Pay / Google Pay tokenization: for adding a card to Wallet — PKAddPaymentPassViewController (iOS) / PushProvisioningActivity (Android). This is not a standard payment integration — it requires a special agreement with Visa/Mastercard and certification. The process takes months; start early.
In-App Chat Support
In-app chat with a bank employee. Stream Chat SDK or Sendbird — enterprise-ready solutions with history, search, push on new message. Messages are encrypted in transit and stored on the provider's servers — we verify compliance with regulatory requirements.
Architecture: Native vs Cross-Platform
| Criteria | Native (Swift + Kotlin) | Flutter | React Native |
|---|---|---|---|
| Access to Secure Enclave/Hardware | Full | Via abstraction (needs audit) | Via bridge (extra verification) |
| Performance | Maximum | High (90%+) | Medium (60-80%) |
| Security audit | Easier — native APIs | Requires additional checks | Requires additional checks |
| Development time | Longer (two codebases) | Faster (one codebase) | Faster (one codebase) |
Native Swift (iOS) + Kotlin (Android) is preferred for FinTech. Reason: maximum security control, native access to Secure Enclave, BiometricPrompt, Apple Pay provisioning. Additionally, security audit is simpler.
Clean Architecture: Domain (Use Cases) / Data (Repository, API) / Presentation (MVVM, ViewModels). Testability of each layer is mandatory — unit tests on Use Cases, integration tests on Repository.
Flutter — acceptable for FinTech if you have experienced Flutter developers. Limitations: flutter_secure_storage uses Keychain/Keystore but through an abstraction layer that needs auditing. local_auth for biometrics works correctly.
Development Stages and Timelines
| Stage | Duration |
|---|---|
| Security architecture review | 1–2 weeks |
| Design and UI | 2–4 weeks |
| Authentication, biometrics | 2 weeks |
| Accounts, transfers, history | 4–6 weeks |
| Cards and Apple/Google Pay | 3–4 weeks |
| Push notifications, chat | 2 weeks |
| Security audit and regulatory approval | 2–4 weeks |
| Store publication | 1 week |
Example project structure
```
Project/
├── app/
│ ├── src/
│ │ ├── main/
│ │ │ ├── kotlin/com/bank/
│ │ │ │ ├── domain/
│ │ │ │ ├── data/
│ │ │ │ └── presentation/
│ │ │ └── res/
│ └── build.gradle
├── domain/
├── data/
└── presentation/
```
What's Included
- Security architecture review and threat modeling
- Design system for your brand
- Authentication: biometrics, PIN, JWT, root detection
- Accounts and balances, transfers with idempotency
- Payment system integration: Apple Pay, Google Pay
- Push notifications with rich content
- Chat SDK for support
- Documentation: architecture, API, security policies
- Access to repositories, CI/CD, store accounts
- Client team training
- Post-release support: 3-month warranty
Process
Security architecture review → design → authentication and biometrics → accounts and balance → transfers with idempotency → transaction history → cards and Apple/Google Pay → push notifications → security audit → regulatory approval → publication.
Timeline Estimates
MVP FinTech app (authentication, accounts, transfers, history): 8–12 weeks. Full mobile bank with cards, Apple/Google Pay provisioning, support chat, investment module: 4–8 months. Investment for MVP starts from 2 million RUB; exact cost determined after requirements analysis and security scope.
Contact us to estimate your project — get an exact calculation in 2 days. Request a consultation, and we will prepare a commercial proposal with a detailed work plan and timeline.