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.
An end-to-end legal-entity assurance journey
Two trust boundaries are explicit: business-source data and representative identity.
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 |
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.
PERSON SOURCE
CCCD/VNeID · identity attributes · biometric holder verification.
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 fixtureFrom 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.
KYB Sandbox
Interactive synthetic tax-ID → company → representative KYC → evidence.
Evidence Package
Organisation + representative + sources + time + decision + trace.
KYB: Business assurance bound to a verified representative
Replaces generic solution cards with actor, source, verification, policy and evidence flow.
CCCD, ePassport, VNeID or enterprise/tax identifier as appropriate.
Retrieve or verify source data under the permitted source boundary.
Use eID/document plus biometric holder verification when policy requires.
Evaluate policy, role/binding and verification metadata.
Approve, review or reject under KYC/KYB policy and exception handling.
Store source, method, result, time and audit references.
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.
