Skip to main content

​
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. This reduces friction, improves CX, increases completion rates, and enhances security against fraud.

​
Concepts and definitions

To better understand the core components of the Prove Pre-Fill® solution, here are the key concepts and terms used on this page:
  • Mobile Auth℠ A technology that discovers and verifies a consumer’s phone number silently behind mobile network firewalls, providing protection against device-based fraud like cloning or emulation.
  • KYC (Know Your Customer) Add-On: A compliance layer that screens data against anti-money laundering (AML) lists and validates consumer information against more than 1 data source to support Customer Identification Programs (CIP).
  • Possession Check: The process of verifying that a user is in physical control of the given phone number, conducted via Mobile Auth, SMS OTP, or Instant Link.
  • Instant Link: A fortified link sent via SMS to desktop users to complete a possession check by leveraging the mobile network’s authentication.

​
Global availability

Prove Pre-Fill is available in the following regions:
  • The United States with its territories

​
Integration components

To implement, gather the following components:
  • Prove Platform server-side SDK: You can use one of the server-side SDKs on the back end of your web app. These are available in Go, Java, .NET, TypeScript, and JavaScript. The SDK handles OAuth 2.0 token management and simplifies the request and response handling. Using a different back end language? You can integrate using the API endpoints.
    The following endpoints apply to this flow:
  • Prove Platform client-side SDK: You must use the web, iOS, or Android client-side SDK on the front end of your web app. The client-side SDK handles all server calls for Mobile Auth, one-time password (OTP), and Instant Link possession checks and handles fallback features.
  • Web or Native Application: Your app Prove integrates into.

​
Prove Pre-Fill flow

Diagram illustrating the Prove Pre-Fill flow
Diagram illustrating the Prove Pre-Fill with Mobile Auth flow
  • The Start call generates the OAuth 2.0 token, initiates the session, and indicates whether the session is desktop or mobile.
  • The client-side SDK initiates the Prove possession check.
    • For Mobile
      • SMS OTP authenticates the customer by default.
      • If you enable Mobile Auth, the SDK completes silent authentication with fallback to SMS OTP to authenticate a customer.
    • For Desktop
      • The SDK sends a fortified link within an SMS message to authenticate the customer, known as Instant Link.
  • The Validate call indicates whether Prove can authenticate the phone number the customer uses to complete a possession check.
  • The Challenge call indicates whether Prove can authenticate the customer’s identity information with enough trust and assurance.
  • The Complete call indicates whether the customer’s identity information matches the particular mobile number in real time.
The /validate, /challenge, and /complete API responses includes the Global Fraud Policy (GFP) evaluation object, which provides authentication and identification results with specific failure reason codes.