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 inspect submitted KYC versions and check supporting documents before issuing an on-chain KYC verification. Use this guide when a user has submitted KYC data and a reviewer must approve, reject, or request changes.

Prerequisites

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

About KYC management

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.

Three decisions apply to versions under review.

Decision	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	DALP creates an open update request and marks the profile for 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 includes personal information (name, date of birth, country, residency status, national ID), uploaded documents with download links, version status, submission timestamp, review metadata, and any previous review notes, update requests, or rejection reasons.

Review documents

Download and examine each uploaded document. Check that documents are legible, current, and complete. Confirm that the information matches the form fields and that document types meet requirements (government ID, proof of address).

Choose a reviewer decision

Based on your review, choose one of the three reviewer decisions available in the version detail sheet. The decision buttons appear only for reviewable versions and only when your role permits KYC review.

Approving submissions

Use this flow when a submission meets all requirements and you are ready to issue an on-chain verification.

Open approval dialog

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

Add optional notes

Enter any internal notes about the approval. DALP stores these notes for audit purposes. Depending on your organization's configuration, the notes may be visible to the user, so keep them free of sensitive internal detail.

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 DALP fulfils any open update requests for that profile.

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

Rejecting submissions

Use this flow when a submission has fundamental issues that require complete correction before you can proceed.

Open rejection dialog

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

Provide rejection reason

Enter a clear explanation of why you are rejecting the submission. DALP shows this message to the user, so be specific about what needs to change. The field requires at least 10 characters. 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. 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

Use this flow when the submission is close but needs minor corrections or additional information. This preserves the review trail without a full rejection.

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. The field requires at least 10 characters. 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 outcome as Changes requested, creates an open update request, and marks the profile as needing correction. DALP creates the draft for the user's changes when the user opens the update flow.

Version history

The KYC detail page shows the version history for each user. Click any row to view that version's details, supporting documents, and review notes.

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

Choosing the right reviewer decision

Match the situation to the decision that fits it best. Decisions apply only to versions ready for review. Users must submit draft versions before a reviewer can act on them.

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

Integration with verification workflow

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

The user completes onboarding: creates a wallet and an on-chain identity.
The user provides KYC data: fills the profile and uploads documents.
The Identity Manager reviews the submission and approves, rejects, or requests updates (this guide).
The Identity Manager registers the user in the identity registry.
The Identity Manager issues an on-chain KYC verification.

See Onboarding runbook for the complete workflow.

Best practices

Consistent, well-documented reviews reduce re-work and support audit readiness. Apply the following standards across all submissions.

Review consistency

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

Clear communication

Provide specific, targeted 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 practical for efficiency.

Audit trail

Add notes to approvals explaining the verification steps you took.
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 reviewed. Draft versions must be submitted by the user first.
User not receiving feedback	Confirm the reviewer decision completed. Check that the 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
KYC reviewer version decisions - Approve, reject, or request changes through the API

Manage KYC data