Verification levels

Use exact Sumsub level names. Removing a level stops new transfers and preserves existing files.

Sync from Sumsub updates

Once connected, Sumsub webhooks notify this app when an applicant changes. A level change records the date for the folder; documents upload only when the current review is Completed with a GREEN result (Approved). Customer tag updates and review markers continue to follow your rules.

Webhook delivery requires a public HTTPS address ending in /webhooks/sumsub, configured in Sumsub with the matching secret. Sumsub cannot send updates directly to 127.0.0.1. Until a public address is connected, use Import applicants or Retry sync to start a transfer. Failed transfers retry automatically.

Refreshing the Logs tab only checks this app’s stored activity.

kDrive connections

All applicant folders are created under the selected parent folder for each connection. Credentials are configured on the server.

Applicant folder names

Use the exact applicant name from Sumsub, another field in the applicant record, or a name you supply. Applicants keep their existing folder when their name changes.

Invalid names and duplicate customer names need attention. The archive does not change the name or combine applicants to resolve them.

Folders inside each applicant

Choose where each folder sits inside the applicant folder. You can rename folders, add more, or place one inside another. Removing a folder from this layout preserves its existing files.

KYC upload rules

Choose which evidence to archive and its folder for selected verification levels. The first enabled matching rule wins; other levels archive all KYC documents and reports in the default folder above. Level names must also be enabled in Sumsub settings. Files are transferred only when the current verification is Complete with a GREEN result (Approved).

Drag a handle to change priority, then Save settings. To reorder with a keyboard, focus a handle, press Space, use the arrow keys, then press Space again. Escape cancels.

No upload rules yet. Documents use the default KYC folder.

Rules are checked on every sync using the current approved level, so later questionnaire answers and uploads are included. Already archived versions stay where they are. Customer categories and review tags continue to update independently. Transaction and wallet evidence keep their own destinations.

Documents

Original active documents, questionnaire uploads, and available liveness video snippets are included. Files use the applicant name and Sumsub document type. JSON files are never uploaded.

Questionnaire file names

Choose the label used after the applicant’s name for files uploaded through questionnaires.

This label applies to all questionnaire uploads unless a rule below matches. A single file uses “Applicant name - SoF:SoW”; multiple files use “Applicant name - SoF:SoW_1”, “Applicant name - SoF:SoW_2”, and so on, with their original file extensions.

Onboarding reports

These settings apply to the first approved onboarding sync and later approved syncs that include all KYC documents. Unchanged reports are not uploaded again; updated reports are saved as new revisions. Questionnaire-only upload rules use their own PDF settings.

Choose each native Sumsub PDF’s file name and sections below.

The starting reports keep Questionnaire separate as “Onboarding questionnaire”. Unselected sections are excluded; Sumsub’s branding and standard disclaimers may still appear. Changing a report name renames its current file while preserving earlier revisions. Removing a report preserves its existing files.

Section selection is available for individual applicants. Company report generation is paused until its section selection is verified; other company documents continue to sync.

The app creates a PDF from Sumsub’s verified Satoshi test or signed blockchain message evidence. This is an app-generated evidence report, not a native Sumsub PDF. Unverified payment methods are excluded.

Waiting for Sumsub to provide an API-supported native transaction PDF export.

You can prepare report types and destinations now. Transaction PDFs remain off while we wait for Sumsub’s API support.

Native applicant summary reports and onboarding questionnaires continue to work with your existing settings.