Skip to main content
A User entity represents a single individual (your customer, end-user, or applicant) across every verification, transaction, and compliance interaction they have with your platform on Didit. Once a User exists, all activity tied to the same vendor_data flows into the same profile — you get a single pane of glass for identity, risk, and compliance for each person.

​
What lives on a User

See the full User data model for types, indexes, and edge cases.

​
When a User is created

1

Automatically — on first session with a new vendor_data

The typical case. You call POST /v3/session/ with a vendor_data value Didit has never seen. A User entity is created in ACTIVE status and linked to that session.
2

Explicitly — via POST /v3/users/create/

You pre-create the User before any session runs. Useful for seeding metadata, setting initial status, or bulk-onboarding customers from an existing database.
3

From the console

A compliance operator creates the User from the Users page — for example, when onboarding a manually verified customer.

​
What you can do

​
Users and Businesses

A single User can be linked to one or more Businesses — for example, when the same person is a director of one company and a UBO of another. Didit preserves these links automatically when KYB identifies people from company registries.

​
User ↔ session relationship

The User aggregates the latest state of each feature across all sessions. A failed aml check on the most recent session will show up in the User’s features.aml field even if older sessions approved.

​
Next steps

Data model

Every field, type, and index.

Operations

Create, update, change status, delete.

Faces & biometrics

Attach a face for search and blocklisting.

Blocklist

How blocklisting works for users.

KYC history

Every session tied to the user.

Console

Full Users UI walkthrough.