Webhooks allow us to notify you about important events or changes in your payments. Your webhook URL should be an endpoint on your server where you can receive these notifications. Whenever your payments are updated, we’ll send you a hook containing the transaction information, payment status, and customer information. Not all transactions require you to listen for webhooks, just asynchronous payments or actions that would not be completed in real time.Documentation Index
Fetch the complete documentation index at: https://epayclub.com/llms.txt
Use this file to discover all available pages before exploring further.
Setting up your Webhooks
Webhook Structure
When you receive a webhook, each event is a JSON object with:response.data: This object contains the actual transaction and order information.response.data.customer: This object returns customer-related information to confirm who completed the payment.response.data.orderPayments: This returns the order status and other important order-related information.
Webhook Example
Best Practices
- Acknowledge webhook receipt promptly to prevent timeouts, return a 200 HTTP status code immediately, and offload long-running tasks.
- Prevent duplicate actions and validate data consistency. Re-query the API to verify data, and track processed events.
- Set up a back polling job for cases of downtime with your webhook server.




