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.