Two ways to pay, one payment: idempotency in Request to Pay
A request that reaches the customer as a push notification and a USSD prompt at the same time needs one rule above all the others: it can only be paid once.
Led delivery of Request to Pay: a merchant requests money from a customer, who can pay from a push notification or a USSD prompt, and can never pay twice.
Pick a step to replay it
Merchants needed to collect payments from customers on any phone, smartphone or not. Sending every request down two channels at once raised the obvious risk: a customer paying on both.
Stack.NET, Microservices, USSD, Push notifications and Idempotency
A request that reaches the customer as a push notification and a USSD prompt at the same time needs one rule above all the others: it can only be paid once.
An EMV QR code is a string of tag-length-value fields with a checksum at the end. Here's how the format works, static and dynamic, and how to build one in C#.
Built the scheduler behind bulk push campaigns: 700–800k notifications per run in 7–8 minutes, read in chunks and sent with controlled parallelism to Android (FCM) and Huawei devices.
Built with.NET, Schedulers, Semaphore and FCM
Read case studyOpen to full stack, product & backend roles.