Most Failed Verifications Are Photography Problems
Sit with any compliance team’s rejection queue and count the causes: glare across the photo, a corner cropped off, fingers over the document, an expired license, a selfie taken in a dark room. Fraud is rare. Bad capture is constant. Which means the highest-leverage improvement in any identity pipeline is not better reviewers — it’s a form that teaches the capture standard before asking for the document.
This form is that standard, operationalized. It belongs wherever identity gets verified — account openings, rentals, memberships, age-gated services — and it works because it explains each rule while enforcing it.
The Document Standards, Stated Before the Upload
Each requirement carries its reason in one line, because a rule with a reason gets followed:
- All four corners visible — reviewers verify authenticity from the edges and security marks.
- No glare — reflections destroy exactly the features the check reads.
- Flat on a plain surface — warped documents fail automated reading.
- Both sides, uploaded separately — the security features live on the back, and the dedicated second upload field prevents the two-sides-in-one-photo compromise.
- Current, not expired — stated with the expiry date field beside it, so the declaration and the document can be compared at a glance.
The Selfie, Explained
The liveness capture exists to answer one question: is the person holding this document the person in it? The form says so — because applicants who understand the purpose take usable selfies, in plain light, against a plain background, without the filter they forgot was on. The instruction line is short and the payoff is measured in avoided re-review cycles.
Declared Details Match the Document
The name and birth date fields carry one instruction that prevents the most common manual-review trigger: type them exactly as printed on the document — including middle names, hyphens, and accents. The declared details and the captured document are designed to be compared mechanically; every small mismatch between them becomes a human task.
Consent With Purpose
The closing acknowledgment states what verification actually involves — which checks run, what’s retained, for how long — in plain sentences. Verification consent that names its purpose survives scrutiny; blanket consent doesn’t.
A Component, Not a Product
This form is built to be dropped into other flows: duplicate it into an account-opening journey, a rental application, a member onboarding. Take a preview on an actual phone before each deployment — capture standards live or die on real cameras. Verification results route onward through webhooks to whatever review queue sits downstream.
Frequently Asked Questions
Why both sides of the ID?
Machine-readable zones and security features are printed on the reverse of most documents — a front-only check verifies half a document. Separate fields per side keep both captures usable.
My legal name changed and my ID shows the old name. Now what?
Capture the ID as it is, and add the change document — marriage certificate, legal name change — as a supporting upload. The declared-details rule stays: type what the ID says, explain the difference in the note field.
Is the selfie stored alongside the documents?
Per your retention policy — which is exactly what the consent text should state. The form captures consent to your stated practice; it doesn’t set the practice.
Does a digital check replace in-person verification?
Where your regulatory framework permits remote verification, yes — and the form’s structure supports it. Where in-person is required, this form becomes the pre-visit capture that makes the appointment short.