Hypersign.Id
Hypersign.idEntity StudioIdentity Wallet
  • 💬Welcome!
  • Hypersign KYC
    • Introduction
    • Integrations
      • KYC Service
      • Widget Configuration
      • Environments
        • Development
        • Production
      • Webhook
    • KYC Widget
      • Integrations
        • Backend Integration
          • Generate AccessTokens
          • Generate KYC Session Id
        • Frontend Integration
      • Data Capture
        • Data Vault Setup
        • Capture Facial Recognition
        • Capture ID Document
        • Capture zk-proof and KYC token
        • Capture User Consent
      • User Data
        • idToken
    • Hypersign ID Wallet
    • On-Chain KYC
      • Contracts Deployment
      • Use Cases
      • Supported Blockchains
      • KYC Token Metadata
    • Dashboard
      • User Sessions
      • User Session Details
      • Usage
      • Credit
    • Concepts
      • Facial Recognition
      • ID Verification (via OCR)
      • Reusable KYC
      • Encrypted Data Vault (EDV)
      • Facial Authentication
      • Issuer Marketplace
      • Security
      • Privacy
      • Credentials Types
        • Personhood Credential
        • Passport / Govt. ID Credential
      • zk Proof Types
        • Proof Of Personhood (PoP)
        • Proof Of KYC (PoK)
        • Proof Of Age (PoA)
      • Uniqueness Check
      • Credential Revocability
      • Machine Readable Zone (MRZ)
      • Liveliness Check
      • Zero Knowledge Proof (zkp)
        • Introduction
        • zk-SNARK
        • Circuits
        • SSI and ZKP
    • Tutorials
      • How to Integrate KYC in minutes?
      • How to add your team member?
  • Hypersign SSI
    • Introduction
    • Setup SSI Service
      • Create Your First DID
      • Credits
    • 🔗API Reference
      • Service Authentication API
      • DID
      • Schema
      • Verifiable Credential
      • Verifiable Presentation
        • Presentation Template
        • Presentation
    • 🎰API Playground
    • 🏑SSI Playground
  • Hypersign Developer Dashboard
    • Service
      • Managing API keys
      • Network Fee
    • Members & Roles
      • Members
        • Assign Role To Member
      • Invitations
        • Member Access Admin's Dashboard
      • Roles & Permissions
        • Permissions List
    • Security
      • Login
      • Multi factor Authentication (MFA)
  • Hypersign Identity Network
    • Introduction
    • Validators & Delegators
      • Installation of Node
      • Running a Testnet Validator Node
    • Governance
      • Proposals
        • Blockchain Node Upgrade
        • Community Pool Spend Proposal
        • Blockchain Parameter Change Proposal
        • Text Proposal
      • Delegation
    • Faucet (testnet)
    • Developers
      • HID-Node Codebase
      • ⚙️Setup Local hid-network Tutorial
        • Running one-node local hid network
        • Create and fund new account
        • Transfer funds
        • Connect Keplr to local hid network
      • Hypersign SSI Toolkit
        • Hypersign DID SDK
        • Hypersign Schema SDK
        • Hypersign Verifiable Credential SDK
        • Hypersign Verifiable Presentation SDK
        • OfflineSigner
    • Blockchain & ID Explorer
  • Core Concepts
    • Introduction
    • Decentralized Identifier (DID)
      • DID Registry
      • Private and Public DID
      • DID Authentication
      • DID Communication (DIDComm)
      • Adding multiple controller to DID
      • Adding multiple verification methods
      • Verification Method vs Recovery Signature
      • Blockchain Account Id
      • DID Threshold
      • Verifiable Condition
      • Verification Relationships
        • Authorization Capabilities (zCap)
    • Schema
      • Schema Registry
      • Schema.org
    • Verifiable Credential (VC)
      • Credential Revocation Registry
      • Issuing a Credential to Multiple Subjects
      • Bearer Credential
      • Single-Use Credential
    • Verifiable Presentation (VP)
    • Specifications
      • Supported Signature Algorithms
      • Client Specification
        • EVM based chains
        • Cosmos based chains
  • Ecosystem
    • Forum
    • Github
    • HID Explorer
    • Eiko
    • MetaAuth
  • Privacy Policy
