All reports have an overall result, which is either a clear or a consider. When a user receives a clear, they can be considered verified. When they receive a consider, the report breakdown will indicate what caused the user to fail verification.
The different breakdowns indicate different reasons why someone might not have been verified:
- Image integrity: Asserts whether the quality and integrity of the uploaded files were sufficient to perform a face comparison.
-> Face detected: Asserts a single face of sufficient quality has been found in both the document image and the live photo. This will return a consider if no face is found on the front of the document, or no face is found on the selfie or video, or too many faces were found on either.
-> Source integrity: Asserts whether the selfie or video is trustworthy. This will return a consider when selfie or video is found to be digitally tampered, from a fake webcam, emulator, or from other dubious sources. It indicates deliberate attempts at defrauding the system. The dashboard and API response will provide more detail as to what exactly caused this to trigger. - Face comparison: Asserts whether the face in the document matches the face in the live photo.
-> Face Match: This will flag as consider when the person does not match the face on the identity document. A similarity score will also be returned. The closer to zero that score is, the less likely the two faces belong to the same person. - Visual authenticity: Asserts whether the person in the selfie is real.
-> Spoofing detection: This will return a consider when the selfie or video contains a face that is not real, also known as a spoof. For example, a face on a piece of paper, a face on an identity document, a face on a digital screen, a screenshot, etc. A spoofing score will also be returned. The closer to zero that score is, the less likely the face is real.
Comments
0 comments
Please sign in to leave a comment.