Verification guide
Payment Verification API for Ethiopian Businesses
Ethiopian e-commerce platforms, logistics companies, and SaaS products that rely on manual receipt screenshots lose time and money at scale. The Check.et REST API brings structured, real-time verification of CBE, Telebirr, Dashen, Awash, BOA, Zemen, CBE Birr, and M-Pesa into any application with a single API key.
Why build on a verification API
Manual checks do not scale beyond a few counters. An API integration means your checkout, CRM, or fulfillment system verifies payment automatically and progresses the order only after a confirmed result - no human in the loop required.
What Check.et API returns
A normalized JSON response with status, amount, currency, payer details where available, provider, reference, and verification timestamp. The same schema works for every supported Ethiopian bank and wallet, so you write the integration once.
Common integration patterns
COD (cash-on-delivery) confirmation for logistics, automated order release for online stores, back-office reconciliation for accounting teams, and webhook-driven ERP updates for enterprise customers.
Steps
- 1.Sign up for a Check.et account and generate an API key in your workspace settings.
- 2.Choose the endpoint matching the payment provider: CBE, Telebirr, Dashen, or others.
- 3.POST the transaction reference and any required fields (e.g. receiving account for CBE).
- 4.Parse the normalized JSON response and trigger your business logic on a verified status.
- 5.Store the verification ID from the response for audit and dispute resolution.
Frequently asked questions
Which providers does the Check.et API support?
CBE, Telebirr, Dashen, Awash, Bank of Abyssinia, Zemen, CBE Birr, M-Pesa Ethiopia, and Siinqee (image-based).
Is there an SDK?
The Check.et API is a standard REST API that works with any HTTP client. Visit the developers page for endpoint documentation, authentication guides, and code examples.
What happens if the provider is temporarily unavailable?
Check.et returns a clear error status with provider context so your integration can surface the right message to end users rather than a generic failure.