Downtime Alerts

Get notified for partner and beneficiary bank downtimes via email & SMS and webhooks respectively via RazorpayX.


When banks experience downtimes, payouts you initiate on the RazorpayX Dashboard may fail, that is, the payouts move to the failed or deemed_duccess state. Know more about

.

You can enable downtime alerts for partner banks (ICICI/Yes Bank/Axis) and for beneficiary banks (where the recipient receives the amount in their Fund account).

To receive alerts for partner bank downtime via email and SMS,

. We shall enable the feature for you in 2 days.

  • Downtime notifications are sent for RazorpayX Current, Escrow and Lite accounts.
  • We notify you of the partner bank downtimes in near real-time. This is usually within 15 minutes from when the downtime started.

When you make payouts, it is possible that the recipient's bank/beneficiary bank is experiencing downtime. In such cases, your payouts can fail. To make a successful payout, you must retry the payout after the bank restores normalcy.

You can get notified about the beneficiary bank downtimes via

events. To enable downtime webhooks:

  1. Follow the steps to

    .

    Enable Webhooks

    1. Log in to the .
    2. Go to the user profile icon → My Account & SettingsDeveloper Controls in the left menu.
    3. Click + ADD WEBHOOK if you are setting up webhooks for the first time. Otherwise, hover over the already added webhook and click EDIT WEBHOOK.
      RazorpayX Dashboard enable webhooks
  2. In the Active Events list on the RazorpayX Dashboard, select the following webhook events:

    • payout.downtime.started
    • payout.downtime.resolved
    RazorpayX Dashboard enable payout downtime webhooks
  3. Click SAVE.

You have successfully enabled the downtime webhooks for beneficiary banks. Whenever your beneficiary banks experience downtimes, we notify you at the webhook URL you selected during

.

There are two downtime webhooks. Refer to the respective webhooks for the sample payloads and format.

Webhook Response Parameters

id

The unique reference id created for each downtime alert. For example, poutdown_F1Zppa6lcVheSE.

method

Contains the list of

impacted. For example, IMPS, UPI and more.

begin

Timestamp in Unix when the beneficiary bank downtime started.

end

Timestamp in Unix when the beneficiary bank downtime ended.

For payout.downtime.started webhook, this parameter response is NULL.

status

The status of the downtime, whether it is ongoing or resolved. Possible values:

  • started
  • resolved

scheduled

Contains whether the downtime was a scheduled downtime. Possible values:

  • true (if the downtime was scheduled and informed)
  • false (if the downtime is unscheduled)

source

The source of the downtime. Possible value: beneficiary.

instrument.bank

Four-digit alpha code of the beneficiary bank. For example, SBI.

In case of downtimes, you can opt for Payouts Pro. You can either:


Was this page helpful?