Bank Directory
How to Verify Ethiopian Bank Payments Online
CBE
Verify CBE transaction receipts
CBE transfer reference verification for merchants, finance teams, and support desks.
Telebirr
Verify Telebirr transaction receipts
Telebirr receipt verification for wallet payments, merchant orders, and support follow-up.
Dashen
Verify Dashen Bank transaction receipts
Dashen Bank receipt checks for teams that need a traceable transaction verification record.
BOA
Verify Bank of Abyssinia transactions
Bank of Abyssinia transaction checks using receipt references and account suffixes.
CBE Birr
Verify CBE Birr payment receipts
CBE Birr wallet payment verification using receipt numbers and phone details.
Awash
Verify Awash Bank transaction receipts
Awash Bank receipt URL and token verification for payment confirmation workflows.
MPESA
Verify MPESA transaction receipts
MPESA receipt verification for wallet payments, merchant orders, airtime bundles, and support follow-up.
Siinqee
Verify Siinqee Bank transaction receipts
Siinqee Bank receipt URL and token verification for Ethiopian payment checks.
Kaafi Ebirr
Verify Kaafi Ebirr mobile money receipts
Kaafi Ebirr receipt URL and token verification for mobile money payment checks.
Direct answer
Verify.ET helps businesses confirm Ethiopian bank and wallet payment evidence online. Choose the provider, enter the receipt or transaction details shown on the payment record, then submit the check. Sign in is required to run a verification and save its result; provider availability and returned fields can vary.
Three steps to verify
- Choose the bank or wallet that issued the payment receipt.
- Enter the reference, transaction number, account suffix, URL, token, or phone field shown for that provider.
- Sign in, submit the check, and review the returned status before releasing goods or closing a support case.
What you need
You need a Verify.ET account and the payment details from the customer receipt, SMS, or provider history. Never ask a customer to share a password or secret API key.
Important limitation
Verify.ET is an independent verification platform, not a bank or payment gateway. A pending, not-found, or failed result can reflect incomplete details, provider latency, or provider availability; do not release goods from a screenshot alone.
| Provider | Payment fields |
|---|---|
| Commercial Bank of Ethiopia | Reference number, Account suffix (last 8 digits) |
| Telebirr | Transaction number |
| Dashen Bank | Reference number |
| Bank of Abyssinia | Reference number, Account suffix (5 digits) |
| CBE Birr | Receipt number, Phone (251XXXXXXXXX) |
| Awash Bank | Receipt URL or token |
| MPESA | Transaction number |
| Siinqee Bank | Receipt URL or token |
| Kaafi Ebirr | Receipt URL or token, Phone (optional) |
Built for Ethiopians
Verify is much better on Mobile.
Compare verification approaches
Not sure whether you need Verify.ET, a payment gateway, manual portal checks, or an open-source script? Use the comparison pages before you integrate.
Frequently Asked Questions
Start with the transaction or reference number on the receipt. Some banks also need a phone number, account suffix, token, or receipt URL, and each bank page only asks for the fields that provider needs.
The verify hub routes customers to dedicated checkers for CBE, Telebirr, MPESA, BOA, Dashen, Awash, CBE Birr, Siinqee, and Kaafi Ebirr, so staff do not have to guess which form or input format to use.
The mobile app is faster for day-to-day counter and delivery work because staff can scan printed receipts, upload screenshots, or enter references from the same device they use with customers.
The dashboard gives owners and managers a central record of verification activity, failed or pending checks, staff usage, analytics, and reconciliation history instead of leaving proof of payment scattered across chats and screenshots.
Yes. Business plans are designed for owners, managers, and staff to work from the same verification history with clearer accountability than a shared device or a shared messaging thread.
No. Verify.ET verifies submitted transaction information from supported Ethiopian banks and wallets. It does not hold, move, reverse, settle, or custody funds.
Yes. The developer API accepts bank-specific or smart-router payloads, returns request IDs, and supports polling, server-sent events, and webhooks for completion.
Yes. Sign in is required to submit a verification and keep the result in your Verify.ET history. The provider-specific page shows the exact receipt fields required before you submit.
