Example 2: Widow cash transfer scheme
Last updated
Last updated
This process workflow provides an example for generic use case PRS.SR.01: SP-MIS queries the Social Registry to verify eligibility for programme enrolment. The example used is for a scheme that provides unconditional cash transfers to widows that have limited or no sources of income.
In this example enrolment in the scheme is initiated by the applicant directly. This may be in person at a social security office or online via the scheme portal.
SP-MIS uses the API to search the Social Registry using the UIN of the applicant, requesting that available data on both the applicant and their household are returned.
If the UIN for the applicant is found, the Social Registry returns data using the DO.SR.03 Member data object for all members of the household. This provides SP-MIS with the poverty score for the household as well as the UIN and date of death of the applicant’s spouse.
If required SP-MIS may then use the API to query the CRVS to verify the marital status of the applicant, verify that their spouse is deceased and (if required) verify the status of the applicant’s children.
This information is used by SP-MIS to determine if the applicant is eligible to enrol in the scheme.
Sections | Description |
---|---|
Process Purpose | The purpose of registration for the widows cash transfer scheme is to identify eligible widows and provide them with financial support and assistance after the loss of their spouse. |
Actors and Entities | Widow, SP-MIS, CRVS system. |
Assumptions |
|
Prerequisites |
|
Process Inputs | The widow may provide her Foundational ID or Marriage Registration Number for initiating the registration process. |
Process Flow Steps | Step 1: A widow initiates the registration process for the widow allowance scheme by providing her Foundational ID or Marriage Registration Number for identification purposes. Step 2: SP-MIS interfaces with the social registry. It transmits the Foundational ID or Marriage Registration Number and requests the associated household details Social Registry searches it's database for the Foundational ID or Marriage Registration Number. For the matching record it determines the household identifier. It then searches it's database for other people with the same household identifier. Social Registry returns to SP-MIS the full record for the applicant, which includes UIN, Name, DOB, Poverty Score, Household ID, Household Head: UIN, Relationship with Household Head. Social Registry additionally returns to SP-MIS the full records for household members designated as spouse or children. Step 3: SP-MIS securely sends the applicant's Birth Registration Number or Marriage Registration Number to the CRVS system to obtain her marital status and if married, UIN for her spouse. Step 4: SP-MIS sends her spouse UIN to the Civil Registration and Vital Statistics (CRVS) system to determine if her spouse is deceased or not Step 5: If the applicant meets the scheme's rules and criteria, SP-MIS queries the payment system to verify her bank account status. If the bank account is verified, the applicant is then placed on the disbursement list and will receive payments as per the scheduled disbursement process. Step 6: Upon successful verification, the applicant receives a mobile notification confirming the deposit of funds in her bank account. |
Outputs | Using the interoperability with the social registry and CRVS systems, SP-MIS can request beneficiary information that is exchanged at the trust level, and upon getting the information, SP-MIS can immediately decide whether or not to register the beneficiary. In the integrated environment registering the beneficiary and providing them with confirmation may take anywhere between five and seven minutes. Consequently, individuals are not required to carry a variety of documents; with only their Foundational ID, their data can be checked with CRVS, and they can be registered for the social protection programme. |
Control Points | SP-MIS is ultimately responsible for registering or not registering a beneficiary depending on the data received from other systems. |