Downtime Handling - Razorpay

Available in🇮🇳 India

Only methods that are up are shown to the customer. Methods that are down are hidden. Use the Payment Downtime webhooks and the Downtime API to react when a bank or method is unavailable.

Subscribe to payment.downtime.started, updated and resolved.
Check on page load with GET /v1/payments/downtimes, so a page opened mid-outage is right too.
Act on severity: hide the method or bank when severity is high; show a warning when it is medium or low.
Restore it on resolved.

Behaviour	Live mode	Test mode
Downtime webhooks	Real downtimes	Not confirmed whether Test Mode sends them
Downtimes API	Real downtimes	Not confirmed what it returns in Test Mode

Scenarios to test your integration

Scenario ID	Area	Scenario	Trigger	Steps to follow	Test mode
BP-17	Webhooks	Act on downtime webhooks	`payment.downtime.started`, `updated`, `resolved`	Hide the method or bank on high severity; warn on medium or low. Restore it on `resolved`.	Not confirmed in Test Mode
BP-36	Page load	Check downtimes on page load	`GET /v1/payments/downtimes`	Call the API when your payment page loads. Confirm a page opened mid-outage hides or warns correctly.	Not confirmed in Test Mode

Common integration gaps to avoid

Gap	What goes wrong in production	What to do	Test with
Checking only on webhooks	A page opened mid-outage still shows the broken method.	Also check on page load.	BP-36
Never restoring	A method stays hidden after it recovers.	Restore on `resolved`.	BP-17

Simulate failures

Nothing to simulate on this topic beyond the scenarios above. Not available in test mode

Failure	Why not	How to cover it
Bank, method or UPI app downtime	Not confirmed whether Test Mode supports it	Replay a stored downtime webhook to your endpoint

Handy TipsIntegrate the Payments Rainy Day kit to tackle payment exceptions such as late-authorised payments, downtimes and errors.

Last modified on November 12, 2026