Wage Disbursement Project (Aadhaar Authenticated Benefit Disbursement) User Operational Manual Version 3.9

Wage Disbursement Project (Aadhaar Authenticated Benefit Disbursement) User Operational Manual Version 3.9

Contents Aadhaar authenticated Benefit Disbursement Introduction... 5 1. Benefit Disbursement System Device... 6 1.1 Getting Started:... 6 Fig 1.1:Benefit Disbursement System Device... 6 Fig 1.2:Booting & Loading of Ram disk... 6 2. Benefit Disbursement System Application... 7 2.1 Process flow Diagram:... 7 Fig 2.1 Process Flow Diagram... 7 2.2 Home Page:... 7 Fig 2.2: Home Page of Application... 7 2.3 User Interface - Tree View :... 8 2.4 User Login:... 11 Fig 2.3: User Login Flow... 12 2.5 Main Menu:... 13 Fig 2.4.0: Main Menu Screen 1 & 2... 13 Fig 2.4.1: Exit from the Main Menu... 13 2.5.1 Operator Options:... 14 2.5.1.1.1 NREGS Services:... 14 Fig 2.4.2.1.0: NREGS Services Menu Screen... 14 Fig 2.4.2.1.1: Withdrawal with account number/uid 1 & 2... 14 2.5.1.1.2 Withdrawal with Account Number:... 15 Fig 2.4.2.1.2: Withdrawal flow... 19 2.5.1.1.3 Mini Statement :... 20 2.5.1.1.4 Balance Enquiry:... 21 Fig 2.4.2.1.4: Balance Enquiry Menu & Entry Screen... 21 Fig 2.4.2.1.5: Balance Enquiry Details Screen... 22 2.5.1.1.5 Zero Balance Account Receipt:... 22 Fig 2.4.2.1.6: Zero Balance Enquiry Details Screen... 22 Fig 2.4.2.1.7: Zero balance Enquiry Flow... 23 2.5.1.1.6 Last Trans Receipt:... 23 Fig 2.4.2.1.8: Last Tans Receipt Connecting Process... 23 Fig 2.4.2.1.9: Last Tans Receipt generation... 24 2.5.1.1.7 Capture Remarks:... 24 Fig 2.4.2.1.9.0: Capture Remarks Flow Chart... 25 2.5.1.2.1SSP Services:... 25 Fig 2.4.2.2.0: SSP Services Menu Screen... 25 1

Fig 2.4.2.2.1: Withdrawal with account number/uid 1 & 2... 26 2.5.1.2.2 Withdrawal with Account Number:... 26 Fig 2.4.2.2.2: Withdrawal flow... 31 2.5.1.2.3 Mini Statement:... 32 Fig 2.4.2.2.3: Mini Statement Flow... 33 2.5.1.2.4 Balance Enquiry:... 33 Fig 2.4.2.2.4: Balance Enquiry Menu & Entry Screen... 33 Fig 2.4.2.2.5: Balance Enquiry Details Screen... 33 2.5.1.2.5 Last Trans Receipt:... 33 Fig 2.4.2.2.6: Last Tans Receipt Connecting Process... 34 Fig 2.4.2.2.7: Last Tans Receipt generating... 34 2.5.1.2.6 Capture Remarks:... 34 Fig 2.4.2.2.8: Capture remarks flow chart... 35 2.5.1.3 Seeding:... 36 Fig 2.4.2.3.0: Seeding... 36 Fig 2.4.2.3.1: SeedingMenu... 36 2.5.1.3.1 NREGS Seeding:... 36 Fig 2.4.2.3.2: NREGS Seeding Flow... 38 2.5.1.3.2 SSP Seeding:... 38 Fig 2.4.2.3.3: SSP Seeding Flow... 41 2.5.1.4 Best Finger Detection:... 41 Fig 2.4.2.3.4: Best Finger Detection... 41 Fig 2.4.2.3.5: Best Finger Detection Flow diagram... 44 2.5.1.5 RTS... 44 Fig 2.4.2.3.6: RTS Flow diagram... 46 2.5.1.6 Mobile No Seeding:... 46 Fig 2.4.2.3.7: Mobile No Seeding... 47 Fig 2.4.2.3.8: Mobile No Seeding Menu... 47 Fig 2.4.2.3.9: Mobile No Seeding Menu flow... 48 2.5.1.7 UID Correction:... 48 Fig 2.4.2.4.1: UID Correction... 48 Fig 2.4.2.4.2: UID Correction Menu... 49 Fig 2.4.2.4.3: UID Correction Menu flow... 50 2.5.2 Admin Services:... 50 2.5.2.1 GPRS Single sync:... 50 Fig 2.4.3.0: Admin Services Menu... 51 Fig 2.4.3.1: GPRS Sync Connectivity... 51 2.5.2.2 NREGS... 51 2

