Verification Object
Available only for mobile SDK version 3.x and above and web SDK 3.4.2 and above.
Source detection:
enabled: Always true
allowNonPhysicalDocuments: By default is set to false, can be overridden in the mobile SDK configuration. Always true for the web SDK
selectedResolution: Resolution used to perform source detection
optimalResolution: Indicates if the process was performed with optimal resolution. Regarding the mobile SDK, in the majority of the cases it should be true but in rare cases might be false, for instance for phones that don’t support an optimal resolution. Suboptimal resolution can affect the accuracy of the source detection process and therefore should trigger a warning and therefore manually evaluated
Id screen detection:
enabled: Always true
score: An assigned score ranging from 0 to 100 indicates the likelihood of a document scanned through a screen. A higher score suggests a higher probability to be a screen. It's important to be aware that the mobile SDK will reject scanning attempts if the score exceeds 50 unless allowNonPhysicalDocuments is set to true
Id print detection:
enabled: Always true
score: An assigned score ranging from 0 to 100 indicates the likelihood of a document scanned through a printed copy. A higher score suggests a higher probability to be a printed copy. The mobile SDK does not reject scans of printed documents. Please note that low-light conditions may affect the result, potentially increasing the score and leading to false positives. We are committed to improving this aspect in future releases, refining quality check procedures to ensure optimal image quality. Eventually, printed documents above a certain score will be rejected directly from the mobile SDK, similar to how screens are handled. Note: Starting with version 3.2.0 and above, the SDK will reject scans of ID documents presented on paper. It's important to be aware that the mobile SDK will reject scanning attempts if the score exceeds 50 unless allowNonPhysicalDocuments is set to true Dec 6, 2024: We have implemented an advanced machine learning system that identifies unique printing patterns with unprecedented accuracy. This enhancement comes as an addition to the existing print detection features to provide a more reliable detection of printed copies of ID documents, reflected in improved accuracy of the idPrintDetection score in your verification results. Mobile SDK v3.2.0 and above includes built-in features to reject paper-based document scans during the document scanning step. These features operate locally within the SDK for optimal user experience. The newly added enhancement is considered as an added security layer that operates server-side only and thus does not block the user during the document scanning process. Hence, even with allowNonPhysicalDocuments set to False, it is possible that you get a high isPrintDetection score in the verification result object for a successful onboarding.
Id photo tampering detection:
enabled: Always true
score: An assigned score ranging from 0 to 100 indicates the likelihood of tampering with the ID photo. A higher score suggests a higher probability of tampering. It's important to be aware that the mobile SDK will reject scanning attempts if the score exceeds 70. Scores surpassing 40 should trigger a warning and therefore manually evaluated
Data consistency check:
enabled: Always true
fields: List of fields found across all the steps of the KYC journey that are duplicates and therefore can be matched. Please be aware that the list may be empty if there are no fields available for matching.
Field object:
name: Common field name across all the sources
match: MATCH or MATCH_PARTIALLY or NO_MATCH
sources: List of sources that have been matched
Source object:
source: The source of the field. Possible values are SCAN, READING or LOOKUP
documentSide: The side of the document (FRONT or BACK) if source is SCAN
name: Original field name
value: Value of the field
MRZ checksum:
enabled: Enabled if the document contains a MRZ
finalCheckDigit: The check digit number used to validate the checksum of multiple values across the MRZ
valid: If the final checksum is valid or not
checkDigits: List of check digit validations per MRZ field
Check digit object:
fieldName: Field name
fieldValue: Field value
checkDigit: Check digit number
valid: If the checksum is valid or not
Reading:
enabled: If the reading step (NFC chip reading) was enabled or not. Only available in the mobile SDK
passiveAuthentication: Available only if passive authentication is supported by the document
enabled: true If passive authentication is supported by the document (e.g. passport), otherwise passiveAuthentication object is not returned as described above
countrySigningCertificateAvailable: true if the country signing certificate is available
documentSigningCertificateAvailable: true if the document signing certificate is available
documentSigningCertificateSignatureValid: implies that countrySigningCertificateAvailable is true. If countrySigningCertificateAvailable is false the attribute is not exported
documentDataSignatureValid: if digital signature validation of the data was successful or not. For passports could be false as we don't reject the reading because some passports could have a defect
activeAuthentication: Available only if active authentication was performed
enabled: true If active authentication is supported by the document, otherwise activeAuthentication object is not returned as described above
chipAuthentication: Available only if chip authentication was performed
enabled: true If chip authentication is supported by the document, otherwise chipAuthentication object is not returned as described above
Biometric:
enabled: If biometric was enabled or not
type: Can only be FACIAL_RECOGNITION
matchLevel: match level returned
Lookup:
enabled: If lookup was enabled or not
documentFound: If a matching document was found or not
It's important to always validate SDK results against your specific requirements. The SDK is designed to automatically detect and block screen presentations, printed document attacks, and ID portrait substitution attacks, unless these features are disabled. However, our server-side verification goes further by performing these same checks alongside additional specialized verifications, such as print detection models, which can catch issues that may be missed by the SDK. While the SDK acts as an initial security layer, server-side validation is essential. Currently, we replicate all SDK security checks on our servers, following the zero-trust principle toward the client, and are working on introducing more advanced security features that will be available exclusively server-side.
Last updated