Razorpay Webhook Tester — Test & Inspect Razorpay Webhooks Online

If you are wiring up Razorpay webhooks, the first question is always the same: what does Razorpay actually send? The docs show an idealised payload, but the real request — its headers, its X-Razorpay-Signature header, the exact JSON shape — is what your handler has to parse. A Razorpay webhook tester gives you a public URL that captures those real requests so you can read every byte before you write any code.

Get a free Razorpay webhook tester URL

The fastest way is our free Webhook Bin — a no-code webhook tester that gives you an instant public URL and stores every request that hits it, headers and body included. No signup, no deploy:

1. Open the Webhook Bin and copy the URL it generates for you.
2. In Dashboard → Settings → Webhooks, add a webhook endpoint and paste that URL.
3. Trigger an event (see below) and watch the request land in the bin in real time.

Because the bin keeps the full request, you can inspect the X-Razorpay-Signature header, the Content-Type, and the complete payload — the three things you need to build and verify a handler.

What a Razorpay webhook looks like

Razorpay delivers webhooks as an HTTP POST with a application/json body. Razorpay names the event in the body's event field and signs the raw payload in X-Razorpay-Signature — capture a real payment.captured to see the nested payload.payment.entity your handler reads.

A typical payment.captured payload looks like this:

{
  "event": "payment.captured",
  "contains": [
    "payment"
  ],
  "payload": {
    "payment": {
      "entity": {
        "id": "pay_...",
        "amount": 50000,
        "currency": "INR",
        "status": "captured"
      }
    }
  }
}

Common Razorpay events you will want to test:

• payment.captured
• payment.failed
• order.paid
• subscription.charged

Verifying the Razorpay signature

Razorpay signs each request so you can prove it really came from Razorpay. The signature travels in the X-Razorpay-Signature header and is HMAC-SHA256 of the raw request body, using the webhook secret you set in the dashboard. Capture a real request first, then use our HMAC signature verifier and the verify a webhook signature guide to confirm your verification logic against a payload you can actually see.

From inspecting to receiving on localhost

A bin is perfect for seeing the payload. When you are ready to drive your local handler with real Razorpay events — without deploying — forward them straight to localhost with the Webhook Relay agent. The full walkthrough is here: Receive Razorpay webhooks on localhost.

That gives you a stable public URL that tunnels to your machine, so Razorpay keeps delivering to the same endpoint while you iterate on localhost, no firewall changes or public IP required.

Test Razorpay webhooks online in three steps

1. Capture — point Razorpay at a Webhook Bin URL and inspect the real request.
2. Verify — confirm the X-Razorpay-Signature header with the HMAC verifier.
3. Forward — when the shape is clear, receive Razorpay webhooks on localhost and build your handler.

New to webhooks in general? Start with what is a webhook and how to test webhooks.

Ready to inspect your first Razorpay event? Open a free Webhook Bin and paste the URL into Razorpay.