Functional architecture

OpenG2P has a flexible architecture that allows governments and social benefit delivery systems to choose functionalities per their needs. The platform is built to allow inclusion and has supporting features. For example, beneficiaries in remote areas without network connectivity can be registered offline. The platform also supports multiple stages of approval with each approval carried out by a different officer.

Technical architecture

OpenG2P is an open source platform that provides the foundation to build government-to-person (G2P) solutions. The roots of the platform lie in the social benefit delivery systems originally developed in response to the Ebola outbreak in Sierra Leone.

The platform offers people facing processes such as onboarding into schemes, identity verification, and cash transfers to their bank accounts. It also incorporates government department facing features such as the creation of registries and beneficiary lists, eligibility checks, scheme definition, payment disbursement and reconciliation.

OpenG2P is a Digital Public Good (DPG) recognized by the DPGA and has received contributions and support from multiple organisations and implementers. Its roadmap includes support for non-monetary benefits, proof of delivery, beneficiary management, secure registries, and decision making support.

The project, co-founded by the Government of Sierra Leone and UNDP and supported by Mifos in the early stages, is now housed in IIIT Bangalore, a not-for-profit university in India.

Introduction

At the backend, the ID provided (functional or foundational) during registration is verified by submitting the demographic details and ID number by calling APIs of the corresponding ID system. The response from the ID system could be a yes/no response with optional data like ID token and KYC details.

Verification of MOSIP ID

Introduction

A given program will have certain criteria to consider individuals eligible for that program. Assuming that eligibility can be expressed unambiguously based on an individual's demographic data, a program manager can easily run the criteria on the registry to create a beneficiary list using domain filters and eligibility plugins.

Eligibility Manager

In OpenG2P, Eligibility Manager is a separate software module where the eligibility of a program is configured. If custom plugins are written, they are added to the Eligibility Manager.

Note that one eligibility manager can be associated with only one program. Each program should have its own eligibility manager created and configured.

Domain filters

Custom eligibility plugins

Example: Proxy Means Test

Introduction

In a given program, disbursement to beneficiaries is done in cycles. The entire entitlement to a beneficiary may be split into cycles for reasons of availability of funds, certain conditions that the beneficiary has to meet or other factors. Further, the beneficiary list may also undergo a change in different cycles based on updated eligibility criteria.

Cycle definition

Beneficiary list update

Splitting a beneficiary list across cycles

A beneficiary list may be split across cycles such that disbursement to a subset of the list is done in one cycle while for the rest disbursement is done in the next cycle.**

Introduction

Payment Manager is an interface to connect a downstream payment system, like Payment Hub. Multiple Payment Managers may be configured to connect to different systems. Each configuration is specific to the payment system.

Functionality

The Payment Manager creates batches and payment objects.

Introduction

Fund Management

Entitlement

Payments

Payment Batches

Program Fund Report

Accounting Journals

Introduction

OpenG2P platform offers registration of persons into programs via the following interfaces:

1. Mobile registration app

2. Self-registration by a potential beneficiary

3. API-based registration by other systems

Agent-assisted registration supports in areas where connectivity may be a challenge.

Registration can be done for individuals or groups like families, households, schools, etc.

Introduction

The Program Management module offers a rich set of functions to define various beneficiary programs (schemes), enrol beneficiaries based on eligibility, calculate entitlements and disburse benefits to the beneficiaries.

Program definition

Program states

• Created

• Ended

• Reactivated

A program may be targeted to an individual or a group. A group may be a household, family or any other group to which the program is targeted.

Introduction

A program may have disbursement done in multiple time cycles with start and end dates for each cycle. Such cycles may be defined and triggered as per the schedule defined in each cycle.

Cycles

Introduction

Entitlement is the quantity of benefit that a beneficiary is entitled to receive. For cash transfers, this is money that a beneficiary will receive via either direct bank transfer, mobile wallet, cash at the counter, vouchers or other disbursement mechanisms. Entitlement is defined for each cycle.

Entitlement Manager

Approval process

Introduction

