Privacy-preserving KYC

ComPilot can use zero-knowledge proofs to perform privacy-preserving KYC checks that preserve the customers privacy while still providing sufficient KYC proofs to gate your application.

For example, a privacy-preserving KYC workflow could confirm that a particular wallet is not owned by a citizen of the USA while all other information about the customer is kept confidential.

The ComPilot Dashboard has a template that can be used to build your privacy-preserving KYC workflow.

Privacy-preserving KYC workflows use the ComPilot KYC provider, which is a KYC provider built using Subsub.

📄️ Setup and configuration

Setup

📄️ Integration

This section explains how to deploy a privacy-preserving KYC workflow into your application. You need to make changes on both the front end and back end of your application, as well as understanding how to use the information from the webhooks.

📄️ Customer experience

As a developer, it is important for you to understand the steps that the customer goes through when using a privacy-preserving KYC workflow.

📄️ Verification results

To determine the customers final status, first the KYC provider makes a decision. Then your application makes a decision using ComPilot's predefined automations and the rules set in the ComPilot Rules Engine. As a developer or compliance officer, it is sometimes useful for you to know what combinations of statuses are possible.