Source Validation

Success

Exit Code	Outcome	External Metadata	Customer Support Instructions
SV201	`pass`	Passport authenticity was validated using embedded security features and issuing records. Source Type: Authoritative Source Validation	Success
SV202	`pass`	The user’s phone number was corroborated using the information on the submitted government ID. Source Type: Phone Number Validation	Success
SV203	`pass`	The user’s information was verified against trusted reference data. Source Type: Trusted Source Corroboration	Success
SV204	`pass`	The driver’s license or state ID information was validated against an authoritative state motor vehicle record. Source Type: Authoritative Source Validation	Success
SV205	`pass`	The national ID number was validated against an authoritative source. Source Type: Authoritative Source Validation	Success

Not applicable outcomes

Exit Code	Outcome	External Metadata	Customer Support Instructions
SV301	`not_applicable`	Source validation is not supported for `{Country_Name}`. If `{country name}` is not available: - “Source validation is not supported for the provided country.” - “Source validation is not supported based on the user’s information”	The submitted document could not be source verified, and that is required by the project’s settings. If all other required checks are successful for the session, the `not_applicable` status for this check will not impact the overall status of the session.
SV302	`not_applicable`	Motor vehicle records lookup is not supported for `{state, or country if outside of the USA}`. If it is not possible to determine the document issuer, such as country or state: - Motor vehicle records lookup is not supported for this document issuer.	None provided.
SV303	`not_applicable`	The provided document is not a driver’s license or state ID.	None provided.

Indeterminate outcomes

Exit Code	Outcome	External Metadata	Customer Support Instructions
SV501	`indeterminate`	Source validation is temporarily unavailable and cannot be completed.	The source validation services were not available when the user completed the verification. Please have them try again `____` hours from now.
SV502	`indeterminate`	The user declined to complete all necessary steps for the verification.	The Aadhaar user denied consent to send the Aadhaar OTP. Please have the user accept the Aadhaar OTP consent screen, or offer them an alternative identity verification.

Fail outcomes

