Skip to main content
Business verification includes structured document collection to validate company information beyond what’s available in registries.

Pricing

KYB document collection costs $0.20 per workflow step, independent of how many documents are uploaded in that step. Re-uploading a document in the same step does not add another fee; a separate document-collection step has its own charge.

Document groups

Documents are organized into four structured groups, each representing a category of evidence needed for business verification, plus a catch-all group for anything Didit cannot classify: Each group tracks its own progress with per-group counters: total, approved, pending, declined, in_review, other and missing. The business session’s overall documents status aggregates across all groups.

Document types

Document workflow

Automatic requests

Based on your workflow configuration, Didit automatically identifies which documents are needed for the business verification. Required document types are presented to the business for upload.

Upload

Documents are uploaded through the hosted verification flow, via the Business Console, or from your own front end with the upload documents endpoint. Accepted formats are PDF, JPG, JPEG, PNG, TIFF and WebP, or a ZIP archive of them. PDFs can be up to 50 MB and photos up to 6 MB before compression. For a password-protected PDF, send the password in document_passwords when you upload through the API.

OCR extraction

Didit extracts structured data from uploaded documents using OCR:
  • Company name and registration number from certificates
  • Address data from utility bills
  • Financial figures from statements
  • Names and roles from shareholder registers

Cross-referencing

Extracted data is cross-referenced against:
  • Registry data from the company lookup
  • Information provided at session creation
  • Data from other uploaded documents
Inconsistencies are flagged for analyst review.

Review

Analysts review uploaded documents in the console, verify their authenticity, and approve or reject each document individually.

Analyst document requests

During the review process, analysts can request additional documents:
  1. Navigate to the business session in the console
  2. Click Request document and specify the document type and description
  3. The business is notified and can upload the requested document
  4. The document appears in the session with a Requested status until uploaded
This allows analysts to gather additional evidence without rejecting the entire business session.

Document statuses

Each document and the aggregate document_verifications[] check use the standard KYB feature status set:

Cross-check results

When a document is processed, Didit cross-references the OCR-extracted data against the user-provided data submitted in the Key People flow (and any data confirmed during registry review) plus other uploaded documents. The cross-check produces structured results: Cross-check results are displayed in the Business Console alongside the document preview, giving analysts a clear view of what matches and what needs attention.

Retrieving documents via API

Documents are attached to the Business Verification (KYB) session. Fetch them via the session decision:
The response includes a document_verifications[] array — each item has a status, node_id, items[] (each with a signed file_url, a document_group, a document_subtype and an OCR extract), groups, and required_groups. See response schema for the full structure.

Next steps

Response schema

Where documents appear in the payload.

Business console

Reviewing documents as an analyst.
Last modified on October 31, 2026