User Guide & Help Center

1. Create an account — click Sign up, enter your business name, email and a password. You get a web login and one API key (shown once — save it if you plan to integrate; you don't need it for this website).
2. Log in — your session lives in this browser. Use Log in on any device.
3. Verify your first payment — open Verify, pick the provider (or leave Auto-detect), paste the reference from the customer's payment SMS, and click Verify payment.

Tip: BOA and some Dashen references start with FT just like CBE. When in doubt, select the bank explicitly instead of Auto-detect.

Expected amount: enter the amount the customer owes you. If the real receipt says a different amount (a classic trick: pay 15 birr, edit the screenshot to 1,500), the result is flagged with an amount mismatch warning.

Every result carries a risk level — LOW MEDIUM HIGH CRITICAL — built from checks like duplicate receipts, reused references, amount mismatch, wrong receiving account, expired transactions and unusual verification bursts.

"Times verified" shows how often this same receipt was checked on the platform. A count above 1 with a receipt reused badge usually means the same receipt is being shown to more than one merchant.

A receipt can be 100% real and still be someone else's payment. Register your receiving accounts on My Account and every verification will also answer: was this paid into one of my accounts?

1. Open My Account → Settlement accounts.
2. Pick the provider and enter your account number (or telebirr phone) and the account holder name.
3. From then on, results show Paid to your account: yes / NO. Receipts paid elsewhere raise a settlement mismatch fraud signal.

The My Account page shows:

• Your statistics — total verifications, success rate, fraud flags.
• Verification history — every check you ran: when, provider, outcome, risk.
• API keys — generate additional keys for integrations. Each key is shown once; only a fingerprint is stored, so a lost key is replaced, never recovered.
• Settlement accounts — add or review your registered receiving accounts.

Everything on this website is powered by the same REST API you can call from your own systems: point-of-sale, e-commerce checkout, accounting tools or a Telegram bot.

• Start at Developers → Getting started.
• Interactive Swagger docs live at /docs.
• Python SDK: pip install ethiopayverify.
• Webhooks push transaction_verified and fraud_detected events to your backend.

How do I verify a Telebirr payment?

Open Verify, pick Telebirr (or leave Auto-detect), enter the 10-character transaction number from the payment SMS, and submit. No account number or phone is needed.

How do I verify a CBE transfer?

Select CBE, enter the FT reference from the transfer SMS and the last 8 digits of either the sender's or receiver's account, then submit. The digits are part of how CBE publishes its receipts — without them the receipt simply cannot be fetched.

How do I verify a Dashen Bank transaction?

Select Dashen and enter the reference number from the transaction receipt. If the payer shared the receipt link from the Dashen Super App, paste it into the receipt-link field — that's the most reliable route.

How do I verify a Bank of Abyssinia transaction?

Select Bank of Abyssinia, enter the reference number and the last 5 digits of the account, then submit.

Why does BOA ask for an account suffix?

The 5-digit suffix lets the slip be matched to the exact transaction without anyone revealing a full account number — same idea as CBE's 8-digit rule, just shorter.

How do I verify an Awash Bank receipt?

Select Awash and paste the receipt URL shared from the Awash app (or enter the transaction reference as a fallback). Yes — the receipt URL alone is enough.

How do I verify a Zemen Bank transaction?

Select Zemen and enter the reference, or paste the shared receipt link for the most reliable result.

What about CBE Birr, M-PESA, Siinqee or Kaafi Ebirr?

Not supported yet. EthioVerify's adapter architecture means each new wallet or bank is a single, isolated module — these are on the roadmap, and self-hosters can add one by following the developer guide.

• Passwords are stored hashed (bcrypt); we cannot see them. Choose a strong one.
• API keys are hashed at rest and shown only at creation. Treat them like passwords — keep them server-side, never in a browser or mobile app.
• Sessions are signed tokens valid for 60 minutes; logging out clears them from this browser immediately.
• Every account change (keys, webhooks, settlement accounts) is written to an audit trail.