Sumsub Know Your Customer (KYC) Integration Guide
9. Sandbox Testing
Before production go-live, complete level selection, document submission, result handling, and exception paths. Cover <client>-kyc-individuals-address, <client>-kyc-individuals-address-tin, and <client>-kyc-individuals-poa-batch.
On this page
| Test Case | Expected Result |
|---|---|
Create applicant with valid sourceKey, partnerName, and externalUserId | Applicant is associated with the correct client configuration. |
Create applicant without sourceKey | Applicant is rejected, held, or flagged for correction. |
Create applicant with full fixedInfo | Applicant profile and address are stored. TIN is stored only when the selected level requires it. |
Create applicant on <client>-kyc-individuals-address | Applicant is created without TIN and without a proof-of-address step. |
Create applicant on <client>-kyc-individuals-address-tin | Applicant is created with TIN/SSN and without a proof-of-address step. |
Create applicant on <client>-kyc-individuals-poa-batch | Applicant is created on <client>-kyc-individuals-poa-batch and proof of address is required. |
| Upload identity document | Identity step is satisfied when valid images are submitted. |
| Check PoA status after identity upload | On <client>-kyc-individuals-poa-batch, dedicated PoA is skipped only when PROOF_OF_RESIDENCE is already satisfied. <client>-kyc-individuals-address and <client>-kyc-individuals-address-tin have no proof-of-address step. |
| Upload dedicated PoA | PROOF_OF_RESIDENCE is satisfied when the correct document is accepted. |
| Submit questionnaire | Required answers are stored and accepted. |
| GREEN result | Applicant is approved for continuation in Payblr onboarding. |
| RED RETRY result | Applicant is not approved; resubmission is required. |
| RED FINAL result | Applicant is rejected and cannot continue onboarding. |
| PEP scenario | Applicant is routed for compliance review. |
| AML/sanctions scenario | Applicant is routed for compliance review or rejection. |
| Missing required data | Applicant remains pending or requires correction. |
| Duplicate webhook/result | Client and Payblr avoid duplicate onboarding actions. |
| Result retrieved by API | API result matches webhook result. |
Applicant lookup by externalUserId | Applicant 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.