2026-05-17 — Smart routing, hosted checkout, version header
- New:
rail: "auto"on Charge create — Bila picks the rail by MSISDN prefix, then by merchant preference, then by global default order. - New:
payment_methodon Charge create reuses the stored MSISDN/token + preferred rail. - New: hosted checkout at
/checkout/[token]for redirect-based rails (Premier MC and other card rails). Charges includerequires_action_payload.redirect_towhen applicable. - New:
Bila-Versionrequest/response header. Pin by setting the header on requests; responses echo the effective version. - New: phase-2 rail stubs registered (Sahal, MyBank, Amal, Dahabshiil, M-Pesa SO, Telebirr) — all
disabledin the rails table until credentials land. - New: reconciliation report (admin) — daily diff of rail-side vs Bila-side totals.
- New: public transparency page at
/transparency— anonymised aggregate volume + uptime.
2026-05-16 — v1 public launch
- Initial release: Charges, Refunds, Customers, Payment Methods, Webhook Endpoints, Events, Balance.
- Rails: WaafiPay (live), eDahab (beta, stub), sandbox.
- Idempotency keys, request IDs, Postgres-backed rate limiter, signed outbound webhooks with 9-retry backoff.
- Dashboard (charges, refunds, balance, webhooks, developers, KYC), admin console (merchant queue, KYC reviewer, rails).
- Scalar interactive API reference at
/docs/api.
Versioning policy
Breaking changes ship under a new dated version. Your existing integrations keep working against the version they pin until you opt in. Additive changes (new endpoints, new optional fields, new event types, new rails) ship under all current versions.
Bila will announce breaking changes at least 90 days before the cutover and email all merchants whose API requests use the version being deprecated.