Quickteller Rebirth

Recurring payments carry a unique anxiety: users are giving the platform permission to take money from them automatically — often long after the initial setup. The design challenge was building a setup flow that felt authoritative enough to deserve that trust, and a management interface that made it easy to stay in control after the fact.

The setup flow surfaces all the key parameters — amount, frequency, start date, end condition — in a clear sequence with full review before confirmation. No ambiguous "and it will keep going" language — every recurring instruction is explicit about when it starts, what it costs, and how to stop it. The management view shows all active and paused schedules with one-tap pause, edit, and cancel actions. Users should never have to hunt for the off switch.

Split payments involve multiple parties, multiple amounts, and often — some social awkwardness. The design had to handle the arithmetic invisibly while surfacing the right information to the person initiating the split and the people receiving the request.

The flow supports equal splits (divide automatically) and custom splits (assign specific amounts per person). Real-time running totals prevent over-allocation without requiring mental arithmetic. Participant selection draws from the user's existing contacts and beneficiaries — minimising re-entry friction. Each participant receives a clear, actionable notification with the amount owed and a direct payment path. The initiator gets a live status view of who's paid and who hasn't.

Beneficiary management is infrastructure — it sits beneath every transfer, split, and recurring payment flow. If it's slow, confusing, or untrustworthy, every dependent flow suffers. The design prioritised speed and confidence above all else.

Quick-add from transaction history means users never have to manually re-enter someone they've paid before. Inline verification at the point of adding a beneficiary confirms bank details before they're saved — preventing failed transactions downstream. Beneficiaries are organised by frequency of use, with search and filtering for larger lists. Edit and remove actions are accessible but not prominent — they exist, but they don't compete with the primary action of selecting a recipient.

USSD is the most constrained design medium there is: no graphics, no back button, no persistent state, no error recovery UI — just numbered menus on a basic phone. For millions of users without smartphones or reliable data connections, it's the only interface that exists. Designing for USSD is an exercise in radical prioritisation.

Every menu was structured around the most common action first. Menu depth was capped at three levels — USSD sessions timeout, and every additional tap is a drop-off risk. Confirmation screens before any financial action protect users from fat-finger mistakes with no undo. Balance checks were accessible within two inputs from the root menu. Airtime and data top-up flows were streamlined to the minimum necessary steps — amount, confirm, done. The discipline of USSD design fed directly back into how we thought about efficiency in the mobile flows too.

Quickteller agents are operators — not casual users. They process payments on behalf of customers, often in high-volume, time-pressured environments. The agent dashboard needed to prioritise speed and accuracy above everything else, with an interface that felt more like a professional tool than a consumer app.

The dashboard surfaces transaction initiation front-and-centre — not buried behind a navigation menu. Recent transactions are visible immediately for reference and reconciliation. Commission tracking gives agents real-time visibility of their earnings without requiring a separate report. Clear transaction status indicators (processing, completed, failed) mean agents never have to guess whether a transaction went through before telling a customer. Error states were designed with specific recovery paths — because a failed transaction at a physical agent point is a customer standing in front of you.

For a financial superapp used multiple times a day, authentication friction compounds. Every extra second at the login screen is a reason to use a less secure shortcut — or not open the app at all. Biometric login had to be the fastest, most trustworthy path to the app, with a fallback that didn't punish users when biometrics failed.

The opt-in setup flow is framed around convenience, not security theatre — users are told what biometrics enables (faster access) rather than what it prevents. The authentication screen triggers the biometric prompt immediately on open, with PIN fallback one tap away. Clear failure states distinguish between a biometric mismatch and a device capability issue — users aren't left wondering if something is wrong with their account or their phone.

The dashboard was structured around three deliberate layers, each earning its position based on frequency and urgency of use:

Layer 1 — Financial Overview: Account balance and recent activity. This is what users come for first — the answer to "what is my money doing right now." It had to be visible without scrolling and scannable in under two seconds.

Layer 2 — Quick Actions: Send, Pay, Top-up. The three most common transactional actions, permanently accessible from the home screen. Not buried in a menu, not requiring navigation — present and tappable.

Layer 3 — Service Discovery: Insurance, Loans, Travel, and the rest of the superapp ecosystem. Surfaced below the fold — important enough to be discoverable, but not competing with the core financial use case. The goal was ambient awareness, not aggressive promotion.