In each payment cycle, the payment transactions are done in batches. There could be several reasons for batching the payments. The transaction limits may be imposed by payment switch, or any other entity in the payments chain.

Batch statistics

Batch completion status

A typical flow of enrolling a beneficiary by collecting data on the field by an agent, in offline mode, is illustrated below.

Test cases and verification

The Excel sheet below lists test cases and their verification status for different versions of software. This is a live sheet, and will have the latest status of verification.

Description

This guide provides the steps to create MTS Connectors.

There are two types of MTS Connectors differentiated based on input types

1. ODK

2. OpenG2P Registry

Pre-requisites

The user must have a Program Manager role. See guide.

The person's information is filled in forms on Android devices and submitted to the backend for further processing. The ODK application is integrated with a QR code scanning application that enables an automatic population of KYC data of the person in the form along with verification of digital signature establishing the authenticity of the card.

• Program creation

• ODK form template creation

OpenG2P offers the on-demand approach via the Self Service Portal where a person logins via his/her ID and then applies for a program. In self-service mode, typically, OTP would be used for login. In assisted mode, the registering officer may have biometric devices connected to his/her machine, and the registrant can perform biometric authentication in an online manner.

Online registration assumes that an ID verification service is available to connect via APIs and perform verification of the identity of a person. In the case of MOSIP, for e.g, the verification can be done using the solution.

OpenG2P offers a reference implementation of a person facing Self Service Portal that lets a person log in to the portal using a national ID or other IDs, and perform the following functions:

• View enrolled programs

Enrolment is the process of creating a beneficiary list of individuals or groups by querying the registry and applying eligibility criteria. OpenG2P provides convenient filters and plugins to make the entire process frictionless, convenient and time-saving.

Program eligibility could be defined as simple filters on the data collected for individuals (residing in the registry) or could be more sophisticated like Default filters and plugins are provided that would meet most of the eligibility definitions. For complex eligibility criteria, custom plugins can be written and added to the .

Deduplication refers to the process of removing duplicate entries in the registry, thus avoiding double-dipping, and merging all the demographic fields associated with an individual or a group into a single record.

Individuals are deduplicated by any of the below methods or a combination of these:

If a country has issued unique foundational IDs (like ) then deduplication is trivial -- there is only one record associated with an ID. For privacy, the foundational ID itself is not stored in the registry. Instead, a or associated with the ID is stored.

If functional IDs like driver's license, tax number, student ID etc. are accepted while registration, then deduplication across IDs is somewhat challenging if a link between these is not already established and available to the OpenG2P system. In this case, heuristics are applied to demographic data to detect potential duplicates.

In case registrants were onboarded without an ID, the deduplication is performed using heuristics on demographic data.

The Payments module consists of several functions to efficiently execute cash transfers to the beneficiaries and report the status of payments. Out of the box, OpenG2P offers payment connectors for and with flexibility to create custom connectors specific to the payment rails of a country.

Payments are generally executed in and .

Digital payments infrastructure (DPI) could vary from country to country. It is therefore necessary that social benefit delivery systems have the ability to connect to the prevailing DPI and perform G2P payments efficiently. OpenG2P platform provides flexibility to connect to a payment system by writing custom connectors. By default, the platform offers interoperability with the following:

OpenG2P can use for authentication. e-Signet provides an interface for authentication while connecting to the MOSIP's IDA services on the backend.

Here, OpenG2P is a Relying Party and the Authentication System is MOSIP. Learn .

Refer to the guide .

All containing source code are licensed under the terms of .

All trademarks are the property of their respective holders. Other products and company names mentioned may be their respective owners' trademarks and/or service marks.

This documentation work is licensed under a .

The guide here provides steps to create a new user and assign a role. This process is typically done by the Administrator.

The user should have an Administrator role.

1. Navigate to Settings using the menu bar.

This guide will help to provide the form access to the field agent. which helps the agent to download the program form.

The access provider should have the Administrator role in ODK Central.

1. Login to ODK central with a user having an Administrator role.

2. Click on the program name in Projects on which the agent access is to be provided.

This guide will help to download the program form on ODK Collect Application running on an Android tablet or phone.

