Verification guide
How to Verify Ethiopian Bank & Mobile Money Transactions
Ethiopian businesses receive payments through many rails — CBE, Telebirr, Dashen, Awash, BOA, Zemen, CBE Birr, M-Pesa, and Siinqee. Each provider uses different reference formats. This guide explains how to verify payments consistently and why a unified verification hub saves time at the counter.
Choose the correct provider
Always match the customer's receipt brand to the right verifier. Using the wrong form causes false failures — for example CBE requires an account suffix while Telebirr does not.
Verify before you deliver
Confirm amount and payer details while the customer is present. Store successful verifications in a shared workspace so managers can audit staff activity later.
Automate with API when you scale
E-commerce, logistics, and ERP teams should integrate verification into checkout and fulfillment flows using Check.et REST API keys.
Steps
- 1.Identify the payment provider on the customer receipt.
- 2.Open the matching bank or wallet page on Check.et.
- 3.Enter only the fields that provider requires.
- 4.Review verified amount, payer, and timestamp.
- 5.Save or sync results to your operations system.
FAQ
Which Ethiopian payment methods does Check.et support?
CBE, Telebirr, Dashen, Awash, Bank of Abyssinia, Zemen, CBE Birr, M-Pesa Ethiopia, and Siinqee (image verification).
Is verification the same as bank statement reconciliation?
Verification confirms a specific receipt or reference in real time. Reconciliation matches many transactions to accounting periods — Check.et helps with both through history and exports.
How is Check.et different from manual screenshot checks?
Structured data, team history, API access, and standardized responses reduce human error and speed up disputes.