IDWise Webhook Types & Use Cases

🔔 Webhook Types & Triggers

Stay synchronized with key verification events by subscribing to the appropriate webhook types. Each webhook serves a specific purpose and is triggered based on a defined moment in the user verification or review process.

The table below summarizes the different webhook types provided by IDWise and when they are triggered:

Webhook Type	Description
Finished Journey	Triggered when the journey is finalized and all processing on the IDWise backend is complete. At this point, the journey is ready and can be retrieved from IDWise's backend using the corresponding API.
Manually Reviewed	This webhook is triggered when the client's compliance team has completed a manual review using the IDWise dashboard, during which they may confirm or override the system's decision.
Finished User Steps	This webhook is triggered when a user completes their ID verification journey, with all required elements (such as ID and Selfie) submitted to the IDWise backend. This webhook notifies the customer backend that the user steps have been completed, If any custom steps are necessary, the customer backend can initiate them at this point, such as submitting the face from the government database to compare it with the user’s selfie face.
Finished Step	This webhook is triggered whenever a user completes and submits a step during their journey.
AML Monitor Update	The webhook is triggered whenever there is an update to a monitored AML record. For instance, if a person has been added to a sanctions list or is no longer considered politically exposed, the webhook will be activated.
Finished Spot Check	Triggered when the ongoing spot check has been completed and the processing is finalised on the IDWise backend.
Updated Journey	This webhook is triggered only after a journey is completed, when there is a change in the system decision or a compliance-driven update part of the manual review. It keeps your system in sync with important post-verification decision changes.