Registration Processor


Registration Processor (Regproc) is a backend processing engine to enable the ID Lifecycle management. The diagram below shows the Registration Processor along with the other modules that contribute in issuing a Unique Identification Number(UIN) for an individual. Internally, Regproc follows the SEDA architecture where data flows via multiple stages till the UIN is issued.

The relationship of Regproc with other services is explained here. NOTE: The numbers do not signify sequence of operations or control flow

  1. Registration packets are uploaded by Registration Client to Packet Receiver.

  2. After packet validation is done Regproc notifies pre-registration application using datasync service.

  3. Quality of biometrics is checked using an external biometric SDK. This is done in Regproc's Quality Classifier stage.

  4. Regproc shares biometric data with ABIS, Manual adjudication System and Verification System. The policy for sharing this data is fetched from PMS.

  5. The above data is shared by providing a URL that partners use to fetch data. This URL is obtained from Datashare service.

  6. Regproc's ABIS Middleware stage communicates with ABIS via Activemq. The ABIS performs deduplication and sends back result to the Queue.

  7. Regproc stores and updates applicant demographic and biometric information in ID Repository. Also Activates or deactivates applicant UIN.

  8. Regproc calls IDA Internal Authentication Service to authenticate Applicant(for update flow), introducer, operator and supervisor(when bio auth mode is used to create packet).

  9. After the UIN is processed the Printing Stage calls Credential Service to create credential for print. This credential will be pushed to websub and the Printing systems will consume same.

  10. The Notification Service is used to send email/sms notification to the applicant after the request processing is completed in server.

  11. Regproc connects to external "Manual Adjudication System" via queue. Regproc sends applicant information required for adjudication in queue and external adjudication system consumes it. The data is shared from mosip to external adjudication system based on policy.

  12. Regproc calls Key Manager for decrypting packet and for encrypting information.

  13. Regproc uses Masterdata Service to validate center, machine, user etc.

  14. Regproc connects to Virus Scanner for scanning packets in Packet Receiver Stage and Packet Uploader Stage

  15. Each Stage in regproc calls Packet Manager to read information from packet.

Stages and services

The Registration Processor contains several stages and services.

The registration packet flows through the various stages depending on the type of flow. See Registration Flows and Stage Sequence.

Note: The Print Stage has been renamed as the Credential Requestor Stage. For further information, please click here.

Build and deploy

Refer to repo.


Refer to Configuration Guide.

Developer Guide

To know more about the developer setup, read Registration Processor Developers Guide.


Refer API Documentation.

Source code

Github repo.

Last updated

Copyright © 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.