Manual verification

Some checks normally ask an official registry (the income-tax PAN service, a penny-drop bank check, the GST portal, MCA, Udyam). Until a registry provider is connected, OKYC routes these checks to the manual provider: the applicant enters the number and uploads a supporting document, and a reviewer confirms it.

Everything else needs no external service and runs automatically: Aadhaar Secure QR and Offline XML (signature verified), selfie liveness, face match, document reading, sanctions screening, name and date-of-birth matching.

What the applicant seesCopy Anchor Link

The step shows the usual fields plus an upload. When several documents are accepted (bank account), the applicant picks one first. The document is read automatically so the reviewer doesn't have to type anything.

After submitting, the step shows Submitted for review and the applicant continues with the next step: a check waiting for a reviewer never fails the step or uses up attempts. The same applies when an uploaded document can't be read automatically — a reviewer looks at it.

What happens to the sessionCopy Anchor Link

• A manual check stays inconclusive with provider: "manual" until a reviewer decides. The session goes to review with the reason manual_verification — it is never approved automatically.
• Rules are evaluated as if the pending manual checks were confirmed. So a session is still declined automatically for things a reviewer's confirmation can't fix (a face mismatch, a failed Aadhaar check), and a rule like "PAN not passed → decline" does not decline a session only because the PAN is waiting for review.
• A workflow without manual checks (for example Aadhaar + selfie + sanctions) is still decided automatically.

ReviewingCopy Anchor Link

On the session page, Manual verification lists each check with the uploaded document and a side-by-side comparison: what the applicant entered, what the document says, and whether they match. The name printed on the document is also compared with the identity verified from Aadhaar. Values are shown masked, as everywhere else.

• Confirm marks the check passed. The values printed on the (possibly corrected) document become the check's result — the name and date of birth on a PAN card, the account holder on a cheque — so matching and rules treat it like a registry answer.
• Reject marks it failed, with a reason: document doesn't match, unreadable, wrong or invalid document, suspected fraud, or other.
• A misread value can be fixed first with a reviewer correction.
• Approve is disabled until every manual check is confirmed or rejected; the API refuses it with manual_checks_pending. Decline and "request resubmission" are always available.
• Like corrections, reviews are allowed only before a final decision, and are recorded in the audit log (check.manual_confirmed / check.manual_rejected) without any values.

In the API and webhooksCopy Anchor Link

Every check has verified_by:

Use it if your own policy treats reviewer-verified data differently from registry-verified data.

Adding a registry integration laterCopy Anchor Link

This is a configuration change on your account, not a code change. A check can be routed to a registry first, with manual as the fallback — for example PAN through your aggregator. Ask us at [email protected] to set one up. From then on:

• the step no longer asks for the document;
• the registry answers the check (verified_by: "source");
• if the registry is down, the check falls back to manual review instead of failing.

Live mode never uses the mock provider, whatever the routing says. Test mode behaves like live: checks routed to manual are manual in test sessions too; checks routed to a registry use the magic values instead. To try the reviewer's side, use Use test data on the step: it submits the value with a sample document (e.g. a sandbox PAN card) whose fields are read back for the side-by-side view.

Integrations that live sessions needCopy Anchor Link

The workflow builder shows a warning on these steps, and a Manual review badge on steps that will be verified manually.

ErrorsCopy Anchor Link