• The field agent should have ODK Collect Application installed.

• The field agent should have.

This Guide will help to create the .

• The user must have a Program Manager role.

• ODK form should be available.

This Guide will help to create the .

The user must have a Program Manager role.

1. Navigate to the MTS Connectors using the menu bar.

This guide will provide the types of payment managers that can be created and then can be configured to the program accordingly.

Notifications to beneficiaries and administrators are a must-have, especially when there are multiple stages of a delivery chain, usually with long time intervals between various stages. The beneficiaries must be informed about their enrolment status, entitlements, disbursements, exit etc. Multiple methods of notifications may be employed like postal and courier service, SMS, email, and messaging apps.

OpenG2P provides in-built support for email and SMS with simple configuration changes. The notifications are triggered at certain default points in the delivery chain, however, depending on the needs of a specific implementation more trigger points may be added.

There are 3 types of eligibility managers available that can be created and then can be configured to the program accordingly.

There are 2 types of deduplication managers available that can be created and then can be configured to the program accordingly.

There are 3 types of notification managers available that can be created and then can be configured to the program accordingly.

1. SMS Notification Manager

2. Email Notification Manager

• Capitalize the first letter of every word in the guide title.

• Use second-person pronouns i.e. you, your, etc. in the instructions/steps.

• It is mandatory to do spelling and grammatical corrections using tools such as Grammarly.

• Use the italicized font for UI elements i.e. dashboard names, button labels, information fields, etc.

• Use the exact name and case for the UI elements.

• Use quotes for a phrase/word if the phrase/word has to be represented as is.

• Provide a link at the first mention of a new/different topic. For example, if the guide is talking about installing the SmartScanner app, and the WireGuard app is mentioned, then provide the link for WireGuard.

• Use clear and crisp images.

• The filename for images should follow the naming convention of every word in lower case, and words separated by hyphens i.e. view-all-programs.png.

Description

This guide will provide the steps to create an SMS notification manager.

Pre-requisites

The user should have a Program Manager role assigned.

Steps

1. Navigate to Programs using the menu bar

2. Click on Configuration and then on SMS Notification Manager.

3. Click the Create button to navigate to the SMS notification manager creation page.

Introduction

This page describes the integration of OpenG2P with the Mojaloop switch enabling cash transfer from one bank (treasury bank, for instance) to an individual's bank account. The connection to Mojaloop is achieved via an intermediate interoperability layer like the Payment Hub of Mifos.

Functional architecture

Below is the reference architecture of disbursements triggered from OpenG2P resulting in cash transfers.

Payment process

The beneficiary list is created on OpenG2P. After creating payment cycles and entitlements, payment batches are created for each cycle. A batch payment is triggered via the Payment Manager. This batch is received by the Payment Hub (PH) and payments are orchestrated either in bulk or individually. The Payment Hub connects to the Mojaloop interface of the Digital Financial Service Provider (DSFP). DFSP1 takes the transaction forward with Mojaloop Switch.

Reconciliation at the OpenG2P end is done via status API calls to Payment Hub which is responsible for gathering payment status information of all transactions from DFSPs and Switch.

In the current integration, the account id of the payee is available in the OpenG2P registry and passed on to Payment Hub (hence propagated to Mojaloop). The account id of the payer is configured in the.

The payment architecture may vary from country to country. An interoperability layer like Payment Hub shields the downstream variations by offering a uniform payments API interface such that systems like OpenG2P do not have to modify the payments code, thus enabling interoperability with any payment system. Of course, customisation needs to be done on the Payment Hub, where a specific Payment Connector needs to be created specifically for the payment systems interface.

Payment Hub connects to Mojaloop via the Mojaloop Connector.

The source code for OpenG2P - Payment Hub integration can be found .

Description

This guide provides steps to create a new portal form for a program. This form will show up on the Self-Service Portal when the user selects a program to apply.

Pre-requisites

The user must have a Program Manager role. See Create User and Assign Role guide.

Steps

1. Navigate to the Website using the menu bar.

1. Click on Go to Website to navigate to the website home page.

1. Click on the + New button to create new form.

1. Click on Page to create a form.

