Subscribe to various Webhook events related to RazorpayX to receive instant notifications.

Webhooks (Web Callback, HTTP Push API or Reverse API) are one of the ways in which one web application can send information to another application in real-time when a specific event happens. Know more about Webhooks.

Set Up and Edit RazorpayX Webhooks🔗

Set Up and Edit RazorpayX Webhooks

Validate and Test Webhooks🔗

Validate and Test Webhooks

Order of Events🔗

For example for payouts, you should receive webhooks in the following order:

  1. payout.pending (if you have Approval Workflow enabled on your account)
  2. payout.queued (in case your business account does not have sufficient balance to process the payout)
  3. payout.initiated
  4. payout.processed or payout.reversed

The above order may not be followed at all times. You should configure your webhook URL to not expect delivery of these events in this order and handle such scenarios.

The processed and reversed states are the last states for a payout. Their corresponding webhooks payout.processed or payout.reversed indicate this state change. Any webhook received after these should be ignored.

Webhook Events and Descriptions🔗


The table below lists the webhook events available for RazorpayX Payouts.

Webhook Event

Applicable For



all payouts

Triggered whenever a payout moves to the pending state. The payout remains in this state till you approve or reject it.


all payouts

Triggered whenever a payout moves to the rejected state. The payout was rejected by someone from your team.


all payouts

  • Triggered whenever a payout moves to the queued state. Payout goes to queued state when you do not have sufficient funds to process it or when the beneficiary bank/NPCI/partner bank is down. This event is applicable only for Virtual account.

  • You will receive the reason for the payout to be in the queued state as part of the status_details object.


all payouts

Triggered when the payout moves to the processing state when the payout is created or from the queued state when sufficient funds are available to process the payout.


all payouts

Triggered when a payout moves to the processed state. This happens when the payout is processed by the contact's bank.


all payouts

Triggered whenever there is a change in the payout entity. For example, when we receive the UTR for the payout from the bank. For NEFT transactions, this webhook is fired within 90 seconds. For IMPS and UPI transactions, this webhook is generally fired immediately.


all payouts

Triggered whenever a payout fails and the amount is returned to your business account.


all payouts

Triggered when a payout is failed because the beneficiary bank OR NPCI OR processing partner bank is down. If the beneficiary bank/partner banks/NPCI does not recover within the stipulated SLA, a FAILED event will be sent with the respective reason. Handy Tips
It is mandatory to subscribe to the payout.failed event if you are using RazorpayX APIs.

Check the sample payloads.


The table below lists the webhook events available for RazorpayX transactions.

Webhook Events



Triggered whenever you:

  • Make a Payout (virtual account or current account).
  • Add funds to your RazorpayX account (virtual account or current account).
  • Perform any kind of transaction (ATM transaction, cash withdrawal, netbanking transfer, encashed cheque) on your current account.
  • Check the sample payloads.