Skip to content
Vijay Vujjini edited this page Feb 14, 2023 · 23 revisions

G2P Connect - Integration Specifications

1. Overview

G2P Connect Integration Specifications open source effort goal is to standardise the key integrations across functional categories defined in G2P Connect Technology Architecture Blueprint.

G2P Connect Integration Specification assumes interaction between DPG projects, Proprietary/Existing systems may vary due to underlying landscape across countries. For e.g.,

a. Few countries may have centralised payment switch operated by central bank while others may operate directly with financial institutions.
b. Countries may decide to manage ID to Financial Address mapping either at Payment Switch layer or Financial Institution(s) or Beneficiary Management Platforms or an independent entity, etc.,

For these reasons G2P Connect is flexible to enable DPG projects, Proprietary/Existing systems to orchestrate the flows based on various use case scenarios that are specific to country's operating requirements.

2. Technical Design Considerations

2.1. Transport layer agnostic
  1. G2P Connect Integration Specification focus primarily on standardising the interfaces for input and output formats that are transport layer agnostic viz. JSON entities over HTTPS, Event based messaging and File transfers using HTTPs or secure FTP.
  2. Separation of transport layer messaging and functional layer processing using standard header and function specific payloads e.g Disburse, Linking, Resolve, etc.,
2.2 Secure
  1. signature element ensures messages are non-repudiable.
2.3 File based processing
  1. JSON format based payload is recommended for file based exchange. JSON format enables hierarchal and self describing entity structures.
  2. If country wants CSV or similar formats, it is recommended to flatten the JSON structure.
  3. first line to signature, second line message header and 3rd line onwards to hold the message payload.

3. G2P Connect Interfaces

Below interface codes help to easily identity functional areas for implementation partners

Interface Interface Code Description
Authorization AuthZ Guidelines on Authentication & Authorisation
Disbursement DISB Initiate disbursement, check disbursement status, etc.,
Financial Address Mapper FAMAP Link, unlink, resolve, status, etc.,
Identity ID APIs to foundational identity authentication & eKYC services
Scheme Management SM APIs to manage schemes - define, eligibility/disbursement rules, sponsor a/c linking, etc.,
Beneficiary Management BM APIs to manage Beneficiaries - enrol, check eligibility, digital credentialing, etc.,
Digital Credentialing DC APIs to issue, manage digital verifiable credentials to eligible beneficiaries
Clone this wiki locally