The Prove connector streamlines customer onboarding by enhancing convenience for users and strengthening security for financial institutions. The connector leverages Prove’s API suite and Grand Central to provide an out-of-the-box installation for US financial institutions, delivering a frictionless user experience while maintaining high standards of security and compliance.The connector is available on Backbase Marketplace. You can obtain a Prove contract directly through Backbase for faster time to market.The connector’s features are particularly suitable for retail banking user journeys such as customer onboarding and loan origination.
Prove relies on trusted data sources to retrieve prospect’s personal information using either:
Prospect’s phone number + date of birth
Prospect’s phone number + last four digits of SSN
Mobile App Advantage: If using a mobile app, phone number entry is not necessary.Verified Information Returned (after successful OTP submission):
Full name
Date of birth
Mobile phone number
Current address
Previous address (if available)
Email address
SSN
Government ID (if available)
OTP Requirement: To prevent identity theft and ensure robust protection, the OTP step is mandatory. The connector integrates with the One-Time Password journey to facilitate this.Editable Data: Depending on business requirements, users can edit auto-filled data (configurable during implementation).
The Prove Trust Score API evaluates the trustworthiness of a prospect’s phone number in real-time.Trust Score Range: 0 to 1000
0-300: Low Trust
301-629: Medium Trust
630-1000: High Trust
The score is calculated based on Prove’s proprietary algorithms and internal logic, providing a reliable measure of phone number credibility and potential risk.Note: Prove’s trust score thresholds are general guidelines and do not represent Backbase’s recommendation. Clarify project requirements with the financial institution and implement custom logic if necessary.
Prove’s Verify API validates user’s personal information, assessing the likelihood that the user is the rightful owner of provided information.Verification Fields:
First name
Last name
Address
SSN (or last 4 digits of SSN)
Date of birth
Driver’s license number
Driver’s license state
Match Score Range: 0 to 100
0-69: Low reliability
70-100: High reliability
Scoring Methods: Depending on implementation, the API assigns either:
Match score (0-100)
Boolean value (pass/fail)
Custom Logic: Financial institutions define their own logic based on thresholds. For example, they can decide not to consider user information reliable if more than 2 fields score lower than 69.Note: Prove’s verification thresholds are general guidelines and do not represent Backbase’s recommendation. Clarify project requirements with the financial institution and implement custom logic if necessary.