1. Enter the page title and click on Create button under New Page pop-up window.

1. Drag and drop the Form in the Dynamic Content from the BLOCKS section.

1. Edit the form fields from the STYLE section.

1. Add more form fields using +Field from the STYLE section.

2. Save the form using the Save button.

Description

This guide will provide the steps to register beneficiaries through an offline process. offline registration is done by the Field Agent.

Pre-requisites

• The agent should have ODK collect and Smart Scanner Application Installed

• Agents should have form access.

• Agents should have downloaded the program form on his/her device.

• Beneficiaries should have their National ID card with them.

• ODK MTS Connector which is mapped to the form should be in Running status.

1. Open the program form from the ODK Collect application.

1. Click on Fill Blank Form to fill in all form fields with beneficiary data.

1. At some point, the form will have the Launch button. Click on the Launch button to scan the QR code on the National ID of the Beneficiary.

1. Once the scanning is done beneficiary data will be auto-populated as per the form fields configuration.

1. After filling in all the mandatory fields click on the Save and Submit button.

• If the Field Agent is online, the submitted entries will be sent to ODK Central and will be listed under View Sent Form or else they will be saved in the Field Agents device in Send Finalized Form Section.

Description

This guide provides steps to create and configure the payment manager.

Pre-requisites

The user must have the Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on the program name for which configuration to be done.

1. Navigate to the Configuration section on Program detailed view page.

1. Click on Add a line in the Payment Manager section.

1. Click on the Create button on the Add: Payment Managers pop-up window.

1. Select the payment manager type.

1. If a payment manager is already created (), search and select the same or else once the name is provided to the program manager, Create and Edit buttons will appear. Click on Create and Edit to create a payment manager.

1. Provide the details in the payment manager creation manager.

1. Click on the Save button and then click on the Save & Close button which will save the payment manager to that program under configuration.

Description

This guide will help enrol registrants into a program, who are registered through offline registration and online self-registration process.

Pre-requisites

• The user must have a Program Manager role. See Create User and Assign Role guide.

• There should be registrants with respect to the program

Steps

1. Navigate to Programs using the menu bar.

1. Click on the program name on which enrolment needs to be done.

1. After landing on Program detailed view page, check the beneficiaries section for the registrants who are in draft status.

1. Navigate back to the program list view page and click on Enrol Eligible Registrants to enrol the registrants who are in draft status.

2. Enrolment of registrants will be based on the Eligibility criteria set as per the program.

3. The registrants who pass the eligibility criteria will be enrolled on the program with Enrolled status and those who fail the eligibility criteria will be given Not Eligible status.

Introduction

On-demand assistance is especially useful for scenarios like urgent surgeries, treatments, and other crises. However, to prevent instances of fraud, it is imperative to do a thorough assessment of beneficiary entitlement. This section details one reference implementation using multiple stages of approvals.

Process

1. The beneficiary logs into Self Service Portal and provides details of assistance such as the type and cost of treatment along with the name, address, gender, age, occupation, and family information.

2. The assistance application is reviewed and assessed in multiple stages by the officers designated by the program administrator/manager. At each stage, the designated officer will either approve/reject the application with a valid reason. If the application is rejected at any one of the stages, the approval process stops.

3. After all the designated officers approve the application, the final approving officer will also issue an entitlement voucher. The entitlement voucher has a QR code that can be scanned to view beneficiary entitlement and prove the authenticity of the entitlement voucher.

4. The beneficiary takes the entitlement voucher to the service provider. The service provider scans the entitlement voucher. If the QR scan is valid, the service provider assists the beneficiary.

This example describes on-demand assistance with multi-stage approval.

• The program manager/administrator can custom-assign an assessment officer for each stage.

• Though this example shows three stages, the number of stages can be customized.

• The entitlement voucher can be communicated digitally or printed on paper.

Description

This guide provides the steps to create an phone number eligibility manager

Pre-requisites

user should have a Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on ID document Eligibility Manager.

1. Click Create a button on the phone number eligibility manager list view page.

1. Provide the name for the eligibility manager and select the program name from the drop-down for which the eligibility manager is created.

