vendor_data and aggregate all linked sessions and transactions into a single profile.
What lives on a Business
| Category | Fields / objects |
|---|---|
| Identity | vendor_data, uuid, display_name, legal_name, registration_number, country_code |
| Status | ACTIVE, FLAGGED, BLOCKED |
| Session aggregates | session_count, approved_count, declined_count, in_review_count, features map |
| Activity | first_session_at, last_session_at, last_activity_at |
| Key people | Linked officers, directors, UBOs, beneficial owners (each may link to a User entity for KYC) |
| Documents | Certificates of incorporation, articles of association, shareholder registers, POA, financial statements, custom documents |
| AML | Company-level sanctions / PEP / adverse media screening results |
| Metadata | Arbitrary JSON for your own data |
When a Business is created
Automatically — from a Business Verification (KYB) session
When you create a Business Verification (KYB) session with a
vendor_data Didit has never seen, a Business entity is created in ACTIVE status and linked to that session.Explicitly — via POST /v3/businesses/create/
Pre-create the Business before running any Business Verification (KYB) session. Useful for seeding metadata or bulk-onboarding companies.
What you can do
| Operation | How |
|---|---|
| List businesses | GET /v3/businesses/ with filters |
| Get business | GET /v3/businesses/{vendor_data}/ |
| Create business | POST /v3/businesses/create/ |
| Update profile | PATCH /v3/businesses/{vendor_data}/ |
| Change status | PATCH /v3/businesses/{vendor_data}/update-status/ |
| Delete businesses | POST /v3/businesses/delete/ (batch) |
| Review KYB history | GET /v3/sessions?vendor_data=... |
| Review transactions | GET /v3/transactions/?vendor_data=... |
| Inspect key people | Via Business Verification (KYB) session decisions |
| Add to blocklist | Console + Lists API |
| Import / export | Console only (CSV) |
| Manage in console | Full UI walkthrough |
Business ↔ User relationships
A Business entity is rarely standalone. During KYB, Didit identifies every officer, director, UBO, and beneficial owner. Each of those people can be linked to a User entity for individual KYC: When one of the linked Users has a failed KYC or AML hit, it propagates to the Business’s risk profile. See Key people for the linkage pattern.Business vs business session
A business session is one KYB verification event. A Business entity is the durable profile that aggregates all sessions. A single Business can have many Business Verification (KYB) sessions — initial verification, resubmissions, periodic re-KYB. The Business’sfeatures map reflects the latest state across all sessions.
Next steps
Data model
Every field, type, and index.
Operations
Create, update, change status, delete.
KYB history
Every Business Verification (KYB) session tied to the business.
Key people
Officers, UBOs, and director linking.
Blocklist
Blocking businesses from transactions.
Console
Full Businesses UI walkthrough.