The Virtual NIN is a use-once, user consent token which the Relying Party may use to request for personal information of an individual. The concept remains the same - there must be a prior approval before such a request is approved.
It is recognised, that in the establishment of such new technologies, there may be instances where an individual is incapable, perhaps due to a lost SIM/device or not having a prior MSISDN to generate a vNIN from.
18 JULY 2022: Where the USSD Service, in the absence of a Smartphone which has the NIMC MobileID, is also not available, the following is now possible:
MNOs in Nigeria, who have been licensed by the Federal Government (and are in possession of an EnterpriseID for the Tokenisation Platform), may now be able to request for a Virtual NIN on behalf of a customer by providing the 11-digit RAW NIN of the customer.
It is STRONGLY ADVISED that operators optimise their workflows, to reduce the number of middleware components to the bearest minimum. Where there are several layers in between the NIMC endpoint and the front end CRM Interface, the NIMC shall not be held liable for any latency introduced as a result of these layers outside its control or domain.
RAW NIN : Will be a temporary option, only available until the 30th November 2022. NIN Holder must have previously linkled an MSISDN to their NIN and NIMC be aware of that linkage.
In either case, the AgentID (userID of the agent acting on behalf of the Relying Party), must be included in the payload request. The Super Admin must have previously granted permission to the Agent to act on their behalf.
URL: https://testtk.nimc.gov.ng/api/v1/tokenization/telco/vNIN
Method: POST
Headers
x-api-key: nudjthujPIIi0FnmnYGKaXj1mDWfjhgvjhgj
Request Object
agentID: ABCDEF-8910
RPShortCode: 123456
uin: 12345678910
URL: https://tk.nimc.gov.ng/api/v1/tokenization/telco/vNIN
URL: https://tk.nimc.gov.ng/api/v1/tokenization/telco/vNINGen
As the leading consumers of Verification Services in the country, it has become necessary to develop a suite of services for this industry in particular.
Whilst some of the components contained herein may apply to other industry heavyweights, such as banks and Government agencies, the large majority of these calls, will for now, be limited to Telecoms.
There have been cases where an Identity Holder has visited the premises of an Operator to request for services, the agent representing the operator has sought the ID Holder’s consent (via the issuance of a Virtual NIN token - vNIN), and the system has returned “this vNIN was not issued to your organization”, as an error message.
This is because, by accident or design, the vNIN was not in fact issued to that operator/organization and verification would not be possible.
To this end, the Federal Government has now issued a set of prefixes to each Operator, as contained in the table below.
From the 21st September, 2022, if an agent for an Operator receives a vNIN that DOES NOT start with their respective prefix, it should be rejected outright by the agent and not presented for verification.
Alternatively, the front-end validation process of the CRM of the operator should be updated to watch out for the prefix and reject accordingly where the assigned prefix does not match.
Where neither of these processes takes place, and the vNIN is still sent to the NIMC backend for verification, and it is rejected, the NIMC will bill the operator accordingly.
| Operator | Prefix | Example |
|---|---|---|
| Globacom | GG | GG123456789100JE |
| MTN | MX | MX892754551627FZ |
| Airtel | BH | BH9903645728710B |
| Smile | EC | EC0992837374616R |
| Spectranet | PT | PT877288861209TY |
| 9Mobile | ST | ST882872781173MS |
| Ntel | DN | DN772678166271Z8 |
Due to the possible high demands for API calls and low latency responses, it has become apparent that some (if not all) operators, have implemented automated systems for these API calls using the IDs of Agents.
The Federal Government, in the implementation of the Tokenization process, makes a very clear distinction between Agent Management and Device Management.
From the September 25th 2022, the Tokenization platform will implement rate capping on UserIDs (agent IDs). Where it is found that a UserID makes several calls that are not humanly possible, the agentID will be blocked and the UserID suspended.
Each Operator (and any other organization requiring the use of automated calls for middleware implementations), is required to make a request to the National Identity Management Commission (NIMC), for a deviceID, which will be used for specific calls.
This however, DOES NOT negate the requirement to include the ID of the Agent making the request, as every request still has a natural person behind it. The NIMC needs to know who is doing what and from where.
The distinction is that 100 requests in 60 seconds might have 47 different AgentIDs, but the same deviceID.
The DeviceID takes the format of a 128-bit label, following the specifications of RFC4122.
Response Object
{
"success": true,
"data":
"EUnmRG10BE45G2OBLEADclfQS9FnXyzvBMCkIdxe+CuwtgdZ//8NO+qh+a5d1rj+KMMbOd1hz77i/R4K3kegYhUd5
nnX4exIgeFBTLisoL5oAGHYhvzY+CaVNpCdguNu5XTBWK8A6x3RktiSUIMGaSBZB8rRVWRmcieVq9IK+4sbGlY6b
VS4oaQ6aK7k3m5J+rqj7QNXQwRSAl/OJD+Rt4EFvJ+ivrSQdAzNVe1KVCuvIqSwkqTZwKQ8LgWphT0QUKt0UZDA
QNddnlysXzd7B375iQIcXie7EcilD7oL8LGPAIIJAYGdWqh/Je3OlHxwfvaBmTq4x4t5uUe+2O5PLu6mViGopNNMdTrcq
egYNMTN0G/3bV4jIqwWMxCZnNR5bVFEIfdevYA/GjtQyemPkzjF4UXderVUmb89u9PP0X80mLHrzQeOS0ajAsPktW
Trp9Oe5z90nxSbD3Mxl15CjJyqENgdDsCSfkPABpm0ndS9m19ptPMHx/BuqQsf4RTx"
}
Request Object
-URL: https://testtk.nimc.gov.ng/api/v1/tokenization/telco/device/vNIN
-RPShortCode: 000000
-uin: 00000000000
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52
Response Object
{
"success": true,
"data":
"OzHaxle6UREooR0rbP1D5yIsNv8zN6CH7767bouGUxdsI8MUhHSZVT2Mdo2mv/ZeR4F9okXrrTk3yOtbp9pbB6S6Z
HX/G34aiffBF76Yn4PHEr6an0b4dkbXvw7xMSbb/t+iPG7pP/VCmd4MYG8gj/BAyIzuaWvz/j27wreplFz8VdvaK7cdKQ
Q57cLVizdJGpfYfLVqvtgRXP/EKrO9gz9qO91qu/j4xqK9pq0SxhH2HzD++4ZI7ZZtXx5DvZMXPJ/qmMbNsb+2nyV2Zc
WK+qzI15/xpBGxZBC2UQLg7WvlFVNg/n6RND05tZtH84QeCrX8wXF+XhC9RNJoFUjW5+D6ZBNaPnazlOFhI31nIC
hye9r+tkgAPkihJeywTkv++/zFft8N4JdZwohJ9wvu4FILveQ5r3y2XqeMzRdnd6Q+Ec0EAV7NtiETT/0wJ/Yv5nRUQVPn
kmMazW3m2DzMuLjUbpr1CtCHaFABPz/fOwzI2+JL7m+9ZvRuQ4pj8edK",
"photograph": "/9j/4AAQSkZJRgABAgAAAQABAAD/”
}
Request Object
-URL: https://testtk.nimc.gov.ng/api/v1/apiVerification/enterprise/direct/device/vNIN
-RPShortCode: 000000
-vNIN: MX123456789104PQ
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52
Request Object
{
"success": true,
"data":
"OzHaxle6UREooR0rbP1D5yIsNv8zN6CH7767bouGUxdsI8MUhHSZVT2Mdo2mv/ZeR4F9okXrrTk3yOtbp9pbB6S6Z
HX/G34aiffBF76Yn4PHEr6an0b4dkbXvw7xMSbb/t+iPG7pP/VCmd4MYG8gj/BAyIzuaWvz/j27wreplFz8VdvaK7cdKQ
Q57cLVizdJGpfYfLVqvtgRXP/EKrO9gz9qO91qu/j4xqK9pq0SxhH2HzD++4ZI7ZZtXx5DvZMXPJ/qmMbNsb+2nyV2Zc
WK+qzI15/xpBGxZBC2UQLg7WvlFVNg/n6RND05tZtH84QeCrX8wXF+XhC9RNJoFUjW5+D6ZBNaPnazlOFhI31nIC
hye9r+tkgAPkihJeywTkv++/zFft8N4JdZwohJ9wvu4FILveQ5r3y2XqeMzRdnd6Q+Ec0EAV7NtiETT/0wJ/Yv5nRUQVPn
kmMazW3m2DzMuLjUbpr1CtCHaFABPz/fOwzI2+JL7m+9ZvRuQ4pj8edK",
"photograph": "/9j/4AAQSkZJRgABAgAAAQABAAD/”
}
Request Object
-URL: https://testtk.nimc.gov.ng/api/v1/apiVerification/enterprise/direct/device/vNIN
-integratorShortCode: 123456
-RPShortCode: 000000
-vNIN: MX123456789104PQ
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52
Response Object
{
"success": true,
"data":
"OzHaxle6UREooR0rbP1D5yIsNv8zN6CH7767bouGUxdsI8MUhHSZVT2Mdo2mv/ZeR4F9okXrrTk3yOtbp9pbB6S6Z
HX/G34aiffBF76Yn4PHEr6an0b4dkbXvw7xMSbb/t+iPG7pP/VCmd4MYG8gj/BAyIzuaWvz/j27wreplFz8VdvaK7cdKQ
Q57cLVizdJGpfYfLVqvtgRXP/EKrO9gz9qO91qu/j4xqK9pq0SxhH2HzD++4ZI7ZZtXx5DvZMXPJ/qmMbNsb+2nyV2Zc
WK+qzI15/xpBGxZBC2UQLg7WvlFVNg/n6RND05tZtH84QeCrX8wXF+XhC9RNJoFUjW5+D6ZBNaPnazlOFhI31nIC
hye9r+tkgAPkihJeywTkv++/zFft8N4JdZwohJ9wvu4FILveQ5r3y2XqeMzRdnd6Q+Ec0EAV7NtiETT/0wJ/Yv5nRUQVPn
kmMazW3m2DzMuLjUbpr1CtCHaFABPz/fOwzI2+JL7m+9ZvRuQ4pj8edK",
"photograph": "/9j/4AAQSkZJRgABAgAAAQABAAD/”
}
Request Object
-URL: https://testtk.nimc.gov.ng/api/v1/apiVerification/enterprise/qrCodeVerification/device/direct
-RPShortCode: 000000
-hash: 9be9010b337d6c54a289190d677258aa6dd0e2d6 ||
fc732136f5542705b01f12d676b4ed42bc65d938 ||
1f5aca444552ed0f5b1a0e3bbaa2563f94bb7ab5 || SU572739355475XP
-level: b || f || n || t
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52
Request Object
-URL: https://tk.nimc.gov.ng/api/v1/tokenization/telco/device/vNIN
-RPShortCode: 000000
-uin: 00000000000
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52
Request Object
-URL: https://tk.nimc.gov.ng/api/v1/apiVerification/enterprise/direct/device/vNIN
-RPShortCode: 000000
-vNIN: MX123456789104PQ
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52
Request Object
-URL: https://tk.nimc.gov.ng/api/v1/apiVerification/enterprise/indirect/device/vNIN
-integratorShortCode: 123456
-RPShortCode: 000000
-vNIN: MX123456789104PQ
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52● QR Code Verification with DeviceID
Request Object
-URL: https://auth.nimc.gov.ng/api/v1/qrCodeVerification/device/direct
-RPShortCode: 000000
-hash: 9be9010b337d6c54a289190d677258aa6dd0e2d6 ||
fc732136f5542705b01f12d676b4ed42bc65d938 ||
1f5aca444552ed0f5b1a0e3bbaa2563f94bb7ab5 || SU572739355475XP
-level: b || f || n || t
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52
Request Object
-URL: https://auth.nimc.gov.ng/api/v1/qrCodeVerification/device/direct
-RPShortCode: 000000
-hash: 9be9010b337d6c54a289190d677258aa6dd0e2d6 ||
fc732136f5542705b01f12d676b4ed42bc65d938 ||
1f5aca444552ed0f5b1a0e3bbaa2563f94bb7ab5 || SU572739355475XP
-level: b || f || n || t
-deviceid: 06e2d108-2dd9-11ed-b14d-265bfdfa7a52