> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.1/eligibility-and-enrolment/id-account-mapper.md).
# ID Account Mapper
## Introduction
ID Account Mapper (IAM) is an innovative approach for social benefit programs to transfer cash benefits, subsidies, scholarships, and pensions digitally to beneficiaries. IAM provides a minimalistic component that enables programs to direct payments to beneficiary accounts using just the beneficiary identity numbers from an existing ID system.
An IAM is a key/value lookup registry that maps beneficiary ID with beneficiary account address. The registry entries in IAM can be added, deleted (soft/hard), updated, resolved to an account address, and verified for status.
The beneficiary ID is normalised to represent functional or foundational ID. Similarly, the account address is normalised to represent a bank account number, mobile wallet address, voucher, prepaid card, or digital currency. The account address can also point to the financial institution holding the account.
### OpenG2P G2P Payments Bridge
Social benefit delivery programs can use OpenG2P G2P Payments Bridge to connect with ID Account Mapper as shown in the diagram below.
These are the steps of payment disbursement using the OpenG2P G2P Payments Bridge:
1. The G2P Payments Bridge creates a mapping list containing beneficiary IDs and corresponding entitlement amounts for a program.
2. G2P Payments Bridge connects with the Mojaloop Payment Switch and provides the treasury account details and mapping list.
3. Mojaloop Payment Switch retrieves the beneficiary account details from the ID Account Mapper using the beneficiary ID provided by G2P Payments Bridge.
4. Mojaloop Payment Switch transfers the entitlement amount from the treasury bank account to the beneficiary's choice of account, i.e. mobile wallet, bank account, and prepaid card.
#### Advantages of using G2P Payments Bridge
1. Only the beneficiary ID and entitlement amounts are required to process payments. Beneficiary account details are not stored in the OpenG2P registry thus preserving the privacy of the beneficiary
2. The beneficiary has a choice of payment mode - wallet, account, prepaid card, or voucher.
3. A program can initiate bulk payments without dealing with multiple payment service providers.
4. A program can run efficiently without recollecting beneficiary account information and re-configuring payment service providers in the OpenG2P platform.
### Demo video
{% embed url="" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.openg2p.org/1.1/eligibility-and-enrolment/id-account-mapper.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.