1. Click the Save button to save the eligibility manager and it will be listed under the eligibility manager list view page.

User authentication

Individual Registration

Group Registration

Description

This guide provides the steps to create a Default Payment Manager.

Pre-requisites

The user should have a Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on Payment Interoperability Layer Payment Manager.

1. Click on Create button which will navigate to the Default Payment Manager creation page.

1. In the payment manager creation page provide a name for the payment manager, select the program name, select Automatically Create batch if required and select the Currency.

1. Once the payment manager is saved it will be listed under the payment manager list view page which further can be used under the program configuration for which it was created.

Description

This guide provides the steps to prepare payment after approving the cycle of a program.

Pre-requisites

The program cycle should be created for a program.

Steps

1. Navigate to the program for which cycle creation and approval are done.

1. Click on the Prepare Payment button to create a batch for the approved cycle entitlements.

1. Once the payment batch is created, navigate to Accounting.

2. Click on Payment Batches to proceed further with payment.

1. Click on the payment batch to which payment needs to be done.

1. On the payment batch, detailed view page click on Send Payment button to make the payment.

1. Check the payment status in the payments section of the payment batches detailed view page.

Description

This guide provides the steps to create an ID document eligibility manager

Pre-requisites

user should have a Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on ID document Eligibility Manager.

1. Click Create a button on the ID document eligibility manager list view page.

1. Provide the name for the eligibility manager and select the program name from the drop-down for which the eligibility manager is created.

1. Click the Save button to save the eligibility manager and it will be listed under the eligibility manager list view page.

Introduction

OpenG2P integrates with MOSIP to verify the UIN/VIDs provided by individuals as part of the registration process. As a result of the verification, OpenG2P receives a unique token against an individual's UIN/VID along with KYC data. This data is stored in the registry.

There are two ways to obtain the MOSIP tokens:

1. For new registrations that are conducted via ODK form, The MTS Connector is configured to pull data directly from ODK Central and return MOSIP tokens. See ODK MTS Connector.

2. For already existing records in the registry, the is used to trigger a connection with MTS and in turn receive MOSIP tokens for all the records requested.

Description

This guide provides the steps to create Payment Hub EE Payment Manager.

Pre-requisites

The user should have a Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on Payment Hub EE Payment Manager.

1. Click on Create button which will navigate to the Payment Hub EE Payment Manager creation page.

1. In the payment manager creation page provide a name for the payment manager, select the program name, select Automatically Create batch if needed, and all the other configurations will auto-populate and can be changed accordingly.

1. Once the payment manager is saved it will be listed under the payment manager list view page which further can be used under the program configuration for which it was created.

Description

This guide provides the steps to create a default eligibility manager

Pre-requisites

user should have a Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on Default Eligibility Manager.

1. Click Create a button on the default eligibility manager list view page.

1. Provide the name for the eligibility manager and select the program name from the drop-down for which the eligibility manager is created.

1. Use +Add filter to set eligibility criteria using . You may specify multiple eligibility criteria.

1. Click the Save button to save the eligibility manager and it will be listed under the eligibility manager list view page.

Description

This guide provides steps to create a Phone Number Deduplication manager.

Pre-requisites

The user should be assigned to the Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on ID Deduplication Manager.

1. Click the Create button to navigate to the Phone Number Deduplication manager creation page.

1. In the Phone Number Deduplication manager creation page provide a name for the Phone Number Deduplication manager, and select the program name.

2. Once the Phone Number Deduplication manager is saved it will be listed under the Phone Number Deduplication manager list view page which can further be used under the program configuration for which it is mapped.

Description

This guide provides the steps to create a Payment Interoperability Layer Payment Manager.

Pre-requisites

The user should have a Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on Payment Interoperability Layer Payment Manager.

1. Click on Create button which will navigate to the Payment Interoperability Layar Payment Manager creation page.

1. In the payment manager creation page provide a name for the payment manager, select the program name, select Automatically Create batch if required, provide the Payment End Point URL and Select the Payee DFSP ID Type.

1. Once the payment manager is saved it will be listed under the payment manager list view page which further can be used under the program configuration for which it is mapped.

