M-Pesa Ethiopia Receipt Format
Complete technical reference for M-Pesa receipt format.
Read the API docsM-Pesa endpoint URL format
The M-Pesa receipt endpoint is: https://m-pesabusiness.safaricom.et/api/receipt/getReceipt?trxNo={REFERENCE}. The URL takes only the transaction reference as a path parameter. Example: SE12345678.
JSON response structure
M-Pesa 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 M-Pesa
cheki normalizes M-Pesa 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 M-Pesa transaction reference number
- sourceUrl: the full URL cheki fetched the receipt from
Frequently asked questions
What format does M-Pesa use for receipts?
M-Pesa Ethiopia publishes receipts as JSON API response. The endpoint is https://m-pesabusiness.safaricom.et/api/receipt/getReceipt?trxNo={REFERENCE}. The JSON response contains structured fields including sender name, receiver name, amount, currency, and date.
Do I need authentication to access M-Pesa receipts?
No. The M-Pesa receipt endpoint at https://m-pesabusiness.safaricom.et/api/receipt/getReceipt?trxNo={ref} is publicly accessible without authentication. However, it is geo-blocked to Ethiopian IP addresses. 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 M-Pesa receipt?
The M-Pesa JSON response contains: sender name, receiver name, amount, currency, transaction date, and transaction reference.
Read the API docs
Open cheki