# Govt to Person (G2P)

### Financial Address Mapper

As governments explore efficient ways to reach out to its beneficiaries and delivery social assistance in cash, reaching the intended beneficiary financial store of value account (could be a bank account, mobile wallet, loading a pre-paid card, etc) to make quick transfers becomes an important building block in Govt to Person (G2P) Payments context. There is good amount of demand in this space and having this **Financial Address Mapper** registry / module as a self-sustaining building block for quick demonstration and eventually adoption with-in the countries.

This registry of Beneficiary ID to Financial Address in normative forms will enable govt departments spread across various sectors (pensions, education, health, social welfare, etc.) to access this registry for transfers. From Beneficiary perspective, she can easily manage one or more accounts and control flow of benefits instead of managing the linkages across various department apps/services.

More detailed visualization of this high level solution blueprint is [here](https://g2p-connect.gitbook.io/docs/g2p-connect-protocol/blueprint)

Additionally, how Financial Address Mapper interacts with various other solutions in the larger social assistance use cases can be found [here](https://g2p-connect.gitbook.io/docs/g2p-connect-protocol/interfaces/beneficiary-management/financialaddressmapper)

Follow further discussion and updates here <https://github.com/orgs/G2P-Connect/discussions/23>

Check out the demo here: <http://g2p-financial-wrapper.xiv.in/>

Source code: <https://github.com/Sunbird-RC/g2p-mapper-registry>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rc.sunbird.org/reference-solutions-for-functional-registries/govt-to-person-g2p.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
