I am curious about the ability to validate that the Uganda National Identification Number (NIN) is well formed. However this does not validate that the NIN actually belongs to the person presenting it or that it is correct.
The rules that I have been able to gleam are:
- Must be 14 characters long
- First character is a letter of the alphabet. C seems to be a common letter – does it stand for citizen?
- Second letter is either M or F – male or female
- Characters 3 and 4 are numbers, which are the year of birth. Cannot be after 00 since that would make a person below 18
- Characters 5, 6, 7 are numbers
How can you help? Which of these rules do not match your NIN? Share any additional patters to build a repository of rules that can later be mapped to programming language validations – Regular expressions and validation frameworks
Posted by Eisah KM on March 2, 2018 at 16:05
1. TRUE
2. FALSE: P
3. TRUE
4: TRUE
5. TRUE
6. Last 2 are letters
LikeLike
Posted by ssmusoke on March 2, 2018 at 16:14
What does P represent?
LikeLike
Posted by J. W. Lutalo on March 6, 2018 at 07:56
Yep, being able to parse and validate the NIN would be a great idea. Thanks for sharing.
LikeLike
Posted by mcnemesis on March 6, 2018 at 07:58
Great Idea. Thanks for sharing. Also, more interestingly, I wonder if at a later date, we’ll be able to easily query an “externally” available NIN database, where for example cross referencing with MSISDNs is possible. That’d open up some new validation frameworks and KYC possibilities currently difficult to pull off.
LikeLike