Bill Payments (BBPS) Webhook Events
List of Bill Payments (BBPS) webhook events along with sample payloads.
Razorpay's
APIs are asynchronous. By subscribing to Bill Payments webhook events, you get notified when a bill request or a bill payment reaches a terminal state (success or failed), instead of continuously polling the corresponding Fetch API.
The table below lists the webhook events available for Bill Payments.
Handy Tips
The payload for a webhook is a snapshot of the entity when the event occurred. The contains array names the entity present in the payload object (bill_request or bill_payment).
Given below are the sample payloads for Bill Payments webhook events.
Triggered when a bill request is successfully completed and the bill amount is retrieved from the biller.
Handy Tips
For validate-only billers, bills is returned as an empty array ([]).
Triggered when a bill request fails.
Watch Out!
expiry_at is not present on failed bill request events.
Triggered when a bill payment is successful.
Triggered when a bill payment fails.
Watch Out!
On failed bill payment events:
gateway_transaction_idis present only if NPCI assigned a transaction id before the failure. It may be absent.biller_transaction_idis never present.datais not present, as no biller response metadata is available when the payment fails.
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.
Was this page helpful?