Skip to main content
Available in🇮🇳 India🇲🇾 Malaysia🇸🇬 Singapore🇺🇸 United States
You can accept customer payments using Razorpay products. By subscribing to payments webhook events you can get notified about payment state changes.

List of Payments Webhook Events

The table below lists the webhook events available for payments.
Handy Tips
  • The payload for a Webhook is a snapshot of the entity when the event occurred. For example, when a customer makes a payment, its status changes to authorized. It can then immediately move to the captured state.
  • The payment can be in the captured state when the payment.authorized Webhook is fired. However, the payload for the payment.authorized event contains details of the events when the payment was authorised, not when it was captured.
  • In case of network tokenised cards, the last 4 digits will be of the tokenised card and not the actual card.
  • The field flow is present only in the case of Turbo UPI Payments.

Comparison: payment.captured vs order.paid

Orders and payments go hand-in-hand. Once a payment is captured, the order is marked paid. This is reflected in the order.paid and payment.captured webhook events as well. These events are triggered when the payment associated with the order is captured.

Sample Payloads

Given below are the sample payloads for payments webhook events.

Payment Authorised

Payment Captured

Watch Out!You may occasionally observe a payment.failed webhook followed by a payment.captured webhook for the same transaction. While late authorisation is a known reason for this, user-initiated retries, particularly with UPI transactions, also cause this sequence.Here is a common scenario:A customer attempts a UPI payment via their Third-Party Application Provider (TPAP) such as PhonePe or Google Pay. The initial attempt fails, perhaps due to an incorrect PIN or insufficient balance.Most UPI TPAPs offer an immediate option to retry the payment directly within their app. When a customer retries, here is how our system responds:
  1. We trigger and send a payment.failed webhook to your configured endpoint, indicating the initial payment failure.
  2. If the customer retries the payment and successfully completes it (for example, by entering the correct PIN), the transaction concludes.
  3. Subsequently, we send a payment.captured webhook, confirming the successful capture of funds for that same transaction.
This sequence is expected behaviour. It allows customers to correct errors and complete their transactions without having to start a new payment process.

Payment Failed

Watch Out!
  • Do not hardcode the vpa parameter in the integration. If a UPI Intent payment fails, the vpa parameter may not get displayed at times.
  • The webhook sequence is not fixed in the JSON payload for payment events.
  • payment.failed is not triggered if the payment fails during authorisation (while making the first payment).

Payment Pending

The payment.pending event is triggered when an order is placed but the amount is not yet collected. On Standard Checkout, this happens when a customer places an order using Cash on Delivery (COD). Use method=cod to identify a COD order and treat it as your signal to begin fulfilment. A COD order does not generate a payment, so there is no payment.captured event and no settlement for it.
Watch Out!For a COD order, the amount field is the total amount payable on delivery, including the COD convenience fee you set in cod_fee. The cod_fee is not sent separately in the webhook.

Payments Downtime

Downtime is a period during which one or more payment options underperform, leading to considerable delays in payment processing. These downtimes are due to technical issues or outages at Razorpay’s partner or issuing banks side. Razorpay informs you about the downtime to communicate it to your customers.

List of Payments Downtime Webhook Events

The table below lists the webhook events available for payments downtime.

Payment Downtime Started

Payment Downtime Resolved

Payment Downtime Updated

Watch Out!
  • If you have changed your webhook secret, remember to use the old secret for webhook signature validation while retrying older requests. Using the new secret will lead to a signature mismatch.
  • While generating a signature at your end, ensure that the webhook body is passed as an argument in the raw webhook request body. Do not parse or cast the webhook request body.