CASE STUDY · MOBILE PAYMENTS
How Brandsmashers helped Airtel Africa deliver clearer, safer Airtel Money transactions.
- 100%Balance & restriction state coverage*
- Cross-OSiOS & Android behavioral parity*
01 · PROJECT OVERVIEW
Money moves fast. The UI has to keep up.
Airtel Money is where trust gets tested one transaction at a time. If a balance check is unclear, or a failed transaction doesn't explain why it failed, users lose confidence fast regardless of how solid the backend is.
As Airtel Africa continued building out its mobile app, Brandsmashers joined the iOS development team to focus specifically on the Airtel Money experience: the screens, the states, and the messages users see when a transaction goes through or doesn't.
- 1UI screens for the Airtel Money section
- 2Handling for Transaction Not Allowed scenarios
- 3Handling for Insufficient Balance and Frozen Balance cases
- 4Preventing transactions when the usable balance is insufficient
- 5Clear, user-friendly messaging at every transaction state
02 · THE CHALLENGE
Every balance state needed its own clear story.
A payment app can't just show "success" or "error." Users needed to understand exactly what was happening with their money whether it was a hard restriction, a frozen balance, or simply not enough usable funds.
- PROBLEM 01Multiple balance states
Insufficient balance and frozen balance needed distinct handling, not a single generic error
- PROBLEM 02Transaction restrictions
Some transactions needed to be blocked outright, with a reason the user could understand
- PROBLEM 03Risk of user confusion
Vague error messages lead to support tickets and lost trust in the app
- PROBLEM 04Cross-platform consistency
iOS and Android needed to feel and behave the same way for the same scenarios
Payment flows don't get a second chance to explain themselves. The moment a transaction is blocked or a balance looks wrong, the UI has to make sense instantly.
03 · THE PROCESS
Building the screens, then proving them across platforms.
- 01iOS UI Development
Built out the UI screens for Airtel Money, covering different transaction scenarios end-to-end including insufficient balance and frozen balance states so each case had its own clear, correct interface.
- 02Transaction Safeguards
Implemented logic to prevent transactions from going through when the usable balance was insufficient, and surfaced Transaction Not Allowed scenarios clearly instead of failing silently.
- 03Cross-Platform Collaboration
Worked closely with the Android and QA teams throughout testing, validating that UI flows and functionality behaved consistently across both platforms.
- 1→Requirement scope
- 2→UI screen architecture
- 3→Balance state logic
- 4→Restriction handling
- 5→Cross-platform alignment
- 6→QA validation & regression
- 7Production deployment
04 · RESULTS
What changed.
Users received instant clarity on every transaction state, and inconsistent cross-platform errors were eliminated.
| BEFORE | AFTER |
|---|---|
| Generic or unclear transaction error states | Distinct, clear flows for insufficient balance, frozen balance, and restricted transactions |
| Risk of transactions attempted on insufficient usable balance | Transactions blocked proactively with clear messaging |
| Platform behavior validated separately | iOS and Android flows tested together for consistency |
| Unverified UI logic | Full QA validation across transaction scenarios |
- Clear and user-friendly Airtel Money flows
Users receive precise feedback on transaction progress and balance status
- Proper handling of restrictions & balance scenarios
Prevented invalid transaction submissions before network roundtrips
- Consistent experience across iOS and Android
Unified UI and UX rules across both operating systems
- Successful UI validation with the QA team
Ensured zero regression across edge-case payment states
05 · DELIVERABLES
What we delivered.
- Airtel Money UI screensComprehensive native iOS screens designed for clear transaction flows.
- Balance validation logicDefensive frontend handling for insufficient, usable, and frozen balances.
- Restriction guardrailsInstant feedback messaging for Transaction Not Allowed rules.
- Cross-platform parity testingEnd-to-end regression validation alongside the Android and QA squads.
- Platform
- Native iOS (Swift)
- Validation
- Cross-platform parity with Android
- Domain
- FintechMobile MoneyPayment Safeguards
- Testing
- QA edge-case test suites & UI state simulation
WHY IT WORKED
Clarity at the point where trust is won or lost.
Payment flows don't get a second chance to explain themselves the moment a transaction is blocked or a balance looks wrong, the UI has to make sense instantly. By building each balance and transaction scenario as its own clear flow, and validating it hand-in-hand with Android and QA, Brandsmashers helped Airtel Africa deliver an Airtel Money experience users could actually trust.
YOUR TURN
Building a mobile money or fintech app that needs airtight UI logic?
Brandsmashers Tech provides dedicated iOS and Android developers for teams building consumer-facing financial products. Tell us what you're building and we'll tell you how we'd approach it.