Togggle Documentation
  • Togggle Presentation
  • KYC Process
  • Integration Process
    • Webhook structure
    • Custom Fields
    • Successful Payload
    • Failure Payload
  • Decentralized Storage
    • Definitions
    • Types of Storages
    • Creation of the Personal Decentralized Storage
    • New User Verification Flow
    • One Click KYC
    • Company Dashboard
    • Authority Check
    • Data Deletion
  • B2B Dashboard
  • Reusable Credentials - One Click KYC
  • Product Information
  • Frequently Asked Questions
  • On-chain verifiable Proof-of-KYC
  • Wallet creation and VC
  • Architecture and Identity Flow
    • 🛡️ KYC Verification + AML Monitoring Flow
    • Data deletion - Right to be forgotten
Powered by GitBook
On this page

Wallet creation and VC

KYC and Verifiable Credential Issuance

This documentation provides a detailed guide on the process of KYC (Know Your Customer) verification and issuing verifiable credentials in the Togggle webapp. This process is essential for regulatory compliance and enables users to securely establish a verified identity within the app.

Overview

In the Togggle platform, users are authenticated either through a Web3 wallet or Web3 Auth. If no wallet is detected, Togggle offers the option to sign up using Web3 Auth. After authentication, Togggle requires KYC verification to issue a verifiable credential (VC), establishing the user’s identity in a decentralized, trusted manner.

Steps to Complete KYC and Receive a Verifiable Credential

1. User Authentication

  • Wallet Connection: If a user has a Web3 wallet installed (e.g., MetaMask or WalletConnect), they will be prompted to connect it.

  • Web3 Auth Option: If no wallet is detected, users can sign up via Web3 Auth, leveraging social logins like Google or Twitter.

2. KYC Verification Process

  • Initiate KYC: After authentication, Togggle will prompt users to complete the KYC process.

  • Provide Required Documents: Users must submit identification documents and/or undergo additional verification steps as required by Togggle’s KYC provider.

  • Verification Status: Once KYC verification is complete, Togggle updates the user’s profile to reflect a “KYC-verified” status.

3. Issuance of a Verifiable Credential (VC)

  • Generate Verifiable Credential: Upon successful KYC verification, Togggle generates a verifiable credential (VC) that confirms the user's verified identity status.

  • Secure Storage of the VC in the decentralized storage: The VC is issued to the user’s Web3 wallet and we store it encrypted in the user’s decentralized storage.

4. Accessing Togggle Dashboard with Verified Credentials

  • After receiving their VC, users are redirected to the client page.

PreviousOn-chain verifiable Proof-of-KYCNextArchitecture and Identity Flow

Last updated 5 months ago