Skip to main content
When a business verification session starts, Didit queries official company registries to retrieve and validate company information. This automated lookup provides the foundation for the entire business verification process.

Registry lookup

Didit connects to company registries in supported countries to retrieve official data. In the hosted flow the user selects the country of incorporation and fills in the company name, the registration number, or both — at least one is required. Registration numbers are normalized where registries require it (for example, UK company numbers are zero-padded to eight digits), and when both identifiers are provided the registry lookup combines them.

Pre-filling the search with expected_details

If you already know the company, pass expected_details (company_name, registry_country, registration_number) when creating the session. The hosted flow pre-selects and locks the country (and the state for state-level registries like US-CA), pre-fills the matching search fields, and runs the asserted search automatically — the user lands directly on their company’s result. Both fields stay editable so the user can correct a wrong assertion. Prefill only: selecting a different company than asserted does not produce a warning.

Search types

Registry searches support two modes:

Search workflow

The registry lookup follows an asynchronous workflow:

Search

Didit queries the registry with the selected country and the identifiers provided — company name, registration number, or both combined. The response’s searched_by field reports how results were matched (name, registration_number, or registration_number_and_name), and the hosted UI offers a one-tap “Search as company name instead” override on registration-number results. The search runs asynchronously.

Poll results

Poll the search status until results are resolved. Large registries may take a few seconds to return results.

Select company

Review the returned companies and select the correct match. Didit links the selected company to the KYB check and populates all available data.

Confirm and continue

Confirm or correct the company details and continue to the next configured step. Some registries return the company profile before the ownership report is ready; that report continues in the background while the applicant completes independent steps, such as document upload. Registry prefill does not block the Key People form: the applicant can enter people manually, and available registry people appear before submission as the report arrives. Custom report-dependent decisions still wait for the report rather than guessing their outcome. Your corrections are preserved when the report arrives. A pending report does not count as a completed registry check or an automatic approval, and registry billing uses the tier actually delivered.

Manual submission

If the company is not found in the registry, submit company data manually. The session continues with the provided data, and is_from_registry is set to false.

Retrieved data

Company statuses

Companies with a status other than Active may be automatically flagged or declined depending on your workflow configuration.

Data source indicator

Each company record includes an is_from_registry flag:
  • true — data was retrieved from an official company registry
  • false — data was manually submitted because the company was not found in the registry
The fetch_status field tracks whether the registry lookup has completed, failed, or is still in progress.

Data tiers and pricing

In the hosted flow, selecting a company incurs the registry charge, even if the applicant leaves before confirming the details or finishing verification. If the report is ready at selection, the delivered tier is charged immediately. If ownership is still pending, Lite is charged at selection and only the price difference is charged when a higher tier is delivered. If ownership is unavailable, no ownership surcharge applies. The total uses the prices quoted at selection and never exceeds the requested tier’s quote. The selection and any later ownership adjustment count as one registry check; reading the purchased report or confirming its details does not charge it again. Existing flat-rate contracts accrue one registry check at selection, without a second contract unit for later ownership delivery. Hosted workflow searches have no separate search fee. Standalone API searches can incur a $0.50 fee per successful request; see search billing. See KYB registry pricing for the full per-country table. A hosted workflow picks the tier per country from Workflows → KYB Registry Check → Countries. Where the registry holds no ownership record for a company, a Shareholders or UBO request is delivered and billed at the highest tier the country’s registries can serve — usually Lite. A company that is not found and is entered manually (is_from_registry: false) is billed a flat $0.75 — the search still ran, even though no registry record was returned.
Lite returns the company profile only — no shareholders, UBOs, or ownership structure:
The Shareholders tier adds ownership_structure and shareholder entries plus directors/officers. The UBOs tier additionally resolves beneficial owners with ownership percentages. See Ownership and Officers & directors.

Registry data vs user-provided data

Didit keeps registry-returned data and user-confirmed data as separate audit records, with a merged canonical view used by downstream checks. Every company carries three related blocks: The confirmed_by_user_at timestamp marks when the end user confirmed or edited the registry data. While that timestamp is still null and is_editable is true, the end user can continue to modify fields inside the hosted flow. For manual-entry companies (is_from_registry: false), user_provided_data is the only source and is_editable becomes false after the user submits. Analysts can see the two sources side-by-side in the Business Console session review and diff what the registry said vs what the user confirmed.

Configurable registry form fields

You control which company-data fields the hosted verification flow asks for during the registry-confirmation step. Configure them in the Business Console: open the workflow editor, select the KYB Registry check node, and switch to the Fields tab. Each field has one of three states: Three fields are always shown and always required — they identify the company and cannot be configured: company_name, country_code, and region (state/region, where the registry is regional). The 16 configurable fields: registration_number, incorporation_date, legal_address, vat_number, alternative_names, tax_number, company_type, legal_entity_identifier, location_of_registration, nature_of_business, registered_capital_amount, registered_capital_currency, website, email, phone, control_scheme By default — and for all existing workflows — only incorporation_date is Required; every other configurable field is Optional, so the form behaves exactly as it did before this setting existed. Requiredness is enforced server-side: submitting the registry form with a required field empty returns 400 with per-field error messages, and the hosted UI renders only the enabled fields. In the workflow API, the setting is the kyb_registry_fields_config object on the KYB Registry node — see feature configs for the shape.
vat_number marked Required is only enforced for companies incorporated in an EU VAT country (see below) — for all other countries the field is treated as optional even when required, since there is no EU VAT number to collect. Their tax_number is still validated when provided.

