I am not able to identify why my webhook is failing, is there a way to find out what error Digio is receiving while hitting my webhook?
Yes. When an email notification is sent about webhook failure, it contains HTTP Error code, Error message received and The Entity id (eg. Document id or Mandate id) for which the webhook attempt is continuously failing.
Related Articles
Will I be notified when my webhooks are failing?
Yes, Digio makes periodic attempts on non 200 http responses. First email is sent to the registered account email, if the webhook is failing since the last 1 hour. If any failure is observed, subsequent attempts are made after 5 minutes, 10 minutes, ...
I am not able to find out the issue while reading received json? How can I debug ?
For UAT you may create a temporary public endpoint on websites like https://requestbin.com/, update your webhook endpoint on Digio Enterprise Dashboard (Profile section) and perform a transaction where webhook is triggered. These public endpoint show ...
For the period my webhooks were disabled, will I still be receiving the old webhook events or events created within this duration when my webhooks are enabled again?
Yes, webhook events are queued and processed separately when webhook endpoint is working.
How do we make sure that webhook events are coming only from Digio. IP Whitelisting ?
1 - You may allow webhooks only from below IPs: Sandbox : 35.154.20.28 Production : 13.126.198.236 2 - Provide a secret key and validate. Use X-Digio-Checksum header. On the client side, HmacSHA256 hex string of payload can be generated using the ...
My webhook endpoint keeps getting disabled due to various reasons, any best practices should I follow?
Do not execute business logic while receiving webhooks. Even if you execute, make sure a 200 response is returned always. For example an entity not found in your database (due to data archival), or state change of an object where this webhook is not ...