> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started

> Learn how to evaluate customer activity for fraud.

> **FrankieOne Fraud v2 is now available.** This page documents v1 of the Fraud and Activity Monitoring product. For the latest documentation, see [Fraud and Transaction Monitoring (v2)](/docs/fraud-and-transaction-monitoring-introduction).

This tutorial will walk through how to start integrating FrankieOne's fraud solutions: Onboarding Fraud Checks and Activity Monitoring.

## Prerequisites

Recipe configured for fraud

<div><Icon icon="check" /> Recipe configured for fraud — see [What is a recipe?](/docs/v1/portal/getting-started/recipe/overview)</div>

<div><Icon icon="check" /> Risk rules set up in the rule engine — see [Creating rules](/docs/v1/fraud-activity-monitoring/fraud-features#creating-rules)</div>

<Callout icon="thumbtack" iconType="regular" color="#1A6CFF">
  ##### Account configuration required

  Device activity, behavioral biometrics and activity monitoring must be configured for your account by FrankieOne. Please speak with your Customer Success Manager if you are interested in this feature.
</Callout>

## Integration Overview

To use Device and Location signals, you must integrate OneSDK.

| Product             | Phone, Email, Device, Location      | Phone and Email Only |
| :------------------ | :---------------------------------- | :------------------- |
| Onboarding Fraud    | OneSDK                              | KYC API              |
| Activity Monitoring | OneSDK + Transaction Monitoring API | --                   |

## Getting Started with Onboarding Fraud

### Option 1: Using OneSDK (recommended)

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

#### Configure the OneSDK for Fraud checks

Follow [these steps](/docs/v1/onesdk/oneSDK/implementation-guide/module/fraud) to set up the OneSDK to collect device, email, and phone signals during your user's onboarding.

### Option 2: Using the KYC API

Use API only if you will only be using email and phone checks. Device signals require the OneSDK.

#### 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](/docs/v1/kyc/verify-customers) through our KYC API.

#### Add email and phone details as documents

To make an email address or phone details processable or "checkable", the email address or the phone details must be added as a document, either within an entity or on its own. To do so, use the links below:

* [Add an email address](/docs/v1/api/guide-to-the-api/data-types/adding-an-email-address)
* [Add phone details](/docs/v1/api/guide-to-the-api/data-types/adding-a-mobile-phone-number)

## Getting Started with Activity Monitoring

### Using OneSDK and the Transaction Monitoring API

We recommend using both the OneSDK and the Transaction Monitoring API so you can measure email, phone, and device signals for all user activities.

#### Configure the OneSDK for Fraud checks

Follow [these steps](/docs/v1/onesdk/oneSDK/implementation-guide/module/fraud) to set up the OneSDK to collect device signals during your user's session.

#### Initiate a transaction request

Include the customerReference and sessionKey from the OneSDK session in your transaction request payload. These values link the activity to the device and behavioural signals captured during the session. See the [Assess Transaction API](/api-reference/transactions/check-a-transactions-risk) for the full request schema.