Article7 min readUpdated
KYC Flow Design: Document Upload and Photo Capture
KYC flow design for Indian apps: steps, the document upload screen, photo capture guidance and rejected document messages, with example wording.
A user opens a loan app, taps Verify now, and is asked to photograph a PAN card in a dim room. The photo is blurred. The app says "Verification failed". The user closes the app and never comes back. Most of that loss comes from design, not from the user.
KYC means Know Your Customer. It is the step where an app checks who a user is, usually with an ID document and a selfie. KYC flow design is the work of making that check short, clear and recoverable. The business decides which documents and checks are needed. It must confirm those with its compliance or legal adviser. I design the screens around those decisions.
How many steps should a KYC flow have?
A KYC flow should have only the steps the business's rules need, and the user should see the full list before starting. A typical flow has 6 screens, shown as a numbered list on the first screen.
- Why we ask: one short reason and the time it takes.
- Choose a document: a list of accepted documents.
- Capture the front of the document.
- Capture the back, if the document has one.
- Take a selfie.
- Review and submit, then see the status.
Show "Step 2 of 5" at the top of each screen. Show the total at the start, so nobody feels the flow keeps growing. For the general rules of first-run screens, see my post on app onboarding UX. For where KYC sits in money apps, see fintech app UI/UX design in India.
Place KYC as late as the product allows. Let a person look around first. Ask for identity proof at the moment it becomes necessary, for example before a first withdrawal or before listing a product.
What should the document upload screen show?
The document upload screen should show which document is needed, how to capture it, and what happens to the file afterwards. Keep the screen light, because the user is about to use the camera.
Include these elements, from top to bottom:
- A title that names the document: "Upload the front of your PAN card".
- A sample picture of a good photo, with a tick, and one of a bad photo, with a cross.
- Two buttons: "Take a photo" as the main action and "Choose from gallery" as the second.
- A line of reassurance: "We use this only to verify your identity."
- A link to the privacy notice, in plain words.
- A line of accepted formats and size, such as "JPG, PNG or PDF, up to 5 MB". The real limits come from your developer.
Many people in tier-2 and tier-3 cities keep document photos in their gallery or on WhatsApp. Offer the gallery choice. Do not force a live photo unless the business requires it.
Do not ask for a document the user cannot find. If two documents are accepted, show both as equal options with plain names, not codes. If the business supports regional languages, label document names in the user's language too.
How do you guide photo capture on a mid-range phone?
Photo capture guidance works when the camera screen tells the user what to fix while they are still holding the phone. The most useful tools are a frame, live hints and a clear preview.
- A frame overlay. Draw a rectangle in the shape of the document. Write inside it: "Fit the card inside the box".
- Live hints. Show one hint at a time at the top: "Move closer", "Too dark, find more light", "Hold still".
- A flash toggle. Keep it visible, because many users shoot in poor light.
- A preview step. After the shot, show the photo large with two buttons: "Use this photo" and "Retake". Add a line: "Can you read every number?"
- Selfie guidance. Use an oval frame and short instructions: "Look straight at the camera. Remove your cap or glasses if they hide your face."
Keep hints short. A user holding a phone in one hand cannot read three lines. Put the capture button within thumb reach.
On a seller app I designed for a marketplace in Tanzania, verification was one of the most careful flows in the product. Sellers use many kinds of phones, so the guidance had to work without clever tricks: plain frames, plain words and a retake always one tap away. The same rule applies on slow networks. Compress the photo on the phone before upload where your developer can, and read designing for low-end phones and slow networks.
How should you write a rejected document message?
A rejected document message should name the exact problem, say what to do next, and offer a retry in one tap. "Verification failed" is the worst possible message, because the user cannot act on it.
Group reasons into a small set that your verification vendor or team can really return. Then write one message for each.
| Reason | Message example | Action button |
|---|---|---|
| Blurred photo | "We could not read the number. Take the photo again in good light." | Retake photo |
| Cut-off edges | "Part of the card is missing. Place all four corners inside the box." | Retake photo |
| Wrong document | "This looks like a different document. Please upload your PAN card." | Choose document |
| Expired document | "This document has passed its end date. Please upload a valid one." | Upload another |
| Name does not match | "The name on the document does not match your profile. Check your name or upload another document." | Edit name |
| Needs manual check | "We are checking your document. This can take up to 24 hours. We will send you a message." | Back to home |
Do not blame the user. Write "We could not read", not "You uploaded a bad photo". Do not say "fraud" or "suspicious" in a message to a person who may have simply taken a poor photo. Do not promise a time that the business cannot keep. For wording rules, see UX writing and microcopy for apps.
Show the rejected photo as a small thumbnail beside the message, so the user sees what the system saw.
What states does every KYC screen need?
Every KYC screen needs a state for each moment the user can be in, not only the happy path. Missing states are where people get stuck.
- Not started: a clear first screen and a "Start" button.
- In progress: a saved draft. If the user leaves at step 3, bring them back to step 3 with "Continue where you left off".
- Uploading: a progress bar and a "Cancel" option.
- Upload failed: "The upload stopped because the network dropped. Try again." with a Retry button. The file stays selected.
- Under review: a status screen with a time estimate that the business can honestly meet, and a promise of a notification.
- Approved: a short confirmation and the next action, for example "Add money" or "List your first product".
- Rejected: the reason, the fix and a retry, as above.
- Expired or needs update: a calm prompt with the reason and a deadline, if the business has one.
- Camera permission denied: an explanation and a button to open settings.
For the waiting and failure screens, my post on empty states, loading and error screens goes deeper.
What mistakes make people abandon KYC?
People abandon KYC when the flow feels long, unsafe or unfixable. These are the mistakes I check first in any audit.
- Asking for every document up front, before the user sees any value.
- Hiding the number of steps.
- Forcing a live camera shot when a gallery photo would do and the rules allow it.
- Using a camera screen with no frame, no hints and no retake.
- Showing a single "Failed" message with no reason.
- Losing the uploaded files when the app closes.
- Collecting more data than the business needs. Every extra field needs a reason that someone can explain.
- Skipping the privacy line near the upload button.
- Leaving the user in "Under review" with no end date and no notification.
Remember that the rules for what you may collect, how long you keep it and who may see it belong to the business and its advisers. Confirm them before design starts, so no screen has to be rebuilt later.
If your app needs a verification flow that people can finish, my mobile app design service covers flows like this, or you can write to me through the contact section.
Frequently asked questions
How long should a KYC flow take for the user?
+
Aim for the shortest flow the business's rules allow, and tell the user the time on the first screen. Keep each step to one task so the whole flow feels light.
Should the app let users upload from the gallery?
+
Many users keep document photos in their gallery, so offering it helps. Whether it is allowed for your product is a rule the business must confirm with its compliance adviser.
What should the screen say while a document is under review?
+
State that the check is in progress, give an honest time estimate, and promise a message when the result is ready. Offer a way back to the app so the user is not stuck.
Can a designer decide which documents to ask for?
+
No. The business decides with its compliance or legal adviser. The designer shapes the order, wording and states of the screens around that decision.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.