Fig 2.4.3.2: Subsequent data of NREGS Flow... 51 2.5.2.3 SSP Admin... 51 Fig 2.4.3.3: Subsequent data of SSP Flow... 52 2.5.2.4 Change User:... 52 New User... 52 Existing User... 52 Fig 2.4.3.4.0:User Updation & Creation server screens... 54 Fig 2.4.3.4.1: Change User Flow... 55 2.5.2.5 Remote Application:... 55 Fig 2.4.3.5: Remote Application Flow... 56 2.5.3 Reports:... 56 Fig 2.4.4.0: Reports Flow for NREG... 57 2.5.3.1.1 NREGS Trans Report... 57 Fig 2.4.4.1.0: NREGS Transactions Report Flow... 57 2.5.3.1.2 NREGS Payorders Report:... 57 Fig 2.4.4.1.1: NREGS Payments Report Flow... 58 2.5.3.1.3 Balance Amount (NREGS):... 58 Fig 2.4.4.1.2: NREGS Balance Amount Flow... 59 2.5.3.1.4 Day wise LOT (NREGS):... 59 Fig 2.4.4.1.3: NREGS Day wise LOT Flow... 60 2.5.3.1.5 Account Details (NREGS):... 60 Fig 2.4.4.1.4: NREGS Account Details Reports... 60 SSP Reports:... 61 Fig 2.4.4.1: Reports Flow for SSP... 61 2.5.3.2.1 SSP Transaction Report:... 61 Fig 2.4.4.2.0: SSP Transactions Report Flow... 61 2.5.3.2.2 SSP Payorders Report:... 62 Fig 2.4.4.2.1: SSP Payments Report Flow... 62 2.5.3.2.3 Balance Amount (SSP):... 62 Fig 2.4.4.2.2: SSP Balance Amount Flow... 62 2.5.3.2.4 Day wise LOT (SSP):... 63 Fig 2.4.4.2.3: SSP Day wise LOT Flow... 63 2.5.3.2.5 Account Details (SSP):... 63 Fig 2.4.4.2.4: SSP Account Details Reports... 63 2.5.4 Shut down:... 64 Fig 2.4.5: Shut Down screen 1 & 2... 64 2.5.5 Version Details:... 64 Fig 2.4.6: Version Details Screen... 64 3

2.6 APOnline Menu:... 64 Fig 2.5: APOnline Menu Screen 1 & 2... 64 2.6.1 Change User:... 65 Fig2.5.1 Change User... 65 New User... 65 Existing User... 65 Fig 2.5.1.0: User Updation & Creation server screens... 67 Fig 2.5.1.1: APOnline Menu Screen 1 & 2... 68 2.6.2 Date and Time Updating:... 68 2.6.3 BO Details:... 68 Fig 2.5.2: APOnline Menu Screen 1 & 2... 68 2.6.4 Remote Application:... 68 Fig 2.5.3: Remote Application Flow... 68 2.6.6 UIDAI Certificate:... 68 2.6.7 Download User Data:... 69 Fig 2.5.4: User Data Download... 70 2.6.8 RTS:... 70 Fig 2.5.5: RTS... 72 2.6.9 Communication:... 72 Fig 2.5.7: Communication... 72 2.6.10 Mac ID:... 72 2.7.1 Shutting down the POS... 73 Aadhaar Error Codes and Description:... 74 Table 2.8 Error List... 74 POTD Errors Messages:... 75 Table 2.9 Error List... 75 4

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 5

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 will get start and the following screens will be display. 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.fig (1.3) 6

