OneSDK Fraud Detection & Prevention

OneSDK’s Fraud Detection system evaluates potential fraud risks by analyzing device characteristics and form-filling behavior during user onboarding. This enables real-time risk assessment to help you make informed decisions about user registration.

Account Configuration Required

To use device characteristics and behavioral biometrics, your account must be configured by FrankieOne. Contact your Customer Success representative to enable these features.

Implementation Overview

Fraud Detection Implementation Flow

Integration Steps

1

Initialize Server-Side Session

Your server needs to create a temporary session before serving the frontend.

1// Fetch authentication token from backend
2const tokenResultRaw = await fetch('https://backend.kycaml.uat.frankiefinancial.io/auth/v2/machine-session', {
3method: 'POST',
4headers: {
5 // Create Basic Auth header using customer ID and API key
6 authorization: 'machine ' + btoa(`${CUSTOMER_ID}:${API_KEY}`),
7 'Content-Type': 'application/json',
8},
9body: JSON.stringify({
10 permissions: {
11 preset: 'one-sdk',
12 // Customer reference options: pass either unique customer reference or existing EntityID
13 reference: "customer-reference", // Custom customer reference
14 entityId: "abc-def-ghi" // Existing entity ID (if exists)
15 },
16}),
17});
2

Initialize OneSDK with Device Characteristics module

Set up OneSDK with the provided session data.

1const oneSdk = await OneSDK({
2 session: tokenResultRaw, // Pass authentication token
3 mode: "production", // Set to production environment
4 recipe: {
5 ocr: {
6 maxDocumentCount: 3, // Maximum allowed documents for OCR
7 },
8 },
9});
10
11// Initialize device component for registration
12const device = oneSdk.component("device", {
13 activityType: "REGISTRATION", // Set activity type
14 sessionId: "YOUR_CUSTOM_SESSION_KEY", // Custom session identifier
15});
16
17// Start device monitoring
18device.start();
3

Retrieve Fraud Indicators

You can check entity’s fraud indicator from Portal, or via KYC Entity Risk endpoint, read more here.

Using Sardine

Initialization

Once you have initialized OneSDK instance, you can create a device check component

Setting up Device Check
1// Initialize device check component with registration activity
2const device = oneSdk.component("device", {
3 activityType: "REGISTRATION",
4 sessionId: `session-${new Date().toISOString()}`, // Generate unique session ID using timestamp
5});
6
7// Begin device data collection
8device.start();

Capture Phone and Email for Fraud check

Using Individual’s module to capture phone number and email, OneSDK will also allow you to run Fraud checks on these details.

Event System

Best Practices

Risk Level Handling

Low Risk

Standard processing

  • Continue with normal flow
  • Regular verification
Medium Risk

Enhanced verification

  • Additional identity checks
  • Manual review option
High Risk

Restricted processing

  • Block registration
  • Flag for review
Need Help?

For technical support or to enable fraud detection features, contact your FrankieOne Customer Success representative or visit our support portal.

Built with