A simple guide to Telebirr integration requirements, documents, proposal, office process and product choice for e-commerce, ride-hailing and Equb apps.
Related guides in this journey
Telebirr integration should start after the company, license, system, security documents, and business model are ready. The main question is simple: what service are you selling, who pays, and where should the money settle?
Do not start from the API code first. Start from the documents and approval process, then choose the Telebirr product that matches the real customer journey.
Step 1: finish the business foundation
Before requesting Telebirr, make sure the company is registered and licensed for the service it provides. The license, TIN, proposal, bank account, app name, and settlement name should match.
- For e-commerce, finish the business license, app or website, INSA inspection, activity update, and current MInT check where applicable.
- For ride-hailing, finish business field 71113, INSA inspection, MInT process, and transport permission before requesting Telebirr, SMS, or call-center services.
- For Equb, confirm the money flow first. A software-only organizer is different from a platform that collects, holds, or controls member money.
Helpful starting guides: e-commerce company, ride-hailing app, and Equb app.
Step 2: choose the right Telebirr product
Use the product that matches the user journey. These are practical starting points, but the Telebirr team must approve the final product.
E-commerce
For an online shop, marketplace, booking website, or delivery checkout, start by asking for C2B or H5 web checkout. If the checkout is inside a mobile app, ask whether InApp or cross-app payment is the better fit.
Ride-hailing
For a passenger mobile app, InApp or cross-app payment is usually the practical starting point. Before applying, prepare the transport permission, approved system, INSA result, company bank account, and driver or company settlement explanation.
Equb
For Equb, do not request recurring payment before the money model is approved. Subscription Payment may be relevant only when the merchant, consent, schedule, settlement account, and legal model are clear. If the app only records manual contributions, Telebirr integration may not be needed.
Step 3: prepare required documents
Prepare the same clean document set before going to the Telebirr integration office. Missing documents slow the process more than code.
- Renewed business license.
- Registration certificate.
- Tax Identification Number (TIN).
- VAT certificate, if registered.
- Memorandum and articles of association, where applicable.
- Request letter and website or app security inspection approval from INSA.
- Company bank account that will receive transferred money.
- Company stamp for signing documents.
Step 4: prepare the proposal
The proposal should explain the business in simple language. It does not need to be complicated, but it must answer how the service works and why payment integration is needed.
- Company profile, clearly stating the main service to integrate.
- How the current business operates or what the platform provides.
- Business readiness, including time to market and whether the service is already live.
- Technical readiness of the app, website, or both.
- Specific integration channel: app, web, or both.
- How you work with clients and how the payment strategy works.
- User manual or flow chart.
Step 5: go to the right office
Take the documents, proposal, company stamp, company bank account information, and ID card when starting the process.
Step 6: complete the technical integration
After approval starts, the technical team can configure the integration. Keep secrets on the server, not inside the mobile app.
- Register the organization or merchant in the developer process.
- Subscribe to the approved product.
- Receive sandbox credentials.
- Exchange public keys through the approved channel.
- Configure local IP, server IP, callback URL, domain, and HTTPS certificate where requested.
- Test create order, payment, callback, query, failure cases, and reconciliation.
- Complete UAT and request production credentials.
- Launch slowly and reconcile every transaction daily.
For implementation details, use how to integrate telebirr to your app (Technical Guide).
Step 7: go live carefully
Go live only after business approval, technical testing, callback verification, reconciliation, support process, and refund or complaint handling are ready.
- Business license and TIN ready
- INSA approval or report ready where required
- Sector permission ready where required
- Proposal and user flow ready
- Company stamp, bank account, and ID card ready
- Callback, query, and reconciliation tested
Frequently asked questions
What is the best option for e-commerce?
C2B or H5 checkout is usually the starting point for web checkout. For mobile-app checkout, ask about InApp or cross-app payment.
What is the best option for ride-hailing?
InApp or cross-app payment is usually practical for a passenger app, but transport permission and the approved settlement model should come first.
What is the best option for Equb?
If the app only records contributions, Telebirr may not be needed. If recurring payment is needed, Subscription Payment may fit only after the money model and consent are approved.
Do I need INSA before Telebirr?
For apps, websites, and regulated digital services, prepare the INSA inspection approval or report because it can be requested during onboarding.
Can a developer start without company documents?
A developer can read documentation and prepare test code, but production onboarding needs the approved organization, license, proposal, and settlement information.