> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Verification Console

> Review KYB sessions in the Business Console: company data, ownership, AML results, documents, key people. Pay-per-call $2.00 KYB, no contracts.

Business verification sessions are managed in the Business Console alongside user verifications, with KYB-specific sections for registry data, documents, and key people. This page walks through the session detail view.

## Navigating to a business session

From the Business Console, open *Businesses → \[business]* to see all sessions for that business, or open the session directly from the Sessions list. Business sessions show a **business** badge next to the session number so they're easy to spot in a mixed list.

## Session detail — sections

A KYB session detail page shows these sections. Which sections appear depends on the features your workflow enabled.

### Overview

Session summary: status, workflow used, `vendor_data`, session number, creation/expiry timestamps, per-feature status chips (KYB Registry, KYB Company AML, KYB Documents, KYB Key People, and any shared features like AML, Phone, Email, Questionnaires, Device & IP Analysis).

### KYB Registry

The company block extracted from the registry (or submitted manually when not found):

* **Registry data** — registry-returned fields: legal name, registration number, incorporation date, company type, registered address, tax number, industries, accounts / filing dates.
* **User-provided / confirmed data** — what the end user confirmed or edited in the hosted flow, shown side-by-side with the registry data.
* **Data source indicator** — `is_from_registry`, `fetch_status`, `verification_status`, `confirmed_by_user_at`.
* **Financial summary** — where the registry publishes it.
* **Risk level** — composite signal (`LOW`, `MEDIUM`, `HIGH`).

Actions: confirm / edit canonical fields, view the raw registry payload for audit, request the end user to re-confirm.

### KYB Documents

Documents grouped by document type group — Legal presence, Company details, Ownership structure, Representatives authorization.

* **Per-group progress** — approved / pending / missing counts per group, and which groups are required.
* **Document items** — each uploaded document with signed preview URL, OCR extract, cross-check result against the user-provided data.
* **Cross-check diff** — per-field comparison between the OCR data and the canonical company data.

Actions: approve or decline individual documents, request a resubmission, request an additional document, download.

### KYB Key People

The key-people list — UBOs, shareholders, directors, representatives, and other officer roles — shown **side-by-side** in two buckets:

* **Registry** — parties extracted from the registry check, grouped by role category.
* **Submitted** — parties the business admin added during the Key People flow (source = USER).

Each person shows: name, entity type (person or company), role(s) with ownership / voting percentages where relevant, KYC status of the linked child session (`Approved` / `Declined` / `Pending`), AML status, and a link to open the child KYC or KYB sub-session.

The `ubo_kyc_summary` card rolls up UBO KYC progress — total / approved / flagged / pending — at the top of the section.

Actions: open a child session, mark a person as skipped (when the role allows), request resubmission of a specific child session, view the child AML hits.

### AML

Company-level AML screening. For each hit: match score, risk score, category (sanctions, PEP, adverse media, criminal, enforcement), watchlist source, screened name. Per-hit actions: mark false positive, confirm, add note.

Person-level AML hits for key people also surface here, each linked back to the relevant key person.

### Device & IP Analysis

Submitter IP, country, ASN, data-center / VPN flags, device fingerprint when collected.

### Phone / Email / Questionnaires

Appear only when the workflow collects them. Same feature-detail surface as on a KYC session.

### Events

Chronological log of everything that happened on the session — status changes, feature completions, analyst actions, webhook deliveries. Filter by event type and date.

### Webhooks

History of webhook deliveries for this session with response codes, retry counts, and raw payloads. You can resend any delivery.

### Chat

Internal analyst notes with `@`-mentions. Not visible to the end user.

## Tag management

Tag any business session for categorisation and later filtering. Tags appear as chips on the Overview and on the Sessions list — useful for tracking risk tiers, review stages, partner source, or any custom axis.

## Reviewer actions

From any section, an analyst with the right role can:

* **Approve** the session when all checks pass.
* **Decline** the session if a critical issue stands.
* **Request more information** — force a resubmission on specific documents or child KYC sessions.
* **Override a feature status** — manually set a feature to `APPROVED` / `DECLINED` / `IN_REVIEW` with a note.
* **Add a chat note** — visible to teammates, not to the user.
* **Tag** the session for downstream filtering.
* **View the full audit trail** of every action on the Events tab.

See [Roles & permissions](/console/roles-permissions) for the matrix of who can do what.

## Business profiles

Business profiles give you the durable cross-session view of each company. From *Businesses* you can search, filter, tag, bulk-update status, export CSV, and import in bulk. See [Business profiles](/business-verification/business-profiles) for details.

## Next steps

<CardGroup cols={3}>
  <Card title="Business entities" icon="building" href="/entities/businesses/overview">
    The broader Business entity model across sessions.
  </Card>

  <Card title="Manual review" icon="gavel" href="/console/manual-review">
    Deep reviewer walkthroughs across KYB and KYC.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/console/workflows">
    Configuring KYB workflows.
  </Card>
</CardGroup>
