Onboarding
Jump to specific onboarding processes
The general purpose of onboarding is to:
- gather information (for checks and archival)
- facilitate and store digital signatures (to verify formal agreements, declarations)
- facilitate and record keep 3rd party service provider verification (KYC / AML / etc)
The process of onboarding ends with issuance of verifiable credentials to the users. Depending on the role, different information / process may be performed in order to issue one or multiple verifiable credentials.
There are 2 types of verifiable credentials onchain:
- Identity: This is required for all transactions
- Invoice Notarisation: This is required to notarise eInvoices onchain, required only by Suppliers
There are 5 role types in Platform-D in terms of onboarding with common prerequisites, aka [Identity Credential]:
- Suppliers: eInvoice issuers, the suppliers of goods and services, holds both Invoice and Identity credentials
- Buyers: Payers of eInvoices, the buyers of goods and services, holds Identity credential
- Investors: The buyers of the securities - DTs, holds Identity credential
- Validators: The Platform-D node validators, holds Identity credential
- Administrators: The Platform-D authorised administrator accounts (including oracles), holds Identity credential
Identity Credential (Common Prerequisite)
The credential schemas and definitions include:
- Derived physical person identity
- Legal Person Identity
- Power of representations
- PeP (politically exposed person)
- CFT (Combating the Financing of Terrorism)
- Adverse Media (aka Crime)