Overview

This article explains how Begini fits into your application and operational workflow.

At a high level, Begini allows you to create an assessment session, send a user through an assessment journey, process behavioural data in real time, and then return results for review or decisioning.

The purpose of this guide is to give you a clear end-to-end view of the Begini flow before moving into deeper technical setup.

The Begini flow

A typical Begini integration follows four core steps:

1. An assessment session is created
2. The user completes the assessment
3. Begini processes the behavioural data
4. Results are returned and made available for use

This flow can be used in a number of ways depending on how you want to deploy Begini, from a simple no-code setup through to a fully integrated API-based implementation.

Integration options

Begini supports more than one integration path depending on how quickly you want to get started and how deeply you want to embed the assessment into your own user journey.

Option 1 — No-code using the Link Generator

The fastest way to get started is by using the Link Generator in Beacon.

This allows you to:

• Select a deployment
• Generate assessment links in bulk
• Download and distribute those links to users
• Start collecting completed assessments without writing code

This option is ideal for:

• early testing
• pilot deployments
• manual or semi-manual rollout models

Option 2 — API-based integration

For a more embedded experience, Begini can be integrated directly into your application.

This allows you to:

• Create assessment sessions programmatically
• Trigger assessments as part of your own application journey
• Receive results automatically through your preferred integration model
• Build Begini into a live credit or onboarding workflow

This option is typically used when you want a more automated and scalable deployment.

How results are delivered

Once an assessment is completed, Begini processes the submitted behavioural data and generates the relevant outputs.

Results can then be accessed in several ways depending on your setup.

Beacon dashboard

All completed assessments can be reviewed in Beacon, where your team can monitor results and review key outputs.

API

If you are using a direct integration, results can be returned into your own workflow through the API.

Webhooks

For real-time delivery, Begini can also send events and results to your configured webhook endpoints.

This is typically used when you want to automate downstream actions or decisioning as soon as an assessment is completed.

Key concepts

There are a few core concepts that are important to understand before implementing Begini.

Assessment Session

An assessment session is the individual instance of an assessment created for a user. Each session is unique and represents a single journey through the Begini assessment flow.

Integration ID

The Integration ID is used to identify the specific Begini deployment or configuration being used. This ensures the correct assessment setup is applied when a session is created.

Unique ID

The Unique ID is used to identify the end user in your own system. This allows you to match a Begini result back to the correct user, customer or application record internally.

These identifiers are important because they help connect the Begini journey to your own operational and decisioning processes.

Where each component fits

Begini includes several components that work together, depending on the products you are using.

Psychometric Assessment

This is the core Begini product and the most common starting point. It captures behavioural signals through a mobile-first assessment journey and generates a risk score and supporting outputs.

Device Data SDKs

The Device Data SDKs are a separate product layer that can be added where deeper device intelligence and fraud-related signals are required. These typically involve a more technical integration and are not required for an initial psychometric deployment.

Webhooks

Webhooks are used when results or events need to be delivered in real time to your own systems.

Beacon

Beacon is the dashboard used to configure deployments, generate links, review results and monitor usage.

Typical integration patterns

Begini can be introduced at different stages of a customer journey depending on your product and operating model.

Common patterns include:

• Before a lending decision is made
• During digital onboarding
• As part of an application flow
• As an additional layer of risk insight where traditional data is limited

The right approach depends on how you want Begini data to support your internal process.

Choosing the right starting point

For most teams, the easiest starting point is the no-code route using the Link Generator in Beacon.

This allows you to validate the assessment journey, review outputs and understand how Begini fits into your workflow before moving into a deeper integration.

Once that flow is proven, teams typically move on to:

• API-based session creation
• Webhooks for real-time processing
• Production deployment and operational monitoring

Next steps

Once you understand the overall Begini flow, the next step is to decide how you want to get started.

For a simple first deployment, see:

• Quick Start Guide

For implementation planning, see:

• Integration ID & Unique ID Guide
• Webhooks Overview
• Security Overview
• Go Live Checklist