Commercial Bank of Ethiopia Receipt Format
Complete technical reference for CBE receipt format.
Read the API docsCBE endpoint URL format
The CBE receipt endpoint is: https://apps.cbe.com.et:100/?id={REFERENCE}{LAST_8_DIGITS_OF_ACCOUNT}. The URL combines the transaction reference and the last 8 digits of the receiving account into a single id parameter. Example: FT26140P01YB.
PDF response structure
CBE returns a PDF file. cheki downloads the PDF, extracts text using pdf parsing, and maps the extracted text to structured fields. The PDF contains a standard layout with the bank header, transaction details, and a QR code.
Field mappings for CBE
cheki normalizes CBE receipts into a standard JSON shape regardless of the source format:
- senderName: the account holder who sent the payment
- receiverName: the account holder who received the payment
- amount: the transferred amount in ETB
- currency: always ETB for domestic transfers
- date: transaction date and time
- reference: the CBE transaction reference number
- sourceUrl: the full URL cheki fetched the receipt from
Frequently asked questions
What format does CBE use for receipts?
Commercial Bank of Ethiopia publishes receipts as PDF document. The endpoint is https://apps.cbe.com.et:100/?id={REFERENCE}{LAST_8_DIGITS_OF_ACCOUNT}. The PDF contains payer name, receiver name, accounts, amount, date, reference, and branch.
Do I need authentication to access CBE receipts?
No. The CBE receipt endpoint at https://apps.cbe.com.et:100/?id={ref}{account} is publicly accessible without authentication. This is by design: banks want merchants to be able to verify payments without needing API keys or login credentials.
What fields are in a CBE receipt?
The CBE PDF receipt contains: Commercial Bank of Ethiopia header, payer name, payer account, receiver name, receiver account, transferred amount (ETB), payment date and time, reference number, and branch name.
Read the API docs
Open cheki