Webhook Responses and Types for Entities and Individuals
Verification typically takes ~2 minutes on average to process. When an entity has finished processing, the retrieve entity status endpoint can be used to retrieve extracted registry data along with the verification result.
If the process has not yet completed, the call with return one of the intermediary Status as per the below list.
If subscribed to the webhook, the webhook will only be sent once the verification process has finished processing.
Applicant Status Types
Created The entity has been created.
Pre-Checked The entity's documents are being processed.
Pending The entity's data is being processed.
Reviewed The verification is complete, and results are ready.
Review Answer Types
Approved The entity has successfully been verified.
Rejected The entity wasn't able to be verified. Look at rejectLabels to see why.
During the verification process, the entity is checked for potential fraud, forgery, and many other factors to ensure you're dealing with legitimate entities. When an entity is rejected, the following rejectLabel table sets out why the entity were rejected.
Entities
Reject Label | Reject Type | Description |
|---|---|---|
COMPANY_NOT_DEFINED_STRUCTURE | Retry | Entity's control structure could not be established |
COMPANY_NOT_DEFINED_BENEFICIARIES | Retry | Entity's beneficiaries could not be identified or verified |
COMPANY_NOT_VALIDATED_BENEFICIARIES | Retry | Entity's beneficiaries could not be validated |
COMPANY_NOT_DEFINED_REPRESENTATIVES | Retry | Entity's representatives could not be defined |
COMPANY_NOT_VALIDATED_REPRESENTATIVES | Retry | Entity's representatives could not be validated |
DE-REGISTERED | Final | In respect to the Australian Business Register, the entity's ABN has been cancelled/or is no longer active |
DB_DATA_NOT_FOUND | Final | The entity can't be found within the registry, and may not exist |
INCORRECT_DATA, MISMATCH_WITH_REGISTRY | Final | The provided entity details don't match what's contained within the registry (after fuzzy matching). It's likely the entity name or registration number has been entered incorrectly |
INACTIVE_COMPANY | Final | The entity is listed as inactive, de-registered, or closed within the registry and is/should no longer be trading |
PROBLEMATIC_OWNERSHIP | Final | The verified UBOs associated with the entity have been rejected when linking applicants to an entity |
INCORRECT_OWNERSHIP_VERIFIED | Final | The verified UBOs details do not match the ownership provided by the registry (eg. after fuzzy matching, the wrong individual has been verified) when linking applicants to an entity |
SPAM | Final | The applicant has tried verifying themselves multiple times, with multiple companies |
BLACKLIST, BLOCKLIST | Final | The applicant has appeared on known blocklist databases for fraud, identity misuse or other illegitimate purposes |
CRIMINAL | Final | The applicant has a criminal record |
COMPROMISED_PERSONS | Final | The applicant appears on known databases of compromised persons |
PEP | Final | The applicant is a politically exposed person |
ADVERSE_MEDIA | Final | The applicant appears within negative news or media articles, from reputable sources |
FRAUDULENT_PATTERNS | Final | The applicant has displayed signs of fraudulent behaviour while uploading their documents |
SANCTIONS | Final | The applicant has sanctions against them |
Individuals
Verification typically takes ~2 minutes on average to process. When an individual applicant has finished processing, the retrieve individual status endpoint can be used to retrieve extracted data from their documents along with the verification result.
If the process has not yet completed, the call with return one of the intermediary status as per the below list.
If subscribed to the webhook, the webhook will only be sent once the verification process has finished processing.
Applicant Status Types
Created The individual applicant has been created.
Pre-Checked The individual applicant's document images are being processed.
Pending The individual applicant's identity data is being processed.
Reviewed The individual verification is complete, and results are ready.
Applicant Action Status Types
Pending The verification is being processed.
Reviewed The verification is complete, and results are ready.
Applicant Status and ActionStatus update at the same time. It's recommended to use Status as it contains more information.
Review Answer Types
Approved The applicant has successfully been verified.
Rejected The applicant wasn't able to be verified. Look at rejectLabels to see why.
There are two types of rejections: Rejected (Retry) and Rejected (Final)
Rejected (Retry) allows an applicant to attempt their verification again, if they've uploaded a blurry photo for example.
Rejected (Final) is final, and does not allow another attempt. This is used when an applicant has attempted to forge their documents, or if they appear on a sanction or watchlist.
The table below sets out the list of Reject Label's, their Reject Type and description
Reject Label | Reject Type | Description |
|---|---|---|
LOW_QUALITY | Retry | The document images are of low quality, or they're unreadable |
NOT_DOC | Retry | The documents uploaded/provided aren't required for your chosen flow |
ID_INVALID | Retry | The document is no longer valid, or has been cancelled |
INCOMPLETE_DOC | Retry | The document has information missing, or only parts are visible |
UNSATISFACTORY_PHOTOS | Retry | The document image is blurry or has masked information |
DOC_PAGE_MISSING | Retry | The document has pages missing, eg. The front side was uploaded, but not the back side |
DOC_DAMAGED | Retry | The document appears damaged or broken |
PROB_APPLICANT_DATA | Retry | The document and extracted data don't match the applicant |
GRAPHIC_EDITOR | Retry | The document has been graphically edited, in an application like Photoshop |
DOC_DEPRIVED | Retry | The applicant has been deprived of the document, or can no longer legally use it |
FRONT_SIDE_MISSING | Retry | The document's front side was not uploaded |
BACK_SIDE_MISSING | Retry | The document's back side was not uploaded |
SCREENSHOTS | Retry | The applicant has uploaded screenshots of their document |
BLACK_AND_WHITE | Retry | The applicant has uploaded black and white images of their document |
EXPIRATION_DATE | Retry | The applicant has displayed signs of fraudulent behaviour while uploading their documents |
UNFILLED_DOC | Retry | The document doesn't appear to have signatures or stamps |
BAD_SELFIE | Retry | The applicant's selfie is unclear or blurry |
BAD_PROOF_OF_ID | Retry | The document is not required for your chosen flow, or is not supported |
BAD_PROOF_OF_ADDRESS | Retry | The document is not required for your chosen flow, or is not supported |
FORGERY | Final | A forgery attempt has been made to the document, or it is fake |
DOC_TEMPLATE | Final | The document is a template, downloaded from the internet |
SPAM | Final | The applicant has tried verifying themselves multiple times, with multiple companies |
SELFIE_MISMATCH | Final | The applicant's selfie does not match the document's photo |
BLACKLIST, BLOCKLIST | Final | The applicant has appeared on known blocklist databases for fraud, identity misuse or other illegitimate purposes |
INCONSISTENT_PROFILE | Final | A document of another person was uploaded to the applicant |
AGE_REQ_MISMATCH | Final | The applicant is below the minimum 16 years of age to verify |
CRIMINAL | Final | The applicant has a criminal record |
COMPROMISED_PERSONS | Final | The applicant appears on known databases of compromised persons |
PEP | Final | The applicant is a politically exposed person |
ADVERSE_MEDIA | Final | The applicant appears within negative news or media articles, from reputable sources |
FRAUDULENT_PATTERNS | Final | The applicant has displayed signs of fraudulent behaviour while uploading their documents |
SANCTIONS | Final | The applicant has sanctions against them |
FRAUDULENT_LIVENESS | Final | The applicant has tried to bypass or spoof the adaptive liveness/selfie check |