Skip to content
Switch to light mode

Sumsub Know Your Customer (KYC) Integration Guide

11. Go-Live Checklist

Use this checklist to confirm that configuration, credential handling, testing, result processing, and operational support are ready before production launch.

On this page

ItemOwnerRequired
Payblr-assigned sourceKey confirmedPayblrYes
Payblr-assigned partnerName confirmedPayblrYes
Sumsub App Token and Secret process confirmedClient / PayblrYes for API
SDK access token generation testedClientYes for SDK
Verification level confirmedPayblrYes
SDK flow confirmed, if applicableClient / PayblrYes, if SDK is used
API applicant creation flow confirmedClient / PayblrYes, if API is used
Proof of address decision rule testedClient / PayblrYes
Webhook/result processing confirmedPayblrYes
externalUserId format confirmedClientYes
Custom metadata submission confirmedClientYes
Applicant data/status retrieval testedClientYes
Sandbox testing completedClientYes
Duplicate handling testedClientYes
Token expiration handling testedClientRequired for SDK
Production monitoring confirmedClient / PayblrYes
Support and escalation process confirmedClient / PayblrYes

12. Implementation Notes

Use the following notes to align client implementation behavior with Payblr's Sumsub onboarding requirements.

Key Notes

  • sourceKey is mandatory for Payblr Sumsub processing.
  • externalUserId must be stable and unique for each applicant in the client's system.
  • partnerName must be the Payblr-provided Partner Id value.
  • SDK integration is used for the applicant-facing verification experience.
  • API integration is used when the client backend submits the KYC package directly.
  • Final KYC decisions must be based on Payblr's processed Sumsub result.
  • GREEN results may continue onboarding, subject to Payblr rules.
  • RED, RETRY, FINAL, PEP, AML, sanctions, and missing-data outcomes must follow Payblr rules.
  • Clients should not expose Sumsub credentials in frontend or mobile applications.
  • Sandbox testing must cover positive, negative, retry, final rejection, compliance-review, and proof-of-address scenarios before go-live.

Next steps

Continue to the Appendix for Sumsub reference links and supporting documentation used throughout this guide.