SPAR
Social Payments Accounts Registry
Introduction
The Social Payments Account Registry (SPAR) is an extension of the ID Account Mapper that maintains a mapping of a user ID and Financial Address (FA) like bank code, account details, mobile wallet number, etc., primarily aimed at cash transfers in a social benefit delivery system. SPAR implements the functionality of an ID Account Mapper with additional feature of offering a self service portal for a beneficiary to add/update his/her FA. While in countries like India, the ID Account Mapper is updated by a bank (after authenticating a beneficiary), this may not be immediately feasible in many countries as all FSPs need to integrate with ID Account Mapper. In such situations, social welfare department can install SPAR and offer self service update, or via an agent. Of course, one important assumption is that online ID authentication mechanism is available in the country via APIs. For example, in MOSIP adopting countries both biometric and OTP based authentication is available.
SPAR is powerful inclusion tool as it gives end users ability to choose how they would like to receive the benefits.
SPAR may be housed centrally in a country as a building block of the Digital Public Infrastructure (DPI). Alternatively, a social welfare department can house it and enable other departments to use the same for cash disbursements.
The SPAR subsystem consists of 2 functional components
ID-Account Mapper
Self-Service-Portal
The ID-Account Mapper contains the actual mapping between beneficiary IDs and their respective accounts.
The Self-Service-Portal provides a Self Service to the beneficiaries who can log in into SPAR and update their own account information into the registry. The Self Service portal facilitates an easy to use interface like searching for a beneficiary's bank, his branch, her mobile service provider so that the beneficiary is able to provide the full financial address, where he/she wishes to receive the cash credits for the benefit programs.
Technical concepts
Configuration & deployment
Configuration Guide - TODO Link
SPAR Kubernetes Deployment Guide
Monitoring & Reporting
SPAR uses the Apache Superset for visualisation of data. Refer to Monitoring and Reporting for deployment and loading pre-configured dashboards.
User guides
Self-Service Portal Usage Guide
SPAR API Usage - TODO
API docs
Stoplight Link for Social Payments Account Registry
Swagger UI using OpenAPI for SPAR
Swagger UI for SPAR G2PConnect ID Mapper (which is used by SPAR, by default unless configured otherwise)
Swagger UI for G2P-Connect Financial Address Mapper
Swagger UI for Sunbird-RC's Financial Address Mapper (Alternative impl of G2P Connect ID Mapper)
Source code
Social Payments Account Registry Source Code - https://github.com/OpenG2P/social-payments-account-registry
SPAR UI Components Source Code - https://github.com/OpenG2P/spar-ui
SPAR G2P Connect ID Mapper Source Code - https://github.com/OpenG2P/social-payments-account-registry/tree/develop/spar-g2pconnect-id-mapper
Sunbird-RC's Financial Address Mapper Source code - https://github.com/Sunbird-RC/g2p-mapper-registry. Alternative impl of ID Mapper, which can be switched with SPAR G2P Connect ID Mapper
Roadmap
Components under development:
Linking of SPAR PSUT with Application PSUT.
Consent page for users to map token for a time period specifically for an app (like OpenG2P)
Automatic deletion of records based on expiry set
Maintaining linkage status (reflected on the portal for the user)
SPAR does not keep any status of account validation. Primarily, the financial account validation must be performed at the upstream system like OpenG2P etc. The suggested way in which the upstream system can do the validation is by performing a small amount or a zero amount transfer if supported by banks. And the upstream system can maintain the status and inform the user appropriately so that he/she or the bank can update it accordingly.
Last updated