Suspicion types
If the verification includes one or more:
- Fraud tags
- Mismatch tags
- Suspicion reasons
The overall status in webhooks will be "SUSPECTED"
Information of suspicions in Callbacks
All of the mentioned tags and reasons for suspicion can be found in the webhook "status" object presented as lists (fraudTags, mismatchTags).
They indicate some kind of client suspicion or fraudulent behavior but they do not have any influence on the identity verification itself. If any of these suspicions are added, the verification will be suspected but the document and face could be approved in the same time.
In other words, the face and document may be valid but additional verifications can detect some discrepancies. Please refer to mismatchTags and fraudTags for concrete reasons for suspicion.
After receiving a webhook, you can check if the overall status is SUSPECTED and proceed to inspect if the "manualDocument"
is with a value "DOC_VALIDATED"
, and "manualFace"
is with a value "FACE_MATCH"
(meaning that the verification has been approved by our manual review staff). fraudTags, mismatchTags fields will help you decide whether to onboard the user on your system or not.
Callback status example with suspected status
{
...
"status": {
"overall": "SUSPECTED",
"mismatchTags": ["UNDER_AGE", "NAME"],
"fraudTags": ["FACE_IN_BLACKLIST", "AML_SUSPECTION"],
"autoDocument": "DOC_VALIDATED",
"autoFace": "FACE_MATCH",
"manualDocument": "DOC_VALIDATED",
"manualFace": "FACE_MATCH",
"additionalSteps": null
...
}
Telemetry
In dashboard suspected verifications are marked as APPROVED (SUSPECTED) or DENIED (SUSPECTED):
Suspicion values
During the implementation, please keep in mind that new fraud and mismatch tags may appear at any point in the future.
Suspicion reasons
Value | Explanation |
---|---|
FACE_SUSPECTED | Automatic algorithms triggered a suspicion that selfie face is not genuine. |
FACE_BLACKLISTED | A selfie is blacklisted. |
DOC_FACE_BLACKLISTED | A photo of a document is blacklisted. |
DATA_BLACKLISTED | A data of verification is blacklisted. |
DOC_MOBILE_PHOTO | A photo of a document is shown from a mobile screen. |
DEV_TOOLS_OPENED | A client performing verification has opened dev-tools in the browser. |
DOC_PRINT_SPOOFED | Automatic algorithms triggered a suspicion that document is printed on paper. |
FAKE_PHOTO | General identifier for a fake photo. |
AML_SUSPECTION | If AML functionality is turned on for you - this reason specifies that a client is in PEPs or Sanctions list. |
AML_FAILED | If AML functionality is turned on for you - this reason specifies that the check has failed. |
LID_SUSPECTION | If LID functionality is turned on for you - this reason specifies that client's document is found in lost or stolen documents database. |
LID_FAILED | If LID functionality is turned on for you - this reason specifies that the check has failed. |
RC_FAILED | The check conducted by the Registry Center has failed. |
AUTO_UNVERIFIABLE | Automatic verification is not possible. |
Fraud tags
Fraud tags also can have any value from suspection reasons
Value | Explanation |
---|---|
FACE_IN_BLACKLIST | This particular verification face photo was added to face blacklist. |
DOC_FACE_IN_BLACKLIST | This particular verification document face photo was added to document blacklist. |
DATA_IN_BLACKLIST | This particular verification data was added to data blacklist. |
FACE_BLACKLISTED | This verification was triggered due to match in face blacklist. |
DOC_FACE_BLACKLISTED | This verification was triggered due to match in document face blacklist. |
DATA_BLACKLISTED | This verification was triggered due to match in data blacklist. |
DUPLICATE_FACE | A face matched with earlier done verification selfie. |
DUPLICATE_DOC_FACE | A document face matched with earlier done verification document face. |
VIRTUAL_CAMERA | Likely virtual camera was detected. |
ADDRESS_UNVERIFIED | More information in vocabulary under ADDRESS_UNVERIFIED |
Mismatch tags
Value | Explanation |
---|---|
NAME | The user's name provided by the partner does not match the name extracted from the document. |
SURNAME | The user's surname provided by the partner does not match the surname extracted from the document. |
DOCUMENT_NUMBER | The document number provided by the partner does not match the document number extracted from the document. |
PERSONAL_CODE | The personal code provided by the partner does not match the personal code extracted from the document. |
EXPIRY_DATE | The expiry date provided by the partner does not match the expiry date extracted from the document. |
DATE_OF_BIRTH | The date of birth provided by the partner does not match the date of birth extracted from the document. |
DATE_OF_ISSUE | The date of issue provided by the partner does not match the date of issue extracted from the document. |
NATIONALITY | The user's nationality provided by the partner does not match the nationality extracted from the document. |
SEX | The gender provided by the partner does not match the gender extracted from the document. |
FULL_NAME | The full name provided by the partner does not match the full name extracted from the document. |
DOC_INFO_MISMATCH | Some of the provided data by the partner does not match the extracted data from the document, and the "Detect info mismatch" setting is turned off. If the "Detect info mismatch" setting is activated, and discrepancies are detected, a specific mismatch tag (e.g., NAME , SURNAME , etc.) will be applied, otherswise verification is placed as SUSPECTED in our dashboard - with the webhooks expect to receive "overall":"DENIED" with: - "autoDocument":"DOC_INFO_MISMATCH" , - "manualDocument":"DOC_INFO_MISMATCH" . |
UNDER_AGE | The age derived from the document is below the partner's minimum age requirement. |
UNKNOWN_AGE | The document does not contain age information, but the partner has set a minimum age requirement. |
INVALID_ADDITIONAL_STEP | The document provided for the additional step (e.g. Proof of address, Utility bill) is found to be invalid. |
ADDITIONAL_STEP_NOT_FOUND | The document required for the additional step (e.g. Utility bill, Proof of address) could not be located. |
ADDITIONAL_STEP_INFORMATION_MISMATCH | The information from the additional step (e.g., Proof of Address or Utility Bill) does not match the information provided by the partner. |
EXPIRED_ADDITIONAL_STEP_INFORMATION | The document provided for the additional step (e.g., Proof of address, Utility Bill) is expired. |
REGISTRY_CENTER_INFO_MISMATCH | The information obtained from the Registry Center database does not match the information extracted from the document. |