Verify by Receipt Text
Send OCR’d or copied receipt text for verification
receipt_text in the request body. The text can be OCR output from a receipt image or manually copied from the app.Use case
- Customer photographs their receipt
- Your app runs OCR (e.g. Google ML Kit, Tesseract)
- You send the extracted text to Check.et
- Check.et parses the bank and reference, then verifies
Tips
- Add
"bank": "cbe"as a hint if you know the bank - improves parsing accuracy - The text doesn’t need to be clean; Check.et handles noise from OCR
- Max
receipt_textlength: 50,000 characters
Example
Authorizations
API key from your dashboard - starts with chk_. Requires a business account.
Body
Bank code. Required unless using receipt_url, receipt_file, or receipt_text.
cbe, telebirr, dashen, awash, boa, zemen, cbebirr, mpesa, sinqee "cbe"
Reference number from the receipt. Required unless using receipt_url, receipt_file, or receipt_text.
"FT26144SG2ST"
Your receiving account (required for CBE, BOA). For CBE Birr, pass the payer's phone number (251XXXXXXXXX).
"1000876543218"
ID of a saved bank account - use instead of account_number.
Share URL from the banking app. Auto-extracts bank and transaction number.
"https://apps.ethiotelecom.et/receipt/DEL889NG4S"
OCR'd text from a receipt image (max 50,000 chars). Required alongside image files.
Response
Verified - success: true means the payment is confirmed
true = transaction confirmed
true
true = transaction found in bank records
true
true = already verified in this branch
false
null
Only present when duplicate=true
9812
Only present when duplicate=true

