Skip to main content
This issue may arise due to multiple reasons, such as:
  • High latency in response to the test payload.
  • Webhook endpoint didn’t return HTTP 200 OK.
To troubleshoot this issue, follow this step: Ensure your webhook endpoint returns a 200 OK response within 50 ms during configuration.
This issue may arise due to multiple reasons, such as:
  • Parsed payload is being used.
  • Timestamp provided in the ‘x-webhook-timestamp’ isn’t used for creating the signed payload.
To troubleshoot this issue, follow these steps:
  • Use the raw payload and x-webhook-timestamp to generate the signed payload.
  • Sign it using your client secret and HMAC SHA256.
  • Refer here for the sample code.
This issue may arise due to multiple reasons, such as:
  • Endpoint not returning 200 OK.
  • Required events not selected.
  • Endpoint expects a non-JSON format.
  • Payment is still in an intermediate state.
To troubleshoot this issue, follow these steps:
  • Ensure the endpoint returns 200 OK and can parse JSON.
  • Use the Get Payment Status API to check the payment status.
This issue arises because HTTP (instead of HTTPS) webhook endpoint configured in production.To troubleshoot this issue, follow this step:
  • Use only HTTPS URLs for webhook endpoints in the production environment.