Commercial Bank of Ethiopia Receipt Format

Complete technical reference for CBE receipt format.

Read the API docs

CBE endpoint URL format

The CBE receipt endpoint is: https://mbreciept.cbe.com.et/{RECEIPT_ID}. The URL takes only the transaction reference as a path parameter. Example: https://mbreciept.cbe.com.et/fHCxyV4mg5pRIwEkJO.

JSON response structure

CBE returns a JSON object. The response is structured and can be consumed directly without parsing. cheki passes the JSON through with normalized field names.

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 JSON API response. The endpoint is https://mbreciept.cbe.com.et/{RECEIPT_ID}. The JSON response contains structured fields including sender name, receiver name, amount, currency, and date.

Do I need authentication to access CBE receipts?

No. The CBE receipt endpoint at https://mb.cbe.com.et/api/v1/transactions/public/transaction-detail/{ref} 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 JSON response contains: sender name, receiver name, amount, currency, transaction date, and transaction reference.

Read the API docs

Open cheki

Related guides