verification.completed
: Identity Verification either has completed its processing successfully or has been terminated as failed.onboarding.completed
: Onboarding either has been completed successfully or has been interrupted and set on an awaiting state.verification.completed
event is triggered when an Identity Verification has completed its processing successfully or has been terminated as failed. The value of the status property can either be VERIFIED
if the verification completes successfully or, FAILED
if any subprocess has been rejected.VERIFIED
, this is the status when an Identity Verification passed all its subprocesses successfully.FAILED
, this is the status when an Identity Verification failed to pass any of its subprocesses, eg. liveness detection process.onboarding.completed
event is triggered when an Onboarding has completed its processing successfully or has been interrupted and set on an awaiting state. The value of the status property can either be SUCCESSFUL
if the onboarding completes successfully or one of the uploading images has been rejected but Onboarding passed or, AWAITING
if any exception has been raised on Onboarding subprocess.SUCCESSFUL
, this is the status when an Onboarding passed successfully or any uploading images has been rejected but Onboarding itself is correct.AWAITING
, this is the status when an Onboarding failed to pass. Intead of setting it as a failed Onboarding, it awaits for its correction, so this subprocess can be retried as many times as long as it's on this status.ticket
string
event
string
status
string
created
number
processed
number
response_headers
and response_body
are present in the response you received via the webhook. The cipher initialization vector will be sent over as a 16 bytes metadata (header) of the response.