Skip to content
Switch to light mode

Sumsub Know Your Customer (KYC) Integration Guide

10. Sandbox Testing

Before production go-live, complete sandbox testing with Payblr to confirm applicant creation, document submission, SDK behavior, result handling, and exception paths.

On this page

Test CaseExpected Result
Generate or request SDK access tokenToken is generated server-side and not exposed in frontend code.
Create applicant with valid sourceKey, partnerName, and externalUserIdApplicant is associated with the correct client configuration.
Create applicant without sourceKeyApplicant is rejected, held, or flagged for correction.
Create applicant with full fixedInfoApplicant profile, address, and TIN are stored.
Upload identity documentIdentity step is satisfied when valid images are submitted.
Check PoA status after identity uploadDedicated PoA is skipped only when PROOF_OF_RESIDENCE is already satisfied.
Upload dedicated PoAPROOF_OF_RESIDENCE is satisfied when the correct document is accepted.
Submit questionnaireRequired answers are stored and accepted.
SDK launch with valid applicantWebSDK or MobileSDK opens successfully.
SDK token expirationClient can request or receive a refreshed token.
GREEN resultApplicant is approved for continuation in Payblr onboarding.
RED RETRY resultApplicant is not approved; resubmission is required.
RED FINAL resultApplicant is rejected and cannot continue onboarding.
PEP scenarioApplicant is routed for compliance review.
AML/sanctions scenarioApplicant is routed for compliance review or rejection.
Missing required dataApplicant remains pending or requires correction.
Duplicate webhook/resultClient and Payblr avoid duplicate onboarding actions.
Result retrieved by APIAPI result matches webhook result.
Applicant lookup by externalUserIdApplicant can be reconciled using the client user reference.

Next steps

Continue to the Go-Live Checklist for production readiness items before enabling Sumsub KYC in live environments.