Skip to main content
This tutorial will walk through how to start integrating FrankieOne’s fraud solutions, Onboarding Fraud Checks.

​
Prerequisites

Workflow configured for fraud checks
Risk rules set up in the rule engine
Account configuration requiredDevice and Behavioural intelligence must be configured for your account by FrankieOne. Please speak with your Customer Success representative if you are interested in this feature.

​
Integration Overview

Product FunctionPhone, Email, Device, Location Checks (recommended)Phone and Email Only Checks
Onboarding Fraud (Data Collection)OneSDKKYC API
Review and ManageFrankieOne Portal, KYC APIFrankieOne Portal, KYC API

​
Limitation

  • OneSDK requirement: To use Device and Location signals, you must integrate OneSDK. Without it, only email and phone signals can be used.
  • Single Provider per Step: The fraud step is designed to support only one provider at a time. If you need to use different providers for different signals, you must configure separate fraud steps.
  • Supported Connectors: To find out which connectors are available for the v2 fraud step, please consult your implementation support manager.

​
Getting Started with Onboarding Fraud

​
1: Use OneSDK

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

Use the FrankieOne KYC API to collect email and phone signals. An extensive guide can be found here.
1

Verify customers using FrankieOne KYC API

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

Register a session for device & IP checks (OneSDK)

If you only want to use phone and email checks, you can skip this part. This step is only necessary if you require device and IP checks (integrated with OneSDK). Make a server-side call to register the session against the entity.
3

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 .