Skip to main content
This guide is for developers integrating onboarding fraud checks into their application. By the end of this guide, you will have configured FrankieOne OneSDK or the KYC API to collect fraud signals, and you will be able to review fraud check results in the FrankieOne Portal.

​
Getting Started with Onboarding Fraud

Check out the integration page for an overview of the implementation process.

​
1: Use OneSDK

To use device and behavioural biometric checks, your FrankieOne OneSDK integration must be configured to enable device data collection. Contact your Customer Success Manager to enable this. If you only want to use phone and email checks, you can skip the OneSDK integration.
1

Integrate OneSDK

Use OneSDK if you want to capture device signals from your user session, along with email and phone checks.
2

Configure the OneSDK for Fraud checks

Follow these steps to set up the OneSDK to collect device, email, and phone signals during your user’s onboarding.

​
2: Use the KYC API

If you only want to use phone and email checks, you can skip the OneSDK integration and use the FrankieOne KYC API to collect email and phone signals. The KYC API is also required for device and behavioral biometric checks.
1

Verify customers using FrankieOne KYC API

To use phone and email screening, you need to use the FrankieOne KYC API. Follow the steps to verify customers through our KYC API.
2

Add email and phone details as documents

When creating a verification session, include the user’s email and phone number as identity documents.

​
3: Review and Manage Fraud Checks results in the Portal

Review your fraud rules and check results alongside your KYC checks via the API or in the FrankieOne Portal. Use the information to make informed decisions about onboarding users.
Need Help?
For technical support or to enable fraud detection features, contact your FrankieOne Customer Success representative or visit our support portal.