Product
Designing for Ethiopian payment rails
Telebirr, CBE, ArifPay and Chapa each behave differently. Lessons from integrating them into ERP, mobility and commerce products.
Accepting payments in Ethiopia means speaking several dialects at once. Mobile money, bank transfers and aggregators all settle differently — and customers expect every one of them to “just work”.
One interface, many rails
We wrap every provider behind a single payment module shared by Hive OS, Swift, Ignition and Mela. Products ask for a payment; the module decides how to collect it, tracks its state and reconciles it.
Design for the pending state
The most important screen in a payment flow is the one between “paid” and “confirmed”. Callbacks arrive late, USSD sessions time out, and customers close the app. We show clear progress, poll gently and never ask someone to pay twice.
Reconciliation is a feature
- Store the provider’s reference and your own, always.
- Run a daily job that compares settlements with orders.
- Give finance teams an export they can trust.
Written by
Techive Team
Innovating the future, one byte at a time.