Sumsub Know Your Customer (KYC) Integration Guide
10. 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
| Item | Owner | Required |
|---|---|---|
Payblr-assigned sourceKey confirmed | Payblr | Yes |
Payblr-assigned partnerName confirmed | Payblr | Yes |
| Sumsub App Token and Secret process confirmed | Client / Payblr | Yes |
Three Payblr-assigned levelName values confirmed | Payblr | Yes |
Level selection tested for <client>-kyc-individuals-address, <client>-kyc-individuals-address-tin, and <client>-kyc-individuals-poa-batch | Client | Yes |
| API flow confirmed | Client / Payblr | Yes |
Proof of address decision rule tested on <client>-kyc-individuals-poa-batch | Client / Payblr | Yes, for <client>-kyc-individuals-poa-batch |
| Webhook/result processing confirmed | Payblr | Yes |
externalUserId format confirmed | Client | Yes |
| Custom metadata submission confirmed | Client | Yes |
| Applicant data/status retrieval tested | Client | Yes |
| Sandbox testing completed | Client | Yes |
| Duplicate handling tested | Client | Yes |
| Production monitoring confirmed | Client / Payblr | Yes |
| Support and escalation process confirmed | Client / Payblr | Yes |
12. Implementation Notes
Use the following notes to align client implementation behavior with Payblr's Sumsub onboarding requirements.
Key Notes
sourceKeyis mandatory for Payblr Sumsub processing.externalUserIdmust be stable and unique for each applicant in the client's system.partnerNamemust be the Payblr-provided Partner Id value.- Select
levelNamebefore applicant creation. Replace<client>with the client name prefix, then use<client>-kyc-individuals-address,<client>-kyc-individuals-address-tin, or<client>-kyc-individuals-poa-batch. Do not change the level after the applicant is created. - United States applicants use
<client>-kyc-individuals-address-tinand must provide TIN/SSN. - High Risk countries use
<client>-kyc-individuals-poa-batch. - All other countries use
<client>-kyc-individuals-address. TIN and proof of address are not required. - The client backend submits the KYC package through the Sumsub API. Do not call Sumsub from frontend or mobile code.
- 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,
<client>-kyc-individuals-address,<client>-kyc-individuals-address-tin, and<client>-kyc-individuals-poa-batchscenarios before go-live.
Next steps
Continue to the Appendix for Sumsub reference links and supporting documentation used throughout this guide.