Test Users

You can test 1-Click Signup with mock data in Sandbox, using either your own phone number or one of our test users below.

Use Sandbox for Development and Testing

Please do all development work and testing against our Sandbox environment, which returns mock data. You can use our Production environment when you're ready to go live.

Don't Send Messages to Test User Phones/Emails

The test user phone numbers and email addresses are not valid, so sending messages to them won't work. To simulate SMS verification, for example, use the test user (static) verification codes. To test real SMS verification, use your own (real) phone number.

How to Use Test Users

You can use our test users with our Demo and directly with our API.

With the Demo:

1. Go to the Demo and customize the settings as desired.
2. Select Mock Data (sandbox) and click Start Demo.
3. Enter the test user's phone number (varies by user).
4. Enter the test user's (static) verification code (always 111111).
5. If prompted, enter the test user's birth date (always 08/01/1989) and/or SSN4 (always 6789).

With the API:

1. Access the Dashboard and go the Brand Details page for your brand,
2. Note what integration type setting your brand has (Hosted, Semi-Hosted, or Non-Hosted).
3. Copy a Sandbox API key for your brand.
4. Use the API, following the steps in the Integration Guide, making sure you have the correct integration type tab selected. For example, for Non-Hosted:
   1. Call POST /1-click with the test user's phone number (varies by user).
   2. (if applicable) Call POST /1-click again, adding the test user's birth date (always 1989-08-01) and/or SSN4 (always 6789).

Success

Use these test users to go through successful 1-Click Signup flows (where Verified returns credentials).

Phone Only

For these users, only a phone number is needed to source credentials.

Primary Test User

Our primary test user is Richard Hendricks:

Phone	+10123456789
Verification Code	111111
Email	richard@piedpiper.net
Birth Date	1989-08-01
SSN4	6789

Yes, You Read That Right

This is Richard Hendricks from the show Silicon Valley! 😂

Allowed

Use this user to specifically test the low risk case of risk signals metadata. Compare it to the medium risk (flagged) and high risk (blocked) test users.

Phone	+15555550000
Verification Code	111111
Birth Date	1989-08-01
SSN4	6789

Flagged

Use this user to specifically test the medium risk case of risk signals metadata. Compare it to the low risk (allowed) and high risk (blocked) test users.

Phone	+15555550001
Verification Code	111111
Birth Date	1989-08-01
SSN4	6789

Phone and Additional Info

For these users, both a phone number and additional information is needed to source credentials.

If you start with phone only, as we recommend (see the Integration Guide), you will get the OCE011 error code, indicating that additional information is required. Within the error, data.additionalInputs specifies which additional inputs you can pass (see OCE011 for details).

tip

The OCE012 error code indicates that there's a mismatch for one or more of the additional inputs you provided. To trigger this error code, use any value that doesn't match the value for the test user.

For example, use 1979-01-01 for birthDate (since all test users have 1989-08-01 for birthDate).

Phone and Birth Date and/or SSN4

For this user, both a phone number and either a birth date or SSN4 is needed to source credentials.

Phone	+10019999999
Verification Code	111111
Birth Date	1989-08-01
SSN4	6789

Error Attribute	Value
data.errorCode	OCE011
data.additionalInputs	["birthDate", "ssn4"]

Phone and Birth Date

For this user, both a phone number and either a birth date or SSN4 is needed to source credentials.

Phone	+10019999997
Verification Code	111111
Birth Date	1989-08-01

Error Attribute	Value
data.errorCode	OCE011
data.additionalInputs	["birthDate"]

Phone and SSN4

For this user, both a phone number and either a birth date or SSN4 is needed to source credentials.

Phone	+10019999996
Verification Code	111111
SSN4	6789

Error Attribute	Value
data.errorCode	OCE011
data.additionalInputs	["ssn4"]

Credential Cases

Use these test users to write specific cases for credential data, if it's relevant to your use case.

Address

Different Values

For each of these 10 test users, you will get a 1ClickEntity with a different address. Each address is a standard address in a US state (as opposed to an address in an overseas territory or a P.O. box address).

Phone	+12225550000 → +12225550009
Verification Code	111111
Birth Date	1989-08-01
SSN4	6789

Overseas Territory

For this test user, you will get a 1ClickEntity with an address in Puerto Rico (a US overseas territory).

Phone	+12225550010
Verification Code	111111
Birth Date	1989-08-01
SSN4	6789

1ClickEntity

{
    "identifiers": {
        "phone": "+12225550010"
    }
    "credentials": {
        ...
        "address": {
            "line1": "3167 Av Roosevelt",
            "city": "Ponce",
            "state": "PR",
            "zipCode": "00717",
            "country": "US"
        },
        ...
    },
    ...
}

P.O. Box

For this test user, you will get a 1ClickEntity with a P.O. box address.

Phone	+12225550011
Verification Code	111111
Birth Date	1989-08-01
SSN4	6789

1ClickEntity

{
    "identifiers": {
        "phone": "+12225550011"
    }
    "credentials": {
        ...
        "address": {
            "line1": "P.o. Box 8672",
            "city": "Ketchikan",
            "state": "AK",
            "zipCode": "99901",
            "country": "US"
        },
        ...
    },
    ...
}

Birth Date: Under 18

For this test user, you will get a 1ClickEntity with a birth date less than 18 years ago (until January 1, 2035).

info

You should never receive data from Verified for a user under 18 years old, but this test user facilitates writing a check for that on your side if you wish.

Phone	+12225550012
Verification Code	111111
Birth Date	2017-01-01
SSN4	6789

1ClickEntity

{
    "identifiers": {
        "phone": "+12225550012"
    }
    "credentials": {
        ...
        "birthDate": "2017-01-01",
        ...
    },
    ...
}

Failure

Use these test users to go through unsuccessful 1-Click Signup flows (where Verified does not return credentials).

No Credentials Found

For this user — if you start with phone only, as we recommend (see the Integration Guide) — you will get the OCE011 error code, indicating that additional information is required. Within the error, data.additionalInputs specifies which additional information you can pass (see OCE011 for details).

Phone	+10019999998
Verification Code	111111

Error Attribute	Value
data.errorCode	OCE011
data.additionalInputs	["birthDate", "ssn4"]

If you then pass additional inputs (with any values), you will get the OCE013 error code, indicating that Verified found no credentials.

Error Attribute	Value
data.errorCode	OCE013

Blocked

Use this user to specifically test the high risk case of risk signals metadata. Compare it to the low risk (allowed) and medium risk (flagged) test users.

For this user, you will get the OCE017 error code, indicating that Verified blocked returning data for the user because the risk score is too high.

Phone	+15555550002
Verification Code	111111
Birth Date	1989-08-01
SSN4	6789

Error Attribute	Value
data.errorCode	OCE017
data.riskSignals	RiskSignals