ID Verification
Last updated
Last updated
Copyright © 2024 OpenG2P. This work is licensed under Creative Commons Attribution International LicenseCC-BY-4.0 unless otherwise noted.
Social Registry with MOSIP Token Seeder (MTS) uses MTS Connector to authenticate registrants, who are registered using the ODK Collect App. The Unique ID Number (UIN) and demographic details provided by registrants are verified by calling APIs of the MOSIP ID Authentication (IDA) system. The MOSIP IDA responds with an Authentication Token upon successful verification. MTS is a standalone service offered by MOSIP.
MTS Connectors can take inputs from both ODK Central and Social Registry. Since one MTS Connector takes only one type of input, separate MTS connectors are required for ODK Central and Social Registry.
A high-level representation of the interactions between different components during authentication is shown below:
Verify ID information at the backend by connecting to APIs of the ID system (using MTS connector).
Bulk ID verification.
Tokenize the ID and populate it in Social Registry.
Is ID number by itself considered Personally Identifiable Information (PII) ?
If ID is random, revokable and tokenized (not used for seeding), it is not PII. But if it is codified, used for seeding everywhere and not changeable, then it can be used to identify the person or know something about them