Accepting TeleBirr and CBE Birr on a Website: A Practical Guide
A recurring question from clients — churches wanting a giving page, businesses wanting to sell online — is some version of "can't we just use Stripe?" The short answer is usually no, or at least not in a way that helps most Ethiopian customers. International payment gateways are built around cards and bank rails that a large share of the local audience simply doesn't use day to day. TeleBirr and CBE Birr transfers are, so any payment flow that ignores them is asking users to jump through hoops that don't need to exist.
Two different integration levels
There's a meaningful difference between "display our TeleBirr and CBE account details so people can send money and confirm manually" and "fully automated payment with instant confirmation." Most client projects we build start at the first level, because it's reliable, doesn't depend on API access that isn't always easy to get for a small organization, and is something users already understand — it's how they send money to family and pay small businesses already.
The design work that actually matters here isn't technical integration, it's clarity: showing account numbers and names in a way that's impossible to mistype, making clear which account maps to which purpose (general giving vs. a building fund, for example), and giving users an easy way to submit a reference or screenshot after they've sent a transfer, so an admin can reconcile it.
Building an admin-manageable "multiple bank accounts" giving page
For organizations with more than one purpose for receiving money, a static, hardcoded payment page becomes a maintenance problem fast — every new account or campaign means another code change. We typically build this as an admin-editable Firestore or database collection instead: an admin can add a new bank account, label it, and reorder how they appear, without needing a developer involved. This also makes trilingual support (English, Amharic, and in some cases Oromiffa) much easier to maintain, since the account labels and instructions live in the same manageable content system as everything else.
Where automated integration makes sense
For higher-volume commercial use cases — an e-commerce checkout, a subscription product — the manual-confirmation approach doesn't scale as well, and that's where a direct TeleBirr merchant integration is worth the extra setup effort: automated callbacks confirming payment, avoiding the back-and-forth of manual reconciliation, and giving customers instant confirmation instead of waiting on an admin to check a bank statement. We reserve this for projects where transaction volume actually justifies the added complexity.
The core principle
Design the payment experience around the rails people already trust and use, not around what's easiest to plug in from an international payments SDK. It's more work upfront, but it's the difference between a payment page people actually use and one that quietly gets abandoned at checkout.