2. Benefit Disbursement System Application 2.1 Process flow Diagram: AADHAR BASED AUTHENTICATION & PAYMENT PROCESS Aadhar Server (CIDR) 9 Response Code Match, Mismatch, No AadharNo Aadhar No Finger Print 8 ASA Beneficiary POTD Aadhar No Response Code OR X Finger Print 12 Response Code OR 11 7 Cash if Match Response Code 5 Amount, Finger Print 6 Amount, Acct No Finger Print Show Balance 4 AUA 3 Balance amount 1 Entry of Acct No 2 Sends Acct No APOnline 10 Fig 2.1 Process Flow Diagram 2.2 Home Page: After displaying the Application Home Screen it prompts the 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 7

2.3 User Interface - Tree View: Main Menu Operator Options NREGS Services Withdrawal with Account No Withdrawal with UID Balance Enquiry Mini Statement Zero Bal Enquiry Last Trans Receipt Capture Remarks SSP Services Withdrawal with A/C Withdrawal with UID Balance Enquiry Mini Statement Last Trans Receipt Capture Remarks Seeding NREGS Seeding SSP Seeding BFD NREGS Seeding SSP Seeding RTS Same BO Error from server Wrong response User is not active ASA server failure Modem baud rate error Can t resolve host Need to balance Excess amount Log file writing failure Device not mapped PT verify API error USB not responding Sim not present Others Other BO Error from server Wrong response User is not active ASA server failure Modem baud rate error Can t resolve host Need to balance Excess amount Logfile writing failure Device not mapped PT verify API error USB not responding Sim not present Others Mobile No Seeding NREGS Seeding SSP Seeding UID Correction NREGS Seeding SSP Seeding 8

Admin Options GPRS single sync NREGS Download NREGS Data SSP Download SSP Data Change User Remote Application Reports NREGS Reports NREGS Trans Reports Payorders Report Balance Amount Consolidated Latest All Day Wise Lot Accounts Info SSP Reports SSP Trans Reports Payorders Report Balance Amount Consolidated Latest All Day Wise Lot Accounts Info Shut Down Version Details Selfdiag Test Printer Paper Test Motor Test Print Test Battery GPRS SIM Status NW Signal Strength GPRS Status Connectivity SD Card SD card Presence SD card Mounting Data Writing Data Copying Data Reading Database Backup. 9

APOnline Menu Change User Date Time Setup BO details Selfdiag Test Printer Paper Test Motor Test Print Test Battery GPRS SIM Status NW Signal Strength GPRS Status Connectivity SD Card SD card Presence SD card Mounting Data Writing Data Copying Data Reading Data base Backup. Remote Application UIDAI Certificate Download User Data RTS Communication GPRS Ethernet Mac Id 10

2.4 User Login: After displaying the Application Home Screen it will connect to server to fetch UID of the BPM (Branch Post Master) as per 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 connect to Server and get details from server. 11

Fig 2.3: User Login Flow After User ID is entered, it automatically connects to Aadhaar server. If UID and BFD exist, it asks for best finger verification and connects to Aadhaar server three times. If it is successful, a success message is displayed and moves to main menu or if Best finger verification fails it asks for the local verification. After successful local verification it displays the main menu. If we go for local verification that particular BPM local 12

Finger prints should be in local memory of POS. Then only local verification allows other wise it shows error as like Local FP not exist in POS (or) API verify error. After User ID is entered, it automatically connects to Aadhaar server. If UID exists and BFD not yet done then it asks to capture 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 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 generated automatically. Then it moves to main menu or if Best finger verification fails it asks for the local verification, after successful local verification, it displays the main menu. If BFD fails, a fail message is displayed and reason for failure displayed in Action wise receipt will generated automatically. After User ID is entered, it automatically connects to Aadhaar server, if UID is not seeded then directly it asks for Local verification. After successful local verification, it displays the main menu. 2.5 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 13

2.5.1 Operator Options: Operator Options consists of Seven options i.e., NREGS Services, SSP 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 and Capture Remarks. Fig 2.4.2.1.0: NREGS Services Menu Screen Withdrawal can be done in two modes which are in NREGS services. They are: Withdrawal with account number. Withdrawal with UID. Fig 2.4.2.1.1: Withdrawal with account number/uid 1 & 2 14

2.5.1.1.2 Withdrawal with Account Number: 15

Fig Cont 16

Fig Cont 17

Fig Cont 18

