Nobody builds “the next M-Pesa.” M-Pesa already won that race — you build what plugs into it, routes around it, or survives the day Safaricom changes its API terms.

I spent three years on the reconciliation team at a licensed Nairobi payment processor, the person who got paged when a batch of Daraja callbacks didn't match the ledger. That job taught me more about Kenyan fintech than any course could. I watched two well-funded startups miss their CBK compliance deadlines and get frozen out of the market for months. I watched a B2B payments startup lose a six-figure client because their settlement reporting couldn't reconcile to the shilling. And I watched a two-person team out-execute a funded competitor because they understood Pesalink interoperability better than anyone else in the room. When I finally left to build my own product, a bill-payment aggregator for SACCOs, I got provisional CBK sandbox approval in four months instead of the year most first-timers take, because I already knew which license category we actually needed and which compliance officer to call with which question. I also made my own expensive mistake along the way: I spent four months building a microservices payment core before I'd even confirmed which CBK category we needed, then redesigned half of it once the compliance requirements were finally clear. That mistake is why sequencing is the first thing I teach anyone who joins.

Here's the gap nobody tells founders about before they start: Kenya has some of the best payment rails on the continent, Daraja, Pesalink, agency banking networks, but almost none of that is documented well outside Safaricom's own developer portal. The CBK's licensing categories, Payment Service Provider, Money Remittance, Digital Credit Provider, each come with different capital requirements and different timelines, and most founders find this out the expensive way, after they've built the product and are trying to launch. Add to that the reality that M-Pesa has near-total mobile money market share in Kenya, so distribution isn't just a marketing problem, it's a habit-change problem, and most technical founders have no idea how to solve for it. Airtel Money and T-Kash exist, but building a product that assumes users will switch primary wallets is a losing bet, the ones that win plug into existing M-Pesa behavior instead of fighting it. This group exists because I was tired of watching smart people burn a year re-learning what a small circle of us already knew, one regulatory question or one API quirk at a time, when it could have been answered in a single conversation.

What we cover inside:

Regulatory-first architecture. We start every build conversation with the CBK category question, not the tech stack question. You'll learn to map your product idea to the right license category before you write production code, understand the sandbox application process, and build KYC/AML into your data model from day one instead of bolting it on before a compliance review.

Rails and integration depth. Daraja is the obvious starting point, STK Push, C2B, B2C, B2B, but most products eventually need more: Pesalink for real-time interbank transfers, direct bank API integrations for corporate clients, and reconciliation architecture that can survive a Safaricom API version change without your finance team finding out from an angry customer.

Float and liquidity management. Nobody explains float until it breaks. We cover how to model float requirements across paybills and agent networks, how to structure treasury so you're not caught short on a high-volume day, and how successful products here actually price float risk into their fee structure instead of guessing.

Distribution in an M-Pesa-dominated market. Building a better product doesn't matter if nobody switches. We break down how products that actually gained traction, embedded finance inside SACCOs, B2B rails that plug into existing accounting workflows, remittance products riding diaspora corridors, won distribution without trying to out-market Safaricom directly.

Inside the group: a resource library with CBK application templates, a shared glossary of terms from the National Payment System Regulations so you're not decoding legal language alone at midnight before a compliance call, and a running doc of which compliance consultants and KYC vendors, Smile Identity, Onfido, and a few local providers, actually respond to a first-time founder's email. Every Tuesday we run a live technical teardown of a real integration problem someone in the group is stuck on, Daraja callback failures, PCI scope questions, agent float reconciliation, with screens shared and logs on the table. Every Friday is founder office hours, unstructured, bring whatever's actually blocking you that week. Between sessions, the private channel is where most of the real problem-solving happens, someone posts an error code at 11pm and has three answers by morning, because everyone here has hit a version of the same wall before.

This is for people actually building: a working prototype, a sandbox integration in progress, or a live product with real transaction volume. It is not for people who want to talk about fintech as an idea, we don't run general future-of-payments discussions, and it's not for people looking for a co-founder or funding introductions, that's not what this room is for. If you're choosing between two CBK license categories right now, or debugging a Daraja callback at midnight, you're in the right place.

✅ Weekly Daraja/API integration teardown, using real logs
✅ CBK licensing and compliance roadmap template
✅ Direct feedback from founders who've already shipped live payment products
✅ Founder office hours every Friday, no agenda required

Members have gone from idea to CBK sandbox approval in under six months, cut integration timelines by weeks by avoiding mistakes the group already documented, and found their first enterprise or SACCO client through introductions made inside the group. Nobody here is promising you a licensed, funded fintech startup. What you get is the compressed version of three years of expensive lessons. If you're past the idea stage and into the sandbox, join the group.