To enable clients to better troubleshoot failures and reduce their reliance on customer support, CLEAR exposes metadata describing the detailed results of checks.

Source Validation

Reason Code	Check Result	Reason	Support Instructions
SV201	`success`	Passport authenticity was validated using embedded security features and issuing records. Source Type: Authoritative Source Validation	Success
SV202	`success`	The user’s phone number was corroborated using the information on the submitted government ID. Source Type: Phone Number Validation	Success
SV203	`success`	The user’s information was verified against trusted reference data. Source Type: Trusted Source Corroboration	Success
SV204	`success`	The driver’s license or state ID information was validated against an authoritative state motor vehicle record. Source Type: Authoritative Source Validation	Success
SV205	`success`	The national ID number was validated against an authoritative source. Source Type: Authoritative Source Validation	Success
SV206	`success`	The user’s phone number was corroborated using the information from the submitted government ID. The user’s full name, address, and date of birth were verified against trusted reference data. Country: <Country> Source Types: Phone Number Validation, Trusted Source Corroboration	Success
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.
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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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 with a United States passport 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.	Confirm the user is using an active personal mobile number. Have them retry with a different active personal mobile number.
SV420	`fail`	The provided date of birth could not be verified using trusted reference data.	Confirm the user is using their own personal mobile number. If correct, retry with a different personal mobile number.
SV421	`fail`	The provided identity has been matched to multiple unique social security numbers.	Confirm the user's legal name, date of birth, and address match the submitted government ID. If correct, retry with a different supported document or verification path.
SV422	`fail`	The provided phone number has recently been connected to a new owner.	Confirm the number is a personal mobile number and was not recently reassigned. Retry with an established personal mobile number or try again after carrier records update.
SV423	`fail`	The provided phone number was disconnected after the provided identity was first associated with it.	Confirm the number is active and belongs to the user. Retry with a current personal mobile number.
SV424	`fail`	The provided identity has been matched to multiple dates of birth.	Confirm the date of birth matches the submitted government ID. If correct, retry with a different supported document or verification path.
SV425	`fail`	The provided identity has been matched to an atypical number of relatives with the same or similar names.	Confirm the legal name, date of birth, address, and phone number are correct. If correct, retry with a different supported document or verification path.
SV426	`fail`	The matched identity is associated with an SSN that was issued before the date of birth on the submitted government ID.	Confirm the date of birth was captured correctly. If OCR is incorrect, recapture the document. If correct, retry with a different supported government ID or verification path.
SV427	`fail`	The provided phone number is a business line and cannot be verified to an individual.	Have the user retry with their own personal mobile number instead of a business or office line.
SV428	`fail`	The provided phone number is a non-personal or shared line and cannot be uniquely verified.	Have the user retry with a personal mobile number that is not shared, VoIP, or otherwise non-personal.
SV429	`fail`	The provided phone number is part of a shared or secondary account.	Have the user retry with a phone number on an account uniquely associated with them.
SV430	`fail`	The provided full name could not be verified using trusted reference data.	Confirm the legal full name matches the submitted government ID. If correct, retry with a different supported document or verification path.
SV431	`fail`	The provided date of birth could not be verified using trusted reference data.	Confirm the date of birth matches the submitted government ID. If OCR is incorrect, recapture the document; otherwise retry with a different supported document or verification path.
SV432	`fail`	Source validation is not supported for the provided country.	Confirm the document country and project configuration. Use a supported document or alternate verification path if available.
SV433	`fail`	The provided first and last names were swapped.	Verify that the first and last names are entered in the correct fields and match the government ID, then retry.
SV434	`fail`	The network status information (i.e. Active, Deactivated, Suspended) of the provided phone number isn't available from the carrier.	Confirm the number is an active personal mobile number. Retry later or use a different personal mobile number.
SV435	`fail`	The provided phone number was ported between carriers.	Confirm the user still controls the number. Retry after carrier records update or use a different personal mobile number.
SV436	`fail`	The user declined to complete all necessary steps for Aaadhaar verification.	Ask the user to accept consent to send the Aadhaar OTP and complete the OTP step. If they do not consent, offer an alternate verification path if available.
SV437	`fail`	Passport authenticity could not be validated using embedded security features and issuing records.	Confirm the user has a valid passport with an NFC chip and completed the scan. Because this is a conclusive NFC failure, use a different supported document or alternate verification path if available.
SV438	`fail`	The digital signature on the document could not be verified.	Have the user try another supported government ID (passport) or an approved alternate verification path. If they believe the document is valid, route the case through the established review process.
SV501	`not_applicable`	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.

