Chapa — Encyclopedia
Last updated: January 2024
Overview
Section titled “Overview”Chapa Financial Technologies is Ethiopia’s most developer-friendly payment gateway. Founded in 2021, Chapa positioned itself as the “Stripe of Ethiopia” — a modern, API-first payments company targeting developers and startups who found the existing options (Telebirr, CBEBirr) too painful to integrate.
Unlike Telebirr or CBEBirr, Chapa is not a mobile money operator. It is a payment aggregator — it connects merchants to multiple payment methods through a single checkout experience.
Ownership & Structure
Section titled “Ownership & Structure”| Detail | Value |
|---|---|
| Company | Chapa Financial Technologies PLC |
| Founded | 2021 |
| Headquarters | Addis Ababa, Ethiopia |
| Type | Private company |
| Funding | Raised seed funding (undisclosed) from African and international investors |
| Regulator | National Bank of Ethiopia (NBE) |
| License | Payment Instrument Issuer license (NBE) |
Chapa is the first company of its kind in Ethiopia: a private-sector, developer-first payment gateway operating under NBE licensing. This is meaningful because the alternatives are either state-owned (Telebirr = Ethio Telecom) or bank-owned (CBEBirr = Commercial Bank of Ethiopia).
Market Position
Section titled “Market Position”Chapa is the go-to for Ethiopian tech startups and international companies entering the Ethiopian market. Among developers, it has the best reputation for:
- API quality and documentation
- Developer support
- Sandbox environment
- Onboarding speed
It is not the largest by transaction volume — Telebirr handles more volume by orders of magnitude. But for the developer and startup market, Chapa dominates mindshare.
Supported Payment Methods
Section titled “Supported Payment Methods”When a customer pays via Chapa’s hosted checkout, they can choose from:
| Method | Availability |
|---|---|
| Telebirr | Yes |
| CBEBirr | Yes |
| Commercial Bank of Ethiopia (direct) | Yes |
| Awash Bank | Yes |
| Cooperative Bank of Oromia | Yes |
| Amhara Bank | Yes |
| Abyssinia Bank | Yes |
| Dashen Bank | Yes |
| Visa Card | Yes (limited) |
| Mastercard | Yes (limited) |
This is Chapa’s core value proposition: one integration gives merchants access to most Ethiopian payment methods. Contrast this with integrating Telebirr, CBEBirr, and each bank separately.
Fee Structure
Section titled “Fee Structure”| Tier | Rate | Notes |
|---|---|---|
| Standard | 1.5% per transaction | Default for new merchants |
| Volume negotiated | 0.8-1.2% | Available to higher-volume merchants |
| Minimum fee | 5 ETB | Applied to small transactions |
| Monthly fee | None | No subscription or setup fees |
Fee transparency: Chapa is more transparent about fees than most Ethiopian gateways. Fees are shown clearly in the dashboard.
Negotiation: Merchants processing above roughly 1 million ETB/month have room to negotiate. Contact your Chapa account manager. The negotiated rate is typically 1.0-1.2% — 0.8% is achievable at very high volume.
Card fees: Visa/Mastercard transactions carry higher fees (~2.5-3%) due to card network costs. This is separate from the standard rate and applied automatically.
Settlement
Section titled “Settlement”| Detail | Value |
|---|---|
| Advertised cycle | T+1 business days |
| Real-world cycle | T+1 to T+2 |
| Settlement threshold | 500 ETB minimum |
| Settlement days | Monday - Friday |
| Currency | ETB |
| Method | Bank transfer |
Real-world notes: T+2 is more common than T+1, especially for transactions processed in the afternoon. Chapa’s batch processing cutoff is approximately 2 PM Ethiopian time (UTC+3).
Holiday periods (Ethiopian Christmas, Timkat, Easter, Eid) cause 1-3 day delays in settlement. Build this expectation into your cash flow planning.
Merchant Onboarding
Section titled “Merchant Onboarding”This is where Chapa genuinely differentiates. Most of the process is online:
- Register at dashboard.chapa.co
- Submit documents online:
- Trade license
- TIN certificate
- Business bank account details
- Review period: 2-5 business days (vs. weeks for Telebirr)
- Receive API keys immediately for sandbox; live keys after approval
Sandbox access is instant — you can start testing the same day you register, before KYC approval.
API Quality
Section titled “API Quality”Honest assessment: the best in Ethiopia.
| Aspect | Rating | Notes |
|---|---|---|
| API documentation | 4/5 | Well-maintained, accurate |
| Sandbox reliability | 5/5 | Excellent; closely mirrors production |
| Production stability | 4/5 | Strong uptime track record |
| Error messages | 4/5 | Clear and actionable |
| Support responsiveness | 4/5 | Active developer community, responsive email |
| Webhook reliability | 4/5 | Reliable with retry support |
Chapa maintains a status page and has a developer Telegram community (one of the few Ethiopian payment companies that does).
Known API quirks:
- Uses
tx_refin requests buttrx_refin return URL query parameters (inconsistent naming) - Webhook signature uses a custom hash scheme, not standard HMAC-SHA256
- USD payments are available but require additional merchant approval
Regulation
Section titled “Regulation”Chapa operates under:
- NBE Payment Instrument Issuer Directive — licensed as a payment service provider
- NBE Foreign Exchange Directives — applies to USD transactions
- AML/CFT requirements — KYC on merchant onboarding and periodic reviews
Chapa is one of the first private fintechs to obtain an NBE payment license, which was a significant regulatory milestone for Ethiopia’s fintech ecosystem.
Chapa vs. Direct Gateway Integration
Section titled “Chapa vs. Direct Gateway Integration”| Factor | Chapa | Direct Integration |
|---|---|---|
| Integration time | Hours | Weeks per gateway |
| Payment methods | 10+ | 1 per integration |
| Sandbox quality | Excellent | Poor (Telebirr/CBEBirr) |
| Fee | 1.5% + provider cut | Provider fee only |
| Settlement | Chapa’s cycle | Provider’s cycle |
| Refunds | Programmatic | Manual (for most providers) |
The tradeoff: Chapa adds a fee on top of the underlying provider fees. For high-volume merchants where every basis point matters, direct integration may be worth the engineering cost. For most merchants, Chapa’s convenience justifies the fee.
Common Integration Issues
Section titled “Common Integration Issues”Return URL gets trx_ref, not tx_ref
Section titled “Return URL gets trx_ref, not tx_ref”Chapa appends ?trx_ref=YOUR_REF to the return URL. Note the spelling difference — trx_ref vs tx_ref. The Zirzir SDK normalizes this, but if you’re integrating Chapa directly, watch for it.
Webhook payload changes
Section titled “Webhook payload changes”Chapa has changed their webhook payload format at least twice since launch. Version your webhook handlers defensively.
Test card behavior
Section titled “Test card behavior”Test cards in sandbox always succeed. To test failure scenarios, use the dedicated test failure card numbers from the Chapa docs. Not all failure scenarios are simulatable in sandbox.
Useful Links
Section titled “Useful Links”- Dashboard: dashboard.chapa.co
- Documentation: developer.chapa.co
- Status page: status.chapa.co
- Developer Telegram: Search “Chapa Developers” on Telegram
- Support email: [email protected]