The KYC Document Quality Checklist Reviewers Actually Use in 2026

The single largest cause of avoidable KYC rejection in 2026 is not fraudulent intent. It is document quality that falls below the threshold the reviewer's queue is calibrated to accept. The same passport, the same selfie, the same proof of address can pass one reviewer's evaluation and fail the next reviewer's evaluation simply because of details of the capture environment that the submitter never considered. This piece documents the specific criteria that reviewers actually apply, written from conversations with current and former reviewers across multiple major KYC vendors.

The criteria are unglamorous and largely a matter of preparation rather than of technique. An operator who reads the checklist, prepares the capture environment accordingly, and submits documents that meet the criteria on the first attempt achieves dramatically higher first-pass approval rates than the operator who submits whatever the phone camera produced and hopes for the best. The reviewers are not adversaries. They are queue operators with metrics, and meeting their metrics is the discipline that produces accepted documents.

The single most common rejection reason is glare on the document. A document held under direct overhead light produces reflections from the plastic coating that obscure text and obscure the security features the reviewer needs to inspect. The reviewer cannot validate what they cannot see, and the default decision in the absence of clear validation is rejection.

The capture environment that consistently passes is even, diffuse lighting from above and slightly in front of the document, with no direct light source between the camera and the document surface. A window during daylight hours, with the document held parallel to the window plane, produces nearly ideal conditions. A controlled indoor environment with a diffused light source — a softbox, a large lampshade, a sheet of paper held over a bright lamp — produces equivalent conditions. The phone flash is almost always the wrong choice; the direct flash produces hot spots that obscure exactly the features the reviewer needs to inspect.

The second most common rejection reason is insufficient focus on the document text. The reviewer needs to read the text on the document — the name, the date of birth, the document number, the expiry date — and the reviewer's queue tools enlarge the image to perform the reading. An image that appears sharp at the original capture size frequently becomes unreadable at the enlargement, and the reviewer marks it for resubmission rather than spending time trying to interpret the unclear text.

The capture discipline that solves this is to hold the camera at the minimum focus distance of the camera, to allow the autofocus to settle on the text before capturing, and to use the camera's full resolution rather than a reduced-resolution setting. Most modern smartphones produce images that are more than sufficient at full resolution and at minimum focus distance. The error is in capturing at greater distance, with the autofocus drifting, or with the resolution reduced to save storage. None of these economies make sense in a context where the cost of a rejection is dramatically higher than the cost of a larger file.

The background of the document capture matters more than most submitters realize. A document captured on a dark, plain background is dramatically easier for the reviewer to evaluate than a document captured on a busy surface like a patterned tablecloth or a desk covered with other papers. The reviewer's tools include edge-detection algorithms that identify the document boundary, and a busy background interferes with the edge detection, which in turn slows down the reviewer's processing and increases the rejection rate.

The recommended background is a plain dark surface — a black mat, a dark wooden table, a sheet of dark construction paper. The document should fill most of the frame but not extend to the edges; a small margin of background around the document allows the edge-detection algorithm to work cleanly. The contrast between the document and the background should be substantial, and the lighting should produce no shadow from the document onto the background that interferes with the edge detection.

The document itself must be in a state that allows clean review. A document with a folded corner, a coffee stain, a crack across the plastic coating, or a peeling laminate produces an image that the reviewer must spend time interpreting, and the time pressure of the queue often produces a rejection in favor of a cleaner resubmission. The discipline is to inspect the physical document before capture, to flatten any folds, to clean any smudges, and to ensure that the security features are clearly visible.

The unscaled question is whether the image has been edited in any way before submission. Most KYC platforms run image-forensics algorithms that detect the signatures of common editing operations — resizing, sharpening, color adjustment, even compression and recompression. Any of these detection signals can trigger an automatic rejection or an escalation to a more careful manual review. The discipline is to submit the unedited capture directly from the camera. Resist the temptation to crop, brighten, or sharpen the image. The original capture, properly composed, is what the platform wants.