VAT and tax ID validation

When the registry step is submitted, Didit validates the company’s vat_number against the official source for its country. A company without a vat_number has its tax_number validated instead. The number can be submitted with or without its country prefix and with any separators (DE 123 456 789, DE123456789 and 123456789 are equivalent for a German company). Official registries. In these countries the number is checked live against the government or official business register, which also returns the registered name (and, for most, the address): A French SIREN or SIRET, a Dutch RSIN or a full Hungarian tax number, submitted as the VAT number, is converted to the matching VAT number before it is checked. Greek VAT numbers are checked under the EL prefix automatically. Check-digit rules. In these countries no registry can be queried, so the number is checked against the country’s official format and check-digit rules: Albania, Andorra, Argentina, Australia, Azerbaijan, Belarus, Canada, Chile, China, Dominican Republic, Egypt, El Salvador, Ghana, Guatemala, Iceland, India, Indonesia, Israel, Japan, Kenya, Liechtenstein, Mexico, Moldova, Monaco, Montenegro, Morocco, Mozambique, New Zealand, North Macedonia, Peru, Russia, San Marino, Serbia, Singapore, South Africa, South Korea, Taiwan, Thailand, Tunisia, Türkiye, Ukraine, United Kingdom, United States, Uruguay, Venezuela and Vietnam. These rules also apply in the EU when a tax_number is a national tax ID that has no VAT number to check, such as a German Steuernummer. A tax_number only claims a tax identifier, not a VAT registration, so when VIES does not list it the result falls back to these rules instead of invalid. Companies from any other country get vat_validation_status: "not_applicable". So do sandbox sessions, which never contact a tax registry. The result is stored on the company and exposed in the KYB decision payload: vat_validation_source is one of eu_vies, pl_vat_white_list, no_brreg, ch_uid_register, br_receita_federal, co_rues, cr_hacienda, ec_sri, py_dnit, or format_rules. Once a number is valid, invalid, format_valid or invalid_format, the result is kept for the rest of the session and the registry is not asked again unless the number changes. Name cross-check. When the number is valid and the source discloses the registered name, Didit fuzzy-compares it against the submitted company name. A meaningful divergence raises the KYB_COMPANY_VAT_NAME_MISMATCH warning without changing the session status - it is a soft signal for reviewers. Its additional_data carries registry_name, registry_source and submitted_name, plus vies_name when the source is VIES. Some EU member states do not disclose the name or address; the fields come back empty and no comparison runs. Configurable actions. Two settings on the KYB Registry check node control what an unsuccessful check does to the session (values REVIEW, DECLINE, NO_ACTION): A tax_number that is invalid_format is reported in the payload without triggering an action, because the free-text tax field often holds a different company identifier. Each outcome also raises the matching warning (KYB_COMPANY_VAT_INVALID, KYB_COMPANY_VAT_COULD_NOT_VALIDATE) on the registry check - see Business Verification warnings.

Data cross-referencing

Didit automatically compares the user-provided / canonical data with what the registry returned, and with OCR data extracted from uploaded documents:
  • Company name — fuzzy matching to account for abbreviations and formatting differences
  • Registration number — exact match validation
  • Country — consistency check between provided and registry country
  • Address — geocoding and normalization for comparison
Any inconsistencies are flagged as warnings in the session and visible to analysts in the console.

Financial summary

Where available, Didit retrieves summary financial data from the registry:
  • Revenue or turnover
  • Number of employees
  • SIC/NACE industry codes
  • Filing dates and compliance status

Additional registry fields

Depending on jurisdiction coverage, the registry response may also include:
  • alternative_names - trade names, dbas, former legal names
  • legal_entity_identifier (LEI) — for financial institutions and listed entities
  • website, email, phone — contact information on file with the registry
  • nature_of_business — short description (in the language of the registry)
  • registered_capital — authorized / issued capital as an {amount, currency} object
All fields land in the business block of the KYB decision.

Confidence and verification status

Each registry response carries a verification_status: Combine with is_from_registry to drive your own downstream logic:

Cross-referencing outputs

Each cross-reference runs per field and returns one of:
  • MATCH — provided data agrees with registry.
  • MISMATCH — meaningful divergence. Flagged as a warning.
  • NO_DATA — one side was empty; no comparison possible.
Mismatches are visible per-field in the console session review.

What drives the outcome

Company status, country of incorporation, AML results and the match with the declared data feed the decision as warning tags on the registry check and the AML screening. Your workflow decides whether each warning approves, reviews or declines. See risk assessment for the signals and the workflow keys that control them.

Supported countries

Coverage varies by country — see supported countries for the per-region tier breakdown.

Next steps

Ownership

UBO identification and ownership chains.

Response schema

Where each field appears in the payload.

Supported countries

Coverage by region.
Last modified on October 31, 2026