Fig Cont Fig 2.4.2.1.2: Withdrawal flow Note: 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 19

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 beneficiary s account number. Case 2 Valid Account number but No Aadhaar and No Local: If beneficiary has a valid account number it is sent for authentication.if the user does not have Aadhaar number and not enrolled in APOnline then the machine allows BPM authentication Payment. The BPM authentication mode is valid for single time only. Case 3 UID Not Exist and Local Enrolled: If beneficiary has a valid account number it is sent for authentication, If not seeded, UID Seeding process should begin. Upon a valid account match at the server, it will search for the UID. If UID does not exist, the POTD will prompt for UID seeding. Operator needs to enter the 12 digit UID number. It prompts to enter the UID twice for confirmation. The UID number will be sent to server for updation. Then the POTD prompts for local verification for completing the transaction. Case 4 Valid Account number and UID Exists 1. Upon a valid account match at server, it will retrieve the corresponding UID and the Job card details into the POTD. 2. If corresponding UID exists for the account but BFD not yet done, it will display the UID number and prompts for finger ranking menu. After capturing minimum 6 fingers finger print, rank receipt will be generated. Then it will prompt for Aadhaar authentication. If the Aadhaar authentication is successful, the transaction will be done. 3. If corresponding UID exists for the account, it will display the UID number and prompts for finger authentication menu. Captured finger print data will be sent to UID server for authentication. 1.1 Successful Aadhaar Authentication 1.1.1 Corresponding Account information will be displayed on the POTD. 1.1.2 After confirming the withdrawal amount, same will be updated in server and the transaction will be completed and a receipt is also generated. 1.2 Unsuccessful Aadhaar Authentication 1.2.1 Operator needs to repeat the same process for 3 times in case of Unsuccessful match at Aadhaar server. 1.2.2 If it still fails after 3 attempts then POTD will prompt for local verification for completing the transaction Case 5 UID Not Exist and Local Verification also failed: If UID not exists and local verification also failed then the POTD prompts for Manual Payment for completing the transaction. 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 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.5.1.1.3 Mini Statement: Selection for receipt prompts to connect the antenna initially. On checking antenna connection to POTD it 20

checks for the SIM card and mounting for server connection. 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 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 21

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, Masked UID Number, Account Number, Job card number, Name and Reason. 22

Fig 2.4.2.1.7: Zero balance Enquiry Flow SSP 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 with a display Processing Request downloading please wait. After downloading the data successfully a display message is shown as a print. Fig 2.4.2.1.8: Last Tans Receipt Connecting Process 23

2.5.1.1.7 Capture Remarks: Fig 2.4.2.1.9: Last Tans Receipt generation 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. 24

Fig 2.4.2.1.9.0: Capture Remarks Flow Chart 2.5.1.2.1SSP Services: Using this option operator can avail the services related to SSP Wage seekers, such as Withdrawal through Account number or UID, Balance Enquiry, Mini Statement, Last Trans Receipts and Capture Remarks. Fig 2.4.2.2.0: SSP Services Menu Screen Withdrawal can be done in two modes which are in NREGS services. They are: Withdrawal with account number Withdrawal with UID. 25

Fig 2.4.2.2.1: Withdrawal with account number/uid 1 & 2 2.5.1.2.2 Withdrawal with Account Number: 26

27

Fig Cont 28

Fig Cont 29

30

Fig 2.4.2.2.2: Withdrawal flow Note: 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 beneficiary s account number. Case 2 Valid Account number and No Aadhaar and No Local If beneficiary has a valid account number it is sent for authentication.if the user does not have aadhaar number and not enrolled in APOnline then the machine allows to BPM authentication Payment. The BPM authentication mode is valid for single time only. Case 3 UID Not Exist and Local Enrolled If beneficiary has a valid account number it is sent for authentication, If not seeded, process should begin. Upon a valid account match at the server, it will search for the UID. If UID does not exist the POTD will prompts for UID seeding. Operator needs to enter the 12 digit UID number; it prompts to enter twice for confirmation. The UID number will be sent to server for updating. Then the POTD prompts for local verification for completing the transaction. Case 4 Valid Account number and UID Exists. 1. Upon a valid account match at server, it will retrieve the corresponding UID and the Job card details into the POTD. 2. If corresponding UID is exists for the account but BFD not yet done, it will display the UID number and prompts for finger ranking menu.after Capturing minimum 6 fingers finger print rank receipt will be 31

