Behavioural Biometrics

How to implement Behavioural Biometrics solution?

To collect user device and behavior data, you will need to integrate the Bureau SDK into your mobile or web application. This data can be used to identify suspicious devices and prevent fraud.

The implementation process is simple and can be started as soon as you have signed up for a Bureau account and obtained your Client ID or Credential ID. Contact us at [email protected] to sign-up for an account.


Getting Started

Bureau SDK collects and provides insights for each session. A session is defined as a sequence of interactions with your app or website by a single user. Each session has two types of insights: a unique device fingerprint for that session and signals that measure the risk level of the session.

For the best results, we recommend integrating our solution at each major milestone throughout your user journey, not just at the beginning. The more information we have, the better, as it helps us refine our risk score.

The common milestones include login, registration, changing password, adding more user, application completion, KYC, payment, withdrawal, address change, nominee addition, refund request, chargeback request.

The Bureau's Device Intelligence Solution implementation requires a two-step process for both mobile and web.

  1. SDK integration: This involves adding the SDK code to your app or website
    1. Android SDK
    2. Web SDK
  2. Backend API integration: This involves connecting your app or website to the Bureau's backend API
    1. Behavioural Biometrics API Documentation

Bureau Behavioural Biometrics SDK Glossary

  1. Client ID or Credential ID
    1. The Client ID or Credential ID is a unique identifier that Bureau provides to you to interact with our system programmatically. This ID is required for all API calls to the Bureau SDK.
  2. Session ID
    1. The Session ID is a unique identifier that you must set for each session. This identifier is used to track the session and to fetch the insights for that session for example - app launch, app signup or login flow
  3. User ID
    1. The User ID is a unique identifier that you must set for each user. This identifier is used to track the user across sessions and to correlate the insights for different sessions. For example - Hashed SSN/PAN/Other government identity number, mobile number and so on.
  4. Flow
    1. This describe the nature of the risky activity that is being cosnidered LOGIN_AUTHENTICATION
  5. Fingerprint
    1. The fingerprint is a unique identifier that is generated by Bureau based on different device parameters. This identifier is used to uniquely identify the device and to generate the insights for the session.
  6. init ()
    1. This function initiates the process of collecting data from the user's device / browser for further processing by our systems
  7. startSession ()
    1. After the SDK initialization, this starts collecting the user behavioral data like keystroke data, click data, motion data and sensor data. Using these data points, the user similarity behavior, behavioral anomaly score and bot prediction score are calculated. To train the model on each user, six sessions are needed.
  8. stopSession ()
    1. This stops collecting the behavioral data.
  9. submit ()
    1. This function transfers the collected datapoints from the user's device / browser to our systems for further processing