Remittance
Kavi
Payday to home in eleven seconds
- Sector
- Remittance
- Location
- Dubai, UAE
- Year
- 2025
- Kickoff to production
- 17 weeks
A remittance app built for the fifteen minutes after payday: the last transfer, already priced, two taps from done.
Kavi's customers sent the same amount to the same person every month, and every month they filled in the same eight screens. Rates were indicative, payout partners failed quietly, and the app assumed a connection its customers did not have.
- 01
Repeat is the default
The home screen is the previous transfer, priced and ready. The form only appears when something genuinely changed.
- 02
Built for a weak signal
Everything up to funding works offline. The request queues and confirms when the network returns, so a transfer is never lost between a basement and a lift.
- 03
Corridors that fail over
Each corridor has ranked payout partners with live health checks. A partner that slows down is drained of traffic automatically, not after the complaints arrive.
Repeat transfers now complete in seconds rather than minutes, and the operations team stopped spending its evenings re-sending failed payouts by hand.
What changed
- Repeat transfer
- Two taps
- Before confirm
- Priced
- On payday evenings
- Ops quiet
Stack
- React Native
- Go
- Postgres
- Redis
- Temporal
Disciplines applied
- Financial technology
- Automation & operations
- Custom software development
