Setup
| Time to Complete | 15 minutes |
|---|---|
| Skills Required | No technical skills! |
Complete this Setup guide before following the SDK Integration or API Integration guide. (Which integration guide you should follow depends on which integration type you choose.)
1. Access the Dashboard.
Create or log into your Verified Dashboard account so you can:
- Start development immediately with Sandbox API keys
- Manage your team’s access
- Create one or more brands within your company’s account
- Configure each brand’s settings
- Ask for integration assistance from the Verified team
- Request approval for Production
- View metrics for your integration
Someone at your company may have already created a Dashboard account for your company and invited you via email. Check with your team internally before creating a new, duplicate account — or ask your Verified representative for assistance.
How to Create a Dashboard Account
a. Enter your email and click the 1-Click Login button.
We'll send you a verification code by email.
Use your work email. We use AI to auto-magically set brand information based on your email domain, so you don't have to manually enter it!
b. Complete the verification step.
Click the verification button in the email or enter the verification code. We'll automatically log you in. It's a 1-click experience, as promised!
c. (optional) Set up MFA.
Set up multi-factor authentication with an authenticator app. This is optional until you request approval for Production access, at which point it's required.
d. (if necessary) Confirm your company name.
If you're creating the Dashboard account for your company, we'll ask you to confirm your company name. If someone on your team has already created your account, you won't need to do this.
If your account doesn't have a brand yet, we'll automatically create one for you and take you to its Brand Details page.
Your company account can have one or more brands. Generally, you'll only need one brand, but there are some cases where it's helpful to use multiple. For example:
- If you have multiple products: If you have products that go by different names, it can be useful to create different brands to help users know which product they're using 1-Click Signup for — and to help your team track metrics specific to that product.
- If you want to try different brand settings: If you want to change brand settings without affecting your existing implementation (even in Sandbox), you can duplicate your brand and configure different settings on the new brand.
e. (optional) Invite team members.
Invite your team members to join your Dashboard account.
2. Configure brand settings.
On the Brand Details page in the Dashboard, you can configure settings for your brand.
Brand Name
Choose a name for your brand. This will be used elsewhere in the Dashboard (for example on the Metrics page) and displayed to users if you choose the SDK integration type.
Integration Type
Choose which integration type you want to use:
| Option | Development Effort | Description |
|---|---|---|
| SDK Recommended | <1 day | You use our (web) client SDK, and we handle the rest |
| API Requires Approval | 1-2 weeks | You use our API only and build everything yourself |
The SDK integration type is by far the easier option, and we strongly recommend using it. The SDK handles almost everything for you and is highly customizable, so you can use it to exactly match your branding and desired user experience. It implements our recommended user experience, which is hyper optimized from our experience verifying millions of users.
With the API integration type, you need to handle everything yourself, and you need approval from us to go live.
- Hosted in v2.0 is replaced by SDK in v2.1
- Semi-Hosted in v2.0 is no longer available in v2.1
- Non-Hosted in v2.0 is equivalent to API in v2.1
Challenges
A challenge is a piece of information we will prompt the user to input if we're unable to source data for them based on previous inputs (for example, phone).
Choose which challenge(s) to allow:
| Option | Description |
|---|---|
| Birthday or SSN4 Recommended | Prompt the user for their birthday, SSN4, or both (only if necessary). Birthday always comes first. |
| Birthday only | Prompt the user for their birthday only — never their SSN4. |
| SSN4 only | Prompt the user for their SSN4 only — never their birthday. |
Why We Recommend Birthday or SSN4
Birthday or SSN4 is the option we recommend because the user is only prompted for both challenges if necessary. This is quite rare, so it adds very little friction, but it increases conversion by a few percentage points.
One example is the case of twins:
- Based on just a phone number, we find two users.
- We prompt for birthday, but we still find two users — because they're twins with the same birthday!
- So, we prompt for SSN4, which narrows down to a single user.
The birth rate of twins (and triplets, etc.) in the US is 3.2%, so choosing Birthday or SSN4 instead of Birthday only increases success rate by about that much.
Prompt for Challenges
Choose when to prompt for challenge(s):
| Option | Description |
|---|---|
| Only if necessary | Prompt the user for challenge(s) only if Verified can't source data based on just phone. |
| Always | Prompt the user for a challenge upfront, every time. |
If you choose Always, the user will only be prompted for one challenge.
- If you chose Birthday or SSN4 or Birthday only for the Challenges setting, the challenge will be their birthday.
- If you chose SSN4 only for the Challenges setting, the challenge will be their SSN4.
Always prompting for a challenge can help improve data quality for some user populations.
Risk Signals
Risk signals are metadata that enhance 1-Click Signup's anti-fraud capabilities.
Choose which risk signals to include in Verified's responses:
| Option | Description |
|---|---|
| Basic | Include only high level risk signals (Overall Score, Level, and Recommendation). |
| Advanced Extra | Include all risk signals (Reason Codes, carrier data, and more). |
| Off Not Recommended | Include no risk signals. |
Advanced risk signals come with extra cost. They're particularly relevant if you're using 1-Click Signup for a high sensitivity use case where fraud is a major risk.
Off is not recommended. It will prevent Verified from sourcing risk signals for a user and blocking them if the risk score is too high.
Default Credential Requests
- A credential is a piece of identity data about a user (like a first name or address).
- A credential request is how you ask Verified for a particular credential. It encodes what type of data you're asking for, whether it's required or optional, whether multiple values should be returned, etc. See the
CredentialRequesttype for full details.
Choose which credentials Verified should try to source about the user:
Settings for a Credential Request
| Setting | Relevant to Integration Type | Options | Default | Description | Example |
|---|---|---|---|---|---|
| Field Type | SDK and API | Credential type | - | Type of user data this field is for | Full Name |
| Field Description | SDK only | Text | - | Text that appears under the field | Legal name (for Full Name field type) |
| Optional or Required | SDK only |
| Optional | Whether the field is optional or required | Optional |
| Allow User Input | SDK only |
| Yes | Whether the user is allowed data returned for the field | Yes |
| Multiple Values | SDK and API |
|
| Whether the user can choose among multiple values (if they're returned) | No |
Field Description, Optional or Required, and Allow User Input are only relevant to the SDK integration type because they affect the user interface the SDK displays.
If Optional or Required is set to Required if available:
- If data is returned for the field, the user is required to share it. (If Allow User Input is set to Yes, the user can edit the data.)
- If data is not returned for the field, the user can optionally share it. (If Allow User Input is set to Yes, the user can edit the data. If it's set to No, the field is not displayed to the user.)
When you create a new brand, the Dashboard starts you off with standard credential requests to provide you with a helpful starting point:
Standard Credential Requests
| Field Type | Field Description | Optional or Required | Allow User Input | Multiple Values |
|---|---|---|---|---|
| Full Name | - | Optional | Yes | No |
| ↳ First Name | - | Optional | Yes | - |
| ↳ Last Name | - | Optional | Yes | - |
| Phone | - | Optional | Yes | No |
| Address | - | Optional | Yes | Yes |
| ↳ Line 1 | - | Optional | Yes | - |
| ↳ Line 2 | Apt, Unit, etc. | Optional | Yes | - |
| ↳ City | - | Optional | Yes | - |
| ↳ State | - | Optional | Yes | - |
| ↳ ZIP Code | - | Optional | Yes | - |
| ↳ Country | - | Optional | Yes | - |
| Birth Date | - | Optional | Yes | - |
| SSN | - | Optional | Yes | - |
SDK Styling
These styling settings are only relevant to the SDK integration type because they affect the user interface the SDK displays.
We use AI to auto-magically configure styling settings based on your email domain, so you don't have to do so manually from scratch!
| Setting | Options | Default | Description |
|---|---|---|---|
| Logo | Any square image (max size 200 KB, JPG or PNG) | - | Logo displayed to users |
| Primary Color | Any hex code | #0DBC3D | Color used for primary buttons and success indicators |
| Error Color | Any hex code | #EB0D28 | Color used for errors |
| Muted Color | Any hex code | #BDBDBD | Color used for secondary buttons and text |
| Background Color | Any hex code | #FFFFFF | Color used for background |
| Alignment |
| Center | Alignment used for most text, buttons, and the powered by Verified graphic |
| Font Family | Any Google font | Lato | Font used for all elements |
| 1-Click Word |
| Signup | Word that appears after "1-Click" in the powered by Verified graphic |
| Graphic Color |
| Green | Color of the Verified logo in the powered by Verified graphic |
| Input Border Radius | Any number | 4 | Border radius used for all inputs |
| Button Border Radius | Any number | 4 | Border radius used for all buttons |
The SDK will automaticallly adjust the color of text to achieve good contrast, given the color of an element. For example:
- If you set Background Color to be dark, the SDK will adjust text on the background to be light.
- If you set Primary Color to be light, the SDK will adjust text on buttons to be dark.