Integrating KYC model

[maektwain]

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

1. User allowed to created with his document etc.
2. 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.

[xurror]

Shouldn't this be something to be used with the web api. Right now I'm kinda confused where to implement this given the multiple packages available. Maybe giving me some pointers would help alot.

I have some options for the 3rd party KYC API:
trulioo.com
alloy.co
identitymindglobal.com

[maektwain]

We would not be using any third party API as of now, the approach would be to start off with the Api convention.

We simply allow users to submit their document over the app or any mode and then leading to storing their document over the blockchain

POST /v2/wallet/verify

contains the wallet information 

return the walletVerified information.

The development process is defined also for clear processing of the document.