Money debited. Order failed.
The payment worked. The webhook did not.
What you'll learn
- Why a slow payment webhook loses orders after the money is taken
- Why a webhook should save the event and answer 200 before doing any work
- How a reconciliation timer finds payments whose webhook never arrived
Share this passage
Drawing…
Understand it one step at a time
The short runs these in order in about 56 seconds. Here they are written out — pick any step to jump the short straight to it.
The customer pays
Sunday lunch. ₹414 by UPI. The gateway captures the payment.
Free app · no app store
These are built for a phone
Every short is drawn at full portrait height, the shape a phone already is. Installed, it opens full-bleed with no address bar across the top — and the whole library reads offline.
Read deeper on Azure
Twenty seconds gets the shape of an idea across. These go into how it behaves in production.
-
Money Debited, Order Failed: Payment Webhooks and Reconciliation on Azure
Payment succeeded but the order was not created? Save the webhook first, process it from Service Bus, and reconcile with the gateway on a timer.
-
One Hotel, Three Suppliers, Three JSON Shapes: Hotel Aggregator System Design
How a hotel aggregator integrates Expedia, Booking.com, Agoda and Trip.com when each returns different JSON: adapters, one model, hotel mapping.
-
The Blast Radius of a Hardcoded API Key in a Mobile App
The attacker costs you hours. Rotating a key baked into 40,000 installed apps costs you days — and that gap is the real price of a hardcoded secret.
More shorts
-
Azure
One tap. Two orders.
10 steps · 57s
-
Azure
1.6 million downloads. One photo.
10 steps · 58s
-
Azure
Your public API has no login — and no identity
8 steps · 26s
Get new posts by email
New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.