I learn best by building real things.
So I'm teaching myself M-Pesa integration from scratch using NestJS and Typescript.
Day1: Daraja sandbox is live☑️
Going to document every step the wins , the bugs everything.
Let's see where it goes👀
#Mpesa#Safaricom#Fintech
The most dangerous gap isn't your code but it's compliance
You can spend months building the cleanest most reliable system in east Africa and safaricom can pull your API access overnight because of a clause buried in your merchant agreement that you never read.
Microservices should talk to each other only via queues. If a microservice failure leads to your system failure, you’re doing it wrong.
If you don’t have the skills to design such a system, make a monolith.
And if you can’t design a scalable monolith, read a fucking book.
Another day in the life of a fintech developer, where every figure has to add up.
Today was all about learning, debugging & making sure every transaction behaved exactly as expected. 🔥
Did the money go through? ✅ Yes.
Did the accounts reconcile? ✅ Yes.
In fintech, the code isn't done until the numbers agree.
Been off the grid for a bit. Back to building until further notice.. unless I die or worse my code does or until production takes me out first
#FinTech#Mpesa#BuildInPublic
Been off the grid for a bit. Back to building until further notice.. unless I die or worse my code does or until production takes me out first
#FinTech#Mpesa#BuildInPublic
Missing M-Pesa callbacks will teach you the Transaction Status API faster than any tutorial ever will😂
You'll be reading Daraja Tatu docs wondering why your callback URL went silent.
The fix? Always persist your CheckoutRequestID the moment you fire the STK Push before anything else. That's your lifeline when callbacks ghost you.
Then hit the Transaction Status API to query what actually happened.
Day 3 building Mpesa integration in public no filter
A learning journey
Database layer done but it wasn't easy
Challenges I hit
✔️Prisma 7 no longer supports url in schema.prisma
✔️It requires a driver adapter(Prisma pg)
✔️Permission denied for shadow db.
I
Day 3 building Mpesa integration in public no filter
A learning journey
Database layer done but it wasn't easy
Challenges I hit
✔️Prisma 7 no longer supports url in schema.prisma
✔️It requires a driver adapter(Prisma pg)
✔️Permission denied for shadow db.
I