Why am I getting error from my webhook? – Xendit Guide

When you have set a URL to receive webhook, there will be a chance when you received an error instead of successfully receiving the webhook successfully.

Troubleshooting the error will be needed in order to ensure that you can receive Xendit's webhook and for a smoother transaction process

Common Errors

When Xendit receives error responses from your system, we display the response payload to help you to troubleshoot what went wrong. The response payload may contain useful information such as HTTP status code, HTTP error code, and response time to diagnose issue.

We try to find and map all functional and transient errors we can find across all customers alongside recommendation/action items in the following table below to help you to troubleshoot. All of these information are also available in Event Detail page by hovering over information icon right besides the error code displayed

HTTP Error	Description
4xx Client Error	Client error means there is an issue due to your system handles our webhook incorrectly. Please review your payload handler to proceed.
5xx Server Error	Server error means your server is unavailable when we send our webhook. Please enable automatic retry on your dashboard to help you to reconcile events: https://dashboard.xendit.co/settings/developers#callbacks Here is the document for your reference: https://docs.xendit.co/webhook/delivery-attempts-and-retries
ETIMEDOUT / ECONNABORTED	ETIMEDOUT or ECONNABORTED means your system did not properly respond our webhook after 30 seconds. Kindly check the record in your system before retrying to avoid duplicate delivery and implement idempotent handling if you haven't already.
ECONNRESET	ECONNRESET means your system forcibly closed your connection with Xendit, resulting in a loss of connection. Kindly check the record in your system before retrying to avoid duplicate delivery and implement idempotent handling if you haven't already.
CERT_HAS_EXPIRED	CERT_HAS_EXPIRED means we couldn't reach your server's URL due to an expired certificate. Kindly check and renew your SSL certificate to receive webhook normally again. You can use public SSL diagnose website like https://www.digicert.com/help/ to help you to troubleshoot this error.
EAI_AGAIN / ESOCKETTIMEDOUT	EAI_AGAIN or ESOCKETTIMEDOUT means we couldn't reach your server due to DNS lookup timeout, possibly due to an issue on your proxy settings or intermittent network issue. Kindly check your internet connection or your system performance and retry the until webhook delivery is completed.
ECONNREFUSED	ECONNREFUSED means no connection could be made because your system actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host. Kindly retry the webhook delivery until it is completed
UNABLE_TO_VERIFY_LEAF_SIGNATURE	UNABLE_TO_VERIFY_LEAF_SIGNATURE means your server's certificate chain is incomplete and we're unable to verify your SSL/TLS certificate. When replacing an SSL/TLS certificate, the intermediate certificates is typically part of the certificate installation process.
ENOTFOUND	ENOTFOUND we couldn't reach your webhook URL because DNS lookup failed. This is usually caused by the webhook URL appeared to be invalid. Kindly check your webhook URL for any typo to fix this.

Accept Payments

Common Errors