Telebirr H5 web checkout
For payments on a website. The customer goes to a Telebirr payment page, pays and comes back to your site. Your server confirms the payment before the order is marked paid.
Telebirr InApp payment
For Android and iOS apps. Your backend creates the order, then the app opens Telebirr to finish the payment. We test the flow with the Telebirr testbed app before going live.
Telebirr Mini App
A mini app runs inside the Telebirr app, so customers do not install anything new. We designed one for an electric minibus fare system: passengers scan a QR code, pick a seat and pay in Telebirr.
Telebirr Subscription Payment
For repeat payments on a schedule, such as plans or memberships. Telebirr must first approve the product, the customer consent and the settlement account. We help you check that your money model fits.
Chapa checkout and API
Chapa gives one checkout for cards, Telebirr, CBE Birr and other wallets. We connect the hosted checkout or the API, verify each transaction on your server and handle failed and pending payments.
CBE Birr payments
CBE Birr can be added through Chapa, or connected directly when CBE gives you merchant access. We confirm the route after we see your account details.
What our payment integration includes
Help with the provider documents and proposal. Sandbox and live setup. Order creation, callbacks and signature checks. Status queries and failed or pending payments. Reconciliation that matches each payment to an order. Testing, go-live support and handover to your team.
Payment integration packages
Choose Chapa, direct Telebirr, CBE Birr or a combination. Website checkouts, existing apps, ERPs, Mini App and Subscription work each get a fixed quote after a short assessment. If we build your mobile app, Telebirr integration is included in the development price.
Integration timeline by provider
Telebirr: about 3 months end to end, covering the license, proposal, INSA inspection, merchant approval and testing. The coding itself is much shorter. Chapa and similar payment gateways: about 1 week for a simple checkout once your documents and app are ready. CBE Birr through Chapa follows the Chapa timeline; a direct CBE Birr connection is confirmed once we see the onboarding steps.
Platforms we connect payments to
Websites and web apps. Android and iOS apps, including Flutter. Backends in Node.js and Laravel. Telegram Mini Apps. Odoo, ERPNext and custom ERPs, so a confirmed payment can mark the invoice or order as paid.
Our open-source Telebirr SDKs
We publish free Telebirr packages on GitHub: telebirr_inapp_purchase_plus for Flutter, telebirr-laravel-plus for Laravel and telebirr_plus for Node.js. Your developers can use them, or we use them to integrate for you.
How the integration process works
1. We choose the provider and product with you. 2. We check your documents and help write the proposal. 3. You apply, and we build and test in the sandbox meanwhile. 4. We set up callbacks, IP whitelisting and SSL. 5. We finish testing and get live credentials. 6. We launch carefully and reconcile payments every day. The whole process takes about 3 months for Telebirr and about 1 week for Chapa and similar gateways.