The usual causes
1) The webhook never reached you: a firewall, security plugin or CDN blocked Razorpay's POST, or the URL changed in a deploy. 2) It reached you but was rejected: the webhook secret in your app doesn't match the one in the Razorpay dashboard, so signature verification fails. 3) It was accepted but not processed: the handler crashed on an unexpected field, or looked up the wrong order.
Fix the immediate problem
Check the webhook delivery log in the Razorpay dashboard for failed attempts and their response codes. Confirm the secret matches, the endpoint answers 2xx quickly, and nothing in front of your app blocks POSTs. Then reconcile: fetch captured payments from Razorpay's API and update any orders still marked pending — and keep that reconciliation running on a schedule, because webhooks can always go missing.
Catch it before customers do
MockCard's limbo scenario simulates a captured payment whose webhook never arrives, so you can check your app doesn't fulfil without confirmation and does reconcile. Production probes check every hour that your webhook route is still reachable and wired correctly, and alert you on Slack or email the moment a deploy breaks it.