On-chain KYC(™) - explanation


On-chain KYC is a zero-knowledge product for Businesses that do not want to collect KYC data of users but want to understand whether a crypto user has been verified.


For On-chain KYC(™), Blockpass manages the Dashboard of the Business and processes the KYC verifications. 


The Business is then able to send a crypto-address to Blockpass and Blockpass confirms the KYC status of the user. 


The Business decides on the KYC rules; Blockpass enforces those rules on behalf of the Business in the Dashboard. All support is managed by Blockpass during the process.


During and after the KYC process the Business cannot access any KYC data on users. 


As said, a Business can only access the status of the user. What that means is whether a user is Approved or not. 


If it is a one-time event then Blockpass deletes the data from the Business Dashboard after the event. If it is ongoing then Blockpass regularly deletes the data from the Business Dashboard. This procedure does not delete the Identity Profile of the user.


To delete an Identity Profile there are two ways:


  • Mobile app -> uninstall
  • Web app -> send support ticket


FAQs on On-chain KYC(™) 


Does the agreement you enter into with clients provide indemnity from your side regarding any error in doing KYC on part of Blockpass? Eg., If a wallet address for which KYC is done by you for a client - is investigated by a country's regulators for money laundering/ terrorism financing and there are legal proceedings against the client because of this, will you indemnify the client. 

No we do not provide an indemnity.

Are there any jurisdictions for which you are unable to do the user KYC? 

Please see list as follows: 

Is there a token provided by blockpass upon doing the KYC for the user - through which your client can avoiding accessing and storing personal information of the user?

For On-chain KYC you would be our client and would have the option not to access the underlying data while and after verifications are being processing. If you terminate the engagement you would have access to a Dashboard that contains the verifications but not any underlying data on users. During the engagement you would be able to check via API on the status of a user by sending a crypto address to Blockpass and us providing a response on status. 

Is there any mechanism put in place by blockpass to prevent user from passing on this verification certificate/token to another user? i.e. lending of the KYC certificate/token. 

On-chain KYC does not involve the issuance of a token. We are working on a new solution whereby you would be able to issue a non-transferable NFT to your users but this solution would only be available to clients that retain the data of users. 

What happens if a user 'X' already has a blockpass certificate from a previous login with another client of yours but that certificate only shows KYC for national ID + Eth address, but now does login to another one of your client which wants KYC done from you for national ID + face recognition + eth addres + bsc address, etc.? 

Blockpass users create a single KYC Profile that they can re-share. As requirements change with different Services they have to update or add to their Profile. 




Article is closed for comments.

Was this article helpful?

7 out of 18 found this helpful
Powered by Zendesk