What this verification route checks
Verify.ET uses the submitted CBE receipt details to start a traceable verification request. The result popup shows the request status, receipt details, and repeat confirmation signals after the first run.
All Banks
Verify CBE transaction receipts
Reference number
Account suffix (last 8 digits)
Verify Transaction
Bank Verification Guide
How to verify Commercial Bank of Ethiopia transactions.
Verify Commercial Bank of Ethiopia transactions online by submitting the transfer reference number and the last 8 digits of the account number. Verify.ET turns that receipt evidence into a traceable verification request for counters, delivery teams, finance ops, and developers.
CBE transfer reference verification for merchants, finance teams, and support desks.
Who this route is for
Merchants, shop staff, delivery agents, finance teams, and support desks that receive CBE transfer screenshots or printed receipts and must confirm payment before fulfillment.
Required Fields
- Reference number
- Account suffix (last 8 digits)
Step-by-step
- Open the CBE verification route at /verify/cbe.
- Copy the transfer reference (often an FT-style code) from the CBE receipt or SMS.
- Enter the last 8 digits of the relevant account number as the account suffix.
- Submit the form and wait for a verified, pending, not-found, or failed result.
- Keep the Verify.ET request in history before releasing goods or closing a support ticket.
Need the SWIFT code instead? View CBE SWIFT / BIC details.
Comparing tools? See Verify.ET vs manual checks, gateways, and open-source scripts.
How to read the result
A successful CBE check returns structured verification status plus available receipt fields such as amount, parties, reference, and timestamps when the provider data is available. Pending means the job is still processing; not found or failed means the details did not resolve to a usable receipt—re-check typing, suffixes, and provider status before releasing goods.
Wrong account suffix length
CBE checks require exactly 8 suffix digits. Extra spaces, full account numbers, or 7/9 digit paste errors commonly produce not-found results.
Edited or forged screenshots
A photo of a receipt is not proof by itself. Always re-enter the reference and suffix into the checker instead of trusting only the image.
Provider latency or downtime
If CBE upstream data is slow or unavailable, the request may stay pending longer. Check /status/cbe and retry with the same reference rather than releasing on a screenshot alone.
How do I verify a CBE transaction?
Open the CBE verification route, enter the transfer reference number and the last 8 digits of the account number, then submit the request for a verification result.
What CBE receipt details are required?
CBE verification requires the transaction reference number and the 8-digit account suffix shown in the Verify.ET input panel.
Where do I find the CBE reference number?
It appears on the CBE mobile banking receipt, SMS alert, or printed transfer slip—often as an FT-style reference used for non-financial receipt verification.
Can staff verify CBE payments on mobile?
Yes. The Verify.ET mobile app supports receipt scanning and manual reference entry so counters and delivery teams can check CBE payments without a desktop.
Does Verify.ET move CBE funds?
No. Verify.ET only verifies submitted CBE receipt details. Funds stay in the bank settlement path the customer already used.