Powered by GitBook
On this page
  • Facial Recognition
  • ID Document Verification
  • User Consent
  • Zero Knowledge Proof (zk-proof)
  • On-Chain KYC
  • Trusted Issuer
Edit on GitHub
  1. Hypersign KYC
  2. Integrations

Widget Configuration

PreviousKYC ServiceNextEnvironments

Last updated 6 months ago

is web based application to capture user's data. It is used to capture, user facial detail, ID document, user consent etc. In order to use KYC Widget in your frontend, you first need to configure it in the . Widget configuration enable you to do custom configurations of KYC widget for your users.

Logon to . and proceed to "Know Your Customer" tab of your services and click on your KYC service tile.

Your KYC service dashboard opens up. Now navigate to "Widget Configuration" page by clicking on "Widget" menu item in the side nav bar.

Facial Recognition

The first configuration is Facial recogination which is already enabled. So no need to do anything here.

This feature, if enabled, will ask user to open their camera and record a video on KYC widget to prove he/she is a human. Once the data is collected and verified, KYC server issues a "Personhood Credential" to the user which acts as a proof that "he/she is indeed a real human and not bot".

Check list of all supported credentials and proofs types here.

ID Document Verification

Now enable ID document verification setting and select document type as "Passport". The feature, if enabled, the KYC widget will ask users to provide ID document. The ID document is captured, data extracted and sent to the KYC service. KYC service does the following things with the data:

  1. Document Verification: Checks if document was tampered or not in correct format. In some cases, it also verifies if digital signature attached with the document is correct or not.

  2. OCR: Extracts relevant data from the ID document.

  3. Facial Authentication: Matches user's image in the ID document with the user's photo taken during the facial recognition step

  4. Uniqueness Check: Checks if the user unique in the system - restricting same user not using same ID document with multiple accounts.

Check list of all supported credentials and proofs types here.

User Consent

Configure user consent page by providing a valid reason for "why you are collecting user's data". Read more about user consent here:

Zero Knowledge Proof (zk-proof)

Enable zk-proof configuration if do not want to collect user's personal data but the proof of facts. We have following proofs available.

Configure one of more proofs and click on Update Configuration button to save your settings.

On-Chain KYC

Make sure to enable zk-proof configuration before enabling On-Chain KYC configuration.

Trusted Issuer


Now that your widget configuration is finished, you are ready to integrate Hypersign KYC in your application.

Upon successful verifications of all, the KYC service issues him/her "Passport Credential", which is technically a , to the user.

: Proves that user has finished his/her KYC.

: Proves that user is not a bot

: Proves user is above the specified age (age need to be specified in text box)

You might want to provide service to users based on verification in your Dapp. For that your smart contracts wants to verify user's Identity before allowing to access other features of the smart contract. Since users cannot send his personal data to a contract because of obvious privacy issues with public blockchains, user first generates zk-proofs of their ID claims and only sends proofs to contracts, preserving privacy while enabling secure verification. Make sure to in one of the supported blockchain before enabling this setting.

Select one or more trusted issuers, with the default being 'self' - your own KYC service. This pertains to . If configured, users who already possess KYC credentials issued by these trusted issuers in their will not need to repeat the KYC steps in the widget. They can simply authorise the sharing of their existing credentials with your app, streamlining user onboarding for your application and providing a smoother experience for your users.

verifiable credential
Capture User Consent
Proof Of KYC (PoK)
Proof Of Personhood (PoP)
Proof Of Age (PoA)
create On-Chain KYC configuration
Contracts Deployment
Reusable KYC
data vault
Integrations
Hypersign KYC widget
Entity Developer Dashboard
Entity Developer Dashboard