Pan-African B2B cross-border payment rail (KES ↔ NGN)
Live dashboard → https://afropay-network-xi.vercel.app/
This repository is a portfolio case study.
It demonstrates product thinking, systems architecture, correctness guarantees, and end-to-end ownership.
The production source code, proprietary pricing & settlement logic, full ledger schema, and internal algorithms remain private.
Cross-border B2B payments across African markets remain expensive, slow, and fragile.
Typical correspondent-banking routes still dominate:
- High all-in costs (often 8–15%+ when FX spreads, fees, and intermediary banks are included)
- Multi-day settlement times
- Forced USD detour even for regional trade
- Poor visibility and weak auditability for the businesses that actually need the money to move
This creates real friction for SMEs, traders, and formal businesses trying to operate under the AfCFTA framework. Policy progress (AfCFTA, PAPSS, growing local-currency corridors) has opened a window — but the operational rails that make direct, reliable, local-currency settlement practical are still thin.
AfroPay Network was built to attack that gap on a concrete corridor first (Kenya ↔ Nigeria) while designing for expansion.
AfroPay Network is a working B2B payment infrastructure that provides:
- Direct local-currency corridor support (KES ↔ NGN)
- A production-grade double-entry ledger as the single source of truth
- Strong correctness guarantees (idempotency, zero-sum settlement integrity, auditability)
- Real-time operational visibility through an executive dashboard
- AfCFTA-aware tariff / Rules-of-Origin surface for trade context
- Throughput forecasting and liquidity/pricing observation layers
- Hash-verified audit trail
The live dashboard shows the system in operation: corridor state, settlement activity, audit stream, predictive throughput, and liquidity observations.
High-level shape only — implementation details of pricing, matching, settlement algorithms, and exact schema are intentionally omitted.
| Layer | Responsibility | Key Technologies |
|---|---|---|
| Ledger Core | Source of truth, double-entry accounting, invariants, transaction integrity | Go, PostgreSQL |
| Orchestration | Decision support, workflow coordination, external signals | Python + Gemini |
| Data Guarantees | Idempotency, serializable isolation, decimal-precision money handling, auditability | Postgres constraints + application-level controls |
| Observation & Forecasting | Throughput forecasting (SMA-based), liquidity/pricing matrix, audit log | Backend services + dashboard |
| Interface | Executive HUD, corridor map, settlement states, live audit stream | Next.js (Vercel) |
| Deployment | Backend + frontend separation | Railway + Vercel |
Core design principles
- Postgres is the system of record — not an afterthought cache
- Money is handled with explicit precision and strong invariants
- Every critical path is designed for auditability and replay safety
- The system is built so future contributors can be onboarded without tribal knowledge
I am the sole architect and builder of AfroPay Network.
Responsibilities covered end-to-end:
- Problem framing and product scope
- System architecture and technology selection
- Ledger design and correctness guarantees
- Orchestration layer and AI-assisted decision support
- Dashboard and operational visibility
- Deployment, observability, and ongoing iteration
I operate with a structured engineering process (decision records, clear boundaries between layers, evidence-based release criteria) so the work remains maintainable and transferable.
- Ability to take a real economic and operational problem and turn it into working infrastructure
- Production systems thinking under constraints that matter (money, correctness, latency, auditability)
- Comfort with both low-level guarantees (ledger integrity) and higher-level product surfaces
- Practical use of modern AI tooling inside a real system (orchestration layer) without treating it as magic
- Leadership-ready habits: clear architecture boundaries, documented decisions, and a system that others can eventually contribute to
- Ledger & Core Services: Go, PostgreSQL
- Orchestration: Python, Gemini
- Frontend / Dashboard: Next.js, TypeScript, Tailwind
- Infrastructure: Railway (backend), Vercel (frontend)
- This is a portfolio artifact, not a deployable production mirror.
- No production secrets, API keys, or live customer data are included.
- Proprietary logic (rate construction, settlement matching, full schema, internal algorithms) is deliberately excluded.
- The live dashboard is the primary proof that a functional system exists.
Daniel Muhoro
Portfolio → https://dmuhoro-portfolio.vercel.app/
GitHub → github.com/dmuhoro
Open to technical conversations, remote roles, and opportunities where end-to-end ownership and strong systems thinking matter.