How business verification (KYB) works

KYB verifies a company before you onboard it: registry lookup, ownership, officers, AML and documents in one workflow, with child sessions for its people.

Business verification (KYB) checks a company before you onboard it as a customer, vendor, or partner. You send a verification link, the company's representative fills it in, and you get back a structured decision with company data, ownership, and screening results.

#What a KYB session checks

A KYB session runs through several checks in one flow:

• Company registry lookup - confirms the company exists, is active, and matches the details provided.
• Key people - identifies UBOs (beneficial owners), shareholders, directors, and other officers.
• AML screening - screens both the company and every identified person against sanctions, PEP, and adverse media sources.
• Documents - collects supporting paperwork, like certificates of incorporation or shareholder registers, where your workflow requires them.

Each check has its own status, and the session as a whole is only approved once every required check passes. See what each session status means.

#Looking up a company

You don't have to collect company details by hand. In a hosted KYB session, the applicant searches by company name or registration number, and Didit queries official company registries to return a short list of matches. They pick the right one, and the available fields - legal name, registration number, status, registered address, and more - are pre-filled for confirmation. If a company isn't found in the registry, the flow falls back to manual entry.

You can also run the registry search and selection as standalone API calls if you want to show the match to your users before starting a full KYB session.

#Ownership and officers

Once the company is confirmed, Didit surfaces its beneficial owners, shareholders, and officers where the registry discloses them. Coverage varies by country - some registries publish full ownership structures, others only list officers and directors. When ownership data isn't available from the registry, you can collect it through documents, like a shareholder register, or have the business submit it directly in the flow.

Didit's business entity model covers companies, LLCs, funds, foundations, sole proprietorships, and trusts.

#Awaiting user is normal, not stuck

This is the most common KYB support question. Once the key-people step is submitted, the parent business session moves to Awaiting user and stays there until every required person has completed their own verification. The parent has child sessions, one per party, and it re-aggregates to a final status automatically when they're all terminal.

So when a KYB session sits at Awaiting user:

• Look at the child sessions, not the parent. That's where the work is.
• If a child session is resubmitted, the parent returns to Awaiting user until it completes.
• A declined registry check takes precedence over Awaiting user - the parent will decline without waiting.
• If a person can't or shouldn't finish, open the business verification's key people: Skip verification exempts that party so the business check can settle, and Regenerate verification sends them a new session when theirs was deleted.

#What it costs

KYB is paid from your plan credit or balance from the first session. A company with four screened officers costs meaningfully more than one with one - budget per structure, not per company. See what counts as a billable check.

#Getting started

Create a KYB workflow in the Business Console, choose which checks to include, then start a session from the console or your backend. Test it in a sandbox application first - the decline_kyb_registry_mismatch and review_kyb_registry_partial scenarios let you rehearse the failure paths. See the KYB quickstart for a full walkthrough.

#Related

• Registry coverage and ownership data
• Verifying the people behind a business
• Understanding AML screening results