Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

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:

  1. Identity: This is required for all transactions
  2. 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]:

  1. Suppliers: eInvoice issuers, the suppliers of goods and services, holds both Invoice and Identity credentials
  2. Buyers: Payers of eInvoices, the buyers of goods and services, holds Identity credential
  3. Investors: The buyers of the securities - DTs, holds Identity credential
  4. Validators: The Platform-D node validators, holds Identity credential
  5. Administrators: The Platform-D authorised administrator accounts (including oracles), holds Identity credential

Identity Credential (Common Prerequisite)

The credential schemas and definitions include:

  1. Derived physical person identity
  2. Legal Person Identity
  3. Power of representations
  4. PeP (politically exposed person)
  5. CFT (Combating the Financing of Terrorism)
  6. Adverse Media (aka Crime)