Phone Line Intelligence

Reason Code	Check Result	Reason	Support Instructions
PL200	`success`	The provided phone line was verified to be a mobile or fixed phone number.	Success
PL301	`not_applicable`	Phone number validation is not supported for the provided country.	Phone number validation is not supported for this country. Use a supported phone number or alternate verification path if available.
PL402	`fail`	The person associated with this phone number was found to be deceased.	Have the user retry with a different active personal mobile number.
PL403	`fail`	Verification could not be completed using trusted carrier data; only non-carrier data was available.	Confirm the user is using a personal mobile number. Retry later or use a different personal mobile number.
PL409	`fail`	The phone line data for this phone number could not be found.	Confirm the number is correct and personal. Retry later or use a different personal mobile number.
PL410	`fail`	Phone carrier data is unavailable for this recently established phone account. The check could not be evaluated.	Retry after the phone account has more tenure, or use an older established personal mobile number.
PL411	`fail`	The provided phone number cannot be verified as a mobile or fixed number.	Have the user retry with an active personal mobile number that is not a landline, fax, shared, business, or VoIP number.
PL419	`fail`	The provided phone number is either suspended or deactivated and cannot be validated.	Confirm the user is using an active personal mobile number. Have them retry with a different active number.
PL427	`fail`	The provided phone number is a business line and cannot be verified to an individual.	Have the user retry with their own personal mobile number instead of a business line.
PL428	`fail`	The provided phone number is a non-personal or shared line and cannot be uniquely verified.	Have the user retry with a personal mobile number that is not shared, VoIP, or otherwise non-personal.
PL429	`fail`	The provided phone number is part of a shared or secondary account.	Have the user retry with a phone number on an account uniquely associated with them.

Motor Vehicle Records

