LogoLogo
CommunityLicense
1.0.0
1.0.0
  • 🏠Home
  • 🏢Architecture
  • 📋Registration
    • Registration Interfaces
      • Mobile Registration App
      • Self Service Portal
      • API Interface
    • ID Verification
    • Registry
  • 🅿️Program Management
    • Eligibility Assessment
    • Enrolment
    • Deduplication
    • Disbursement Cycles
    • Entitlement
    • Verifiable Credentials
  • 💵Payment Management
    • Payment Cycles
    • Payment Batches
    • Payment Manager
    • Payment Types
      • In Account
      • Voucher
      • Cash
      • In Kind
    • Payment Rails
    • Accounting
      • Accounting
      • Reconciliation
      • Reports
  • Notifications
  • 📊Monitoring and Reporting
  • ⛓️Workflows
    • Cash grant scenario
    • On-Demand Assistance
  • 🔗Integrations
    • Mojaloop Integration
    • MOSIP Integration
      • ODK MTS Connector
      • Registry MTS Connector
      • Integration with e-Signet
  • ↔️API
  • ⚒️Testing
  • 👥Community
    • Contributing
    • Code of Conduct
  • 📗License
  • Guides
    • 📔How-To Guides
      • Create Program
      • Configure Proxy Mean Test
      • Create User and Assign Role
      • Create ODK Form
      • Create Portal Form
      • Provide Form Access to Field Agent
      • Download Form on ODK Collect
      • Register Offline
      • Self Register Online
      • Create MTS Connector
        • Create ODK MTS Connector
        • Create OpenG2P Registry MTS Connector
      • Enrol Registrants into Program
      • Create and Approve Disbursement Cycle
      • Prepare and Send Payment
      • Create Payment Manager under Program
      • Create Payment Manager Types
        • Create Payment Hub EE Payment Manager
        • Create Payment Interoperability Layer Payment Manager
        • Create Default Payment Manager
      • Create Eligibility Manager under Program
      • Create Eligibility Manager Types
        • Create Default Eligibility Manager
        • Create ID Document Eligibility Manager
        • Create Phone Number Eligibility Manager
      • Create Deduplication Manager under Program
      • Create Deduplication Manager Types
        • Create ID Deduplication Manager
        • Create Phone Number Deduplication
      • Create Notification Manager under Program
      • Create Notification Manager Types
        • Create SMS Notification Manager
        • Create Email Notification Manager
        • Create Fast2SMS Notification Manager
      • Send Notification to Individual Registrants
      • Configure ID Types
      • Map ODK Form
      • Integrate with MOSIP e-Signet
      • Map Self Service Portal Form
      • Install WireGuard App And Activate Tunnel
      • Install SmartScanner App
      • Submit Reimbursement Using the Service Provider Portal
    • 📙Documentation Guides
      • Creating Diagrams
      • Writing Guidelines For How-To Guides
    • 👩‍💻👩💻 👩💻 👩💻 👩💻 👩💻 Developer Zone
      • Getting Started
      • Technology Stack
      • About Github Repositories
        • openg2p-registry
        • openg2p-program
    • 📘Deployment Guide
      • Deployment on Kubernetes
        • K8s Cluster Requirements
        • K8s Cluster Setup
        • Rancher Server Setup
        • NFS Server Setup
        • SSL Certificates using Letsencrypt
      • Access to Deployed Setup
      • Post Install Configuration
      • Packaging OpenG2P Docker
Powered by GitBook
LogoLogo

Copyright © OpenG2P. This work is licensed under Creative Common Attribution (CC-BY-4.0) International license unless otherwise noted.

On this page
  • Introduction
  • Registration approaches
  • Registration interfaces
  • Registration features
  • Developer References
  • Guides
  • FAQs
Export as PDF

Registration

PreviousArchitectureNextRegistration Interfaces

Last updated 1 year ago

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 . 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 in the . 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)

Individual vs group registration

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

Continuous vs time-bound

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

Registration interfaces

Registration features

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:

Authentic

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.

Always available

Secure

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

Privacy-preserving

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.

Customizable intake

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

Notifications

Developer References

Guides

FAQs

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's allows social workers and field registration officers to record the applicant's information without any internet connectivity.

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

📋
Registration Interfaces
Mobile Registration App
Notifications
API
Code
Registry
Eligibility Assessment
Registry