Finished Journey Webhook
The Finished Journey Webhook notifies your backend when a verification journey has completed processing and a final decision has been reached. Use this webhook to trigger downstream actions in your system — such as approving a user account, flagging an application for manual review, or blocking a rejected applicant.
When It Triggers
IDWise sends this webhook when:
- A user completes all required steps in the journey and IDWise finishes processing the verification.
- A journey is reprocessed after a KYC Renewal resubmission.
- A manual review decision is made by a compliance reviewer.
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 Journey",
"body": {
"eventId":"4****-****-****-*********7",
"journeyId": "6720***********22e",
"referenceNo": "840...........23",
"systemDecision": "<SYSTEM_DECISION>"
}
}
NotePlease 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 journey webhook this will always beFinished Journey.
Inside the body element you find these elements:
eventId: A unique identifier to identify this event instance. Should the event be attempted again, theeventIdwill 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 Case | Description |
|---|---|
| User onboarding | Automatically activate a user account when systemDecision is Complete, or hold the account when the decision is Refer or Rejected. |
| Manual review queue | Route journeys with a Refer decision to your compliance team for manual review. |
| Rejection handling | Notify the user and block access when systemDecision is Rejected. |
| KYC renewal processing | After a user resubmits during KYC Renewal, use this webhook to update the user's verification status based on the new decision. |
| Audit logging | Record every finished journey event — including the eventId, journeyId, and decision — for compliance and audit trail purposes. |
Updated 7 days ago
