Verified Users Overview

Learn about the components that make up the Verified Users solution

Prove Verified Users solution

Enterprises need a way to establish and verify customer identity for online transactions. The Verified Users solution provides a method to bind a phone number to an individual in the real world. With a name and a phone number, the Prove Verified Users solution asserts whether the name claimed by an individual is the one that owns that phone number.

Pain points

• Users Lack Trust in Digital Interactions. Impersonators, fraudsters, bots, scams, and inappropriate content are rampant, resulting in diminished trust that impacts platform reputation and engagement.
• Fraud and Abuse in Online Communities. Absence of strong, global identity verification using phone ownership manifests in fake profiles, scams, and fraud that harm legitimate interactions.
• Balancing Security With a Smooth User Experience. Repeated identity checks and lack of an adaptive approach that can serve all layers of verification and authentication creates user friction.

Value drivers

1. Single, Global Solution to Actively Protect Against Fraudsters and Bots. Continuous identity monitoring and verification make it difficult for malicious actors to operate, creating a more secure environment for legitimate users.
2. Enhanced Engagement, Trust and Loyalty. Verified Users instills confidence that users are interacting with genuine individuals, leading to increased trust and engagement on digital platforms and fostering loyalty in programs
3. Unlock Better Digital Experiences. Verified Users enables a balance between strong security and a smooth user experience by offering a highly accurate global verification product that is seamlessly integrated within user experience.

Input parameters

Field	Field Type	Verified Users	Description
phoneNumber	string	Required	The number of the mobile phone. Acceptable characters are: alphanumeric with symbols ’+’.
phoneNumber (date last verified)	string		The last date that a possession check was completed for a phone number. The format is YYYY-MM-DD. Acceptable characters are: numeric with symbol ’-‘
verificationType	string	"verifiedUser"	Prove offers different verification methods based on your use case and authorization level required. Available verification methods are: bot verifiedUsers prefill prefillForBusiness accountOpening identityResolution
firstName	string	Required	The verified first name of the user.
lastName	string	Required	The verified last name of the user.
emailAddress	string		The email address associated with the phone number.
email (date last verified)	string		The date the email address was last verified (e.g., 2023-01-01 ).
address	list object		A list of up to three verified addresses for the user, each containing street , street2 , city , region , and postalCode .
street	string		The street address of the individual.
extendedAddress (street2)	string		The apartment number or other extended address information.
city	string		The city of the individual.
region	string		The state or locality of the individual.
postalCode	string		The zip code of the individual. It can be either 5 digits (XXXXX) or ZIP+4 (XXXXX-XXXX).
dateOfbirth	string		The date of birth associated with the phone number.
nationalId	string		The user’s national ID, such as the full or last four digits of their SSN.
ipAddress	string		The IP address of the user.
userAgent	string		The user agent of the session of the individual.
avsResult	list object
identityID	string
correlationId	string		A unique ID that links all calls for the same flow. This is a crucial field to save for subsequent calls.
clientRequestId	string		Your unique request identifier.
clientCustomerId	string		A client-generated unique ID for a specific customer. This can be used by clients to link calls related to the same customer, across different requests or sessions.
clientHumanID	string		A client-generated unique ID for a specific customer that has been identity proofed. This can be used by clients to link calls related to the same customer, across different requests or sessions. The format of this ID is defined by the client - Prove recommends using a GUID, but any format can be accepted. Do not include personally identifiable information (PII) in this field.
businessName	string		The legal business name of the business attempting a verification.

Output parameters

Field	Field Type	Verified Users
success	string	✅
phoneNumber	string	✅
verifyResult (GFP Result)	string
assuranceLevel	string	✅
correlationId	string	✅
proveId	string	✅
proveKey	string	✅
identityId	string	✅
clientRequestID	string	✅
clientHumanID	string	✅
clientCustomerId	string	✅
identity	list of objects
firstName	string	✅
lastName	string	✅
nationalId	string
dateOfBirth	string
email(s)	list of objects
email1	string
email2	string
address(es)	list of objects
streetAddress	string
streetAddress2	string
city	string
region	string
zipCode	string
reasons	list of objects	✅
additionalIdentities	list of objects	✅
firstName	string	✅
lastName	string	✅
nationalId	string	✅
dateOfBirth	string
email	list of objects
email1	string
email2	string
address(es)	list of objects
streetAddress	string
streetAddress2	string
city	string
region	string
zipCode	string