Prove Pre-Fill for Consumers solution
The Prove Pre-Fill for Consumers solution streamlines online account creation by automatically filling forms with bank-grade verified consumer data via phone number, reducing friction, improving CX, increasing completion rates, and enhancing security against fraud.Pain points
- High Friction and Abandonment Rates: Digital onboarding processes often suffer from high friction and abandonment rates due to lengthy forms and complex steps. Simplifying workflows and optimizing design is crucial for a seamless user experience.
- Growing Fraud Losses: Fraud vulnerabilities during account opening are a major concern. Robust security measures like advanced identity verification and multi-factor authentication are essential to mitigate risks.
- Poor Data Quality: Manual data entry leads to inefficiencies, delays, and errors. Automating these processes streamlines workflows, reduces costs, and improves the customer experience.
Value drivers
- Streamlined Onboarding with Reduced Friction and Faster Completion: The solution significantly simplifies the user onboarding process, eliminating complexities and streamlining steps for a frictionless experience. By minimizing manual intervention and automating key verification processes, users can complete onboarding swiftly. This leads to a substantial reduction in onboarding time, enhancing efficiency and user satisfaction. The faster completion rate contributes to quicker service access and increased initial engagement, maximizing early user adoption and value realization.
- Enhanced Security and Fraud Prevention: Security is a paramount concern, and this solution integrates robust measures to protect user data and prevent fraudulent activities. Advanced authentication protocols, coupled with real-time risk assessment and identity verification, create a secure environment. The system proactively identifies and mitigates potential threats, reducing the risk of unauthorized access and fraud. This comprehensive security framework safeguards sensitive information, builds user trust, and ensures regulatory compliance, establishing a reliable and secure platform.
- Improved Customer Experience and Satisfaction: The overall customer experience is greatly improved through the solution’s user-centric design and intuitive interface. By providing a seamless and efficient process, users encounter fewer roadblocks and enjoy a positive interaction. The reduced wait times, automated verifications, and secure environment contribute to increased satisfaction. Enhanced customer satisfaction translates to stronger customer loyalty, positive referrals, and sustained business growth. A superior customer experience ensures long-term engagement and reinforces the platform’s value proposition.
Input parameters
| Field | Field Type | Pre-Fill | 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 | prefill | 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 | The verified first name of the user. | |
lastName | string | The verified last name of the user. | |
emailAddress | string | Required | 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 of objects | ||
address | string | The street address of the individual. | |
extendedAddress | 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 of objects | ||
identityID | string | ||
provePhoneAlias | 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. | |
authToken | string | A bearer token for use by the Prove client SDK. |
Output parameters
| Field | Field Type | Description | Pre-Fill |
|---|---|---|---|
success | boolean | True if the API call was successful. | ✅ |
phoneNumber | string | The number of the mobile phone. | ✅ |
verifyResult | string | The result of the verification according to the Global Fraud Policy. | ✅ |
assuranceLevel | string | Prove’s tiered confidence metric, ranging from -1 to 3, that dynamically adapts to user behavior and various authentication keys. It allows for adaptive security policies, meaning you can require different levels of verification for different types of transactions. This is a key attribute of the Prove Key. Possible values are: “AL-1”, “AL0”, “AL1”, “AL2”, “AL3”. | ✅ |
correlationId | string | The unique ID that Prove generates for the flow. To continue the flow, the field will also be used for each of the subsequent API calls in the same flow - it cannot be reused outside of a single flow. | ✅ |
proveId | string | A globally unique identifier in Prove language that represents a user (or business). If provided to a customer, this ID is “salted” to make it specific to that customer before being shared. It links a user’s keys to their National ID and is the center of our universe linking identity data and events throughout our fabric. | ✅ |
proveKey | string | ✅ | |
identityId | string | ✅ | |
clientRequestID | string | ✅ | |
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. | ✅ |
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. | ✅ |
identity | list of objects | ✅ | |
firstName | string | The first name of the individual. | ✅ |
lastName | string | The last name of the individual. | ✅ |
nationalId | string | The national identity number of the individual. | ✅ |
dateOfBirth | string | The date of birth of the individual in one of these formats: YYYY-MM-DD, YYYY-MM, or MM-DD. Acceptable characters are: numeric with symbol ’-’. | ✅ |
email(s) | list of objects | ✅ | |
email1 | string | The email address of the customer. Acceptable characters are: alphanumeric with symbols ’@.+’. | ✅ |
email2 | string | The email address of the customer. Acceptable characters are: alphanumeric with symbols ’@.+’. | ✅ |
address | list of objects | ✅ | |
address | string | The street address of the individual. | ✅ |
extendedAddress | 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. | ✅ |
zipCode | string | The zip code of the individual. It can be either 5 digits (XXXXX) or ZIP+4 (XXXXX-XXXX). | ✅ |
business(es) | list of objects | ||
businessName | string | The legal business name. | |
businessAddress | list of objects | ||
address | string | The street address of the individual. | |
extendedAddress | 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. | |
zipCode | string | The zip code of the individual. It can be either 5 digits (XXXXX) or ZIP+4 (XXXXX-XXXX). | |
tradeName | string | The doing business as (DBA) name of the legal business entity. | |
taxId | string | The Employee identification Number or Tax Identification Number of the business. | |
relatedPersons | list of objects | ||
firstName | string | The first name of the individual. | |
middlesName | string | The middle name of the individual. | |
lastName | string | The last name of the individual. | |
title | string | The title of the related person. | |
registrationFiling | string | ||
date | string | The date of the registration filing. | |
registrationType | string | The type of registration. | |
region | string | The state or locality of the business registration. | |
identityId | string | A unique ID that Prove generates to refer to a specific identity. | |
verifyResult | string | The result of the Verify process. Possible values are success, pending, and failed. If the Verify result is pending, clients will need to call the Verify Status API to get a result. | |
possessionResult | string | The result of the possession check. Possible values are pending and not_applicable, based on the possessionType passed in the input. Clients will have to call the Verify Status API to get a result if possessionResult=pending. | |
success | string | The result of the combination of verifyResult and possessionResult. Possible values are true, pending, and false. The value will be pending until the results of both Verify and Possession are returned or one of them fails, blocking the other. | |
allowOTPRetry | boolean | If true, the customer can re-enter the OTP up to three times. Code must also be implemented. See client-side SDK guide for more details. |