Why is a mapper needed?
An Aadhaar-addressed benefit payment needs to reach the correct participating bank. The mapper provides the routing relationship used by the Aadhaar Payment Bridge, or APB, system.
NPCI’s APB FAQ hosted by UCO Bank describes the mapper as a repository used to route APB transactions to destination banks. It explains that the mapping includes the bank’s Institution Identification Number, or IIN.
The receiving bank then handles the relevant account information through its own systems. That is why mapping to a bank and identifying the customer’s actual account are related but distinct responsibilities.
Does the mapper store every bank-account detail?
The cited NPCI FAQ explicitly distinguishes the mapper from a database of customers’ account numbers, IFSCs and branch addresses. Its function is routing, not presenting the customer’s full banking profile.
A customer therefore cannot read a mapper result as a bank statement. The result does not tell them the available balance or prove that a particular subsidy has been credited.
| Record | Question it helps answer |
|---|---|
| Mapper information | Which bank mapping is relevant to APB routing? |
| Bank account record | What account information and entries does the bank hold? |
| Scheme payment status | Has the administering authority released the particular benefit? |
| Withdrawal record | What happened to a later cash-withdrawal attempt? |
Bank linking and mapper seeding
NPCI’s APB FAQ, question 9, describes banks seeding Aadhaar in their core banking records and subsequently uploading Aadhaar information into the NPCI mapper. A bank-side record and a mapper upload are distinct steps.
Consequently, “Aadhaar is in my bank file” is not a complete answer to every mapper question. Ask the bank which record has been checked and what action, if any, remains necessary.
Do not instruct a customer to change bank details repeatedly until an unrelated application accepts a request. A mapping change should follow the bank’s authorised process and the customer’s informed choice.
Why a mapping does not approve a benefit
The mapper helps with payment routing. The scheme-administering authority decides entitlement and the release of a particular benefit under its rules.
A correct routing record does not create eligibility or guarantee that a payment has been sent. Likewise, a missing expected credit cannot always be explained by a mapping problem. The authority may not have released the payment, or the receiving bank may need to investigate the actual transaction.
Keep the evidence attached to the question. A mapper result, scheme-status message and bank statement can each be useful, but they do not replace one another.
An example at an AEPS counter
Illustrative example: A customer expects a benefit in one bank and tries to withdraw it at an AEPS counter. The amount is not available, so they ask the retailer to “fix NPCI”.
The retailer explains what the counter can actually check and asks the customer to identify the scheme and intended bank. The responsible bank can clarify linking and mapper information; the authority can clarify whether the benefit was released.
The retailer does not present a fingerprint retry as a mapper update. Our AEPS-decline guide treats bank messages and failed withdrawals separately from an unverified diagnosis.
Questions about the mapper
Is mapper seeding the same as getting Aadhaar?
No. Aadhaar issuance and the bank-routing mapping are different processes involving different responsibilities.
Does the mapper show my account balance?
No. Use the bank’s authorised account enquiry for balance information.
Can any retailer change the mapping?
Do not assume so. The bank and authorised process govern the mapping activity. A shop’s registration for recharge, PAN or AEPS assistance does not automatically grant mapper-update authority.