Outputs

An output is a piece of data we return from the SDK or API.

1-Click Verify

1-Click Signup

Credentials

A credential is a piece of identity data about a user.

Credential Formats

We support multiple formats for some credential types (see below). If you'd like to use formats different than the defaults, please reach out to us at Support@Verified.inc and we'll enable them for you.

Core Data

Coverage

We can source the data below for ~95% of US adults if you provide both phone and a challenge (either birthday or SSN4) as inputs — and for about 20% if you provide only phone. (The one exception is the Sex credential, which we can source for ~80% of US adults.)

Exact coverage depends on your user base and varies widely across companies. Some companies see >97% coverage, while a few see only 50%. See Coverage for more information.

Output	Key	Type	Format(s)	Description	Example
Phone	phone	string	E.164	Phone number	"+12125550010"
Full Name	fullName	Default: object string	Default: Object with keys for all child credentials listed below Any combination of child shortenedCredentialTypes under fullName, , (comma), and - (dash)	Full name	See 1ClickEntity example "Hendricks, Richard"
↳ First Name	fullName.firstName	string	Title Case	First name	"Richard"
↳ Middle Name	fullName.middleName	string	Title Case	Middle name	"Harrison"
↳ Last Name	fullName.lastName	string	Title Case	Last name	"Hendricks"
Address	address	Default: object string	Default: Object with keys for all child credentials listed below Any combination of child shortenedCredentialTypes under address, , (comma), and - (dash)	Address	See 1ClickEntity example "Palo Alto, US-CA"
↳ Line 1	address.line1	string	Title Case	Line 1 of address	"5320 Newell Rd"
↳ Line 2	address.line2	string	Title Case	Line 2 of address	""
↳ City	address.city	string	Title Case	City of address	"Palo Alto"
↳ State	address.state	string	Default: 2 letter abbreviation (last 2 characters of ISO 3166-2 code for US state/territory) Full state/territory name (ISO 3166-2 subdivision name)	State of address	"CA" "California"
↳ ZIP Code	address.zipCode	string	ZIP Code (5 digits, 0-9)	ZIP Code of address	"94303"
↳ Country	address.country	string	Default: 2 letter abbreviation (ISO 3166-1 alpha-2 code, currently always "US") Full country name (ISO 3166-1 English short name, currently always "United States of America")	Country of address	"US" "United States of America"
Birth Date	birthDate	string	Birth date	Default: yyyy-MM-dd Any combination of y(year), M(month), d(day), /(slash), and -(dash) Unix time (milliseconds)	"1989-08-01" "08/01/1989" "617947200000"
SSN (or ITIN)	ssn	string	9 digits (0-9)	Social Security Number (or Individual Taxpayer Identification Number)	"000456789"
Sex	sex	string	enum Possible values: "Male" "Female" "Non-Binary"	Sex	"Male"

Risk Signals Enable Multiple Addresses

We can return up to 3 most recent addresses for a user, if you have risk signals turned on. We order these addresses from most to least recent, as best as we're able to determine recency.

You can show the user a dropdown to select one of the addresses on the info confirmation step (see here on the User Experience page). We highly recommend this because it helps reduce the chance the user will need to manually enter an address, reducing friction and boosting conversion.

We Return ITINs When Applicable

If we find an ITIN but not an SSN for a user, we return the ITIN under the ssn key. ITINs and SSNs are both 9 digit numbers, and ITINs are easily distinguishable because they start with the number 9.

Government IDs

Beta

Coverage and Recency for Driver's License

Access to driver's license data varies state by state, so coverage and recency are substantially lower than for core data.

