How to Monitor Razorpay Webhook Callbacks

Razorpay checkouts rely heavily on asynchronous event notifications (webhooks) to update subscription state, capture billing cycles, and deliver services. If your server fails to process a webhook payload, the transaction fails silently—the user gets charged, but their plan is never activated.

Pingzo allows you to set up continuous, automated HTTP POST monitoring targeting your Razorpay webhook listener to detect drops, script latency, or database locks before they impact your customer volume.

Setting Up Razorpay Webhook Monitoring

Monitoring your webhook listener endpoint requires dispatching a simulated payment payload to check your server's response code:

1. Open Monitors Dashboard: Log in to your Pingzo Dashboard and click Add Monitor.
2. Set Request Method: Select POST from the dropdown menu.
3. Enter Webhook URL: Input the absolute path of your webhook listener (e.g., https://api.yourdomain.com/webhooks/razorpay).
4. Draft request payload: In the Request Body text field, paste a standard Razorpay payment captured callback payload:

{
  "entity": "event",
  "account_id": "acc_razorpay_001",
  "event": "payment.captured",
  "contains": ["payment"],
  "payload": {
    "payment": {
      "entity": {
        "id": "pay_TEST_9988776655",
        "amount": 290000,
        "currency": "INR",
        "status": "captured",
        "order_id": "order_TEST_11223344",
        "method": "upi",
        "email": "test@yourdomain.com",
        "contact": "+919876543210"
      }
    }
  }
}

5. Configure Response Success Status: Under the Response Options, add your expected status code. If your webhook listener validates the signature, it will reject this unsigned ping with a 400 Bad Request or 401 Unauthorized instead of 200 OK.
   • Set Pingzo to accept 400 or 401 as a Success code.
   • If your endpoint throws a 500 Internal Server Error or times out, Pingzo will mark the check as a failure.
6. Select Check Interval: Choose a checking frequency of 1 minute to detect problems instantly.

Routing Webhook Failures to WhatsApp

Because webhooks fail silently, you need critical alerts delivered where you are guaranteed to see them immediately.

Once your Razorpay webhook check returns an unexpected code (like a 500 Server Error or a network timeout), Pingzo routes an official WhatsApp alert directly to your on-call team containing:

• Outage Target: Razorpay Webhook listener
• Error Details: (e.g., 500 Internal Server Error, Response Time: 6500ms)
• Debug Links: A direct link to check latency charts and response payload logs.