An app built by a tech team entirely from Kenya just got featured on Forbes, big up to my team @NdemoVeronica@gefiune@KahenyaAnita@jomwashighadi who all have participated in to bring this live in different roles.
Auggie is a parenting app that connects parents to experts and helps them figure out parenting, we have created a network of over 200 experts in the US to help support parents at different stages
Read more π
https://t.co/bNwPMp9DU0
very weird thing happening rn
technical people are sad, they think their skills are now useless
non-technical people are desperately wishing they were more technical so they could use agents better
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. π
@_bighussla Both have a lot of factors to put into consideration, things like initial capital and resources e.g. for a Petrol station: do you own the land or it's a lease by your OMC. And for Petrol stations your profit margin is capped.