Verification workflow

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

parameter.

Overview

Individuals

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

Status	Description	Possible actions
verified	The ID verification was successful. It satisfies the bronID ID verification requirements.	–
rejected	Not 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.
locked	There 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

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

Status	Description	Possible actions
pending	The 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 .	–
info	The 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.
verified	The ID verification was successful. It satisfies the bronID ID verification requirements.	–
rejected	The 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.

Important

When creating your KYB identity verification flow, ensure it is asynchronous, as processing times can range from 10 seconds to 24 hours, with a median processing time of under 15 minutes. Design the flow so that, after form submission, the user does not wait on the form for the next step. Instead, notify them through a preferred method for your application (e.g., email or in-app notification) when the next step is needed, based on the webhook response.

For example, after submitting the entity MY COMPANY, notify the user that the entity is being processed and that you’ll follow up once it’s complete. Suppose bronID sends an "Info" webhook response requesting verification for John ok Citizen and an upload of the Shareholder Register. Once you receive the webhook, you can notify the user that additional actions are required and display the actions along with options for them to complete them.

Another example: You submitted MY COMPANY with John ok Citizen as a director. bronID then returns a “Verified” status in the webhook. You can now notify the user that their identity has been verified and guide them to the next step.

Please note that there may be a delay between initial submission and the response. While the median processing time is under 15 minutes, certain cases—such as registry maintenance or high processing loads—can extend the time to 24-48 hours.