Skip to main content
Didit’s Business Verification (KYB) lets you verify companies and legal entities before onboarding them to your platform. The system automates company registry lookups, identifies beneficial owners and officers, screens all parties against AML watchlists, and collects supporting documents — all within a single workflow.

​
How it works

Create a business session

Start a business verification by creating a session with a KYB workflow. When the workflow type is KYB, Didit automatically creates a business session:
curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "your-kyb-workflow-id",
    "vendor_data": "company-123"
  }'
The session type is determined by the workflow — no extra fields needed. KYB workflows automatically create business sessions with business-specific features enabled.

Company registry lookup

Didit queries official company registries to retrieve:
DataDescription
Company nameLegal name as registered
Registration numberOfficial company registration number
CountryCountry of incorporation
StatusActive, dissolved, struck off, etc.
Company typeLtd, LLC, PLC, SA, GmbH, etc.
Incorporation dateDate the company was registered
Registered addressOfficial registered office address
Tax numberTax identification number (where available)
Registry data is cross-referenced with the information provided to detect inconsistencies.

Ownership & officer identification

The system automatically identifies:
  • Beneficial owners (UBOs) — individuals who ultimately own or control the company, with ownership percentages and voting rights
  • Directors & officers — company officers, their roles, appointment dates, and active status
  • Corporate shareholders — parent companies in the ownership chain
Each identified person can be linked to a KYC verification session for individual identity verification.

AML screening

All identified parties are automatically screened against global AML watchlists:
  • Company AML — screens the company entity against sanctions, adverse media, and regulatory enforcement lists
  • Person AML — screens each beneficial owner and officer individually
  • Uses the same two-score risk system (match score + risk score) as user verification

Document collection

Collect and verify supporting documents:
Document typeExamples
Certificate of incorporationCompany formation certificate
Articles of associationBylaws, memorandum of association
Proof of addressUtility bills, bank statements for the registered address
Shareholder registerOfficial register of shareholders
Financial statementsAnnual accounts, audit reports
Tax certificatesTax registration or compliance certificates
Custom documentsAny additional documents required by your compliance process
Analysts can request additional documents from the business during the review process.

Review and decide

The business session receives an overall status based on all checks:
StatusMeaning
ApprovedAll checks passed — company is verified
In ReviewOne or more checks require manual review
DeclinedA critical check failed (e.g., dissolved company, sanctioned entity)
Analysts can review all collected data in the Business Console, add comments, request additional documents, and make a final decision.

​
Key capabilities

CapabilityDescription
Automated registry lookupsQuery official company registries in supported countries
UBO identificationAutomatically extract beneficial ownership structures with percentages
Officer screeningIdentify and verify directors, secretaries, and other officers
Company AMLScreen the company entity against sanctions and watchlists
Person AMLScreen all identified UBOs and officers individually
KYC linkingLink each identified person to a KYC session for identity verification
Document collectionStructured document requests with upload tracking
OCR cross-checkingExtract data from uploaded documents and cross-reference with registry data
Risk assessmentOverall risk level based on company status, AML results, and ownership complexity
WebhooksReceive status.updated and data.updated events for business sessions

​
Business sessions vs. user sessions

FeatureUser sessionBusiness session
TargetIndividual personCompany or legal entity
Session kinduser (default)business
Core checksID, liveness, face match, AMLRegistry lookup, UBO, officers, company AML
Additional checksPhone, email, proof of address, NFCDocument collection, person AML, KYC linking
Webhook payloadsStandard session eventsInclude session_kind: "business" and business_session_id

​
Next steps

Company data

Registry lookups, company status, and data cross-referencing.

Ownership structure

UBO identification, corporate shareholders, and ownership chains.

Officers & directors

Director identification, roles, and KYC linking.

AML screening

Company and person-level AML checks.

Documents

Document collection, requests, and OCR verification.

Console guide

Managing business verifications in the Business Console.