4.1.1. Beneficiary PWA (Mobile-First)

BR-UM-4.1.1.1: Registration and Login

1. A new beneficiary can register using a phone number (not required to be unique).

2. The system auto-generates a username in the format (this is configurable according to the requirement): FirstName_FirstLetterOfLastName_Last4DigitsOfMobileNumber

3. A secure password policy must be enforced (e.g., minimum 8 characters, mix of uppercase, lowercase, numbers, and symbols).

4. The system shall provide a clear, user-friendly interface for returning users to log in securely.

5. Email registration capability is not yet implemented.

BR-UM-4.1.1.2: Beneficiary Profile

1. The system shall provide a dedicated section for users to manage their personal information.

2. The profile will be automatically built from imported VCs (Blue Dot profile).

3. Users profile fields are non-editable.

4. After soft-deleting the VCs, the following fields are being removed.

- Gender
- Caste
- Disability Status
- Annual Income
- Aadhaar Number
- Age
- Nsp Otr
- Student Type
- Udid
- Class
- Current School Name
- Previous Year Marks
- Disability Type
- Disability Range
- Bank Account Holder Name
- Bank Name
- Branch Code
- Bank Account Number
- Bank Ifsc Code
- Bank Address
- Tuition And Admin Fee Paid
- Misc Fee Paid
- State

1. User profile delete is not yet implemented.

BR-UM-4.1.1.3: Explore Benefits – Eligibility SDK Checks

1. The PWA shall display a catalog of all benefits available from integrated providers.

2. The system will use the Eligibility SDK to check the user's profile and VCs against scheme criteria.

3. The user interface must clearly highlight benefits for which the user is eligible under ‘My Benefits’ tab.

BR-UM-4.1.1.4: Benefit Detail - View Benefit Details

1. As a user, I want to see detailed information about the selected benefit, so that I can understand eligibility and requirements before applying.

2. Each benefit detail page must include a comprehensive description, a list of required documents, and a breakdown of eligibility criteria.

3. On this page, only the uploaded VCs are displayed in front of the required documents for the benefits to enhance the user experience.

BR-UM-4.1.1.5: Application Process

1. The application form shall be pre-populated with data from the user's profile and VCs based on the scheme's required fields.

2. The system shall indicate which fields are pre-filled and which require manual input.

3. The user must be able to review and confirm all data before submission.

BR-UM-4.1.1.6: My Applications

1. The PWA shall have a dedicated section to display the status of all submitted applications.

2. The status of the application will be updated by a cron job based on the Provider's actions on their end.

3. The user will be able to view the significant status changes (e.g., 'Approved' or 'Rejected' or ‘Any comment given by provider’).