Description

This guide provides steps to create an ID Deduplication manager.

Pre-requisites

The user should be assigned to the Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on ID Deduplication Manager.

1. Click the Create button to navigate to the ID deduplication manager creation page.

1. In the ID deduplication manager creation page provide a name for the ID deduplication manager, and select the program name and the ID type from the Supported ID Document Types drop-down.

1. Once the ID deduplication manager is saved it will be listed under the ID deduplication manager list view page which can further be used under the program configuration for which it is mapped.

Description

This guide will provide the steps to create a Fast2SMS notification manager.

Pre-requisites

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on Fast2SMS Notification Manager.

1. Click the Create button to navigate to the Fast2SMS notification manager creation page.

1. Fast2SMS notification manager creation page

• Name: Provide a name for the manager

• Program: Select the program from the drop-down for which the manager is created

• On Enrolled In Program Template: Select the template from the drop-down for program enrolment notification.

1. After clicking on the Save button notification will be saved under the Fast2SMS notification manager list view page.

Description

This guide will provide the steps to create an Email notification manager.

Pre-requisites

The user should have a Program Manager role assigned.

Steps

1. Navigate to Programs using the menu bar.

1. Click on Configuration and then on Email Notification Manager.

1. Click the Create button to navigate to the email notification manager creation page.

1. Email notification manager creation page

• Name: Provide a name for the manager

• Program: Select the program from the drop-down for which the manager is created

• On Enrolled In Program Template: Select the template from the drop-down for program enrolment notification.

1. After clicking on the Save button notification will be saved under the email notification manager list view page.

Description

The guide here provides steps to install WireGuard App and activate the tunnel. This app allows users to create an encrypted VPN for secure communication.

Pre-requisites

The user must possess an Android Phone. The user should reach out to the system administrator to generate the Wireguard conf file before proceeding with the installation.

Steps

1. Search for "wireguard" in the Android Play Store.

1. Install the WireGuard app, open it, and click on the + icon to add the tunnel.

1. A list of options will appear from the bottom of the app. Click the Import from file or archive option.

1. Select the WireGuard conf file provided by the system administrator. On successful tunnel creation, the tunnel name will appear at the top of the app.

1. Activate the tunnel in WireGuard.

OpenG2P registry is a single repository containing details of the registrants. The registry uses for maintaining the information in a single DB table.

The purpose of the registry is to provide a single source of truth to the program administrators and managers. Program administrators can grant access to other program participants to act on this information.

Identification of records in the registry is done with configured . ID can be foundational like MOSIP ID or functional like a voter's card, tax number, driving license, etc.

Individual registrant information is entered in a single row. Whereas group details are stored in multiple rows in the form of relationships with the head or representative of the group.

OpenG2P platform supports multiple entries for a registrant in the registry. The intent is to keep all the entries for a registrant and deduplicate later at the program level if required. Multiple entries allow program administrators the flexibility to build a registry without bothering about duplicate entries, especially during a crisis situation such as a flood, earthquake, tsunami, etc. and work on deduplication later using the

This guide helps beneficiaries to self-register through the beneficiary portal.

Beneficiaries should have the MOSIP-issued national ID with them.

1. Go to the beneficiaries portal login page.

1. Click on

OpenG2P is a collaborative effort of several contributors. We welcome contributions to the OpenG2P Project.

Raise bugs/issues/tasks on GitHub Issues of individual repositories.

All the issues and tasks are tracked using .

To contribute code to the OpenG2P project, follow the steps given below:

1. Create an issue on Github related to your task.

This guide provides steps to create and configure the eligibility manager inside the program.

The user must have the Program Manager role.

1. Navigate to Programs using the menu bar.

This guide provides steps to create and configure the notification manager.

The user must have the Program Manager role.

1. Navigate to Programs using the menu bar.

The guide here provides steps to submit reimbursement using Service Provider Portal.

The Service Provider Portal user has login access to the portal using MOSIP ID/National ID. The user should be able to scan the QR code from the entitlement voucher using .

