Compare Chapa and Telebirr integration requirements, ease of setup, settlement, escrow needs, and realistic time to launch in Ethiopia.
Chapa vs Telebirr: the short answer
For a standard website or app checkout, Chapa is usually the quicker integration path once your business is registered and its compliance documents are ready. Its dashboard gives developers test keys, hosted checkout, callback and webhook options, and a transaction verification API. For a straightforward project, budget up to one week for integration and testing; live payment still depends on Chapa approving the business.
Telebirr is a longer business and technical onboarding project. If the company is still preparing its license, proposal, applicable sector permissions, security inspection, merchant agreement, and settlement details, plan for more than three months end to end. That is a planning estimate from the full process, not an official Ethio telecom service guarantee. Teams that already have approvals and credentials can complete the code much faster.
| Question | Chapa | Telebirr direct integration |
|---|---|---|
| Best starting point | Standard online checkout with several supported payment methods through one gateway | A business that needs an approved Telebirr product and direct merchant arrangement |
| Business readiness | Registered business, valid license and Chapa compliance approval for live mode | Registered and licensed company, proposal, settlement details, and any applicable inspection or sector approval |
| Developer access | Sign up, obtain test keys in the dashboard, integrate and verify, then request live access | Register the organization, choose and subscribe to the approved product, exchange credentials and keys, complete testing and UAT |
| Typical planning time | Up to one week for a simple integration when documents and app are ready; compliance approval may add time | Over three months end to end when approvals and documents must be obtained; actual duration varies |
| Indicative merchant transaction fee | About 2.88% | About 0.3%–1%, depending on the approved Telebirr payment product |
| Settlement | Confirm the approved payout account, fees and payout schedule with Chapa | Agree which merchant Telebirr account receives payment and where funds are transferred or settled |
| Escrow or marketplace funds | Do not infer escrow from ordinary checkout or split payment APIs | Do not infer escrow from a Telebirr merchant or settlement account |
These timelines are project estimates, not published provider commitments. The fee figures are indicative rates supplied for this comparison, not verified public price quotes: the Telebirr rate varies by the type of payment product approved for the business. Actual charges can also depend on the merchant agreement, payment method, taxes, and settlement or transfer costs. Ask both providers for a written fee schedule before pricing your product. A complex marketplace, recurring billing, refunds, or a regulated money flow needs separate scoping.
What do the fees mean in practice?
Using the indicative rates above, a ETB 1,000 payment would cost about ETB 28.80 with Chapa at 2.88%, or ETB 3–10 with direct Telebirr at 0.3%–1%, depending on the approved Telebirr payment product and before any other applicable charges. Chapa may offer more payment methods through one integration; direct Telebirr may have a lower transaction rate but a longer onboarding process. Compare the written merchant quotes for your actual payment methods and expected volume. Do not apply Telebirr wallet transfer or cash-out tariffs as though they were API merchant processing fees.
What you need before you start
Chapa requirements
Have your business registration, valid business license, owner or authorized representative details, and the payout account information ready for compliance review. Create a Chapa dashboard account, complete its compliance process, and use test keys while approval is pending. Chapa's quick start says live mode is available only after compliance is accepted. Confirm the exact current document list and account eligibility in the dashboard.
For a basic checkout, your developer needs an app or website with an HTTPS backend, a unique order reference, a return URL, and a callback or webhook endpoint. The backend must verify each payment before fulfilling an order.
Telebirr requirements
Start with the approved business model and money flow. Prepare a renewed business license, registration certificate, TIN, VAT certificate if applicable, company bank account, company stamp, and a proposal explaining the app, customers, payment journey, and settlement. An INSA inspection report and sector permission may be required for the type of app or service. The exact list depends on Ethio telecom's current onboarding decision.
Choose the Telebirr product that fits the journey: for example, H5 or C2B for web checkout, or an approved InApp or cross-app flow for mobile. Then follow the developer process for sandbox access, public-key exchange, callback and IP or domain configuration, testing, UAT, and production credentials. Our Telebirr onboarding guide explains the document and office process in more detail.
Which integration is easier for a developer?
Chapa has the shorter path for a normal checkout. Its documented flow is: create an account, get API keys, initialize a transaction on your backend, redirect the customer to the checkout URL, receive the callback or webhook, and verify the transaction before marking the order paid. Chapa also publishes SDK and plugin options. Live launch still waits for approved compliance and production keys.
Telebirr requires more coordination before code can go live. A developer must know which Telebirr product was approved, who owns the merchant account, the assigned settlement route, and the required security and network configuration. After credentials arrive, implement order creation, the approved payment flow, callback handling, transaction query or verification, and reconciliation. Use the Ethio telecom developer documentation for the exact API and product approved for your merchant.
In either case, keep secret keys on the server. A return screen or payment screenshot is not proof of payment. Match the provider result to your order reference, expected amount and currency, process repeated callbacks safely, and reconcile provider transactions against your bank or wallet statements.
System Integration & API Services
Connect identity, payment, SMS, ERP, CRM, mobile, and web systems with secure API integration in Ethiopia.
How much time should I allow?
| Stage | Chapa estimate | Telebirr direct estimate |
|---|---|---|
| Business documents | Prepare before requesting live mode; missing documents delay approval | Prepare license, proposal, settlement account, and applicable inspection or sector documents before applying |
| Technical work | A few days for a simple hosted checkout, verification, and failure handling | Several days to weeks after the correct product and credentials are available, depending on API flow and UAT |
| End-to-end launch | Plan up to one week when the business is ready, while allowing extra time if compliance review is pending | Plan over three months when the full business, security, and merchant approval process remains |
The biggest schedule risk is usually approval and readiness, not typing API requests. Ask the provider what is still outstanding before promising a launch date. Build and test the app while documents are being reviewed, but do not present a sandbox transaction as a production launch.
Telebirr settlement account: decide who receives the money
Write down the full path of funds before applying: who pays, which legal merchant receives the payment, which Telebirr merchant account is used, which company bank account receives settlement, who pays fees, and who handles refunds or disputes. The merchant name, licensed activity, proposal, and settlement account should describe the same business. Confirm settlement timing, transfer rules, transaction limits, fees, and reconciliation reports in the merchant agreement.
If an app pays drivers, sellers, organizers, or other third parties, explain that arrangement explicitly to Ethio telecom. A merchant settlement account is an account for receiving or transferring proceeds under approved terms; it does not by itself authorize the app to hold customer funds or operate escrow.
What if my app needs escrow?
Escrow means money is held and released only when agreed conditions are met. Ordinary Chapa checkout and a Telebirr merchant account should not be described as escrow services. Chapa documents split payments, but split routing is not the same promise as protected holding and conditional release.
For a marketplace, ride app, Equb app, or service platform, map each step: collection, ownership while pending, release trigger, payout recipient, failed delivery, refund, dispute, and audit record. Ask the provider whether it supports that specific flow and what approvals or licensed financial partner are needed. Get the arrangement confirmed in writing before telling customers their money is held in escrow.
Which should you choose?
- Choose Chapa first: when you need a standard checkout and want the simplest documented route to multiple supported payment methods, subject to business compliance approval.
- Choose direct Telebirr: when the business specifically needs a Telebirr product or direct merchant relationship and can support the longer onboarding and settlement process.
- Scope both separately: when you need provider redundancy or different customer journeys. Each still needs its own merchant approval, testing, reconciliation, and support process.
- Pause the payment architecture: when the app will hold money, release it conditionally, or distribute proceeds to third parties. Confirm the approved legal and provider model before implementation.
Official documentation and related guide
FAQ
How long does Chapa integration take?
For a registered business with its documents and app ready, plan up to one week for a straightforward checkout integration and testing. Live approval depends on Chapa's compliance review and can change the launch date.
How long does Telebirr integration take?
Allow more than three months for end-to-end planning when registration, sector permissions, security inspection, merchant approval, technical testing, and production access are still ahead. The API coding itself may take much less time.
Can I use a payment gateway as escrow for my app?
Do not assume ordinary checkout or a settlement account provides escrow. If an app must hold buyer money until delivery or distribute money to several parties, get the provider's written approval for that exact money flow and confirm the applicable legal and operational requirements before building it.