Verification workflow

Verifications move through a series of statuses from submission to being completed. The status of a verification is represented by the verificationStatus parameter.

Overview

Individuals

KYC individual workflow

Verifications for individuals can be in one of the following statuses:

StatusDescriptionPossible actions
verifiedThe ID verification was successful. It satisfies the bronID ID verification requirements.
rejectedNot enough matches could be found to satisfy the bronID ID verification requirements. The most common reasons for rejection are: missing/incorrect personal details, missing/incorrect ID document details, not enough verification sources.Submit missing/corrected data or add ID documents using the same userId parameter.
lockedThere were too many unsuccessful verification attempts. No further verification attempts will be processed for this entry.Submit a new verification.

Every verification status change will send a webhook to your registered endpoint.

Entities

KYC entity workflow

Verifications for entities can be in one of the following statuses:

StatusDescriptionPossible actions
pendingThe verification is processing. The verification will automatically transition to another status. In some cases, this status may be skipped, and the verification could go directly into info, verified, or rejected.
infoThe most common reasons for this status are: additional documents are required (e.g. a trust deed), or additional individuals need to be verified (e.g. a director or stakeholder).Submit a follow-up request.
verifiedThe ID verification was successful. It satisfies the bronID ID verification requirements.
rejectedThe entity could not be found in a relevant registry. The most common reasons for this status are submitting incorrect entity details.Submit a new verification.

Every verification status change will send a webhook to your registered endpoint.