Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • ID: user ID assigned to the registered user

  • Email: email address of the registered user

...

  • Accept (button): accept the submitted document and the User`s info provided

  • Reject (button): reject the submitted document and the User`s info provided

  • Ban: ban the user and document they submitted for identity verification

  • Document Name:pressing the Document Name defined by the User at the time of document upload opens the document and allows the admin to click, rotate, and zoom on different parts of the document

...

  • State: displays user status as Not Verified / Pending / Verified

  • First Name: see first name

  • Last Name: see last name

  • Date of Birth: see date of birth

  • Address: see street address

  • City: see city

  • Country: see country

  • Postcode: see postal code

  • Document Review: documents uploaded by the user are listed on the right section of the KYC tab with corresponding names. Admin can open each in dropdown, click on the document to zoom in on various parts of the document, and rotate the document

The main conditions for the administrator and the KYC (Know Your Customer) flow are as follows:

  1. Verification Process:

    • The verification process progresses step by step, starting with email verification, followed by phone verification, and concluding with identity verification. This sequential approach ensures a thorough and systematic validation of the user's identity.

    • To unverify a user, the administrator must follow a specific sequence: identity verification is revoked first, followed by phone verification. However, email verification cannot be undone if it has already been verified.

  2. Withdrawal Restriction Level:

    • After successful identity verification, the user's withdrawal restriction level is adjusted from zero to the first level. This transition signifies that the user has completed the necessary steps to confirm their identity, thereby warranting a higher level of trust and access within

Sum Sub Integration (Mobile SDK)

...