LIQverify
LIQverify
All banks

BOA

Verify BOA receipts

Bank of Abyssinia (BOA) is one of Ethiopia's largest private banks. BOA publishes receipt data as JSON via a public API endpoint that requires the transaction reference and the las…

5 guest checks left · no account required on this page

Bank verification guide

How to verify Bank of Abyssinia transactions

Bank of Abyssinia (BOA) is one of Ethiopia's largest private banks. BOA publishes receipt data as JSON via a public API endpoint that requires the transaction reference and the last 5 digits of the receiving account number. For inter-bank transfers (BOA to CBE, Dashen, etc.), BOA receipt QR codes use AES-256-CBC encryption and can be decrypted by LIQverify for instant verification. No Selenium or headless browser required.

Who this route is for

  • Merchants verifying BOA transfers at checkout
  • Businesses reconciling BOA deposits
  • Verifying inter-bank transfers (BOA to CBE, Dashen, etc.) via QR code decryption
  • Apps integrating BOA payment verification with QR code support
  • Finance teams auditing BOA transactions

Required fields

  • Reference Number
  • Account last 5
  • Format: Alphanumeric reference starting with 2 letters (varies by transaction type). Inter-bank transfers use FT references (e.g., FT252003JZPP). (e.g. AB12345678)

Step-by-step

  1. 01For BOA-to-BOA transfers: get the transaction reference and last 5 digits of your receiving account
  2. 02LIQverify calls BOA's public JSON API and returns structured payment data in 1-2 seconds
  3. 03For inter-bank transfers (BOA to CBE/Dashen/etc.): scan the QR code on the receipt with LIQverify's camera scanner or upload a screenshot
  4. 04LIQverify auto-detects BOA QR payloads, decrypts them server-side with AES-256-CBC, and returns the full transaction details. No account number needed.

What this verification route checks

LIQverify starts a live request to Bank of Abyssinia using their public receipt endpoint. A successful check returns structured payment data — parties, amount, time, and any extra fields the bank or wallet exposes.

How to read the result

Confirmed means the bank record matched. Failed shows a clear reason (format, not found, network, or geo-block). Never treat a screenshot alone as proof — only the bank confirmation counts.

Older FT / legacy references

Bank of Abyssinia may need receiving account number (last 5 digits) together with the reference. Newer receipt links often work with the ID alone.

Edited or forged screenshots

Always paste the reference (or use QR / photo OCR) and let LIQverify re-check the bank. Do not trust a polished image without a live confirmation.

FAQ

Does BOA verification require Selenium or a headless browser?

No. Unlike the ethiobank_receipts library which requires Chrome WebDriver for BOA, LIQverify uses BOA's JSON API directly. This is faster, lighter, and works in serverless environments without browser dependencies.

What information do I need to verify a BOA transaction?

For BOA-to-BOA transfers, you need the transaction reference number and the last 5 digits of the receiving account. For inter-bank transfers (BOA to CBE, Dashen, etc.), scan the QR code on the receipt. No account number is needed for QR-based verification.

Can I verify inter-bank BOA transfers (sent to CBE or other banks)?

Yes, but only via QR code. BOA's JSON API returns 'Invalid reference number' for inter-bank transfers (FT references). Scan the QR code on the receipt and LIQverify decrypts it with AES-256-CBC to extract the full transaction details. See our BOA QR code guide for the technical breakdown.

How does BOA QR code verification work?

BOA receipt QR codes contain the transaction data encrypted with AES-256-CBC using CryptoJS format. The encryption key is embedded in BOA's public receipt web app. LIQverify decrypts the QR payload server-side and returns structured JSON with sender, receiver, amount, date, and reference. See our BOA QR code breakdown for full details.

Is the BOA receipt endpoint public?

Yes. The BOA online slip API at cs.bankofabyssinia.com is publicly accessible without authentication. other checkers and other checkers charge you for calling this same endpoint.

Is BOA QR code verification secure?

The AES key is public in BOA's web app JavaScript, so anyone can decrypt (and theoretically forge) QR codes. For high-value inter-bank transfers, request additional confirmation like a bank statement or SMS alert. See our BOA QR code guide for the full security analysis.