Numa
Every dirham, explained
Client identities and brand marks are anonymised. Names, logos and interfaces shown are not real companies or real projects.
- Sector
- Consumer fintech
- Location
- Dubai, UAE
- Year
- 2026
- Kickoff to production
- 15 weeks
Spending insight and card controls for an issuer whose customers could see every transaction and understand none of them.
The app listed transactions exactly as the card scheme delivered them: a merchant string, a code, an amount. Customers rang to ask what a charge was, disputed things they had bought themselves, and had to phone in to freeze a card left in a taxi.
Merchants with names
Raw acquirer strings resolve to a real merchant, a category and a location, so a statement reads like a diary instead of a log file.
Controls where the panic is
Freeze, per-channel toggles, limits and an instant virtual replacement sit one tap from the balance: the screen a customer opens when the card is already gone.
Two sentences, not a chart
The monthly summary leads with the two categories that moved and what caused them. The chart is there for anyone who wants it.
Disputes that were really recognition problems faded, and freezing a lost card became something customers did themselves in the taxi queue.
What changed
- On every charge
- Named merchants
- Card freeze
- Self-serve
- From recognition
- Fewer disputes
- Swift
- Kotlin
- Postgres
- Python
- BigQuery
Tell us what's slowing you down.
Fifteen questions, one screen at a time, and a verdict at the end. No call needed to get it.