generated. Then it will prompts for Aadhaar authentication. If the Aadhaar authentication success the transaction will be done. 3. If corresponding UID is exists for the account, it will display the UID number and prompts for finger authentication menu. Captured finger print data will be sent to UID server for authentication. 1.3 Successful Aadhaar Authentication 1.3.1 Corresponding Account information will be displayed on the POTD. 1.3.2 After confirming the withdrawal amount same will be updated in server and the transaction will be completed and a receipt is also generated. 1.4 Unsuccessful Aadhaar Authentication 1.4.1 Operator needs to repeat the same process for 3 times in case of Unsuccessful match at Aadhaar server. 1.4.2 If it still fails after 3 attempts then POTD will prompts for local verification for completing the transaction Case 5 UID Not Exist and Local Verification also failed : If UID not exist and local verification also failed then the POTD prompts for Manual Payment for completing the transaction. 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 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.5.1.2.3 Mini Statement: Selection for receipt prompts to connect the antenna initially. On checking antenna connection to POTD it checks for the SIM card and mounting for server connection. 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. 32

2.5.1.2.4 Balance Enquiry: Fig 2.4.2.2.3: Mini Statement Flow Selection of Balance enquiry from SSP services will display 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 it downloads the Last Trans receipt data if the data is present at server side with a display Processing Request please wait. After downloading the data successfully a display message is shown as a print. 33

Fig 2.4.2.2.6: Last Tans Receipt Connecting Process 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) SSP. Fig 2.4.2.3.0: Seeding 2.5.1.3.1 NREGS Seeding: Fig 2.4.2.3.1: SeedingMenu In this menu the beneficiary can Seed his/her EID (or) UID if already his/her EID (or) UID seeded for that particular beneficiary it shows like UID already seeded otherwise show like UID seeding success, in this process beneficiary should enter his/her Account number first. Fig Cont 36

Fig Cont 37

2.5.1.3.2 SSP Seeding: Fig 2.4.2.3.2: NREGS Seeding Flow In this menu the beneficiary can Seed his/her EID (or) UID if already his/her EID (or) UID seeded for that particular beneficiary it shows like UID already seeded otherwise show like UID seeding success, in this process beneficiary should enter his/her Account number first. 38

39

Fig Cont 40

2.5.1.4 Best Finger Detection: Fig 2.4.2.3.3: SSP Seeding Flow 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/ EID does not exist 2) UID exists but BFD not exists 3) UID and BFD exists even though we want to do BFD again For UID/EID does not exists case it will ask to Seeding UID or EID. If in case of UID exist but BFD not exist then it ask for BFD. If already BFD done for that account even though we want to do BFD again then there is a one more option is available for over write the previous BFD 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 will prompt for Enter Valid UID. Finally it will generate the receipt with the ranking as in the below flow chart. 41

42

43

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) 44

Fig Cont 45

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 enter same mobile or phone number then response from server is like this mobile or phone 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) SSP. 46

Fig 2.4.2.3.7: Mobile No Seeding Fig 2.4.2.3.8: Mobile No Seeding Menu 47

2.5.1.7 UID Correction: Fig 2.4.2.3.9: Mobile No Seeding Menu flow With the help of UID Correction option the beneficiary can correct his/her UID Number. If already UID Number is existed 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 enter same UID number then response from server is like This UID number already seeded otherwise response from server is like UID number Update Successfully. This is the case accrue only that particular beneficiary have UID without BFD only. Suppose if BFD also done for that particular beneficiary then response from server is like No provision to change UID. Once he enters the Mobile No Seeding menu he can choose what to seed whether NREGS (or) SSP. Fig 2.4.2.4.1: UID Correction 48

Fig 2.4.2.4.2: UID Correction Menu 49

2.5.2 Admin Services: Fig 2.4.2.4.3: UID Correction Menu flow 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. 50

Fig 2.4.3.0: Admin Services Menu 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 NREGS On selection of NREGS Admin, it displays the below menu option i.e., Download NREGS Data. On successful connectivity of server, it downloads the NREGS Bir data if the data is present at server side. 2.5.2.3 SSP Admin Fig 2.4.3.2: Subsequent data of NREGS Flow On selection of SSP Admin, it displays the below menu option i.e., Download SSP Data. On successful connectivity of server, it downloads the SSP Bir data if the data is present at server side. 51

