Integrating KYC model #5
Description
Current API does not support KYC'ing the client, we need the support to add a standard user (or say a root user or admin user) who could add other user connected to the above mentioned user.
We might need to integrate some kind of third party API services to verify user (like Social Security Number)
Sub tasks
- User allowed to created with his document etc.
- User stores all the data to mobile, we use mobile as key Identifier , appropriate model would be like below
User : {
mobileNumber,
documentType,
verified,
publicSharingKey
}
The role of the publicSharingKey is:
Once verified this key could be used as standard client since we have done first level of verification, the client needs not to be verified.
This key could contain, the above information, which can be only extracted if the user wishes to send to the user privately signed with his cryptographic key and contains value.
This value should be typically provided by the end user, perhaps we need to think of this model.(Revisit this model)
We can start working on the first layer solution.