1. Login into the Service Provider Portal using MOSIP ID/National ID. In the example below, the National ID of the Philippines (PhilSys ID) is shown.

This guide provides steps to create a new ODK form for a program.

• should be deployed and available.

• The user should have an Administrator role in ODK Central. See guide.

This guide will provide the steps to create and approve the disbursement cycle under a program.

The user should have a role which is configured in the Approver Group under Configure the Cycle Manager while .

1. Navigate to Programs using the menu bar.

This guide provides steps to create and configure the deduplication manager inside the program.

The user must have the Program Manager role.

1. Navigate to Programs using the menu bar.

The guide here provides steps to install the SmartScanner app. This app allows users to scan the QR code in the entitlement voucher.

The user must possess an Android Phone with activated.

1. Download the SmartScanner APK file named idpass-smart-scanner-untagged-<version>.apk on your Android mobile from .

Introduction

In the OpenG2P platform, registration is a series of three processes - intake, recording, and verification. Intake is the process of gathering information from applicants while recording and verification are the processes to add the authenticated information to the Registry. The platform verifies the applicant's details in the background by confirming the identity and demographic details of the applicant digitally.

Registration aims to provide detailed records for Eligibility Assessment in the Registry. It must be noted that at this stage, the people are referred to as applicants or registrants. Once the applicants/registrants pass the eligibility criterion set by the program manager, they become eligible to enrol in the program and are referred to as beneficiaries.

This is a pictorial representation of the OpenG2P registration process.

Registration approaches

Registration can be carried out via multiple channels such as digital service windows/kiosks, social workers, local registration offices, door-to-door visits, referrals from other programs, etc. The registration approach can be either on-demand or administrative-driven. Three key features distinguish between these two approaches:

Applicant-initiated vs program-initiated

Whether the registration process was initiated by the applicant (on-demand) or by the program administrator (administrator-driven)

Whether applicants registered themselves individually (on-demand) or registered as a group/family/household (administrator-driven)

Whether applicants could register at the time of their choosing (on-demand) or had to apply in a specific time window (administrator-driven)

While on-demand and administrative-driven approaches are two distinct models, the registration process operates in a spectrum between these two models. For example, a program may allow the applicants to register individually (on-demand) but may allow them to apply only in a certain time window (administrative-driven). OpenG2P platform has a flexible implementation and through its various aims to cater to a combination of approaches across different registration modalities and programs.

OpenG2P registration interfaces are key client-facing interfaces. The clients here could be the applicants, social workers, program administrators, program managers, etc. There are the main features offered by these interfaces:

The clients log into the system using their MOSIP ID/National ID allowing the information to be verified while it is being recorded. Additionally, logging in using National ID can pre-fill the information fields in an authentic manner.

OpenG2P's allows social workers and field registration officers to record the applicant's information without any internet connectivity.

The applicant's information is encrypted at rest and during transit allowing the information to be secure against malicious attacks.

The platform allows for consent forms to be filled out and recorded before starting the intake. The recorded information is not used for any purpose other than the explicitly stated purpose in the consent form.

The applicant information is filled in using general intake sheets. These intake sheets can be customized per the assessment information required by the program.

The platform can be configured to send to the applicants via multiple channels such as email, sms, etc.

Contributor Covenant Code of Conduct

Preamble

OpenG2P was created to foster an open, innovative and inclusive community around open source & open standard. To clarify expected behaviour in our communities we have adopted the Contributor Covenant. This code of conduct has been adopted by many other open source communities and we feel it expresses our values well.

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

• Demonstrating empathy and kindness toward other people

• Being respectful of differing opinions, viewpoints, and experiences

• Giving and gracefully accepting constructive feedback

• Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

• Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

• The use of sexualized language or imagery, and sexual attention or advances of any kind

• Trolling, insulting or derogatory comments, and personal or political attacks

• Public or private harassment

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

This Code of Conduct is adapted from the .

Community Impact Guidelines were inspired by .

For answers to common questions about this code of conduct, see the . Translations are available .

Description

The guide provides steps to enable and configure the proxy mean test.

Pre-requisites

The user must have a Program Manager role.

Steps

