Learn about the components that make up the Prove Pre-Fill® solution
Welcome to the Prove Platform documentation. This documentation applies if you use the client-side SDK and Prove Platform APIs.For access to classic documentation, contact support@prove.com or your Prove representative.
The Prove Pre-Fill solution streamlines online form completion by prefilling verified customer information like name and address, while also providing strong identity authentication to prevent fraud. It leads to faster onboarding and reduced friction for customers while maintaining a high level of security.
Mobile Auth Add-On
The Prove Mobile Auth solution discovers an authenticated phone number without customer interaction, verifying possession without customer interaction.Operating behind the mobile network firewalls, Mobile Auth is immune to modern-day security threats used for on-device manipulation, such as device flashing, emulation, device cloning, device and SDK spoofing AI-enhanced bots, and more, stopping fraud before it even starts.
KYC Add-On
The Know Your Customer (KYC) solution screens customer data against anti-money laundering (AML) lists to mitigate risks related to security, bribery, corruption, and ensure KYC compliance. Prove also supports your Customer Identification Program (CIP) by validating the customers verified data against more than one data source.
To implement, you’ll need the following components:
Prove Platform server-side SDK: You can use one of Prove’s server-side SDKs on the back end of your web application. These are available in Go, Java, .NET, TypeScript, and JavaScript. The SDK handles OAuth token management and simplifies the request and response handling.Using a different back end language? You can integrate using the API endpoints.
Prove Platform client-side SDK: You must use the web, iOS, or Android client-side SDK on the front end of your web application. The client-side SDK handles all server calls for Mobile Auth, one-time password (OTP), and Instant Link possession checks and handles fallback functionality.
Web or Native Application: Your application Prove integrates into.
The Start call generates the OAuth 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 Mobile Auth is enabled, 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 (SIM key) being used to complete a possession check.
The Challenge call indicates whether Prove can authenticate the customer’s identity information with enough trust and assurance. If so, this step passes back the customer’s verified identity information.
The Complete call indicates whether the customer’s identity information is associated with the particular mobile number in real time.