Reason Codes
Understanding the reason codes returned by Straddle’s Identity verification process
Identity Reason Codes
When you create or update a customer using Straddle’s API, our system performs an identity verification process. This process returns reason codes that provide insights into the verification results. These codes are crucial for understanding the risk assessment and decision-making process.
Overview
Reason codes are alphanumeric identifiers that explain specific aspects of the identity verification process. They are categorized into different types, each starting with a specific letter:
I
: Informational codesR
: Risk indicator codesBI
: Business Identity Informational codesBR
: Business Identity Risk indicator codes
Reason codes provide valuable context for the verification decision. Always review these codes to understand why a particular decision was made.
Accessing Reason Codes
You can access the reason codes in the response when creating or retrieving a customer. The codes are located in the identity_details
object of the response.
Interpreting Reason Codes
Informational Codes (I, BI)
Informational codes provide context about the verification process and the data used. They don’t necessarily indicate a risk but offer additional insights.
Risk Indicator Codes (R, BR)
Risk indicator codes highlight potential risks or discrepancies in the provided information. These codes are crucial for assessing the overall risk of a customer.
R1001
: Found at least 2 distinct DOBs associated with the given identityR201
: The input SSN is invalidR520
: Emailrisk score represents high riskR701
: Address is inactive, not receiving mail, or vacantR901
: SSN/ITIN cannot be resolved to the individual
Using Reason Codes in Your Application
When implementing identity verification in your application, you can use these reason codes to:
- Provide specific feedback to users about their verification status
- Implement custom logic based on certain codes
- Flag high-risk applications for manual review
Here’s an example of how you might use reason codes in your application:
Best Practices
When working with identity reason codes, consider the following best practices:
- Regularly review and update your handling of reason codes: As Straddle may introduce new codes or modify existing ones, ensure your application can handle new codes gracefully.
- Combine multiple codes for a comprehensive risk assessment: Don’t rely on a single code to make decisions. Consider the full picture provided by all returned codes.
- Provide clear feedback to users: When possible, use reason codes to give specific instructions to users for resolving verification issues.
- Monitor code frequencies: Keep track of which codes appear most often in your verifications. This can help you identify patterns and potential areas for improvement in your onboarding process.
- Consult with Straddle: If you’re unsure about the meaning or implication of certain codes, don’t hesitate to reach out to Straddle’s support team for clarification.
Remember, while reason codes are powerful tools for risk assessment, they should be used in conjunction with other fraud prevention measures for the most effective protection against fraudulent activities.
By leveraging these identity reason codes effectively, you can enhance your risk assessment process, improve your user experience, and make more informed decisions about customer verifications.
Reason Codes Documentation
Account Verification Codes
Code | Description |
---|---|
I301 | Account is correlated with the first name |
I302 | Account is conditionally correlated with the first name |
I304 | Account is correlated with the last name |
I305 | Account is conditionally correlated with the last name |
I307 | Account is correlated with the business name |
I308 | Account is conditionally correlated with the business name |
I310 | Account is correlated with the DOB |
I311 | Account is conditionally correlated with the DOB |
I313 | Account is correlated with the SSN |
I314 | Account is conditionally correlated with the SSN |
I316 | Account is correlated with the address |
I317 | Account is conditionally correlated with the address |
I319 | Account is correlated with the phone |
I320 | Account is conditionally correlated with the phone |
Device Verification Codes
Code | Description |
---|---|
I401 | Device token previously encountered |
I402 | Multiple users associated with device |
I403 | Identity may not be primary device user |
I404 | Identity associated with primary device owner |
I405 | Device token previously associated with phone number |
I406 | Device token previously associated with email address |
I407 | Device token previously associated with first name |
I408 | Device token previously associated with last name |
I409 | Device token not encountered within the past 5 days |
I410 | Device session is associated with more than 2 phone numbers |
I411 | Device session is associated with more than 2 emails |
I412 | Device session is associated with more than 2 first names |
I413 | Device session is associated with more than 2 last names |
I414 | Session connected using a proxy |
I415 | Session IP located more than 100 miles from the address |
I416 | Session IP originates from within the United States |
I417 | Session IP originates from outside the United States |
I419 | Session connected using a residential IP address |
I420 | Session connected using a commercial IP address |
I421 | Session connected using a mobile IP address |
I423 | Device is a physical device |
I424 | Device type is a desktop or laptop computer |
I425 | Device type is mobile, tablet, or wearable |
I428 | Mobile network associated with the device is a non-US carrier |
Email Verification Codes
Code | Description |
---|---|
I520 | Email risk score represents low risk |
I550 | Email address is more than 180 days and less than 1 year old |
I551 | Email address is more than 1 year and less than 2 years old |
I553 | Email address is more than 2 years old |
I554 | Exact match between email and first name |
I555 | Email domain is more than 180 days old |
I556 | Email address can be resolved to the individual |
I557 | Email is correlated with the first name |
I558 | Email is correlated with the last name |
I559 | Exact match between email and last name |
I560 | Email domain represents a Fortune 500 company |
I561 | Email domain represents a US college or university |
I562 | Email username contains ZIP code of current application |
I563 | Email domain contains a special use domain (RFC, arpa, example, invalid, local, onion, etc.) |
I564 | Special characters found in email alias |
I565 | Email username contains a role-level alias (support, info, admin, etc.) |
I566 | Email provider is found in public web sources |
I567 | Email username contains five or more alphabetic sections |
I568 | Email handle contains a name |
I569 | Email handle contains input first name |
I570 | Email handle contains input surname |
I571 | Email top-level domain represents a non-US country |
I572 | Email subdomain possibly a typo of a popular email domain |
I573 | Email top-level domain possibly a typo of a popular TLD |
I575 | Provided email is a possible filler email |
I576 | Email handle aligns with the pattern of valid email addresses |
Phone Verification Codes
Code | Description |
---|---|
I601 | Phone number is a landline |
I602 | Phone number is a mobile line |
I605 | Phone number is a premium-rate line |
I608 | Phone number is commercial or dual-purpose |
I609 | Phone number is consumer or residential |
I610 | Phone number is correlated with the address |
I611 | Phone number is associated with a major US carrier |
I614 | Phone number has been in service more than 365 days |
I616 | Phone number is associated with a Mobile Virtual Network Operator |
I618 | Phone number can be resolved to the individual |
I620 | Phone risk score represents low risk |
I621 | Phone is correlated with the first name |
I622 | Phone is correlated with the last name |
I623 | Exact match between phone and first name |
I624 | Exact match between phone and last name |
I625 | Phone number has never been ported |
I626 | Phone number was ported at least 60 days ago |
I630 | Phone subscriber has been correlated with the input phone number for more than 365 days |
Address Verification Codes
Code | Description |
---|---|
I704 | Address is multi-unit or high-rise |
I705 | Address is single unit |
I706 | Address is an accredited college or university |
I707 | Address is residential |
I708 | Address can be resolved to the individual |
I709 | Address is correlated with the first name |
I710 | Address is correlated with the last name |
I711 | Address is confirmed as deliverable |
I712 | Address is confirmed deliverable by dropping secondary information |
I713 | Address is confirmed deliverable but was missing secondary information |
I714 | Address is valid but doesn’t currently receive USPS street delivery |
I715 | Address is correlated with a past address |
I716 | Address is a Small Office/Home Office (SOHO) |
I718 | Exact match between address and first name |
I719 | Exact match between address and last name |
I720 | Address risk score represents low risk |
I721 | Email address is correlated with the input physical address |
I722 | Email address is partially correlated with the input physical address |
General Information Codes
Code | Description |
---|---|
I903 | Address was not provided at input |
I904 | SSN/ITIN was not provided at input |
I905 | SSN/ITIN provided at input contained only 4 digits |
I906 | DOB was not provided at input |
I907 | SSN is issued to a non-US citizen |
I908 | Address is correlated with a military ZIP code |
I909 | First name and last name are possibly reversed |
I910 | Address is correlated with a past address |
I911 | Address is a PO Box |
I912 | SSN was randomly issued by the SSA |
I913 | SSN has not been reported as deceased |
I914 | Identity has not been reported as deceased |
I917 | Full name and address can be resolved to the individual but the SSN/ITIN is not |
I919 | Full name, address, and SSN/ITIN can be resolved to the individual |
I920 | Emerging identity indicator |
I921 | Address is an accredited college or university |
I922 | Mobile number was not provided at input |
I923 | Email address was not provided at input |
I930 | Name and DOB match a notable personality or celebrity |
I931 | First name or last name may refer to a non-person entity |
I932 | Name and DOB match a notable individual in the sports industry |
I933 | Multi-party application detected |
I975 | Non-MLA covered borrower status |
I998 | Name, SSN, and DOB correlation verified by SSA |
I999 | Identity decease unverified by SSA |
Risk Codes
Code | Description |
---|---|
R1001 | Found at least 2 distinct DOBs associated with the given identity |
R1002 | Found at least 4 distinct first names associated with the given identity |
R1003 | Found at least 4 distinct last names associated with the given identity |
R1004 | Found at least 3 distinct phone numbers associated with the given identity |
R1005 | Found at least 3 distinct emails associated with the given identity |
R1006 | Found at least 1 application marked as fraudulent associated with the given identity |
R1007 | Found at least 1 application marked as third-party fraud associated with the given identity |
R1008 | Found at least 2 applications within 30 days of each other associated with the given identity |
R1009 | Found at least 2 applications within 90 days of each other associated with the given identity |