3.1 SDK Flow Summary

1. 1

   The applicant starts KYC in the client web or mobile application.

2. 2

   The client application requests a KYC session from the client backend.

3. 3

   The client backend generates the SDK access token in Sumsub using the applicant’s externalUserId and the configured levelName.

4. 4

   The client backend retrieves or confirms the applicant record using externalUserId.

5. 5

   The client backend provides required custom fields via PATCH.

6. 6

   The client backend returns the SDK access token to the client application.

7. 7

   The client application launches the Sumsub WebSDK or MobileSDK.

8. 8

   The applicant completes the required verification steps.

9. 9

   Sumsub performs automatic checks and may request manual review.

10. 10

    Sumsub sends the applicantReviewed result to Payblr.

11. 11

    The client backend may retrieve applicant review status to view the latest status via API or webhook configuration.

12. 12

    Payblr receives the result and returns the final handling result according to the reviewAnswer from the applicant status flow.