Page Comparison

...

Some of the events triggered on Monnify are:

1. Card transaction completed or account transfer payment received .

2. Settlement is made to your wallet or account.

3. Disbursement (or transfer) completed.

4. An initiated refund is completed.

Click here to see all supported event types and the payload structure.

...

You can secure your webhook by using a combination of the approaches below

1. Transaction Hash Validation: This is applicable by default on our transaction notification webhook. A hash of some properties in the request payload is computed, and you can validate this on your server by computing the same hash and comparing outputs. For more information about this, please see Computing Request Validation Hash

2. IP Whitelisting: To prevent requests from un-authorized origins, you can whitelist our IP address and only honor requests from this IP. Webhook notifications from Monnify will come from the following IP addresses - 35.242.133.146

Responding to webhook request

...

Monnify ignores any other information in the response body or headers.

Best Practices

1. Check for duplicate notifications: It’s important to keep track of all notifications you’ve received. When a new notification is received, always check that this has not been processed before giving value so as not to give double value to customers. A resend of already processed notification can happen if we do not get a 200 HTTP Status code, or in the case of a request time out.

2. Process Complex Logic After Responding to Monnify: If your application will perform complex or time consuming logic with received notifications, this might lead to a time out between Monnify and your system, hence leading to a resend. For this reason, it’s recommended you immediately acknowledge receipt of the notification by returning a 200 HTTP Status code, and then perform your long processing activities.

...