Wage Disbursement Project - TSOnline · Wage Disbursement Project ... (1W Speaker Supporting MP3...
Transcript of Wage Disbursement Project - TSOnline · Wage Disbursement Project ... (1W Speaker Supporting MP3...
Wage Disbursement Project (Aadhaar Authenticated Benefit Disbursement)
NEFMS & NON_NEFMS User Operational Manual Version 1.0
1
Aadhaar authenticated Benefit Disbursement Introduction
APOnline designed and developed an ICT system for Mahatma Gandhi National Rural Employment Guarantee Act
(MGNREGA) in Andhra Pradesh state to ensure payments to wage seekers and pensioners who are enrolled into this
Government program. This project is implemented in association with Department of Posts and Commissioner of Rural
Development. The Biometric Authentication is ensured using Aadhaar Numbers of the beneficiaries.
Several thousands of wage seekers and pensioners have enrolled and their wages are paid after proper authentication.
This process ensures payment of entitled wages to the right beneficiary within the stipulated payment disbursement
cycle, which fulfills the core objective of the government for disbursement of wages to the right beneficiary in time
according to the Mahatma Gandhi National Rural Employment Guarantee Act-2005.
The core objective of this project is:
To reduce the time taken to disburse the funds to enrolled beneficiaries.
To avoid fraudulent activites in the current process.
To ensure whether the amount is disbursed to right Beneficiary through AADHAAR based authentication
using POS device by allowing minimum exceptions.
Roles of stakeholders
APOnline is responsible for design, development, deployment and maintenance of the technology solution.
Department of Posts(DoP) is responsible for disbursement of wages and pensions.
CRD-GoAP is responsible for making the funds available for the disbursement of wages/pensions.
Salient features of the POTD
Full-fledged micro-computer (ARM9 32 bit Core CPU @ 400MHz).
Simplicity of use (Interactive touch screen & rich GUI).
Biometric authentication (ANSI 378/ISO 19794-2 minutia support).
Secure flexible connectivity (Wireless and Wire-line).
Keypad (19 keys including 4 function keys and 3 command keys with LED Back lighting)
Speaker (1W Speaker Supporting MP3 and WAV Files)
Inbuilt Thermal graphic printer; 8 dots/mm: 57mm (2.25 in.) wide paper
2
1. Benefit Disbursement System Device
1.1 Getting Started:
Switch on the terminal button which is provided near the GSM Antenna inlet. Press and release the button to start the
POTD.
Fig 1.1: Benefit Disbursement System Device
Device gets started and the following screens will be displayed.
Fig 1.2: Booting & Loading of Ram disk
The device automatically completes the start-up processes such as loading Ram Disk, processing the SD Card etc and
the application will get started automatically by displaying the home page with application version number. By
selecting the “Enter Key” from the keypad Login Screen will be displayed.
3
2. Benefit Disbursement System Application
2.1 Process flow Diagram:
Fig 2.1 Process Flow Diagram
2.2 Home Page:
After displaying the Application Home Screen it prompts for BPM (Branch Post Master) Authentication. BPM needs to
input the entrusted User Id. Home page will be as below.
Fig 2.2: Home Page of Application
4
2.3 User Login:
After displaying the Application Home Screen it prompts for BPM (Branch Post Master) Authentication. Once the user
ID is entered, it connects to server to fetch UID of the entered User ID. If entered User ID is wrong it displays on
screen as “Invalid User Id” and then press enter, it will again ask for User Id. If entered User Id is Correct then it
connects to Server and gets details from server.
Fig 2.3: User Login Flow
With UID and BFD:
When the entered User ID has both UID and BFD, UID number and mode of authentication are displayed (Finger & IRIS).
User needs to select either 1.Finger or 2. IRIS
On selecting Finger, POTD prompts for Best finger verification (3 attempts) and connects to AADHAAR server. Once the
5
verification is successful, success message is thrown and Main Menu is displayed. On selecting IRIS, POTD prompts for
IRIS authentication (six attempts in the order of left eye and right eye thrice) and connects to AADHAAR server for
verification. Once the verification is successful, success message is thrown and Main Menu is displayed.
AADHAAR Authentication Failed:
If AADHAAR authentication (both Finger and IRIS) is failed, error message is thrown and prompts for local verification
(three attempts). Once the local authentication is successful, success message is thrown and Main menu is displayed.
With UID and without BFD:
If UID exists and BFD not yet done then it prompts for capturing the finger prints (Minimum of 6 and Maximum of 10) for
finger Ranking based on NFIQ score. The process of NIFQ as below
Note: NFIQ is a test which checks the quality of finger print imposed. NFIQ ranks the finger print quality with scores
between 1 & 5 .If the scores are 1/2/3 then the FP Quality is good then it moves to the next finger else if scores are 4/5 it
prompts for the same finger. In case of failure NFIQ asks for the same finger another time. Even if fails it goes to the next
finger automatically. After successful BFD, a success message is displayed and ranking wise FP receipt will be
generated automatically and the above step (“With UID and BFD”) gets executed.
If BFD fails, a fail message is displayed and reason for failure is also displayed in Action wise receipt which will be
generated automatically.
UID not Seeded:
If the BPM is not AADHAAR enrolled, it prompts for local authentication directly. If the local verification is successful,
Success message is thrown and Main menu is displayed.
2.4 Application Mode Selection Page:
After successful authentication of BPM, then application displays for mode selection-NeFMS & Non-NeFMS as
shown in the below image
Fig 2.4: Application mode selection
If User clicks on NeFMS , then screen will be redirected to NeFMS related services
If User clicks on Non- NeFMS, then screen will be redirected to Non-NeFMS related services.
2.5 NEFMS Main Menu:
On selecting any NEFMS option, the following six options i.e., Operator Options, Admin Options, Reports, Shut
Down, Version Details and Selfdiag Test will be displayed. (Fig 2.4.0)
6
Fig 2.4.0: Main Menu-NEFMS
Press Cancel (X) button from the main menu. Application will be exited upon confirmation. (Fig 2.4.1)
Fig 2.4.1: Exit from the Main Menu
2.5.1 Operator Options:
Operator Options consists of three options i.e., NREGS Services, BFD & RTS.
Fig: Operator Menu Screen
2.5.1.1 .1 NREGS Services:
Using this option operator can avail the services related to NREGS Wage seekers, such as Withdrawal through Account
number, Balance Enquiry, Mini Statement, Zero Bal Enquiry, Last Trans Receipt, Capture Remarks and Pass Book
Update.
7
Fig 2.4.2.1.0: NREGS Services Menu Screen
Withdrawal can be done in by account number in NREGS services mentioned below.
Fig 2.4.2.1.1: Withdrawal with account number
8
2.5.1.1.2 Withdrawal with Account Number:
9
10
Fig 2.4.2.1.2: Withdrawal with ACC flow
Note: 1. NFIQ is a test which checks the quality of finger print imposed. NFIQ ranks the finger print quality with scores
between 1 & 5 .If the scores are 1/2/3 then the FP Quality is good then moves to the next finger. else if scores are 4/5 it
prompts for the same finger. In case of failure NFIQ asks for the same finger another time. . Even if fails it goes to the
next finger automatically.
2. For authenticating the finger prints ‘Fusion finger’ concept is used. After successful UID authentication, it will prompts to swipe single finger and sends to Aadhaar server for authentication. If it fails, it prompts to swipe second
finger. Now both the captured finger prints are send to Aadhaar server for authentication. If it again fails, it prompts to
swipe third finger and then the captured second and third finger prints are send to Aadhaar server for authentication.
This process is called ‘Fusion Finger’. If the response fails then POTD will go for local verification.
The POTD Prompts for the account number and once entered, it connects to the AUA server to fetch the information:
The following are some of the Errors/Exceptions commonly encountered:
Case - 1 Invalid Account number:
If the entered Account number is invalid, the POTD machine will display “Invalid Account No”. Operator will have to retry using the correct/valid beneficiary’s account number.
11
Case - 2 Valid Account number and UID Exists
If the entered Account number is valid, POTD connects to the server and retrieve the Account information such as UID, job
card number and display it on the screen. User can select the mode of authentication (1. Finger or 2. IRIS)
On selecting Finger, POTD prompts for Best finger verification (3 attempts) and connects to AADHAAR server. Once the
authentication is successful, payment is done and receipt is generated for the same.
On selecting IRIS, POTD prompts for IRIS authentication (six attempts in the order of left eye and right eye thrice) and
connects to AADHAAR server for verification. Once the authentication is successful, payment is done and receipt is
generated for the same.
Case - 3 UID Not Exist:
During withdrawal, if UID is not seeded for a beneficiary, Payment cannot be done.
Case - 4 UID Exists and BFD not done:
During withdrawal, if BFD is not done for a beneficiary, POTD displays the UID number and prompts for BFD. While doing
BFD, finger prints (Minimum 6) are collected for BFD. UID and finger Prints are sent to server for confirmation and
updation. Once it is successful, Receipt is printed with ranks based on NFIQ.
User can select the mode of authentication (1. Finger or 2. IRIS).
On selecting Finger, POTD prompts for Best finger verification (3 attempts) and connects to AADHAAR server. Once the
authentication is successful, payment is done and receipt is generated for the same.
On selecting IRIS, POTD prompts for IRIS authentication (six attempts in the order of left eye and right eye thrice) and
connects to AADHAAR server for verification. Once the authentication is successful, payment is done and receipt is
generated for the same.
Case – 5 UID Exists and BFD done but AADHAAR Authentication Failed:
During withdrawal, When AADHAAR authentication (3 attempts of Finger auth and 6 attempts of IRIS auth) fails, payment
will not be done. Payment can be done, only if AADHAAR Finger or IRIS authentication is successful.
2.5.1.1.3 Mini Statement:
If the entered account number is valid, it will display the details of wage seeker which consists of account number and
name. It will generate the receipt which consists the details of wage seeker i.e., Masked UID Number, Account
number, name and date of statement. The details of transaction like date of transaction, type of transaction and amount
will also be printed on receipt. It will retrieve the latest transactions based on the date and time of transaction.
Fig 2.4.2.1.3: Mini Statement Flow
12
2.5.1.1.4 Balance Enquiry:
Selection of Balance enquiry from NREGS services will display below screen.
Fig 2.4.2.1.4: Balance Enquiry Menu & Entry Screen
Upon selecting “New Account No” option and entering valid account number, balance details will be displayed as
shown in Fig 2.4.2.1.5
Fig 2.4.2.1.5: Balance Enquiry Details Screen
Upon selecting “Old Account No” option and entering valid account number, balance details will be displayed as
shown below
Fig: Balance Enquiry Details Screen
2.5.1.1.5 Zero Balance Account Receipt:
On selecting Zero balance enquiry it will prompt to enter account number.
13
Fig 2.4.2.1.6: Zero Balance Enquiry Details Screen
It will generate the receipt for the Zero balance account which consists of details like Report Date, Account Number,
Job card number, Name and Reason.
14
Fig 2.4.2.1.7: Zero balance Enquiry Flow
AASARA Services also provide pensioners with the same facilities as NREGS services. But Zero balance enquiry is
not provided for Aasara pensioners as there is no partial payment for them.
2.5.1.1.6 Last Trans Receipt:
On selecting last transaction receipt, it connects to server and if the data is present at server side, it displays the
message “Processing Request downloading please wait” and downloads last transaction receipt data. After
downloading the data successfully, last transaction receipt will be printed.
15
Fig 2.4.2.1.8: Last Tans Receipt Connecting Process
Fig 2.4.2.1.9: Last Tans Receipt generation
2.5.1.1.7 Capture Remarks:
After entering the valid account number, It connects to server to download the data as per the entered Account
Number. If the given account number is not matched, it displays the message “Invalid Account No”. If the entered
Account Number is matched, it displays the Account Holder details. Once we press Enter, it displays the Capture
Remarks menu.
Capture Remarks contain three options i.e., FP Mismatch, Migration, Death. If any one of the option is selected then it
enters to the respective screen with message “Are you sure to capture remarks as.....”. Press Cancel (X) button from the
screen to go back to the previous menu or Press Enter to download. It downloads the NREGS data if the data is present
at server side by displaying “Processing Request downloading please wait” message. After downloading the data
successfully a message is shown “FP Mismatch (or) Migration (or) Death remarks successfully captured” according to the respective option selected.
16
Fig 2.4.2.1.9.0: Capture Remarks Flow Chart
17
2.5 NON-NEFMS Main Menu:
After successful authentication of BPM, Main menu with six options i.e., Operator Options, Admin Options, Reports,
Shut Down, Version Details and Selfdiag Test will be displayed. (Fig 2.4.0)
Fig 2.4.0: Main Menu Screen 1 & 2
Press Cancel (X) button from the main menu. Application will be exited upon confirmation. (Fig 2.4.1)
Fig 2.4.1: Exit from the Main Menu
2.5.1 Operator Options:
Operator Options consists of Seven options i.e., NREGS Services, AASARA Services, Seeding, BFD, RTS, Mobile No
Seeding and UID Correction.
2.5.1.1 .1 NREGS Services:
Using this option operator can avail the services related to NREGS Wage seekers, such as Withdrawal through Account
number or UID, Balance Enquiry, Mini Statement, Zero Bal Enquiry, Last Trans Receipt, Capture Remarks &
Passbook update.
Fig 2.4.2.1.0: NREGS Services Menu Screen
18
Withdrawal can be done in with Account number in NREGS services.
Fig 2.4.2.1.1: Withdrawal with account number
2.5.1.1.2 Withdrawal with Account Number:
19
20
Fig 2.4.2.1.2: Withdrawal flow
Note: 1. NFIQ is a test which checks the quality of finger print imposed. NFIQ ranks the finger print quality with scores
between 1 & 5 .If the scores are 1/2/3 then the FP Quality is good then moves to the next finger. else if scores are 4/5 it
prompts for the same finger. In case of failure NFIQ asks for the same finger another time. . Even if fails it goes to the
next finger automatically.
2. For authenticating the finger prints ‘Fusion finger’ concept is used. After successful UID authentication, it prompts
to swipe single finger and sends to Aadhaar server for authentication. If it fails, it prompts to swipe second finger. Now
both the captured finger prints are sent to Aadhaar server for authentication. If it again fails, it prompts to swipe third
finger and then the captured second and third finger prints are send to Aadhaar server for authentication. This process is
called ‘Fusion Finger’. If the response fails then POTD will go for local verification.
The POTD Prompts for the account number and once entered, it connects to the AUA server to fetch the information:
The following are some of the Errors/Exceptions commonly encountered:
Case - 1 Invalid Account number:
If the entered Account number is invalid, the POTD machine will display “Invalid Account No”. Operator will have to retry
21
using the correct/valid beneficiary’s account number.
Case - 2 Valid Account number and UID Exists
If the entered Account number is valid, POTD connects to the server and retrieve the Account information such as UID, job
card number and display it on the screen. User can select the mode of authentication (1. Finger or 2. IRIS)
On selecting Finger, POTD prompts for Best finger verification (3 attempts) and connects to AADHAAR server. Once the
authentication is successful, payment is done and receipt is generated for the same.
On selecting IRIS, POTD prompts for IRIS authentication (six attempts in the order of left eye and right eye thrice) and
connects to AADHAAR server for verification. Once the authentication is successful, payment is done and receipt is
generated for the same.
Case - 3 UID Not Exist:
During withdrawal, if UID is not seeded for a beneficiary, POTD prompts for local if locally enrolled. Once local
authentication is successful, payment is done and receipt is generated for the same.
Case – 4 UID Exists and BFD not done:
During withdrawal, if BFD is not done for a beneficiary, POTD displays the UID number and prompts for BFD. While doing
BFD, finger prints(Minimum 6) are collected for BFD. UID and finger Prints are sent to server for confirmation and
updation. Once it is successful, Receipt is printed with ranks based on NFIQ.
User can select the mode of authentication (1. Finger or 2. IRIS).
On selecting Finger, POTD prompts for Best finger verification(3 attempts) and connects to AADHAAR server. Once the
authentication is successful, payment is done and receipt is generated for the same.
On selecting IRIS, POTD prompts for IRIS authentication (six attempts in the order of left eye and right eye thrice) and
connects to AADHAAR server for verification. Once the authentication is successful, payment is done and receipt is
generated for the same.
Case – 5 UID Exists and BFD done but AADHAAR Authentication Failed:
During withdrawal, When AADHAAR authentication (3 attempts of Finger auth and 6 attempts of IRIS auth) is failed,
payment cannot be done. Only if AADHAAR Finger or IRIS authentication is successful, payment will be done.
2.5.1.1.3 Mini Statement:
If the entered account number is valid, it will display the details of wage seeker which consists of account number and
name. It will generate the receipt which consists the details of wage seeker i.e., Masked UID Number, Account
number, name and date of statement. The details of transaction like date of transaction, type of transaction and amount
will also be printed on receipt. It will retrieve the latest transactions based on the date and time of transaction.
Fig 2.4.2.1.3: Mini Statement Flow
22
2.5.1.1.4 Balance Enquiry:
Selection of Balance enquiry from NREGS services will display below screen.
Fig 2.4.2.1.4: Balance Enquiry Menu & Entry Screen
Upon a valid account number entry A/C balance details will be displayed as shown in Fig 2.4.2.1.5
Fig 2.4.2.1.5: Balance Enquiry Details Screen
2.5.1.1.5 Zero Balance Account Receipt:
On selecting Zero balance enquiry it will prompt to enter account number.
Fig 2.4.2.1.6: Zero Balance Enquiry Details Screen
It will generate the receipt for the Zero balance account which consists of details like Report Date, Account Number,
Job card number, Name and Reason.
23
Fig 2.4.2.1.7: Zero balance Enquiry Flow
AASARA Services also provide pensioners with the same facilities as NREGS services. But Zero balance enquiry is
not provided for social security pensioners as there is no partial payment for them.
2.5.1.1.6 Last Trans Receipt:
Entering on last transaction receipt, it connects to server and downloads the Last Trans receipt data, if the data is
present at server side by displaying “Processing Request downloading please wait” message. After downloading the
data successfully, last transaction receipt will be generated.
24
Fig 2.4.2.1.8: Last Tans Receipt Connecting Process
Fig 2.4.2.1.9: Last Tans Receipt generation
2.5.1.1.7 Capture Remarks:
After entering the valid account number, It connects to server to download the data as per the entered Account
Number. If the given account number is not matched, it displays the message “Invalid Account No”. If the entered Account Number is matched, it displays the Account Holder details. Once we press Enter, it displays the Capture
Remarks menu.
Capture Remarks contain three options i.e., FP Mismatch, Migration, Death. If any one of the option is selected then it
enters to the respective screen with message “Are you sure to capture remarks as.....”. Press Cancel (X) button from the
screen to go back to the previous menu or Press Enter to download. It downloads the NREGS data if the data is present
at server side with a display “Processing Request downloading please wait”. After downloading the data successfully a
display message is shown” FP Mismatch (or) Migration (or) Death remarks successfully captured” according to the respective option selected.
25
Fig 2.4.2.1.9.0: Capture Remarks Flow Chart
26
2.5.1.2.1AASARA Services:
Using this option operator can avail the services related to SSP Wage seekers, such as Withdrawal through Account,
Balance Enquiry, Mini Statement, Last Trans Receipts and Capture Remarks.
Fig 2.4.2.2.0: AASARA Services Menu Screen
Withdrawal can be done with Account Number in AASARA services.
Fig 2.4.2.2.1: Withdrawal with account number
27
2.5.1.2 .2 Withdrawal with Account Number:
28
Fig cont..
29
Fig cont..
30
Fig 2.4.2.2.2: Withdrawal flow
Note: 1. NFIQ is a test which checks the quality of finger print imposed. NFIQ ranks the finger print quality with scores
between 1 & 5 .If the scores are 1/2/3 then the FP Quality is good then moves to the next finger. else if scores are 4/5 it
prompts for the same finger. In case of failure NFIQ asks for the same finger another time. . Even if fails it goes to the
next finger automatically.
2. For authenticating the finger prints ‘Fusion finger’ concept is used. After successful UID authentication, it will prompt to swipe single finger and send to Aadhaar server for authentication. If it fails, it prompts to swipe second
finger. Now both the captured finger prints are send to Aadhaar server for authentication. If it again fails, it prompts to
swipe third finger and then the captured second and third finger prints are send to Aadhaar server for authentication.
This process is called ‘Fusion Finger’. If the response fails then POTD will go for local verification.
The POTD Prompts for the account number and once entered, it connects to the AUA server to fetch the information:
The following are some of the Errors/Exceptions commonly encountered:
Case - 1 Invalid Account number:
If the entered Account number is invalid, the POTD machine will display “Invalid Account No”. Operator will have to retry using the correct/valid beneficiary’s account number.
Case - 2 Valid Account number and UID Exists
If the entered Account number is valid, POTD connects to the server and retrieve the Account information such as UID, job
card number and display it on the screen. User can select the mode of authentication (1. Finger or 2. IRIS)
On selecting Finger, POTD prompts for Best finger verification (3 attempts) and connects to AADHAAR server. Once the
authentication is successful, payment is done and receipt is generated for the same.
On selecting IRIS, POTD prompts for IRIS authentication (six attempts in the order of left eye and right eye thrice) and
connects to AADHAAR server for verification. Once the authentication is successful, payment is done and receipt is
generated for the same.
31
Case - 3 UID Not Exist:
During withdrawal, if UID is not seeded for a beneficiary, POTD prompts for local if locally enrolled. Once local
authentication is successful, payment is done and receipt is generated for the same.
If local authentication is failed, Messenger authentication is prompted. User can select the authentication mode(1.Finger or 2.
IRIS). Once the authentication is successful, payment is done and receipt is generated.
Case – 4 UID Exists and BFD not done:
During withdrawal, if BFD is not done for a beneficiary, POTD displays the UID number and prompts for BFD. While doing
BFD, finger prints(Minimum 6) are collected for BFD. UID and finger Prints are sent to server for confirmation and
updation. Once it is successful, Receipt is printed with ranks based on NFIQ.
User can select the mode of authentication (1. Finger or 2. IRIS).
On selecting Finger, POTD prompts for Best finger verification(3 attempts) and connects to AADHAAR server. Once the
authentication is successful, payment is done and receipt is generated for the same.
On selecting IRIS, POTD prompts for IRIS authentication (six attempts in the order of left eye and right eye thrice) and
connects to AADHAAR server for verification. Once the authentication is successful, payment is done and receipt is
generated for the same.
Case – 5 UID Exists and BFD done but AADHAAR Authentication Failed:
During withdrawal, When AADHAAR authentication (3 attempts of Finger auth and 6 attempts of IRIS auth) is failed,
payment cannot be done. Only if AADHAAR Finger or IRIS authentication is successful, payment will be done.
2.5.1.2.3 Mini Statement:
If the entered account number is valid, it will display the details of wage seeker which consists of account number and
name. It will generate the receipt which consists the details of wage seeker i.e., Masked UID Number, Account
number, name and date of statement. The details of transaction like date of transaction, type of transaction and amount
will also be printed on receipt. It will retrieve the latest transactions based on the date and time of transaction.
Fig 2.4.2.2.3: Mini Statement Flow
32
2.5.1.2.4 Balance Enquiry:
Selection of Balance enquiry from AASARA services will display the below screen.
Fig 2.4.2.2.4: Balance Enquiry Menu & Entry Screen
Upon a valid account number entry A/C balance details will be displayed as shown in Fig 2.4.2.2.5
Fig 2.4.2.2.5: Balance Enquiry Details Screen
2.5.1.2.5 Last Trans Receipt:
If last transaction key is pressed it connects to server & downloads the Last Trans receipt data if the data is present at
server side by displaying “Processing Request please wait” message. After downloading the data successfully, last
transaction will be generated
Fig 2.4.2.2.6: Last Tans Receipt Connecting Process
33
Fig 2.4.2.2.7: Last Tans Receipt generating
2.5.1.2.6 Capture Remarks:
After entering the valid account number, It connects to server to download the data as per the entered Account
Number. If the given account number is not matched, it displays the message “Invalid Account No”. If the entered Account Number is matched, it displays the Account Holder details. Once we press Enter, it displays the Capture
Remarks menu.
Capture Remarks contain three options i.e., FP Mismatch, Migration, Death. If any one of the option is selected then it
enters to the respective screen with message “Are you sure to capture remarks as.....”. Press Cancel (X) button from the
screen to go back to the previous menu or Press Enter to download. It downloads the NREGS data if the data is present
at server side with a display “Processing Request downloading please wait”. After downloading the data successfully a
display message is shown” FP Mismatch (or) Migration (or) Death remarks successfully captured” according to the respective option selected.
34
Fig 2.4.2.2.8: Capture remarks flow chart
35
2.5.1.3 Seeding:
With the help of Seeding option the beneficiary can seed his UID (or) EID even before withdrawal.
Once he enters the Seeding menu he can choose what to seed whether NREGS (or) AASARA.
Fig 2.4.2.3.0: Seeding
2.5.1.4 Best Finger Detection:
In Operator Options, We need to select BFD for verifying the best finger among the swiped fingers.
Fig 2.4.2.3.4: Best Finger Detection
On entry Account Number, it will direct to three cases
1) UID does not exist
2) UID exists but BFD not exists
3) UID and BFD exists
For “UID/EID does not exist” case, it will ask to Seed UID or EID. For “UID exist but BFD not exists” case, it asks for
BFD. For “UID and BFD exists” case, if user wants to re-enroll BFD then there is one more option available to
overwrite the previous BFD enrolled for that particular account.
On successful validation of UID, finger prints will be sent to Aadhaar server to get rankings. If UID is not valid, POS
machine prompts to enter valid UID. Finally it will generate the receipt with the ranking as in the below flow chart.
36
37
Fig 2.4.2.3.5: Best Finger Detection Flow diagram
2.5.1.5 RTS
Request Tracking System (RTS) manages and maintains the list of issues required for the machine. RTS is used to
create, update and resolve the issues.
Under RTS there is another sub menu BO Details with two options.
1. Same BO (For raising issues related to the same BO)
2. Other BO (For raising issues related to any other BO)
38
Fig Cont…
39
Fig 2.4.2.3.6: RTS Flow diagram
For Same BO and Other BO there will be 13 predefined and 1 user defined issues list related to POTD. The user has to
select one issue related to the machine. If issues are in Other BOs, the user needs to enter the Other BO user id.
For each issue the machine prompts for confirmation of the issue registration. In case of Other BO, the machine
requests the User ID of the BO along with the phone number. Then the issue is successfully registered.
2.5.1.6 Mobile No Seeding:
With the help of Mobile Number Seeding option the beneficiary can seed his/her Mobile or Phone Number. If already
mobile or phone Number is existed for that particular beneficiary, then Update option is available. By using this option
that particular beneficiary can update his/her mobile or phone number. Suppose the beneficiary enters same mobile or
phone number then response from server is like “Mobile Number already seeded”, otherwise response from server is
like “Mobile Number Updated successfully”.
Once he enters the Mobile No Seeding menu he can choose what to seed whether NREGS (or) AASARA.
40
Fig 2.4.2.3.7: Mobile No Seeding
Fig 2.4.2.3.8: Mobile No Seeding Menu
41
Fig 2.4.2.3.9: Mobile No Seeding Menu flow
2.5.1.7 UID Correction:
With the help of UID Correction option the beneficiary can correct his/her UID Number. If already UID Number exists
for that particular beneficiary, then Update option is available. By using this option that particular beneficiary can
update his/her UID number. Suppose the beneficiary enters same UID number then response from server is like “UID
number already seeded” otherwise response from server is like “UID number Updated successfully”. This is the case
applicable only if that particular beneficiary has UID without BFD. Suppose if BFD also done for that particular
beneficiary then response from server is like “No provision to change UID”.
Fig 2.4.2.4.1: UID Correction
42
Fig 2.4.2.4.2: UID Correction Menu
43
Fig 2.4.2.4.3: UID Correction Menu flow
2.5.2 Admin Services:
2.5.2.1 GPRS Single sync:
Connecting Antenna: If we press enter for receipt, it prompts to connect the antenna initially.
Sim Status Verification: On checking antenna connection to POTD it checks for the Sim presence and mounting.
Connectivity check: On Checking Sim status, it acquires connectivity to server to upload transactions to server and
download the pay orders from server.
Validating the User: On acquiring server connectivity, it validates the user before processing the request.
POS Machine date and time updation: POS machine date and time will be updated after user validation as below.
Fig 2.4.3.0: Admin Services Menu
44
On selecting GPRS single sync, it will connect to server and it will sync the data between POS machine and server.
Fig 2.4.3.1: GPRS Sync Connectivity
2.5.2.2 Messenger Config:
Under Admin options, two menus Set messenger and Rest messenger are available.
Using Set messenger option, single messenger can be set against the habitation so that at the time of payment, POTD will not
display the list of messengers and displays only one messenger.
Using Reset option, user can reset the messenger, so that at the time of payment POTD will display all the messengers
mapped to the habitation for authentication.
Fig 2.4.3.2: Messenger Config
45
2.5.3 Reports:
If we select reports from main menu, it will display the below screen which contains three options i.e., NREGS
Reports and AASARA Reports.
NREGS Reports:
Fig 2.4.4.0: Reports Flow for NREGS
2.5.3.1.1 NREGS Trans Report
NREGS transaction report will be generated on a receipt with its post office name, report date and the report summary.
46
Fig 2.4.4.1.0: NREGS Transactions Report Flow
2.5.3.1.2 NREGS Payorders Report:
NREGS pay orders report will be generated on a receipt with its post office name, report date and the report summary.
If there is no pay order data it will display as in the below flow.
Fig 2.4.4.1.1: NREGS Payments Report Flow
47
2.5.3.1.3 Balance Amount (NREGS):
NREGS Balance amount will be generated on a receipt with its post office name, report date and the report summary. If
there is no pay order data it will display as in the below flow.
Fig 2.4.4.1.2: NREGS Balance Amount Flow
2.5.3.1.4 Day wise LOT (NREGS):
NREGS Day wise LOT will be generated on a receipt with its post office name, report date and the report summary. If
there is no pay order data it will display as in the below flow.
48
Fig 2.4.4.1.3: NREGS Day wise LOT Flow
2.5.3.1.5 Account Details (NREGS):
NREGS account details report will be generated on a receipt with its post office name, report date and the report
summary such as account number, name and balance.
Fig 2.4.4.1.4: NREGS Account Details Reports
49
AASARA Reports:
Fig 2.4.4.1: Reports Flow for AASARA
2.5.3.2.1 AASARA Transaction Report:
AASARA transaction report will be generated on a receipt with its post office name, report date and the report
summary.
Fig 2.4.4.2.0: AASARA Transactions Report Flow
50
2.5.3.2.2 AASARA Payorders Report:
AASARA pay orders report will be generated on a receipt with its post office name, report date and the report
summary. If there is no pay order data it will display as in the below flow.
Fig 2.4.4.2.1: AASARA Payments Report Flow
2.5.3.2.3 Balance Amount (AASARA):
AASARA Balance Amount will be generated on a receipt with its post office name, report date and the report
summary. If there is no pay order data it will display as in the below flow.
Fig 2.4.4.2.2: AASARA Balance Amount Flow
51
2.5.3.2.4 Day wise LOT (AASARA):
AASARA Day wise LOT will be generated on a receipt with its post office name, report date and the report summary.
If there is no pay order data it will display as in the below flow.
Fig 2.4.4.2.3: AASARA Day wise LOT Flow
2.5.3.2.5 Account Details (AASARA):
AASARA account details report will be generated on a receipt with its post office name, report date and the report
summary such as account number, name and balance.
Fig 2.4.4.2.4: AASARA Account Details Reports
52
2.5.4 Shut down:
On selecting Shut down option from main menu, it will prompt for confirmation and shuts down the POS machine.
Fig 2.4.5: Shut Down screen 1 & 2
2.5.5 Version Details:
On selection of Version details from main menu, it displays the version details of the application as below.
Fig 2.4.6: Version Details Screen
There is APOnline default Menu which guides BPMs to verify functionalities and working condition of POS machine.
Below is the list of the provisions given in the application.
2.6 APOnline Menu:
After successful authentication of BPM, APOnline Menu with ten options i.e., Change user, Date time setup, BO
details, CC User details, Download CC Data, Download user data, Mac Id, UIDAI certificate, selfdiag test, Remote
application, RTS, Communication. Details will be displayed.
Fig 2.5: APOnline Menu Screen 1 & 2
53
Fig 2.5.0: APOnline Menu Screen 3
2.6.1 Change User:
Fig2.5.1 Change User
New User
Using this option POTD can be assigned to a new operator (BPM).After selecting the option, connectivity will be
established between POTD and Server. After successful User ID verification, it will prompt for user data download and
after confirmation, data will be downloaded to POTD. After downloading the data, it asks for finger print enrollment
(Minimum of 6 and maximum of 10). After successful enrollment, it displays a message “User Data Downloaded Successfully” and prints the BO details.
Existing User
Whenever the User is to be changed, the existing user must be de-activated through the webportal.
The user can be deactivated through the user updation page in the portal. In this page the user status must be set to
INACTIVE and UPDATE button is to be clicked. Then the existing user gets INACTIVATED. Then the new user who
replaces the existing user must enroll his details like User Id, BO details personal information etc in USER
CREATION page and should set his status as ACTIVE and click CREATE USER button and he automatically gets
updated to the respective BO.
54
Fig 2.5.1.1: APOnline Menu Screen 1 & 2
2.6.2 Date and Time Updating:
Before it downloads the application, it updates the date and time of POTD with Server date and time.
2.6.3 BO Details:
If Operator selects BO details option it prompts for confirmation of BO Name, BO Code, User ID and User Name.
Fig 2.5.2: BO Details
2.6.4 CC Details:
If the operator selects the CC details option it will connect to the server and fetch the details of the CC user.
55
Fig 2.5.3:CC User Details
2.6.5 Remote Application:
Operator can download the updated version of application remotely from the APOnline server. Upon successful
updating of application, the POTD will shutdown automatically.
Fig 2.5.3: Remote Application Flow
On switching ON the POTD, updated application will be running.
2.6.6 Download CC Data:
This option is used for downloading the CC User Details to the respective device.The user needs to enroll in the
enrollment user login and should give his details(name,phone no,email id,uid,address) and the details of the
POTD(district,mandal,bo) and download the details .
56
Fig 2.5.4:Download CC Details
2.6.7 Download User Data:
Switch on the POTD. On completion of booting process it displays home page. On Pressing Enter key it displays “User
Enrollment not at done”. Press any key, it displays “Enter User Id” for User login. User should enter APOnline login
(User: 11111 Password: 123456789) for BPM Enrollment. APOnline Menu is displayed in which user has to select
seventh (7) option which is “Download User data”. After selecting this option it displays message as “connection in
progress please wait”. During user data download it displays the message as “Downloading please wait”. On
completion of data download it displays the message on POS screen as “User data downloaded” Press enter for
enrollment. On pressing Enter button, it prompts with the fingerprint screen “Please choose the finger”, choose ten
fingers for enrollment (enrollment has to done for ten fingers)then press enter for upload.
Note: If there is any problem with enrollment of ten fingers you should enroll with minimum of six fingers (Ex:
Handicapped or leprosy).
On capturing all the ten fingers, POS machine displays the message as “downloading please wait”. A message is
displayed as “user downloaded successfully”. On pressing enter button it generates the print receipt with respective BO
details. Now User should check with the user login details on entering in POS Machine.
57
58
Fig 2.5.5: User Data Download
2.6.8 RTS:
Request Tracking System (RTS) manages and maintains the list of issues required for the machine. RTS is used to
create ,update and resolve the issues.
Under RTS there is another sub menu BO details with two options.
3. Same BO (For raising issues related to the same BO)
4. Other BO (For raising issues related to any other BO)
59
Fig 2.5.6: RTS
For Same BO and Other BO there will be 14 issues regarding the problems in the POTD. The user has to select one
issue regarding the problem related to the machine. The user can create a new issue (or) add details to the existing
issues. The System requests confirmation from the user before registering (or) submitting the issue. For issues related
to Other BO’s the user needs to enter the Other BO’s user ID.
2.6.9 Communication Type:
With the help of Communication option the beneficiary can select either GPRS connection or Ethernet connection
depends on availability. Whenever beneficiary select any one of option in communication then after the POTD reboots
automatically, from then onwards POTD communication depends on selected mode.
Once he enters the Communication menu he/her can choose what to communicate whether GPRS (or) Ethernet.
Fig 2.5.7: Communication type
60
2.6.10 Mac ID:
This option displays the Mac Id of the POTD. This Mac ID can be used for identifying the POTD. Each POTD has a
unique Mac Id.
Fig 2.5.8: Mac Id
2.6.11 UIDAI Certificate:
It will download the latest Aadhaar details.
2.6.12 Shutting down the POS
If Operator selects shutdown option it will prompts for confirmation and upon confirmation POTD will shutdown.
Fig 2.5.9: Shut Down
2.7 Enrollment
2.7.1 Enrollment User Creation:
Enrollment menu is a separate menu that is held for enrolling the beneficiaries through POTD. It has a specific login
and normal user cannot use that login. The user has to enroll his/her details in the Enrollment User portal and enter
his/her details in the respective fields. After successfully enrolling in the portal he/she has to upload his/her biometric
files to the server and download his/her user id in the respective device.
61
Fig 2.7.1:Enrollment User Creation
62
2.7.2 Beneficiary Enrollment:
For enrolling a beneficiary through POTD he/she must have a valid Job card/Pension Id. First they have to
enter the Household number and worker code for an NREGS beneficiary and Pension Id for an SSP beneficiary.
The Potd will fetch the details of the beneficiary from the server. If the beneficiary is already enrolled the
device shows “Already enrolled” along with the beneficiary details. If the beneficiary is not enrolled the device will
prompt for enrollment. He/she has to enroll all their fingers and should press Enter to verify the enrollment. If
verification is success the device will show a message that “Enrollment successful” else “Enrollment failed” message
will be displayed.
Fig 2.7.3: Beneficiary Enrollment Flow
2.7.3 Enrollment Reports:
The Enrollment reports give the consolidated count of total beneficiaries enrolled and beneficiaries to be
enrolled.
1) All Enrollment:
All Enrollment report gives the report of the Enrollment done from the beginning.
Fig 2.7.4: All Enrollment Report
2) Date wise Enrollment:
Date wise report will give the information of the enrollment done on a particular date. We need to enter the
date in the POTD in mmddyyyy format.
63
Fig 2.7.5 :Date wise Enrollment Report
Fig 2.7.6: Enrollment Reports
2.7.4 Status:
With this option we can get to know the enrollment status and the job card number / PensionId of the beneficiary
without actually going into the Enrollment process. We need to enter the account number of the beneficiary and the
POTD will fetch the details of the respective account number.
Fig 2.7.7: Enrolled Status
64
Aadhaar Error Codes and Description:
Table 2.8 Error List
Error Code Error Name Error Description
300 Biometric mismatch (300) Biometric mismatch, please go for Aadhaar re-enrollment
997
Not sure. Pls. check spec.
(997)
Not sure. Please check spec(997), Aadhaar internal error, please
call Helpdesk.
561 Expired request (561)
Request Expired, please try again.
937
Digital signature error
(937) Digital signature error, please try again or please call Helpdesk.
999 Unknown error (999) Unknown error.
811
Missing biometrics in
CIDR (811)
Biometrics are not available at CIDR for given
Aadhaar number, please go for Aadhaar re-enrollment.
931 Auth server error (931) Technical Error i.e., please try again.
935 Skey store error (935) Technical Error i.e., please try again.
584
Invalid pin code in Meta
(584)
PINCODE is not matched with Aadhaar PINCODE, please call
helpdesk.
310
Duplicate fingers used
(310) Same finger is used, please try next best finger.
939 On boarding error (939)
Technical Error i.e., Internal to Authentication server. Please try
again.
511 Invalid Pid XML (511) Error in PID block, please try again.
562 Future request (562) Time stamp is ahead of authentication time, please try again.
65
POTD Errors Messages:
Error Name Error Description
Incorrect UID, Enter Valid UID If the entered UID is incorrect or invalid while doing
withdrawal through UID number. So, please enter
correct UID with valid proof of UID card.
Incorrect UID, Enter 12 digits UID If the entered UID number less than 12 digits this
error occurred. So, please enter correct UID with
valid proof of UID card.
Incorrect server, Conn. Terminated, please try later This type of error is occurred when network
connection is terminated from server.
Incorrect server response, Page error This type of error is occurred when any problem
occurred in server.
Incorrect server response wrong format This type of error is occurred when any problem
occurred in server.
UIDAI PUBLIC KEY, Certificate not found or
Expiry date error
This type of error is occurred when any problem from
Aadhaar.
FP data Encryption or B-64 Encoding Failed This type of error is occurred when any problem
occurred in server.
Hmac Encryption or B-64 Encoding Failed This type of error is occurred when any problem
occurred in server.
UID Seeding Failed If entered UID number for seeding is already seeded
with another account number then this type of error
occurred.
Table 2.9 Error List