Exit Code	Check Result	Reason	Support Instructions
MV204	`success`	The driver’s license or state ID information was validated against an authoritative state motor vehicle record.	Success
MV301	`not_applicable`	Motor vehicle records lookup is not supported for the provided document issuer.	Use a supported driver’s license or state ID, or use an alternate verification path if available.
MV302	`not_applicable`	The provided document is not a driver’s license or state ID.	Have the user submit a supported driver’s license or state ID, or use an alternate verification path.
MV414	`fail`	This ID number was not found in state motor vehicle records.	Confirm the ID number was captured correctly. If OCR is incorrect, recapture the document. If correct, retry with a different supported document or verification path.
MV415	`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.	If the first name was captured incorrectly, recapture the document. If correct, retry with a different supported document or verification path.
MV416	`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.	If the last name was captured incorrectly, recapture the document. If correct, retry with a different supported document or verification path.
MV417	`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.	If the date of birth was captured incorrectly, recapture the document. If correct, retry with a different supported document or verification path.
MV418	`fail`	For this ID number, multiple pieces of information on the document do not match state motor vehicle records.	If the document information was captured incorrectly, recapture the document. If correct, retry with a different supported document or verification path.
MV419	`fail`	The digital signature on the document could not be verified.	Have the user try another supported government ID (passport) or an approved alternate verification path. If they believe the document is valid, route the case through the established review process.
MV501	`indeterminate`	Motor vehicle records validation is temporarily unavailable and cannot be completed.	Have the user try again later. No changes to the submitted information are required unless it is incorrect.

Phone Number Validation

Reason Code	Check Result	Reason	Support Instructions
PV200	`success`	The provided phone number was validated against trusted phone records.	Success
PV301	`not_applicable`	Phone number validation is not supported for the provided country.	No action is needed for this check; Phone number validation isn’t supported for the provided country.
PV402	`fail`	The person associated with this phone number was found to be deceased.	Have the user retry with a different active personal mobile number.
PV403	`fail`	Verification could not be completed using trusted carrier data; only non-carrier data was available.	Confirm the user is using a personal mobile number. Retry later or use a different personal mobile number.
PV404	`fail`	The provided name does not match the name associated with this phone number.	Confirm the legal name matches the submitted government ID and the phone account. If correct, retry with the user’s own personal mobile number.
PV405	`fail`	The provided date of birth does not match the date of birth associated with this phone number.	Confirm the date of birth matches the submitted government ID. If correct, retry with the user’s own personal mobile number.
PV407	`fail`	The provided phone number could not be verified in the trusted reference data.	Confirm the number is correct and personal. Retry later or use a different personal mobile number.
PV409	`fail`	The name data for this phone number could not be found.	Confirm the user is using a personal mobile number. Retry later or use a different personal mobile number.
PV410	`fail`	Phone carrier data is unavailable for this recently established phone account. The check could not be evaluated.	Retry after the phone account has more tenure, or use an older established personal mobile number.
PV411	`fail`	The provided phone number cannot be verified as a mobile or fixed number.	Have the user retry with an active personal mobile number that is not a VoIP, landline, fax, shared, or business number.
PV413	`fail`	The provided identity could not be verified with trusted data.	Confirm the legal name, date of birth, and address match the submitted government ID. If correct, retry with a different supported document or verification path.
PV433	`fail`	The provided first and last names were swapped.	Verify that the first and last names are entered in the correct fields and match the government ID, then retry.
PV434	`fail`	The network status information (i.e. Active, Deactivated, Suspended) of the provided phone number isn't available from the carrier.	Confirm the number is an active personal mobile number. Retry later or use a different personal mobile number.
PV435	`fail`	The provided phone number was ported between carriers.	Confirm the user still controls the number. Retry after carrier records update or use a different personal mobile number.

SSN Validation

Reason Code	Check Result	Reason	Support Instructions
SSN200	`success`	The SSN is valid and matches the provided full name and address.	Success
SSN201	`success`	The SSN is valid and matches the full name from the government ID.	Success
SSN202	`success`	The SSN is valid and matches the provided address.	Success
SSN301	`not_applicable`	SSN validation is not supported for the provided country.	No action is needed for this check; SSN validation isn’t supported for the provided country.
SSN401	`fail`	The SSN did not match the full name from the government ID.	Confirm the name matches the government ID and correct any entry errors. If the information is accurate, use an approved alternate verification path or review process.
SSN402	`fail`	The SSN did not match the provided address.	Confirm the address is accurate and correct. If the information is accurate, use an approved alternate verification path or review process.
SSN403	`fail`	The SSN returned a death indicator.	If the user believes this result is incorrect, route the case through the established review process. Do not ask the user to alter their SSN information to clear the result.
SSN404	`fail`	The SSN is not in a valid format.	Confirm the SSN was entered in the expected nine-digit format and check for transcription errors, then retry.

Regulatory Screening Validation

Reason Code	Check Result	Reason	Support Instructions
RS201	`success`	No matches were identified on politically exposed persons lists.	Success
RS202	`success`	No matches were identified on sanctions lists.	Success
RS203	`success`	No matches were identified on regulatory or warning lists.	Success
RS204	`success`	No matches were identified in adverse media sources.	Success
RS401	`fail`	A match was identified on one or more politically exposed persons lists.	A screening match was identified. Route the case through the established review process; do not promise that changing submitted information will resolve the result.
RS402	`fail`	A match was identified on one or more sanctions lists.	A screening match was identified. Route the case through the established review process; do not promise that changing submitted information will resolve the result.
RS403	`fail`	A match was identified on one or more regulatory or warning lists.	A screening match was identified. Route the case through the established review process; do not promise that changing submitted information will resolve the result.
RS404	`fail`	A match was identified in one or more adverse media sources.	A screening match was identified. Route the case through the established review process; do not promise that changing submitted information will resolve the result.
RS501	`indeterminate`	Regulatory screening is temporarily unavailable and cannot be completed.	Have the user retry later. No changes to submitted information are needed unless it is incorrect.