Read a Lukki KYC Status Before Taking Action
The status label is the starting signal. Queued means no decision has been issued; resubmission required means the reviewer found a defined defect; profile review points to account data rather than image quality. Preserve that distinction so unnecessary uploads do not reset the evidence trail.
Read the Lukki verification statusClassify the status message
Copy the exact label, timestamp and document category. Ask for the internal reason category when the message is generic, and distinguish an unreadable image from an expired record or an account-data discrepancy.
Follow the matching correction
For image quality, create a clearer capture of the same valid record. For expiry, select a newer accepted record. For profile data, request an account correction path instead of producing a different document that repeats the conflict.
Keep the queue chronology
Retain each upload receipt and decision in order. Refer to the existing case when sending the corrected item, then record the final state so an older rejection is not mistaken for the current outcome.
Frequently asked questions
Does queued mean rejected?
No. It means a decision has not yet been issued.
What if no rejection reason is shown?
Ask authenticated support for the reason category before uploading more records.
Will repeated uploads speed the queue?
Not necessarily; they can create duplicates or reset the review trail.
Last reviewed: 8 August 2026