The problem
Onboarding still depends on someone reading a passport or license photo and typing the name, document number, and expiry into a form. A blurry image or a missed expiry date stalls the account, and the original image is easy to lose.
How the workflow runs
Upload the ID
The applicant or an operator submits an ID image plus applicant details. The run starts from that hosted form.
Extract identity fields
An extract agent reads the passport or license for name, document type, document number, and expiry. Those fields land on the results table next to the image.
Confirm before you rely on them
The starter extracts. It does not call an external identity bureau. Add a human review step on the canvas when a person must confirm the image matches the applicant.
What the hosted app shows
The KYC desk shows the upload, applicant form, run status, extracted fields, and the ID image. Verifiers work the exception on that page instead of a shared drive.
Who it is for
Fintech, lending, and operations teams that collect government IDs and need the identity fields in a run their staff can verify.
Questions
It extracts the fields printed on the document. A person, or a review step you add, confirms them. The starter does not perform a bureau check.
Passports and driver’s licenses are the intended uploads. The extract step is aimed at identity fields such as name, document type, and expiry.
Use this starter for the ID itself. Loan processing and mortgage underwriting cover the rest of the application packet.