The duplicate charge that taught me idempotency
A handful of customers were charged twice for the same gold purchase. The bug wasn’t in our payment code — it was in the assumption that only one thing would tell us the payment had succeeded.
I’m Mritunjay — an engineer who works best in the messy middle between product and shipping. Mostly payments and mobile, where correctness isn’t abstract: a rounding error is somebody’s real money. I take things end to end, from the schema to the on-call page, and I’d rather build 0 → 1 than polish something that already works.
If you’re building something interesting, happy to connect.





A handful of customers were charged twice for the same gold purchase. The bug wasn’t in our payment code — it was in the assumption that only one thing would tell us the payment had succeeded.
I put a retrieval-augmented recommendation layer into a storefront and conversions went up 40%. Almost none of that came from the language model — it came from the retrieval, which is the half nobody wants to talk about.
Our checkout wasn’t slow in any way a profiler would show you. It was slow in the way a user feels — too many taps, too many moments of not knowing what was happening. Here’s what actually moved the numbers.
I’m always up for talking about payments, mobile performance, or anything you’re building. The fastest way to reach me is email.
Email me

