Additional Information About Verification Failure Reasons
In some cases, it may be important to know in detail why the verification was considered unsuccessful. This is especially important when verifying with a photo of an ID document. The photo may be blurry, in which case it is worth repeating the verification. The reason for the refusal may also be an invalid document, in which case repeating the verification is pointless.
Authologic executes this scenario, returning a failure cause list as a result. Example:
{
"id": "2161d11b-24ff-1430-8635-e3d4dc138fff",
"userKey": "ff97b4cc-81f4-413a-8bab-d0bd89da9a1f",
"url": "https://id.sandbox.authologic.com/c/2161d11b-24ff-1430-8635-e3d4dc138fff",
"status": "FINISHED",
"result": {
"identity": {
"status": "FAILED",
"errors": ["SCAN_DOCUMENT_NOT_DETECTED"],
"user": {}
}
}
}
In the given example, we could not find the document in the photo.
Authologic returns the following grounds for refusal:
SCAN_GENERIC_ERROR: Other errors associated with scanning documentsSCAN_DOCUMENT_NOT_DETECTED: Document not detected in the pictureSCAN_DOCUMENT_TYPE_MISMATCH: given a different type than the actual scanned documentSCAN_DOCUMENT_EXPIRED: The expiration date of the document passedSCAN_DOCUMENT_SIDE_MISMATCH: Document page not shownSCAN_DOCUMENT_NOT_SUPPORTED: This document type is not supported by the vendorSCAN_DOCUMENT_TOO_BLURRY: Document photo too blurrySCAN_DOCUMENT_COUNTRY_MISMATCH: The country selected by the user does not match the documentSCAN_DOCUMENT_DAMAGED: The document is corrupted in some waySCAN_DOCUMENT_NOT_FULLY_VISIBLE: Document not fully visibleSCAN_DOCUMENT_READ_FAILED_ID: Could not read document numberSCAN_DOCUMENT_READ_FAILED_NATIONAL_ID: Failed to read user IDSCAN_DOCUMENT_READ_FAILED_FIRSTNAME: Failed to read nameSCAN_DOCUMENT_READ_FAILED_LASTNAME: Could not read nameSCAN_DOCUMENT_READ_FAILED_FULLNAME: Could not read full nameSCAN_DOCUMENT_READ_FAILED_ADDRESS: Could not read addressSCAN_DOCUMENT_READ_FAILED_ISSUE_DATE: Failed to read document issue dateSCAN_DOCUMENT_READ_FAILED_EXPIRY_DATE: Failed to read document expiration dateSCAN_DOCUMENT_READ_FAILED_BIRTHDATE: Date of birth could not be readSCAN_DOCUMENT_DATA_INCONSISTENCY: The data in the document is inconsistent. For example, the dates in the document are not logically consistentSCAN_DOCUMENT_MRZ_NOT_DETECTED: The document MRZ data could not be foundSCAN_DOCUMENT_MRZ_READ_FAILED: Could not read document MRZ dataSCAN_DOCUMENT_PROBABLY_FAKE: The document may be fakeSCAN_DOCUMENT_LOW_QUALITY: The quality of the scanned document is too lowSCAN_DOCUMENT_WRONG_ADDRESS: The address does not match the one in the databaseSCAN_DOCUMENT_UNIQUE_DOCUMENT: The uniqueness of the document is not confirmedSCAN_DOCUMENT_DATA_MISMATCH: User data does not match the data in the documentsSCAN_FACE_TOO_MANY_PEOPLE: More people have been detected in the photoSCAN_FACE_TOO_BLURRY: Photo of the face is too blurrySCAN_FACE_NOT_DETECTED: No face detected on the photoSCAN_FACE_UNCERTAIN: The face cannot be confirmed to match the photoSCAN_FACE_MISMATCH: The face does not match the face in the photoSCAN_FACE_PROBABLY_FAKE: The face cannot be confirmed to match the photographABANDONED: User abandoned the verification processABANDONED_AFTER_PROCESSED: User abandoned the verification process after the data was processedFRAUD_SUSPICION: Suspected fraudINSUFFICIENT_AGE- User has insufficient age to perform operation requested by identity service providerINSUFFICIENT_PRIVILEGES- The user has insufficient privileges to perform operation requested by identity service provider e.g. user has an account with limited accessELECTRONIC_DOCUMENT_ACCESS_ERROR- Failed to read the electronic layer of the document or wrong PIN number providedBANK_NO_ACCOUNTS_SHARED- The user has not selected an account on the bank's side or the accounts have not been made availableNO_DATA_SHARED- User authentication or authorization process has not been completed based on a user action e.g. user rejected to share personal data, user cancelled process on identity provider sideNO_IDENTITY_FOUND- The end user does not have an identity that matches the assumptions made by the identity provider e.g. user not eligibleNO_USER_FOUND- The user account was not found by identity service provider e.g. the identity provider could not find the user account associated with the specified national identification numberPROVIDER_SERVER_ERROR- Provider has returned technical error (for example internal server error)PROVIDER_UNAVAILABLE- There is a problem with connecting to provider's system(s)SOURCE_UNAVAILABLE- There was a problem connecting the provider to the identity source system, e.g. between the provider and the banking systemPROVIDER_BLACKLIST- The user is blacklisted by the providerUSER_NOT_AUTHORIZED- The user could not be authorized due to providing wrong password, pin, code, etc.ENQUIRY_FORM_NOT_FILLED- The user didn't fill out the requested form fully.E_IDENTITY_ACCESS_ERROR- The user could not be authorized due to a problem with accessing the electronic id wallet.TOO_MANY_ATTEMPTS- The user attempted to go through the process too many times, resulting in the provider rejecting the verification.MANUAL_OPERATION_REQUIRED- Verification process requires manual verification.
The
FRAUD_SUSPICION and PROVIDER_BLACKLIST response codes are intended solely for internal use and diagnostics.
These indicators are provided to help in decision-making processes.They must not be exposed to end users or utilized in any user-facing messaging, Ensure these errors are handled
securely and remain within internal systems or logging mechanisms only.The reason list depends on the verification method. We are also constantly working on identifying further
reasons for refusal, so you should not assume in your code that this list is final.
Despite our sincere intentions, it is difficult to create perfect technical documentation.
If you have an idea on how to improve this documentation, or you have trouble understanding any section,
please email us at tech-support@authologic.com
Was this page helpful?