The selfie that accompanies the document is subject to its own set of criteria, separate from but related to the document criteria. The face must be centered in the frame, evenly lit, with no shadow from the brow obscuring the eyes and no shadow from the chin obscuring the lower face. The expression should be neutral. The eyes should be open and looking directly at the camera. The head should not be tilted in any direction.

Most platforms now incorporate a liveness layer that requires the user to perform a specific action during the selfie capture — turning the head, blinking, smiling, or following a moving target on the screen. The action is detected by the platform's algorithm rather than by the human reviewer, but a poorly captured liveness sequence — too fast, too slow, partially out of frame, with the head leaving the frame during the action — can trigger an automatic rejection that the human reviewer will not override. The discipline is to follow the instructions precisely, to keep the face centered throughout the action, and to perform the action at the speed the platform expects.

The proof of address is the document that most often triggers a second rejection after the primary identity document has been accepted. The platforms have specific requirements for the address proof that submitters frequently miss: the document must be dated within a specified window (typically 90 days), it must show the full name as recorded on the identity document, it must show the full address, and it must be issued by an institution the platform recognizes as authoritative for address verification in the relevant jurisdiction.

The institutions that count vary by jurisdiction. A utility bill is universally accepted. A bank statement is universally accepted. A government correspondence (tax notice, voter registration, council letter) is universally accepted. A mobile phone bill is sometimes accepted and sometimes rejected. A magazine subscription is rarely accepted. The submitter who does not check the platform's documentation in advance frequently submits the wrong document type, triggering an avoidable rejection.

The identity document must be valid on the date of submission. A document that has expired, or a document that will expire within a window the platform considers too short (typically 30 days), is rejected. This is a particularly common failure for operators submitting documents that were captured in advance and are being submitted on a delayed timeline. The submitter looks at the document and sees a valid future expiry; the platform looks at the document and sees that the captured date was many months ago, and the expiry window may have passed since.

The discipline is to capture the document fresh for each submission, to verify the expiry date against the submission date, and to plan submissions to occur well before the expiry window would otherwise be triggered. The cost of the discipline is minor. The cost of a rejection driven by a stale or near-expiry document is dramatically larger.

For higher-tier verifications, the platform may require a live video interview with a compliance officer. The interview is typically brief — five to ten minutes — and consists of confirmation of the identity document, confirmation of the address, and confirmation of the purpose of the account. The criteria the interviewer applies are similar in spirit to the document-review criteria but applied to a live setting: clear video, good audio, a controlled environment with no other people visible in the frame, and an interviewee who can answer the questions confidently without long pauses or signs of consulting an off-camera source.

The preparation discipline is significant. Test the video and audio setup in advance. Choose a quiet, well-lit, plain-backgrounded environment for the interview. Have the identity document physically available for re-confirmation during the interview. Be prepared to describe the business and the intended use of the account in plain, concise terms. The interview is not adversarial, but it is consequential, and the operator who prepares for it as they would prepare for any meaningful customer interaction passes at materially higher rates than the operator who treats it as a routine bureaucratic step.

A final operational consideration is the submission cadence. Platforms process verification submissions in queues, and the queue dynamics affect both the speed and the strictness of the review. A submission made during the platform's peak hours — typically late morning in the platform's primary operating timezone — is reviewed quickly but is subject to faster decisions that may favor rejection in ambiguous cases. A submission made during off-peak hours is reviewed more slowly but is often reviewed more thoroughly, with the reviewer having time to make a more nuanced judgment in ambiguous cases.

The operator with a high-quality, unambiguous submission should submit during peak hours to get the fast decision. The operator with a submission that may have some ambiguity — an unusual address format, a recently issued document, a name that has changed for legal reasons — should submit during off-peak hours to get the more careful review. The discipline of matching the submission to the queue dynamics is small in absolute terms but compounds across the cumulative volume of submissions an operator processes over time. The reviewer is not the obstacle. The reviewer is the partner whose criteria can be met with preparation. The operator who prepares passes.