Fig 2.4.3.3: Subsequent data of SSP Flow 2.5.2.4 Change User: Change User Option is available in the APOnline menu & Admin menu. Refer Fig2.5.1 for Change User option. 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 web portal. 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 use 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. 52

53

Fig 2.4.3.4.0: User Updation & Creation server screens 54

Fig 2.4.3.4.1: Change User Flow 2.5.2.5 Remote Application: Operator can download the updated version of application remotely form the APOnline server. Upon successful updating of application, the POTD will shutdown automatically. On switching ON the POTD, updated application will be running. 55

2.5.3 Reports: Fig 2.4.3.5: Remote Application Flow If we select reports from main menu, it will display the below screen which contains three options i.e., NREGS Reports and SSP Reports. NREGS Reports: 56

Fig 2.4.4.0: Reports Flow for NREG 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. 2.5.3.1.2 NREGS Payorders Report: Fig 2.4.4.1.0: NREGS Transactions Report Flow 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. 57

Fig 2.4.4.1.1: NREGS Payments Report Flow 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. 58

2.5.3.1.4 Day wise LOT (NREGS): Fig 2.4.4.1.2: NREGS Balance Amount Flow 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. 59

2.5.3.1.5 Account Details (NREGS): Fig 2.4.4.1.3: NREGS Day wise LOT Flow 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 60

SSP Reports: 2.5.3.2.1 SSP Transaction Report: Fig 2.4.4.1: Reports Flow for SSP SSP 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: SSP Transactions Report Flow 61

2.5.3.2.2 SSP Payorders Report: SSP 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. 2.5.3.2.3 Balance Amount (SSP): Fig 2.4.4.2.1: SSP Payments Report Flow SSP 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: SSP Balance Amount Flow 62

2.5.3.2.4 Day wise LOT (SSP): SSP 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. 2.5.3.2.5 Account Details (SSP): Fig 2.4.4.2.3: SSP Day wise LOT Flow SSP 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: SSP Account Details Reports 63

2.5.4 Shut down: On selecting Shut down option from main menu, it will prompt for confirmation and shuts down the POS machine. 2.5.5 Version Details: Fig 2.4.5: Shut Down screen 1 & 2 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 gist 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, selfdiag test, Remote application, UIDIA certification, Download user data, RTS, Communication, Mac Id. Details will be displayed. (Fig 2.5) 64

Fig 2.5: APOnline Menu Screen 1 & 2 2.6.1 Change User: New User Fig2.5.1 Change 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 use 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. 65

66

Fig 2.5.1.0: User Updation & Creation server screens 67

2.6.2 Date and Time Updating: Fig 2.5.1.1: APOnline Menu Screen 1 & 2 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 will prompts for confirmation the BO Name, BO Code, User ID and User Name. Fig 2.5.2: APOnline Menu Screen 1 & 2 2.6.4 Remote Application: Operator can download the updated version of application remotely form 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 UIDAI Certificate: It will download the latest Aadhaar details. 68

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. 69

2.6.8 RTS: Fig 2.5.4: User Data Download 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) 70

71

Fig 2.5.5: 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 relating to Other BO s the user need to enter the Other BO 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 reboot 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 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.7: Mac Id 72

2.7.1 Shutting down the POS If operator selects shutdown option it will prompts for confirmation and upon confirmation POTD will shutdown. Fig 2.5.7: Shut Down 73

Aadhaar Error Codes and Description: 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. Request Expired, please try again. 561 Expired request (561) 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. Table 2.8 Error List 74

POTD Errors Messages: Error Name Incorrect UID, Enter Valid UID Incorrect UID, Enter 12 digits UID Incorrect server, Conn. Terminated, please try later Incorrect server response, Page error Incorrect server response wrong format UIDAI PUBLIC KEY, Certificate not found or Expiry date error FP data Encryption or B-64 Encoding Failed Hmac Encryption or B-64 Encoding Failed UID Seeding Failed Error Description 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. If the entered UID number less than 12 digits this error occurred. So, please enter correct UID with valid proof of UID card. This type of error is occurred when network connection is terminated from server. This type of error is occurred when any problem occurred in server. This type of error is occurred when any problem occurred in server. This type of error is occurred when any problem from Aadhaar. This type of error is occurred when any problem occurred in server. This type of error is occurred when any problem occurred in server. If entered UID number for seeding is already seeded with another account number then this type of error occurred. Table 2.9 Error List 75