Validate and Test Webhooks
Validate and test Payments webhooks before you start using them. Read about idempotency and the importance of the order of Webhook Events.
You need to validate and test the webhook before starting using them. It is also important to understand idempotency and the importance of the order of Webhook Events.
You can test the webhooks to verify payloads or check if your webhook integration is working. Test events get triggered on a transaction done in the Test mode. As the payload structure remains the same in the Live and Test modes, you can rely on your stage testing.
You can test webhooks:
There are many free webhook testing tools available online. A simple Google search for test webhooks online returns multiple sites that you can use to test webhooks. For example,
.To test webhooks:
- Open .
- Click Create Request Bin and log in using Google or GitHub to create a private bin. Alternatively, you can opt for a public bin.
- Copy the endpoint created for you.
- Proceed to set up webhooks, but with the following changes:
- Ensure you are using Test mode on the Curlec Dashboard.
- Paste the endpoint you copied in the previous step in the Website URL field.
If you have enabled the appropriate webhook event during setup, you will receive the corresponding webhook payload on your requestbin.com site.
You cannot use localhost directly to receive webhook events as webhook delivery requires a public URL. You can handle this by creating a tunnel to your localhost using tools such as
or .You can refer to the
to get started. Use the URL endpoint generated by these tools in the webhook URL while setting up your webhooks.You can test your webhook integration in the staging environment before taking it live. You should set up webhooks in the Test mode. You can configure your staging host endpoint in test mode and receive test events on it.
Handy Tips
Enter the default OTP 754081 when prompted, while setting up, editing or deleting a webhook in test mode.
When your webhook secret is set, Curlec uses it to create a hash signature with each payload. This hash signature is passed with each request under the X-Razorpay-Signature header that you need to validate at your end. We provide support for validating the signature is in all of our
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.
X-Razorpay-Signature
The hash signature is calculated using HMAC with SHA256 algorithm; with your webhook secret set as the key and the webhook request body as the message.
You can also validate the webhook signature yourself using a
as shown below:Do Not Parse or Cast the Webhook Request Body
While generating the signature at your end, ensure that the webhook body passed as an argument is the raw webhook request body. Do not parse or cast the webhook request body.
There could be scenarios where your endpoint might receive the same webhook event multiple times. This is an expected behaviour based on the webhook design.
To handle duplicate webhook events:
- You can identify the duplicate webhooks using the
x-razorpay-event-idheader. The value for this header is unique per event. - Check the value of
x-razorpay-event-idin the webhook request header. - Verify if an event with the same header is processed at your end.
Ideally, you should receive a webhook in the order in which the webhook events occur. However, you may not always receive the webhooks in the order.
For example, in the case of a payment, you should receive webhooks in the following order:
payment.authorizedpayment.captured
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.
Was this page helpful?