A merchant was able to register their payment success, failed, and expired webhooks in Maya Manager. Upon testing, they were able to receive webhooks from Maya. However, when clicking the Test button in Maya Manager, the error “500 Internal Server Error” appears.
Why is there a disconnect between the actual merchant experience (was able to receive the webhook payload) and the test done in Maya Manager (500 Internal Server Error)?
The ‘500 Internal Server Error’ when clicking the Test button in Maya Manager is due to a known issue: the Webhook Test tool is currently under maintenance and does not reflect the actual status of your webhook endpoint. This is a UI limitation, not a problem with your integration. Since you are successfully receiving webhook payloads in real transactions, your endpoint is correctly configured. To validate your webhook, use cURL or Postman to send a sample payload to your endpoint — this is the recommended method per Maya’s documentation. Do not rely on the Test button in Maya Manager for verification.
For Sandbox concerns and other technical implementation inquiries, please get in touch with us via:
To Know More:
We value your input and would love to hear your insights. Please submit you feedback here.
Hi @jsjarabejo, the error “500 Internal Server Error” is a response from the merchant’s platform. The Test webhook from the Maya Manager only sends dummy values and tests connectivity.
The webhook endpoint should always return a 200 OK response before executing complex logic or validations.
References: