We send verification_approved
and verification_rejected
notifications for each KYC level and add-on that you have requested initially and they can come in any order. Given the client requested light
KYC level with selfie
add-on, for example, we will send 2 notifications of the same type with different values (light
and selfie
) provided in a level
field. Available values are described in the KYC levels section.
The order of callbacks to webhook endpoints is not guaranteed. See Delivery section for details.
Once the user is approved, the partner can get notified about the user verification process being successfully completed. Upon getting verification_approved
notification, the partner can use specified user access token and retrieve the latest information about the user and/or perform its business logic.
Example payload:
{"type": "verification_approved","data": {"level": "v1","user_id": "14ec6af0-12f8-4bce-a6ab-01ce87fa1812","timestamp": "2020-04-02T13:35:35Z"}}
When the user fails verification for the selected level, the partner can get a webhook notification about the rejection. This can be caused by fake or expired documents, refusal to provide proof documents for certain validations, inability to pass liveness check, etc. Fractal does not disclose the exact reason for rejection via the webhook call. Upon getting verification_rejected
notification, the partner should mark the user internally as failed to pass the verification.
Example payload:
{"type": "verification_rejected","data": {"level": "v1","user_id": "14ec6af0-12f8-4bce-a6ab-01ce87fa1812","timestamp": "2020-04-02T13:35:35Z"}}