Person data mapping
Collect and map identity fields to Person data through a User questionnaire step.
How it works
Person data fields — such as name, date of birth, and personal number — are normally populated automatically via the ID document step through OCR, MRZ, NFC, or QR/Barcode extraction. Person data mapping allows clients to populate these same fields through a User questionnaire step instead, covering flows where document scanning is not required or where the client already holds some of the applicant's data.
When mapping is enabled on a User questionnaire step, individual questions can be linked to specific Person data fields. Answers submitted by the applicant populate those fields in the session's Person data section and become available for downstream identity verification checks.
This is a general-purpose feature and is not tied to any specific verification provider.
Field sources and precedence
Person data fields can originate from multiple sources within the same session. Each field displays a source tag so operators can identify where the value came from:
OCR / MRZ / NFC / QR
Extracted automatically from the document via OCR, MRZ, NFC, or QR
User review
Edited by the applicant during document data review after scanning
User input
Entered by the applicant in the User questionnaire
Client provided
Preset by the client via API or Configuration before the session started
Operator
Entered or corrected by the operator during review
When a session includes both an ID verification step and a mapped User questionnaire step, the following precedence applies:
Document data takes precedence over questionnaire-mapped values for any overlapping field.
Fields not populated by the document step are filled from the questionnaire-mapped values.
Both values are stored and visible in session details.
Field change history is accessible via tooltip on each field and is preserved across all edits for audit purposes.
Session routing
Sessions with "Map to Person data" enabled are automatically routed to Manual check on completion, regardless of other step outcomes.
Enabling the feature
How to enable: Turn on Map to Person data in the User questionnaire step settings in the Configuration builder.
When enabled, a Person data field selector appears beneath each compatible question. Not every question needs to be mapped — mapping is optional per question.
Compatible question and field types:
Short answer (Free text or Number)
First Name, Last Name, Middle Name, Father's Name (Eng./Local), Place of Birth, Document Number, Personal Number, Authority, Address, State
Date
Date of Birth, Document Expires On, Document Issuing Date
Radio
Sex
Dropdown
Citizenship, Nationality, Document Issuing State
Checkbox, File Upload, and Attachment question types cannot be mapped to Person data fields.
A Person Data field can only be mapped to one question within the same configuration.
Last updated
Was this helpful?