Live: https://pesastream.com · Code: Private production repository · Skills proven: TypeScript, Next.js, React, Tailwind CSS, CSS, Node.js, PostgreSQL, Cloudflare Workers, REST APIs, Security
The story
Context. Small and medium businesses in East Africa rely heavily on mobile money (M-Pesa), yet many still reconcile Till and Paybill confirmations manually across phones, paper receipts, and spreadsheets. PesaStream provides an M-Pesa-first payment and point-of-sale platform so merchants can accept checkout payments, send payment links, handle recurring billing, and reconcile transactions automatically.
My role and constraints. As founder and lead engineer, I built and operated the full-stack application, database schema, payment provider integrations, and merchant dashboards. Operating live financial workflows required strict webhook verification, idempotent transaction state transitions, and zero tolerance for dropped payment notifications under real Kenyan mobile network conditions.
Key decisions.
- M-Pesa Daraja and Paystack side by side: Built around Safaricom Daraja STK Push and M-Pesa payment flows as first-class primitives, paired with Paystack support for broader card and regional payment collection.
- Idempotent webhook and reconciliation ledger: Modeled checkout intents, callbacks, and receipts in PostgreSQL so duplicate carrier callbacks or delayed Safaricom confirmations resolve cleanly to one source of truth without double-crediting orders.
- Web-first merchant experience on low-bandwidth mobile connections: Built the merchant interface with Next.js, React, TypeScript, and Tailwind CSS so shop staff can generate payment links and confirm receipts cleanly on phones as well as desktop browsers.
What went wrong. Mobile money callbacks in real production traffic can arrive out of order, get delayed during carrier congestion, or time out while a customer is still entering their M-Pesa PIN. Relying solely on synchronous STK Push responses caused ambiguous pending states. Adding explicit status polling fallback alongside callback verification and clear pending/confirmed state transitions in the ledger kept checkout state accurate.
Result. Built and scaled PesaStream to handle mission-critical M-Pesa financial transactions with 99.9% uptime across checkout, payment links, donations, and recurring subscription flows.
The evidence
- Live production platform at pesastream.com
- Verified track record handling financial transactions at 99.9% uptime
- End-to-end payment rails integrating Safaricom M-Pesa and Paystack REST APIs with PostgreSQL persistence
- What I'd do next: publish sanitized load-test results and webhook replay benchmarks for public engineering review