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.
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
| Property | Configuration |
|---|---|
Name
A string to identify the connector
URL to reach MTS
URL for MTS API
MTS Input type
OMC option could be proceeded by selecting OpenG2P Registry.
Mapping
MTS Field mapping as required by the API. Please refer to MTS Documentation. Format of Mapping would be JSON.
Output Type
MTS-C only supports JSON output type of MTS.
Output Format
Output format is a JQ string which will be used by MTS to format its output to suite the caller's requirement.
Delivery Type
Currently supporting only "Callback". Callback feature can be used to make MTS do a submission of results onto an API within Odoo. The output formatting will help in making the desired input for the api.
Job Type
MTS-C provide both recurring and one time execution. Recurring can be configured to do continuous pull from the ODK over MTS.
MOSIP Language
Mosip language setup. Default is eng.
Interval in minutes
Interval at which the MTS-C job runs.
Filters to apply to Registry
A domain filter can be used to identify the records for tokenisation. For. eg. Only records which have VID associated with it and are not tokenised need to be picked for tokenisation.
List of fields to be used
List of fields which will be supplied as auth data. This field list may be a superset of fields required for auth as it may contain data required by the callback API. This list should be a valid JSON string array.
Callback URL
A URL endpoint which would be called upon successful processing at MTS
Callback HTTP Method
HTTP Method (POST/PUT/GET/PATCH) used while MTS makes the callback
Callback Timeout
Timeout awaited by the callback until acknowledged with a response.
Callback Auth Type
Type of authentication expected by callback URL. MTS-C currently support Odoo type which uses the session-based authentication implemented by Odoo.
Callback Auth Database
DB instance used by Odoo.
Callback auth username
Username to access callback API
Callback auth password
Password to access callback API
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
OpenG2P can schedule a daily job to fetch the delta for the day
Manual import feature (TBD)
| Property | Description |
|---|---|
Name
A string to identify the connector
URL to reach MTS
URL for MTS API
MTS Input type
MTS-C connects over "ODK" which is the first option in this selection. OMC option could be proceeded by selecting OpenG2P Registry.
Mapping
MTS Field mapping as required by the API. Refer to MTS Documentation. The format of Mapping would be JSON.
Output Type
MTS-C only supports JSON output type of MTS.
Output Format
Output format is a JQstring which will be used by MTS to format its output to suite the caller's requirement.
Delivery Type
Currently supporting only "Callback". Callback feature can be used to make MTS do a submission of results onto an API within Odoo. The output formatting will help in making the desired input for the API.
Job Type
MTS-C provides both recurring and one time execution. Recurring can be configured to do continuous pull from the ODK over MTS.
Interval in minutes
Interval at which the MTS-C job runs.
MOSIP Language
MOSIP language setup. The default is "eng".
ODK Base URL
Base URL or the complete domain address for the ODK central installation
ODK Odata URL
OData service (.svc) URL for the ODK form to fetch the submissions.
ODK User email
Email Id to authenticate MTS for accessing Odata URL
ODK User password
Password used to authenticate Odata URL
Callback URL
A URL endpoint which would be called upon successful processing at MTS
Callback HTTP Method
HTTP Method (POST/PUT/GET/PATCH) used while MTS makes the callback
Callback Timeout
Timeout awaited by the callback until acknowledged with a response.
Callback Auth Type
Type of authentication expected by callback URL. MTS-C currently support Odoo type which uses the session-based authentication implemented by Odoo.
Callback Auth Database
DB instance used by Odoo.
Callback auth username
Username to access callback API
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:
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.
For already existing records in the registry, the Registry MTS Connector is used to trigger a connection with MTS and in turn receive MOSIP tokens for all the records requested.
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.
Below is the reference architecture of disbursements triggered from OpenG2P resulting in cash transfers.
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 Payment Manager.
If Account Mapper is available as part of Digital Public Infrastructure, then the account id need not be stored in the OpenG2P registry.
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.
As part of the roadmap, OpenG2P is working towards supporting payments interfaces being defined as part of the G2P Connect initiative.
The source code for OpenG2P - Payment Hub integration can be found here.
OpenG2P can use e-Signet for authentication. e-Signet provides an OIDC 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 more.
Refer to the guide Integrate MOSIP e-Signet.
