
Co-Founder @LifePlanner_co. Engineering @spairally . Engineering Educator @reduzer_tech
Joined March 2021
- Tweets48.3K
- Following1.7K
- Followers8.2K
- Likes88.6K
Replying to @ndiku_
Same here lol ‘dw’ and ‘jk’ just to see ‘dw’ and ‘jk’ printed on the screen
Replying to @Iamjeffaustine
😂 they will have to steal it but I'm not giving half a decade of work out for free lol
SamProgramiz retweeted
Replying to @SamProgramiz
Do you devs hate intro and explainer video or getting a designer is the problem or you guys think it expensive to have one!
I create such videos for Playstore.
Replying to @AlgoCFC
Good start
Talk to @philipsfuture for mentorship and guidance in this line of work
Tap to stay organized thelifeplanner.co
Start your day organized with just a tap! Quickly add tasks, set due dates, and prioritize—Life Planner helps you stay on top of it all!
Download now: App Store: thelifeplanner.co/apple/x | Google Play Store: thelifeplanner.co/play/x
#Productivity #TaskManagement
SamProgramiz retweeted
Start your day organized with just a tap! Quickly add tasks, set due dates, and prioritize—Life Planner helps you stay on top of it all!
Download now: App Store: thelifeplanner.co/apple/x | Google Play Store: thelifeplanner.co/play/x
#Productivity #TaskManagement
SamProgramiz retweeted
When I get a 200 from the request, I create a pending transaction with the checkout request id.
I match incoming callbacks against it.
This also helps with manual queries if the callbacks fail to arrive.
We’ll still acknowledge receipt of the Webhook even if we failed to match it to any transaction.
You can take this further by adding auth tokens to the callback urls, whitelist IP addresses but, if you can guess the merchant request ID that is in a pending transaction, you deserve the spoils of the loot.
When you send the Express request, you get the two unique values.
MerchantRequesrID and CheckoutRequestID.
These are your first line of defence. Validate your webhooks against them. It should match at lease one record with this.
Daraja is well designed even though they don’t follow webhooks best practices like signing payloads. But you have to understand, a lot of what Mpesa Express is, is unique to what most of the industry does.
Also rate limit failures.
No need to guess, when the numbers can give you absolutes. thelifeplanner.co
SamProgramiz retweeted
Stop guessing where your money goes.
Meet Life Planner: the all-in-one hub for your tasks, habits, journaling, and finances.
Want to master your budget? Here’s a quick 1-step guide to getting your spending in check. 👇🧵
SamProgramiz retweeted
This year, I’m skipping the trip to Uganda for #DroidconUg, as much as I’m a speaker. It came a little too early, and I need time to rest after #StanChartMarathon 2026. Besides, I can’t afford the fare right now. It’s not yet the end month! 😂
So, I’ll do my session virtually.
SamProgramiz retweeted
Developers, this is for you. please take your payment callbacks seriously. 🔐
Yesterday, out of curiosity, I tested an M-Pesa integration on a critical live system. To my shock, I was able to submit a crafted payload that resulted in a payment being marked as successful.
Never trust a payment callback blindly.
Best practices:
- Verify callbacks against the payment provider.
- Validate the Merchant Request ID and transaction details.
- Verify payment status independently where possible.
- Restrict callback access by IP where supported.
- Make callbacks idempotent to prevent duplicate processing.
- Never mark a payment as successful based on an unverified payload.
One weak payment integration can undermine the integrity of an entire system.
Security is not just about protecting your APIs. It's about protecting the business logic behind them. 🔒
SamProgramiz retweeted
Men receive flowers on one day in their entire lives, and they're never there to smell them.
Thank you, G. It means a lot coming from you 🙏.
open.spotify.com/track/6bKnA…
I shot a friendship shot to the guy who hacked my startup in 2014, @its_eknock....🥲
Since then he's been teaching LO1 and I how to code; LO 1's year 11 project is a ticketing app for school attendance!
Mimi, I am creating the app I always wanted.
Iron sharpens iron🙏




























