Review states | IDmission Docs

These states apply when manual review is configured for IDentity. A review state is not a final decision. State codes alone do not uniquely identify every state across the final and review tables; retain the state name and context. See Final states for the result after review.

APPENDIX D – Manual Review Form Status and State Codes

If Manual Review is requested and the form moves into a ‘Review…’ formStatus, this is the list of values that the formStatus will show until manual review is completed. These are not the final form states, this is just a temporary formStatus that will be present until review is completed.

State Code	Form Status	Description	Recommended Actions
104	Review Barcode	If a barcode is expected to be present, and the barcode data is not detected by our system.	Manual review of the ID in the Back Office to verify the information on the front of the ID against what is shown on the back.
111	Review Duplicate Employee Found	If the submitted biometric data matches data already associated with an enrolled employee.	The submission will be manually reviewed in the back-office to determine if the matches found are true duplicates and will action the form accordingly.
134	Review DOB Match Failed	If the Date of Birth submitted in the request for the Customer or the Employee doesn’t meet the matching thresholds against the Date of Birth extracted from the ID Document.	Manual Review in the Back Office to compare the Date of Birth submitted in the request against the Date of Birth extracted from the ID.
95	Review Expired ID	If an ID has an expiration date that is expired as of today's date.	Manual review of the ID in the back-office to determine if the ID is truly expired or not.
136	Review Expiry Date Match Failed	If the Expiration Date submitted in the request for the Customer or the Employee doesn’t meet the matching thresholds against the Expiration Date extracted from the ID Document.	Manual Review in the Back Office to compare the Expiration Date submitted in the request against the Expiration Date extracted from the ID.
93	Review Face Not Detected	If a face is not detected on an image. The main reason for this is that the face was not present on the ID, however in some cases this could be due to poor image quality, or if there is a glare throughout the image.	Manual review of the ID in the Back Office to determine if a face is actually present on the ID.
102	Review Facial Biometric Match Not Verified	If a customer photo is captured and does not biometrically match the photo in the ID document, the ability to review the images is in the back office.	Manual review of the ID in the Back Office to determine if the Customer Photo is a match to the photo on the ID. If the person appears to be the same, it would be Approved, if not, it would be marked as ‘Facial Biometric Match Failed’.
90	Review Forced	This form state occurs when the Manual Review flag is set to F (Forced), which requires every form to be reviewed by the back-office team.	The ID will be manually reviewed in the back-office and decisioned into the appropriate form state.
94	Review ID Back Image not found	If the flags that determine a back image is not found are questionable, then the ability to review the ID back image is available in the back office.	Manual review of the ID back image in the Back Office to determine if its present and valid.
105	Review ID Front and Back Mismatch	If the back of an ID is expected to be present and if the data extracted from the front of the ID data does not match the data extracted from the barcode, then the ability to review the data is available in the Back Office.	Manual review of the ID in the Back Office because the data from the front does not match the data extracted from the barcode. The back office user will need to be able to see the ID Number field that was extracted from the front of the ID vs what was extracted from the barcode. They can manually compare this to the image to see if it's actually a mismatch or if it was an issue with OCR extraction.
103	Review ID Front Image Not Found	If the front of an ID is not uploaded or a blank image was provided.	Manual review of the ID front image in the Back Office to see if its present and valid.
108	Review ID Type Mismatch	If the ID Type submitted doesn’t match the ID Type extracted from the ID Image.	Manual Review of the ID in the Back Office to determine if the template match is correct based on the ID Type submitted.
126	Review IDNumber Match Failed	The ID Number that was extracted by OCR from the ID does not match the ID Number that was extracted from the MRZ or Barcode, OR the ID Number submitted in the request does not match the ID Number that was extracted through OCR.	Manual Review in the Back Office to compare the ID Number submitted in the request against the ID Number extracted from the ID.
63	Review Invalid ID Number	The ID Number on the ID does not match the pattern defined in the ID Template.	The ID will be manually reviewed in the back office to determine if the ID number matches the pattern defined in the ID template and was extracted incorrectly.
109	Review Key Component Not Visible	A key component that is expected on the ID is missing such as the Date of birth, expiration date, photo, etc.	Manual Review of the ID in the Back Office to determine if the components are present but just weren’t extracted.
116	Review Live Face Not Detected	If the live photo submitted fails the liveness checks based on IDmission's liveness detection logic.	Manual Review in the back-office. This occurs when an image fails the liveness check.
96	Review Low Resolution	If either the front or back image that is uploaded has been detected as low resolution or the ID image is not a color/gray scale image. This is based on resolution thresholds defined in our system.	Manual review of the ID in the Back Office to determine if the ID images have a clear enough resolution to be reviewed and validated.
106	Review MRZ and ID Data Mismatch	If the data extracted from the MRZ does not match the data extracted from the ID image itself.	Manual review of the ID in the Back office because the data from the front does not match the data extracted from the MRZ. The back-office user will need to be able to see the ID Number field that was extracted from the front of the ID vs what was extracted from the MRZ. They can manually compare this to the image to see if it's actually a mismatch or if it was an issue with OCR extraction.
91	Review MRZ Invalid	If the MRZ Validation flag (Machine Readable Zone) is questionable, and MRZ Data is expected to be present, then the ability to review the MRZ is available in the back office. An MRZ parsing tool is provided in the event the MRZ extracted might have a few characters transposed.	Manual Review of the ID in the Back Office. The MRZ String should be provided and an MRZ parsing tool should be present for the back-office user to utilize. In most cases, this is due to a glare on the MRZ so the data was extracted improperly. It can be manually fixed and tested to ensure the MRZ is truly valid.
107	Review Name Match Failed	If the name submitted for the Customer or the Employee doesn’t meet the matching thresholds against the name extracted from the ID Document.	Manual Review in the Back Office of the name submitted against the name extracted from the ID.
98	Review No Image Found	If the ID front and back images were not uploaded or a blank image was provided.	The ID front and back images will be manually reviewed in the back-office to see if they are present and valid.
97	Review Security Feature Invalid	If one or more security features defined for the ID template are detected as not matching with the image provided.	Manual Review in the Back Office. This occurs when the ID Template the image is matched against indicates the placement of the security feature is off or is not present.
112	Review Suspected Tampering	If photo editing software (e.g., Microsoft Paint, Adobe Photoshop) or other means of ID tampering were detected.	The ID will be manually reviewed in the back-office to investigate whether the ID has been tampered with.
113	Review Suspicious ID	If an ID is found to be suspicious based on IDmission’s AI logic.	Manual Review in the back-office. This occurs when an ID is found to be suspicious.
92	Review Template Not Found	If the image provided does not match any ID templates that are configured for a client, it can be reviewed by a back office team to determine if the image was just of poor quality and if it should be accepted OR if it should be rejected OR if the template needs to be setup and configured for that client.	Manual Review in the Back Office. This is generally due to poor image quality, so a manual check is required to see if it's truly a valid and accepted ID type for the region / customer.
101	Review Under the age of 18**	If the date of birth (extracted from the barcode/MRZ) calculates the individual as under the age of 18.	Manual review of the ID in the Back Office to determine if the date of birth extracted has resulted in a proper calculated age.
114	Review Verification Results	If the verification results through a third-party verification process are flagged to be reviewed. For example, the customer name matched against a watchlist.	The verification results will be manually reviewed in the back-office
117	Review Under the age of 21	If the date of birth (extracted from the barcode/MRZ) calculates the individual as under the age of 21.	Manual review of the ID in the Back Office to determine if the date of birth extracted has resulted in a proper calculated age.
128	Review VideoID Audio Match Failed	The user’s Audio captured in the videoID does not match the Audio data in the database from a previously enrolled user.	Manual review of the VideoID Audio in the Back Office to determine if the Customer Audio is a match to the VideoID Audio previously recorded. If the person appears to be the same, it would be Approved, if not, it would be marked as ‘VideoID Audio Match Failed'.
130	Review ID and VideoID Not Matched	The user's captured ID does not match the ID in the VideoID	Manual review of the VideoID ID in the Back Office to determine if the Customer ID is a match to the ID captured in the Video . If the person appears to be the same, it would be Approved, if not, it would be marked as ‘ID and VideoID Not Matched'.
132	Review VideoID Face Match Failed	The user's captured Selfie does not match the Face in the VideoID	Manual review of the Selfie and Face in the VideoID in the Back Office to determine if the Customer's Face is a match. If the person appears to be the same, it would be Approved, if not, it would be marked as ‘VideoID Face Match Failed’.