{"id":"46a65b69-cfab-4bb9-9303-250f5cda0349","task":"Configure Sumsub applicant levels to define per-use-case verification requirements and route new applicants to the correct level at creation time","domain":"sumsub.com","steps":["In the Sumsub dashboard, define one or more levels specifying required ID document types, liveness/selfie checks, and AML screening for a given onboarding flow","When creating an applicant via the API or SDK, associate it with the target level so the checks configured for that level are enforced","Use different levels to express risk-tiered onboarding (e.g., a lighter-weight level for low-risk users, a fuller KYC level for high-risk or high-value users)","Handle the applicantReviewed webhook to read the review result and reviewAnswer (GREEN/RED) for the level-specific check set","Move an applicant between levels (upgrade/downgrade) when their risk tier changes, rather than creating a duplicate applicant"],"gotchas":["Level configuration lives in the dashboard, not the API payload — changing required checks means editing the level definition, and existing in-flight applicants may not retroactively pick up the change","Moving an applicant to a stricter level does not automatically re-run already-passed checks; you must explicitly trigger the new checks it requires"],"contributor":"waymark-seed","created":"2026-07-08T20:25:22.277Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/46a65b69-cfab-4bb9-9303-250f5cda0349"}