1. Navigate to Programs using the menu bar.

1. Click on the program name for which configuration to be done.

1. Navigate to the PMT Configuration section on Program detailed view page.

1. Enable PMT and click on Add a line in the PMT Parameters field.

1. Select the field and provide its weightage.

1. Click on the Save & New button to select a new field and provide its weightage or Save & Close button which will save the fields and their weightage to that program under configuration.

1. Click on the Save button.

1. Navigate to Settings using the menu bar.

1. Click on Technical in the setting menu.

1. Navigate to Models under Database Structure heading.

1. Search Program Registrant Info model in the search bar.

1. Click on g2p.program.registrant_info model.

1. Click on add a line in Fields section.

1. Add field name, type, label, dependencies field and compute logic.

1. Click on the Save & New button to select a new computed field or Save & Close button which will save the computed field in the model.

1. Click on the Save button.

Description

The guide here provides steps to create a new program. A program is typically created by a Program Manager who can create and administer programs.

Pre-requisites

The user must have a Program Manager role. See Create User and Assign Role guide.

Steps

1. Navigate to Programs using the menu bar.

1. Click on the Create Program to reach the Program creation page. Provide Program name, target type and currency. There are tabs for the configuration of various managers.

2. Eligibility criteria:
3. Use+Add filter to set eligibility criteria using . You may set multiple eligibility criteria.

4. Cycle Manager: Set parameters of .

   • Auto-approve Entitlements: To set entitlements via rules, without any manual approvals.

   • Approver Group: The group name of the user who has permission to approve cycles. See

5. Entitlement Manager: Set parameters for .

   • Amount Per Cycle: The amount disbursement of a group or individual per cycle.

6. Map Portal form: Map a portal form to this program. before this mapping.

7. Click the Next button to import the matching registrants to the creating program. In the pop-up window select Yes.

1. Once the program is created it will be listed under the program list view page.

ODK MTS Connector is an OpenG2P Odoo addon that fetches tokenised data from the ODK Central by calling the (MTS) and stores it in the registry.

• Uses callback delivery type of MTS

• Completely asynchronous execution

Overview

Registry MTS Connector (RMC) is an Odoo addon that fetches MOSIP Auth Token against any record in the registry by calling MOSIP Token Seeder (MTS) and stores the same in the registry.

Features

• Generates MOSIP token against the OpenG2P registry by calling MTS.

• Uses callback delivery type of MTS

• Completely asynchronous execution

• OpenG2P can schedule a daily job to fetch the delta for the day

• A manual import feature will also be provided

• Removes VID if MOSIP Auth Token is generated

Context

Creating editable diagrams in open formats using open source tools is challenging. Here, we suggest Draw.io for creating diagrams and saving them directly in GitHub repository.

Creating new diagram

1. On Draw.io website choose Device as your storage.

1. Select the format of the diagram as XML.drawio.

1. Create the diagram and save it on your local machine. Make sure you follow the file naming convention of lowercase with hyphens as word separations.

2. Fork openg2p-documentation repository to your Github account.

3. Disable workflow in your repository fork:

1. On Github, upload/commit the .drawio file to your fork of openg2p-documentation repository in the branch of choice to the following folder: .gitbook/assets.

2. Send a Pull Request.

If a .drawio already exists in the .gitbook/assets folder then you must directly edit the repository version of the same by following the procedure given below.

1. Fork the openg2p-documentation repository to your local Github account. Disable workflow as shown above.

2. On the website choose Github as your storage.

1. Authorize the Draw.io app on Github (follow the steps prompted).

2. Select the diagram in .drawio format from openg2p-documentation --> your branch --> .gitbook/assests folder.

1. Make changes.

2. Save the diagram - it will get Git-committed to your repository.

3. Send a Pull Request to OpenG2P/openg2p-documentation repo.

1. Delete the diagram from Gitbook listing found here:

1. Delete the diagram from Github repository openg2p-documentation from the corresponding branch

This page lists all the technologies used in building OpenG2P. Free and open-source softwares with clear long-term support availability have been chosen. Certain choices can be replaced with other free or commercial options for deployment.