Finished User Steps Webhook

The Finished User Steps Webhook notifies your backend as soon as a user finishes submitting all required steps in the journey (e.g., ID document and selfie) — before IDWise completes its full processing. Use this webhook to trigger backend tasks that depend on user submissions being complete but do not need to wait for the final verification decision.


When It Triggers

IDWise sends this webhook when:

  • The user has submitted all required steps in the journey (e.g., document capture, selfie capture).
  • IDWise may still be processing the submissions at this point — the systemDecision reflects the decision at the time of the webhook, not necessarily the final outcome.

This webhook fires before the Finished Journey Webhook. If you need the final verification decision, wait for the Finished Journey Webhook instead.

The webhook fires once per event. If delivery fails, IDWise retries with the same eventId so you can deduplicate on your end.


Webhook Payload

IDWise sends an HTTP POST request to your configured webhook URL with the following JSON payload:

{  
  "event": "Finished User Steps",  
  "body": {
    "eventId":"4****-****-****-*********7", 
    "journeyId": "6720***********22e",
    "referenceNo": "840...........23",  
    "systemDecision": "<SYSTEM_DECISION>" 
  }  
}
📘

Note

Please note this object might be extended with extra elements. Ensure your code can accommodate any extra elements introduced to this payload object.

The JSON object provided contains information about certain events in the ID verification process. Here is the explanation of its elements:

  • event: Identifies the type of event that triggered this webhook. For finished user steps webhook this will always be Finished User Steps.

Inside the body element you find these elements:

  • eventId: A unique identifier to identify this event instance. Should the event be attempted again, the eventId will consistently remain unchanged throughout all retry attempts.
  • journeyId: A unique identifier for the journey, a specific instance of the verification process.
  • referenceNo: The reference number associated with the journey.
  • systemDecision: The automated decision by the IDWise system based on the inputs received.

Use Cases

Use CaseDescription
Face match with external sourceTrigger a face comparison between the submitted selfie and an image from your own database or a third-party source as soon as the user finishes submitting.
Backend verification tasksKick off additional backend checks (e.g., address verification, credit checks) that can run in parallel with IDWise processing.
User experience updatesNotify the user that their submissions were received and that processing is underway, improving the perceived responsiveness of your onboarding flow.
Audit loggingRecord the exact moment the user completed all steps — including the eventId, journeyId, and reference number — for compliance and audit trail purposes.