CHECKID BUSINESS IDENTITY · KYB

Business KYB — from tax ID to legal-representative verification

Resolve an organisation from its tax/enterprise ID, validate legal status and ownership, KYC the legal representative with eID, bind person to organisation, apply policy/risk and produce evidence.

END-TO-END KYB

An end-to-end legal-entity assurance journey

Two trust boundaries are explicit: business-source data and representative identity.

01MST / Enterprise IDKYB starts from a legal-entity identifier.
02Business SourceQuery and normalize company data.
03Legal StatusValidate operating/registration state.
04OwnershipRepresentatives, contributors and ownership graph.
05RepresentativeResolve the legal representative.
06CCCD / VNeIDKYC representative through electronic identity.
07Holder Verify1:1 biometric holder verification.
08BindRepresentative ↔ organisation binding.
09AssureKYB policy, risk and evidence.
NORMALIZED DATA MODEL

An auditable business-data model

The supplied KYB field model but publishes none of the original PII.

Data domain Representative fields Role in KYB
Company official_name · tax_code · address · charter_capital · tax_state Business subject resolution
Legal representative full_name · title · identity_document · nationality Representative KYC + binding
Ownership / capital member/shareholder · legal identifier · holdings · percentage Ownership graph / UBO-candidate analysis
Business activities industry_code · industry_name · primary activity Context / policy / risk
REPRESENTATIVE BINDING

Business data and person identity are separate trust domains

KYB completes only after the representative is verified and bound to the legal entity; signatory or power-of-attorney rights are not inferred unless sourced.

COMPANY SOURCE

Business profile · status · representative · ownership.

Source statusRetrieved time
TRUST BOUNDARY

PERSON SOURCE

CCCD/VNeID · identity attributes · biometric holder verification.

RAR/C06/VNeID where authorisedConsent
OWNERSHIP / UBO

Ownership as a graph, not a flat list

The model surfaces capital structure and review candidates without automatically labelling a UBO.

ILLUSTRATIVE VIETNAM JSC

Synthetic organisation fixture
Investor ASource ownership data
55%
Investor BSource ownership data
30%
Investor CSource ownership data
15%
Ownership percentage does not automatically establish UBO status. separates Source Ownership Data → UBO Candidate Analysis → Confirmed Beneficial Owner based on policy, law and evidence.
INTEGRATION

From source data to an evidence package

Developer and operations views share the same canonical business/representative model.

KYB API / Integration Model

Actual business-source endpoint is published only when an approved contract exists.

Reference IntegrationNo fake endpoint

KYB Sandbox

Interactive synthetic tax-ID → company → representative KYC → evidence.

OFFLINE MOCKSynthetic data
END-TO-END JOURNEY

KYB: Business assurance bound to a verified representative

Replaces generic solution cards with actor, source, verification, policy and evidence flow.

01
Identity / enterprise input

CCCD, ePassport, VNeID or enterprise/tax identifier as appropriate.

02
Authoritative / document data

Retrieve or verify source data under the permitted source boundary.

03
Person / representative verification

Use eID/document plus biometric holder verification when policy requires.

04
Assurance / binding

Evaluate policy, role/binding and verification metadata.

05
Decision

Approve, review or reject under KYC/KYB policy and exception handling.

06
Evidence

Store source, method, result, time and audit references.

TECHNICAL REFERENCE

KYB: entity, authority-to-act and evidence graph

Legal entity → registry/source → representative → authority → ownership/control → decision/evidence

Entity identity

KYB starts with the legal entity and an authoritative registry/source appropriate to the jurisdiction. A company name or self-declared registration number is not a verified entity.

Registration state

Entity existence/status, identifier, registered address and officers/representatives are verified only within the source/time context.

Representative

Verifying the representative is an individual identity-proofing task; authority to act is a separate relationship/authorization check and is not inferred from a biometric match.

Ownership and control

Shareholder/control/UBO definitions vary by jurisdiction and use case. Public documentation does not apply a universal threshold without a legal source.

Relationship evidence

The entity-person graph should retain provenance: registry, document, mandate, customer evidence or another source, with effective/expiry context where applicable.

Decision

A KYB outcome should distinguish entity verified, representative verified, authority verified, ownership/control assessment and unresolved exceptions rather than a single “KYB passed” badge.