Personal Data Update
A personal data update re-verifies an existing Customer so their stored details can be refreshed from a current document — while biometrically confirming it is still the same person.
When to use it
A Customer's document has been renewed, their name or address changed, or their original data needs correcting. Rather than trusting a self-service form, the Company re-runs verification so the new data is backed by a genuine document and a matching face.
How it works
- Document capture — the Customer photographs their current identity document.
- Face capture & liveness — the Customer takes a selfie.
- Automated checks — document authenticity and OCR, plus a 1:1 face match confirming the selfie belongs to the same person already on file.
- Decision — on success the Customer's personal data is updated and the new attempt becomes their primary identity.
Outcomes
| Outcome | Meaning |
|---|---|
| Updated | Same person confirmed; the Customer's data is refreshed from the new document. |
| Review | Ambiguous — held for an operator decision before any data is written. |
| Rejected | Could not confirm the same person, or the document failed checks. |
| Incomplete | The Customer did not finish. |
Notes
- The face match is against the known Customer (1:1), like authentication, but this flow also captures a document and writes data back.
- Which fields a successful update may overwrite is governed by policy — identity anchors such as date of birth are handled conservatively.
- While an update is in progress, conflicting edits to the same identity fields through the API are blocked to keep the record consistent.