Exit Code	Outcome	External Metadata	Customer Support Instructions
SV401	`fail`	The provided details could not be verified using authoritative reference data.	The user submitted a Mexican passport and failed the CURP source validation, or an Indian passport and failed the Aadhaar source validation.
SV402	`fail`	The person associated with this phone number was found to be deceased.	The person associated with this phone number was found to be deceased.
SV403	`fail`	Verification could not be completed using trusted carrier data; only non-carrier data was available.	This indicates that phone carrier data was not available for this phone number, so the check could not be evaluated. Please first confirm that they are using a personal phone number, and not a shared phone, work phone, or voice-over-IP phone number. If the user is enrolling with a brand new phone number, they may be able to try again once the carrier databases update, or they can retry with a different personal mobile number. If the information submitted is correct and up to date, a final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV404	`fail`	The provided name does not match the name associated with this phone number.	This indicates the submitted full name does not match the name associated with the enrolling phone number. Please first confirm the legal name extracted is exactly as it appears on their government document. If the phone number belongs to a business line, is a new line, is a VOIP line, or is another person’s phone, have them retry with their own personal mobile number that is associated with their identity. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV405	`fail`	The provided date of birth does not match the name associated with this phone number.	This indicates the submitted DOB does not match the name associated with the enrolling phone number. Please first confirm the extracted legal name and DOB are exactly as they appear on their government document. If the phone number belongs to a business line, is a new line, is a VOIP line, or is another person’s phone, have them retry with their own personal mobile number. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV406	`fail`	The provided information matches a different identity in trusted reference data.	This indicates that the submitted evidence aligns to a different identity in a trusted reference database. Please first confirm the extracted legal name, DOB and address are exactly as they appear on their government document. If the information is correct, they may need to use a different document or, if they submitted a passport document, enter a more correct residential address. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV407	`fail`	The provided phone number could not be verified using trusted reference data.	This indicates the submitted phone number does not match the information on the government document. Please first confirm the extracted legal name and DOB are exactly as they appear on their government document. If the phone number belongs to a business line, is a new line, is a VOIP line, or is another person’s phone, have them retry with their own personal mobile number. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV408	`fail`	The provided address could not be verified using trusted reference data.	This indicates that the submitted address could not be verified against trusted reference data. If the user enrolled with a passport, confirm that the user entered their residential address, rather than a mailing address, PO box, or work address. If they submitted a drivers license with an old address and they moved without updating their license, the user may be able to retry by submitting a passport and then self-attesting the residential address that will more likely appear in trusted databases. If the information submitted is correct and up to date, a final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV409	`fail`	The name data for this phone number could not be found.	This indicates that no phone carrier data was available for this phone number, and the phone check could not match against a specific identity. Please first confirm that they are using a personal phone number, and not a shared phone, work phone, or voice-over-IP phone number. If the user is enrolling with a brand new phone number, they may be able to try again once the carrier databases update, or they can retry with a different personal mobile number. If the information submitted is correct and up to date, a final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV410	`fail`	Phone carrier data is unavailable for this recently established phone account. The check could not be evaluated.	This indicates the phone account appears to be too newly established to evaluate reliably. Please first confirm that they are using a personal phone number, and not a shared phone, work phone, or voice-over-IP phone number. If the user is enrolling with a brand new phone number, they may be able to try again once the phone account has more tenure, or they can retry with an older, more established personal phone number. If the information submitted is correct and up to date, a final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV411	`fail`	The provided phone number cannot be verified as a mobile or fixed number.	This indicates that the phone number could not be confirmed as an acceptable mobile or fixed line for verification. Please first confirm that they are using a personal mobile phone number, and not a land line, fax number, shared phone, work phone, or voice-over-IP (VOIP) phone number. If the information submitted is correct and up to date, a final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV412	`fail`	No matching name records exist in trusted reference data.	This indicates that no phone carrier data was available for this phone number, and the phone check could not match against a specific identity. Please first confirm the extracted legal name and DOB are exactly as they appear on their government document. If the information is correct and still not found, they may need to use a different verification path or provide a different corroborating data source. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV413	`fail`	The provided identity could not be verified with trusted data.	None provided.
SV414	`fail`	This ID number was not found in state motor vehicle records.	Inaccurate OCR: If CLEAR’s extraction of the document ID number was incorrect, the support team can reset this user’s account to try a better capture on a second enrollment, or the user can submit a secondary document. Accurate OCR: If the document ID number was extracted correctly, the motor vehicle database could not verify this document. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV415	`fail`	For this ID number, the first name on the document does not match state motor vehicle records. The last name and date of birth match.	Inaccurate OCR: If CLEAR’s extraction of the first name was incorrect (blur, smudge, damage, etc), the support team can reset this user’s account to try a better capture on a second enrollment, or the user can submit a secondary document. Accurate OCR: If the first name was extracted correctly, the motor vehicle database could not verify this document. CLEAR incorporates retry logic for logical variations and common typos of first names, but none of those were successful. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV416	`fail`	For this ID number, the last name on the document does not match state motor vehicle records. The first name and date of birth match.	Inaccurate OCR: If CLEAR’s extraction of the last name was incorrect (blur, smudge, damage, etc), the support team can reset this user’s account to try a better capture on a second enrollment, or the user can submit a secondary document. Accurate OCR: If the last name was extracted correctly, the motor vehicle database could not verify the name on the document. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV417	`fail`	For this ID number, the date of birth on the document does not match state motor vehicle records. The first name and last name match.	Inaccurate OCR: If CLEAR’s extraction of the DOB was incorrect (blur, smudge, damage, etc), the support team can reset this user’s account to try a better capture on a second enrollment, or the user can submit a secondary document. Accurate OCR: If the DOB was extracted correctly, the motor vehicle database could not verify the DOB on the document. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV418	`fail`	For this ID number, multiple pieces of information on the document do not match state motor vehicle records.	Inaccurate OCR: If CLEAR’s extraction of the document information was incorrect (blur, smudge, damage, etc), the support team can reset this user’s account to try a better capture on a second enrollment, or the user can submit a secondary document. Accurate OCR: If the document information was extracted correctly, the motor vehicle database could not verify this document. A final mitigation path for users in the United States and Canada is to download the free CLEAR App, go to the ‘Vault’ tab, and add the passport. Once this is complete, return to the original verification flow to try again.
SV419	`fail`	The provided full name could not be verified using trusted reference data.	None provided.
SV420	`fail`	The provided date of birth could not be verified using trusted reference data.	None provided.