Pain points

  • **Blocked Personalization and Cross-Selling: **With customer data spread across multiple, siloed accounts, businesses can’t get a complete picture of a single customer’s preferences and history. This makes it difficult to offer personalized product recommendations and identify opportunities for cross-selling.
  • **Ineffective Fraud Prevention: **Fragmented data prevents a business from identifying a single person across different services. This makes it challenging to detect fraudulent activity, as a bad actor can exploit these data silos to create multiple accounts and evade detection.
  • Poor Customer Experience: A customer like Gail Smith might have to manage multiple accounts across different brands within the same corporation. They may receive redundant or irrelevant communications and have to provide the same information repeatedly. This lack of a unified customer view leads to frustration and a disjointed experience.

Value drivers

  1. **Unified Customer View: **Prove creates a single, comprehensive view of each customer by connecting all their fragmented accounts and data points to a central “Prove ID.” This allows businesses to understand their customers as a single entity, rather than as multiple, disconnected profiles.
  2. **Enhanced Customer Experience and Marketing: **By linking all customer accounts, brands can deliver a more cohesive experience. This unified view enables personalized marketing and cross-selling, as businesses can leverage a complete picture of a customer’s history and preferences.
  3. **Secure and Privacy-Conscious Data Management: **The solution unifies customer identities without compromising privacy. Using “clean room” techniques, Prove links accounts and builds the identity graph without needing to access clients’ personally identifiable information (PII), ensuring data security and regulatory compliance.

Input parameters

1 of these is required:
  • National ID
  • Phone (And date of last authentication)
  • Email (and date of last authentication)
  • PII (2 each of)
    • First Name + Last Name + Address
    • First Name + Last Name + DOB
    • DOB + Address
All of these are optional (but help with resolution)
  • First Name
  • Last Name
  • Address
    • Address (street)
    • extendedAddress (street2)
    • City
    • Region
    • postalCode
  • Date of Birth
FieldField TypeIdentity ResolutionDescription
phoneNumberstringRequiredThe number of the mobile phone. Acceptable characters are: alphanumeric with symbols ’+’.
phoneNumber (date last verified)stringRequiredThe last date that a possession check was completed for a phone number. The format is YYYY-MM-DD. Acceptable characters are: numeric with symbol ’-‘
verificationTypestring"IdentityResolution"Prove offers different verification methods based on your use case and authorization level required. Available verification methods are: bot verifiedUsers prefill prefillForBusiness accountOpening identityResolution
firstNamestringRequiredThe verified first name of the user.
lastNamestringRequiredThe verified last name of the user.
emailAddressstringOptionalThe email address associated with the phone number.
email (date last verified)stringConditionalThe date the email address was last verified (e.g., 2023-01-01 ).
addresslist of objectsOptionalA list of up to three verified addresses for the user, each containing street , street2 , city , region , and postalCode .
address (street)stringOptionalThe street address of the individual.
extendedAddress (street2)stringOptionalThe apartment number or other extended address information.
citystringOptionalThe city of the individual.
regionstringOptionalThe state or locality of the individual.
postalCodestringOptionalThe zip code of the individual. It can be either 5 digits (XXXXX) or ZIP+4 (XXXXX-XXXX).
dateOfbirthstringOptionalThe date of birth associated with the phone number.
nationalIdstringOptionalThe user’s national ID, such as the full or last four digits of their SSN.
ipAddressstringOptionalThe IP address of the user.
userAgentstringThe user agent of the session of the individual.
avsResultlist of objects
identityIDstring
correlationIdstringA unique ID that links all calls for the same flow. **This is a crucial field to save for subsequent calls. **
clientRequestIdstringYour unique request identifier.
clientCustomerIdstringRequiredA 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.
clientHumanIDstringA 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.
proveKeySdkResponsePayloadstring
businessNamestringThe legal business name of the business attempting a verification.
AccountIDstringOptional
walletMetaData (only required if wallet is onboarding)stringConditional
Wallet : paymentTypes (ex: ACH, RTP, Fednow, Debit, Credit, Crypto)stringConditional
Wallet :createdDate (date the wallet was created for fraud analysis purposes)stringConditional
Wallet :locationRestrictions (regions where this wallet is able to be used)stringConditional
Wallet :industryRestrictions (if the wallet isn’t able to be used for gambling, alcohol, canabis, weapons, etc)stringConditional

Output parameters

FieldField TypeIdentity Resolution
successstring
phoneNumberstring
verifyResult (GFP Result)string
assuranceLevelstring
correlationIdstring
proveIdstring
proveKeystring
PFAstring
clientRequestIDstring
clientHumanIDstring
clientCustomerIdstring
identitylist of objects
firstNamestring
lastNamestring
nationalIdstring
dateOfBirthstring
email(s)list of objects
email1string
email2string
address(es)list of objects
streetAddressstring
streetAddress2string
citystring
regionstring
zipCodestring
reasonsobject