Moves customer funds
Verify.ET
No — non-custodial verification tooling
Alternative
Yes — accepts and routes payments
Verify.ET vs payment gateways
Verify.ET vs Ethiopian payment gateways
Gateways collect money. Verify.ET confirms money already sent to your bank or wallet account.
A payment gateway hosts checkout, authorization, and settlement flows. Verify.ET is used when customers already paid via CBE transfer, Telebirr, or another supported method and staff or systems must confirm the receipt before fulfilling the order.
Decision guide
A quick fit check before you scan the full criteria matrix.
Choose Verify.ET when
- Customers pay by bank transfer or mobile money directly to you.
- Screenshot fraud is the main risk, not card authorization.
- You already have settlement accounts and only need confirmation.
- You want verification API without becoming a payments merchant of record for that flow.
Choose the alternative when
- You need hosted checkout, cards, or gateway-managed settlement.
- You must initiate collections rather than verify after payment.
- Regulated acquiring or PSP services are required for your product.
Side-by-side criteria
Scan the matrix, then open verify or pricing when Verify.ET is the fit.
| Criterion | Verify.ET | Alternative |
|---|---|---|
| Moves customer funds | No — non-custodial verification tooling | Yes — accepts and routes payments |
| Best input | Receipt reference, suffix, phone, or receipt URL | Checkout session, invoice, or payment intent |
| Fake screenshot risk | Designed to challenge forged receipt claims | Different risk model (auth failures, chargebacks) |
| Integration shape | Verify API + dashboard + mobile app | Pay-in APIs, webhooks for paid/failed states |
| When to combine | Use after off-platform bank/wallet payments | Use for online checkout collection |
Best input
Verify.ET
Receipt reference, suffix, phone, or receipt URL
Alternative
Checkout session, invoice, or payment intent
Fake screenshot risk
Verify.ET
Designed to challenge forged receipt claims
Alternative
Different risk model (auth failures, chargebacks)
Integration shape
Verify.ET
Verify API + dashboard + mobile app
Alternative
Pay-in APIs, webhooks for paid/failed states
When to combine
Verify.ET
Use after off-platform bank/wallet payments
Alternative
Use for online checkout collection
Keep exploring
Product, docs, or a deeper comparison — labeled paths, not raw URLs.
Ready to verify payments
Confirm Ethiopian receipts before you fulfill.
Use the web hub for desk work, the mobile app for counters, or the API when checkout and support tools need structured verification.
Comparison FAQs
Only if your commercial flow already receives money outside the gateway and you only need confirmation. If you need the gateway to collect payment, keep the gateway and optionally add Verify.ET for off-platform receipts.
No. Settlement already happened at the bank or wallet. Verify.ET reports whether the submitted receipt details match available provider data.
Verification tooling is built for that failure mode. Gateways reduce screenshot fraud by keeping payment inside their checkout, but they do not solve customers who insist on paying by transfer and sending a photo.