Output	Key	Type	Format(s)	Description	Example
Driver's License	driversLicense	object	Object with keys for all child credentials listed below	Driver's license	-
↳ Document Number	driversLicense.documentNumber	string	Format varies by state	Driver's license number	"A0000000"
↳ Issuance State	driversLicense.issuanceState	string	Default: Unix time (milliseconds) Any combination of y(year), M(month), d(day), /(slash), and -(dash)	Issuance state of driver's license	"CA" "California"
↳ Issuance Date	driversLicense.issuanceDate	string	Default: Unix time (milliseconds) Any combination of y(year), M(month), d(day), /(slash), and -(dash)	Issuance date of driver's license	"1596254400" "08/01/2020"
↳ Expiration Date	driversLicense.expirationDate	string	Default: Unix time (milliseconds) Any combination of y(year), M(month), d(day), /(slash), and -(dash)	Expiration date of of driver's license	"1911787200" "08/01/2030"
↳ Address	driversLicense.address	Default: object string	Default: Object with keys for all child credentials listed below Any combination of child shortenedCredentialTypes under address, , (comma), and - (dash)	Driver's license address	See 1ClickEntity example "Palo Alto, US-CA"
↳ ↳ Line 1	driversLicense.address.line1	string	Title Case	Line 1 of driver's license address	"5320 Newell Rd"
↳ ↳ Line 2	driversLicense.address.line2	string	Title Case	Line 2 of driver's license address	""
↳ ↳ City	driversLicense.address.city	string	Title Case	City of driver's license address	"Palo Alto"
↳ ↳ State	driversLicense.address.state	string	Default: 2 letter abbreviation (last 2 characters of ISO 3166-2 code for US state/territory) Full state/territory name (ISO 3166-2 subdivision name)	State of driver's license address	"CA" "California"
↳ ↳ ZIP Code	driversLicense.address.zipCode	string	ZIP Code (5 digits, 0-9)	ZIP Code of driver's license address	"94303"
↳ ↳ Country	driversLicense.address.country	string	Default: 2 letter abbreviation (ISO 3166-1 alpha-2 code, currently always "US") Full country name (ISO 3166-1 English short name, currently always "United States of America")	Country of driver's license address	"US" "United States of America"

More Government IDs are Coming Soon

We're working on adding support for new types of government ID. Let us know what would be most helpful for your use case! Email us at Support@Verified.inc and we'll prioritize accordingly.

Vehicles

Coming Soon

Employment

Coming Soon

Properties

Coming Soon

Metadata

A piece of metadata is additional data that's not a user's identity data — though it's often about that identity data.

Verification Method

Output	Key	Type	Applies To	Format	Description	Example
Verification Method	verificationMethod	enum Possible values: "credit_bureau" "data_bureau" "phone_carrier" "otp" "customer_otp" "self_attested" null	Identifiers Credentials	snake_case	How an identifier or credential was verified	"phone_carrier"

What Verification Method Means

verificationMethod describes how a credential was verified:

• "credit_bureau": verified via credit bureau records
• "data_bureau": verified via data bureau records
• "phone_carrier": verified via phone carrier records
• "otp": verified via an OTP (one time passcode)
• "customer_otp": verified via an OTP (one time passcode) by a Verified customer, not directly by Verified
• "self_attested": attested by the user themselves (not verified)
• null

You can build custom logic to handle credentials based on their verificationMethod, for example requiring additional verification if an important credential is "self_attested".

Risk Signals

Output	Key	Type	Applies To	Format	Description	Example
Risk Signals	riskSignals	object	Identifiers	Object with keys specified below in Risk Signals	Risk signals associated with the identifiers provided	See RiskSignals example

Risk signals metadata enhance 1-Click Signup's anti-fraud capabilities. They come with extra cost and can be disabled if desired, but we recommend that you use them to improve your ability to prevent fraud.

See also the RiskSignals type.

tip

You can configure which risk signals you receive using the risk signals brand setting:

Option	Description
On	Include risk signals
Off Not Recommended	Don't include risk signals

If risk signals are enabled, we will block users with an Overall Score greater than 600 and return a OCE017 error.

Definition of Risky Services

We and other companies assign specific services — called "risky services" — to interact with numbers that are considered more likely to be malicious. These risky services are not themselves risky. Rather, if the phone number you submit to our API has had a lot of interaction with them, that phone number is potentially risky.

