SumSub - KYC Service

Owned by Vladislav Pavlov
Last updated: Nov 15, 2024 by Denys Tun
1 min read

Variables for Sum Sub:

  • APP_TOKEN - Created in Sum Sub to generate tokens for the SDK

  • SECRET_KEY - Created in Sum Sub together with APP_TOKEN to generate tokens for the SDK

  • LEVEL_NAME - Your level_name is created in the SumSub to indicate which verification steps the user should go through.

  • WEBHOOK_SECRET_KEY - generated when creating a webhook in a Sum Sub

Step for verifying via SumSub:

  1. Front-end gets token for SDK Plugin from GQL

    1. Also, add the Authorization header

      query{ getSumSubAccessToken{ token userId } }

  2. Use for SDK Plugin token

  3. After the verification is completed, the plugin will send a request to the backend to create a user verification request.

  4. When we receive it, we will write a label to the system that the verification is pending

  5. When SumSub verifies a user, it will send us a reply with three possible results:

    1. GREEN (accept) - we record the data on the user that he provided to our system and change the label to verified

    2. RED RETRY (reject) - We change the label to reject so that the client passes the verification again

    3. RED FINAL (ban) - Change the label to ban and ban the client in the system