Webhooks

As discussed in Webhooks Integration, webhook is a crucial items for your integration. Ezypay offers webhooks that send notifications for various scenarios, such as failed payments or retrieving debits by date.

You can create a webhook (API) that sends a callback request to a specified URL in response to events happening in Ezypay. The webhook will return a full response object containing all details of the related object. For instance, when a customer created event occurs, the webhook will return the details of the created customer object, including name, email, contact information, and address.

As the integrator, you need to subscribe to webhook events for each merchant as they are onboarded to Ezypay and your platform. Please ensure the webhook endpoint can return a HTTP response as Ezypay is utilizing it to identify success or failure. You can refer to the full list of webhook events available from Ezypay for more details.

Webhooks are merchant-specific, meaning each merchant can have their own subscribed webhooks. The URL used as the HTTP webhook listener can be the same for all merchants if you can identify which merchant should receive each event.

🚧

NOTE

• A new webhook is required for each new merchant onboarded.

• A public endpoint is required for Ezypay to send webhooks to.