Output	Key	Type	Format(s)	Description	Example
Overall	overall	object	Object with keys for all overall risk signals listed below	Overall risk signals, considering all identifiers provided	See RiskSignals example
↳ Score	overall.score	integer	Number from 0 (low risk) to 1000 (high risk)	Overall risk score, considering all identifiers provided. (If the score is over 600, Verified blocks the user and returns a OCE017 error.)	463
↳ Level	overall.level	enum Possible values: "low" "medium-low" "medium" "medium-high" "high"	kebab-case	Overall risk level, considering all identifiers provided. (This is a bucketing of the risk score, where 0-200 is "low", 201-400 is "medium-low", 401-600 is "medium", 601-800 is "medium-high", and 801-1000 is "high".)	"medium"
↳ Recommendation	overall.recommendation	enum Possible values: "allow" "flag" "block"	kebab-case	Overall risk recommendation, considering all identifiers provided. (This is a bucketing of the risk level, where "low" and "medium-low" are "allow", "medium" is "flag", and "medium-high" and "high" are "block".)	"flag"
↳ Reason Codes	overall.reasonCodes	enum[] Possible values: see Overall reason codes	"OCR" (for One Click Reason) followed by 5 digits (0-9)	Overall reason codes for risk score/level/recommendation, considering all identifiers provided	"OCR10021"
Phone	phone	object	Object with keys for all phone identifier risk signals listed below	Phone identifier risk signals	See RiskSignals example
↳ Carrier	phone.carrier	object	Object with keys for all carrier details listed below	Carrier information	"flag"
↳ ↳ ID	phone.carrier.id	integer	Any number of digits (0-9)	Carrier ID number	309
↳ ↳ Name	phone.carrier.name	string	"Title Case"	Carrier name	"AT&T Wireless"
↳ Reason Codes	phone.reasonCodes	enum[] Possible values: see Phone reason codes	"OCR" (for One Click Reason) followed by 5 digits (0-9)	Phone identifier reason codes for risk score/level/recommendation	"OCR20004"
Email	email	object	Object with keys for all email identifier risk signals listed below	Email identifier risk signals	See RiskSignals example
↳ Reason Codes	email.reasonCodes	enum[] Possible values: see Email reason codes	"OCR" (for One Click Reason) followed by 5 digits (0-9)	Email identifier reason codes for risk score/level/recommendation	"OCR60001"

Reason Codes

Overall

Phone

Email

1-Click Health

Health Insurance Plans

Coverage

We can source the data below for ~80% of US adults. Exact coverage depends on your user base.

See Coverage for more information.

Most Probable Plans are Listed First

If we return multiple health insurance plans for a user, they're ordered from most to least probable. All plans we return have a high probability of matching the user, since we filter out low probability ones.

A user may have multiple plans, for example if they have separate ones for medical, dental, or vision. We recommend that you let the user choose which plan they want to use, setting the first plan we return (which we deem most probable) as the default choice.

Payer IDs

1-Click Health can return many different IDs for a given payer:

• verifiedId: This ID identifies the payer within Verified but is not used in external systems. It never changes, so it can reliably used to identify the payer over time.
• ids[]: These IDs identify the payer in external systems, like healthcare clearing houses or the payer's own system. They may change over time.
  • ids[0]: This is considered the primary ID for the payer and is generally the ID the payer uses for itself. It may change over time.

Output	Key	Type	Format(s)	Description	Example
Member ID	memberId	string	Alphanumeric	Member ID for health insurance plan	"V000000000"
Payer	payer	object	Object with keys for all child credentials listed below	Payer for health insurance plan	{ "name": "Aviato Health Insurance Of California", "verifiedId": "V431835", "ids": ["0000A"] }
↳ Name	payer.name	string	Title Case	Name of payer for health insurance plan	"Aviato Health Insurance Of California"
↳ Verified ID	payer.verifiedId	string	V followed by 6 digits (0-9)	Verified ID (never changes) of payer for health insurance plan	"V431835"
↳ IDs	payer.ids	array	Array of strings	IDs (can change) of payer for health insurance plan — ids[0] is considered primary	["0000A"]
EDI 271	edi_271	string	X12 EDI 271 (Health Care Eligibility Benefit Response)	Address	See X12 EDI 271 examples

Metadata

A piece of metadata is additional data that's not a user's identity data — though it's often about that identity data.

Verification Method

Output	Key	Type	Format	Description	Example
Verification Method	verificationMethod	enum Possible values: "clearinghouse" "self_attested" null	snake_case	How a health insurance plan was verified	"clearinghouse"

What Verification Method Means

verificationMethod describes how a health insurance plan was verified:

• "clearinghouse": verified via clearinghouse records
• "self_attested": attested by the user themselves (not verified)
• null

You can build custom logic to handle health insurance plans based on their verificationMethod, for example applying additional validation if one is "self_attested".