Review and manage KYC submissions in DALP

Review KYC submissions, inspect version history, and approve, reject, or request updates as an Identity Manager.

Identity Managers use the KYC detail page to review submitted KYC profile versions and check supporting documents before issuing an on-chain KYC verification.

Use this guide after a user submits KYC data and a reviewer needs to approve it, reject it, or ask for changes.

Prerequisites

Identity Manager role, or another role with permission to read KYC data
Reviewer permission for KYC version actions if you need to approve, reject, or request updates
Access to Participants > Users
Your organization's KYC acceptance rules

Users complete their KYC profiles with personal information and supporting documents, then submit a version for review. Each submission is kept as a separate version, so reviewers can inspect the history without overwriting earlier records.

When a version is under review, you can take one of three actions:

Action	When to use	Result
Approve	All information is correct and complete	The version becomes approved and the profile points to that version
Reject	The submission has fundamental issues	The version becomes rejected and the user sees the rejection reason
Request update	Minor issues or additional information needed	An open update request is created and the profile needs user attention

Reviewing KYC submissions

Access user KYC data

Navigate to Participants > Users and select a user. On the user detail page, find the KYC section in the sidebar or click the KYC status tile.

View submission details

The KYC detail page shows the user's KYC profile and version history. Click a version row to open the version details sheet. The sheet shows:

Personal information such as name, date of birth, country, residency status, and national ID
Uploaded documents with download links
Version status, submission timestamp, and review metadata
Previous review notes, update requests, or rejection reasons when they exist

Review documents

Download and examine each uploaded document. Verify that:

Documents are legible and complete
Information matches the form fields
Documents are current (not expired)
Document types match requirements (government ID, proof of address)

Take action

Based on your review, choose one of the three actions available in the version detail sheet. The action buttons appear only for reviewable versions and only when your role can review KYC versions.

Approving submissions

When a submission meets all requirements:

Open approval dialog

Click Approve in the version detail sheet. The approval dialog opens.

Add optional notes

Enter any internal notes about the approval. These notes are stored for audit purposes. Note: Depending on your organization's configuration, these notes may be visible to the user, so avoid including sensitive internal information.

Confirm approval

Click Approve to confirm. The version status changes to Approved. DALP records the review outcome, review timestamp, reviewer, and optional notes. The user's KYC profile points to the approved version, and open update requests for that user's KYC profile are fulfilled.

After approval, follow Verify KYC to issue the on-chain KYC verification.

Rejecting submissions

When a submission has fundamental issues that require complete correction:

Open rejection dialog

Click Reject in the version detail sheet. The rejection dialog opens.

Provide rejection reason

Enter a clear explanation of why the submission is rejected. This message is shown to the user, so be specific about what needs to change. Minimum 10 characters required.

Example reasons:

"Document is expired. Please upload a current passport or national ID."
"Name on document does not match the name entered in the form."
"Proof of address document is illegible. Please provide a clearer scan."

Confirm rejection

Click Reject to confirm. The version status changes to Rejected and DALP records the review outcome, rejection reason, reviewer, and review timestamp. If the user already has a previously approved KYC version, that approved version remains active; otherwise the profile returns to incomplete.

Requesting updates

When minor corrections or additional information are needed without fully rejecting the submission:

Open update request dialog

Click Request update in the version detail sheet. The update request dialog opens.

Describe required changes

Enter a clear message explaining what the user needs to update or provide. Minimum 10 characters required.

Example requests:

"Please add a proof of address document (utility bill or bank statement from the last 3 months)."
"Date of birth appears incorrect. Please verify and update."
"Please upload the second page of your passport showing the signature."

Submit request

Click Request update to confirm. DALP keeps the reviewed version under review, records the review outcome as Changes requested, creates an open action request, and marks the profile as needing an update. The draft for the user's corrections is created when the user opens the update flow.

Version history

The KYC detail page shows the version history for each user:

Column	Description
Version	Sequential version number
Status	Current status, such as draft, submitted, under review, approved, or rejected
Submitted	When the version was submitted for review
Reviewed	When and by whom the version was reviewed, when review metadata exists

Click a row to view the version details, supporting documents, and review notes.

Choosing the right reviewer action

Situation	Use this action	Why
The data and documents meet your requirements	Approve	The reviewed version becomes the approved KYC profile version
The submission cannot be accepted as provided	Reject	The user gets a rejection reason and must correct the submission
The submission needs specific missing or changed data	Request update	The user gets a targeted action request without losing the review trail

Reviewer actions are available only for versions that are ready for review. Draft versions must be submitted by the user first.

Integration with verification workflow

KYC data management is part of the broader user onboarding workflow:

User completes onboarding - Creates wallet and on-chain identity
User provides KYC data - Fills profile and uploads documents
Identity Manager reviews - Approves, rejects, or requests updates (this guide)
Identity Manager registers user - Adds user to identity registry
Identity Manager verifies KYC - Issues on-chain verification

See Onboarding runbook for the complete workflow.

Best practices

Review consistency

Apply the same standards to all submissions
Document your organization's specific requirements
Consult with compliance team for edge cases

Clear communication

Provide specific, actionable feedback
Reference exact documents or fields that need attention
Explain why information is insufficient and what must change

Timely processing

Review submissions promptly to avoid delays
Use request update for minor issues rather than full rejection
Batch similar reviews when possible for efficiency

Audit trail

Add notes to approvals explaining verification steps taken
Keep records of document verification methods
Maintain consistent documentation standards

Troubleshooting

Issue	Solution
Cannot see KYC section	Verify you have Identity Manager role with KYC read permissions
Cannot download documents	Check browser permissions for downloads. Try a different browser if issues persist.
Approve/Reject buttons disabled	Only submitted or under review versions can be actioned. Draft versions must be submitted by the user first.
User not receiving feedback	Confirm the action completed successfully. Check user can access their profile page.
Cannot find user submission	Use the search function in Participants. Verify the user submitted the profile instead of saving a draft.

Provide KYC Data - How users complete their KYC profile
Register User - Register users in the identity registry
Verify KYC - Issue on-chain KYC verifications after approval
Onboarding Runbook - Complete user onboarding workflow
Configure Trusted Issuers - Set up verification permissions

Manage KYC data