Insight
Designing a banking middleware for multi-subsidiary organizations
How to protect core banking systems while exposing governed APIs, partner integrations, and observable money flows across multiple entities.
← ← Back to home
Articles & Insights
Lessons and practical techniques from designing payment rails, distributed backends, and resilient platforms in Africa and beyond.
Architecture Decision
ADR: Why a double-entry ledger for payment systems
A short architecture decision record for choosing accounting correctness, auditability, and reconciliation over a simple mutable balance table.
Insight
Why most SaaS fail in Africa
Beyond the landing page: payments, distribution, and trust assumptions that don’t survive first contact with the market.
Code Example
Designing scalable fintech systems
Clear money boundaries, idempotent commands, and ledgers your finance team can reason about — not just a bigger Postgres cluster.
Architecture Decision
Architecture reviews that actually help
Fewer slides, clearer decisions: ADRs as a contract between teams — not a beauty contest for diagrams.
Design Rationale
Design tokens at system boundaries
Semantic tokens for the design system; product layers only where marketing and UX need to diverge — without breaking engineering or accessibility.
Code Example
Mobile money integration patterns for African fintech
Wave, Orange Money, Free Money: the API gaps, callback traps, and idempotency pitfalls that production systems expose — and how to architect around them.
Reference Doc
Product brief — one-page template
A single page to align problem, users, metrics, and explicit non-goals before anyone draws a diagram.
Want to unlock these results in your platform?
Describe your tech landscape and constraints — I’ll offer straightforward advice if there’s a technical match.
Get in touch