For customers who prefer not to access user data, the Blockpass On-chain KYC service is a suitable option.


A Web3-enabled product for Enterprise clients

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.

Supported package

Enterprise Corporate

End-user support level

Managed Service

Dedicated Operator (if required)

Service Description

Service setup - The process for setting up the service is that the Business will decide on the rules for KYC, and Blockpass will enforce these rules on the Customer's behalf using the Dashboard.

Blockpass entirely manages the dashboard/ Support.

Data access - The Customer is not granted access to view the underlying data of users but can check the KYC status of users by using API keys.

Archived - The data is usually kept in the system for one month after a single event (such as the completion of a sale) or for two months for ongoing services, after which it is archived.

API reference

The following APIs are available for use with Blockpass KYC services:

API Keys Creation: Use this link ( to create API keys for your service account.

Dashboard API: This API ( allows you to query and extract the KYC status of users.

Archive Dashboard API: The archived dashboard API ( can archive data in the service dashboard. 


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