Skip to main content
How to build a Rehive KYC extension

This document unpacks the typical KYC extension integration with your chosen partner.

Helghardt Avenant avatar
Written by Helghardt Avenant
Updated over a week ago

We have detailed documentation on how to develop a typical KYC integration with a third-party vendor. Follow the typical integration flow and use Rehive endpoints at each stage of the process. For detailed guidance on building a KYC extension, please refer to the Rehive Developer Docs.

Below is a diagram overview of the KYC flow.

KYC flow

  1. The user submits information via the app. Using the existing wallet front ends, the users can submit their KYC information as well as upload supporting documentation.

  2. The system triggers webhook to extension.

  3. Extension formats information and submits it to the third-party system.

  4. The third-party system applies KYC checks and returns a status

  5. Extension updates status on Rehive.

  6. Rehive Notification Extension notifies the user of a status update.

Rehive supports statuses on key sets of user information fields. For example, basic information, address, external accounts, documents, etc. The extension can update some or all of the status fields, depending on your requirements. The process will start with setting up webhooks for specific user events that relate to our specific KYC requirements.

Notes and guidelines

Rehive recommends using tiers to indicate the KYC level of a user. Tiers can be configured on a group level and can rely on a variety of fields which can be updated using the Rehive API.

Depending on the regional KYC requirements in your chosen industry and the product offered by your KYC partner, the Rehive API can be used to fetch the required data and supporting documentation. Once verified, the applicable fields can be updated on the Rehive Platform.

If Rehive does not support a required KYC field, please let us know, and we can add it.

Did this answer your question?