NPCI Aadhaar Seeding Consent Form Download
What You'll Learn
- What Annexure I means and why it is a bank consent form, not a scheme approval form.
- Which fields and choices normally appear in the Aadhaar seeding request.
- How the bank, NPCI mapper, and customer responsibilities fit together.
- What to do when a bank rejects, delays, or fails to reflect the mapper update.
The NPCI Aadhaar seeding consent form is often described online as a quick mobile download that can be filled, digitally signed, and emailed to any bank. That description is too broad. The official DBT Bharat process treats Annexure I as a consent request submitted to the bank, with the bank deciding which physical or electronic channel it accepts.
The form is used for Aadhaar seeding and NPCI mapping for Direct Benefit Transfer. It can support a benefit such as Annapurna Yojana, but it does not approve a beneficiary, migrate a Lakshmir Bhandar record, or guarantee a payment. The official West Bengal scheme name is Annapurna Yojana. Eligible women receive ₹3,000 per month through DBT to an Aadhaar-linked bank account, subject to the scheme’s conditions. [1] [5]
This guide therefore answers the practical questions. What is the form? Which parts must be completed? Where should it be submitted? What evidence should the bank provide? And what should a customer do when Aadhaar appears in the bank’s system but the NPCI mapper is still inactive?
What the NPCI Aadhaar seeding consent form is
Annexure I is a consent form for linking or seeding Aadhaar and enabling a bank account for Aadhaar-based DBT. The customer gives the bank permission to use the Aadhaar details for authentication, associate the Aadhaar with the bank account, and request the relevant mapper action.
The form is not a contract with NPCI that a customer can submit directly and expect an immediate mapping. The bank receives the consent, verifies the customer and documents, performs the bank-side work, submits mapper information, and handles the response. NPCI provides and processes the mapper platform. It does not independently update a customer’s mapper record.
| Document or system | Role | What it does not prove |
|---|---|---|
| Annexure I consent form | Records the customer’s request and consent to the bank | It does not prove that mapping is already active |
| Bank customer record | Stores the Aadhaar association for the account | It does not by itself prove the NPCI mapper is updated |
| NPCI mapper | Supports Aadhaar-based DBT routing to a mapped bank | It does not approve the welfare scheme |
| Scheme record | Controls eligibility, migration, verification, and sanction | It does not replace bank consent |
The official DBT Bharat Aadhaar seeding process describes Annexure I and the customer, bank, NPCI, and grievance roles. Read it as a process document, not as a promise that every bank accepts the same file through the same channel. [1]
Is this an Annapurna Yojana application form
No. The consent form belongs to the general Aadhaar-based DBT and bank-mapping process. Annapurna Yojana is a separate West Bengal welfare scheme administered by the Women and Child Development and Social Welfare Department. A customer can complete a bank consent request and still have a pending or ineligible scheme record.
Existing Lakshmir Bhandar beneficiaries are migrated to Annapurna Yojana subject to prescribed conditions. New applicants complete the Social Registry process and undergo enquiry and verification. The bank form does not bypass those steps.
This distinction prevents a common mistake. A person may hand a consent form to a bank and believe that the monthly benefit has been activated. The form only asks the bank to complete the banking and mapper work. The scheme department still decides whether the beneficiary qualifies and whether the record is ready for payment.
For the migration side, see the Lakshmir Bhandar to Annapurna Yojana migration guide. For the receiving-account side, the Annapurna Yojana DBT link guide explains the destination account and mapper distinction.
Where to get the official consent form and process
The safest starting point is the bank that holds the account. Banks can publish their own form, provide a branch copy, or direct customers to an approved electronic channel. The DBT Bharat process document also provides the standard Annexure I format and explains the fields and choices used for Aadhaar seeding and DBT mapping.
Do not assume that a PDF found on a private website is the current form accepted by your bank. A copied file may be incomplete, altered, or missing the bank’s own declaration. The standard process document is useful for understanding the form, but the account-holding bank remains the authority for acceptance.
Readers can open the DBT Bharat citizen resources page for official links to Aadhaar-linking status and DBT seeding material. The NPCI official website is useful for mapper and BASE information. Neither website turns a customer’s downloaded copy into an automatically accepted bank request.
Which details appear in Annexure I
The standard form asks for the branch and bank, account number, account name, Aadhaar details, mobile number, email where applicable, and the customer’s signature or thumb impression. It also includes the customer’s consent to Aadhaar authentication and an enclosure for a copy of Aadhaar.
Some versions include a choice about the DBT account. The customer can request seeding of the account for DBT, request movement of an existing mapping from another bank, keep the existing mapping with another bank, or decline seeding. The exact layout can differ when a bank publishes its own version.
| Form section | What to enter or select | Care point |
|---|---|---|
| Bank and branch | Name of the account-holding bank and branch | Use the details for the bank receiving the request |
| Account details | Account number and account-holder name | Check every digit against the passbook or bank record |
| Aadhaar consent | Consent for authentication and seeding | Read the declaration before signing |
| DBT mapping choice | New seeding, movement, retention of existing mapping, or no seeding | Select the choice that matches the actual bank request |
| Signature and enclosure | Signature or thumb impression and requested Aadhaar copy | Follow the bank’s document and authentication instructions |
Do not fill a mapping-transfer option casually. If an Aadhaar mapping is already active at another bank, the new bank may need the existing bank name and a clear request to move or retain the mapping. A wrong choice can send the request into the bank’s correction queue.
How to fill the consent form without creating a mismatch
Start with the name and account number exactly as the bank holds them. If the account name, Aadhaar name, and scheme record differ, ask the bank or relevant authority what correction is required before submitting repeated forms.
Enter the mobile and email details the bank asks for. These fields support communication, but they do not replace the signature or authentication requirement where the bank requires one. Attach only the documents requested by the bank and keep a copy of the complete submission.
Read the DBT mapping choice carefully. If you want the bank to become the active DBT destination, say so in the option provided. If you want to keep another bank mapped, select the retention choice if the form offers it. If you are unsure, stop and ask the bank rather than selecting every option.
The official process says the customer should submit complete details and, for a physical form, sign according to bank records. A typed name in a PDF is not automatically equivalent to an accepted signature or bank authentication.
Can you fill and sign Annexure I on a mobile
You may be able to type into a PDF or complete an electronic mandate if your bank provides that facility. But the existence of a mobile PDF editor does not mean the bank accepts a typed signature, Aadhaar eSign, or a screenshot of the form.
The official DBT Bharat wording is narrower. It allows physical or electronic submission according to the facility provided by the bank. That places the acceptance decision with the bank. A generic instruction saying “sign with eSign and email it” is not safe for every account holder.
If the bank gives a specific electronic workflow, follow that workflow and retain the acknowledgement or reference number. If the bank directs you to a branch, business correspondent, or customer-care channel, use that route. Do not send sensitive documents to an unverified email address found on a private page.
| Submission method | When it may be usable | What must be confirmed |
|---|---|---|
| Branch submission | The bank asks for a physical form and document check | Obtain a bank acknowledgement |
| Electronic mandate | The bank provides an approved online or app route | Confirm that the request includes DBT mapper action |
| Business correspondent route | The bank or authorised channel supports it | Keep the official receipt or reference |
| Email or upload | Only if the bank gives that channel directly | Verify the address and ask how acknowledgement is issued |
The safe rule is simple. Mobile filling is a convenience. Acceptance, authentication, and mapper updating remain bank responsibilities.
What the bank does after receiving the form
The bank verifies the form, documents, account, and customer authenticity. After accepting the consent, it links Aadhaar to the bank account and starts the NPCI mapper process. The bank’s central team or IT division may handle the mapper file even when the branch accepted the customer request.
When the mapper file is processed, the bank receives a response. If the update fails, the bank should identify the cause and take corrective action. This is why a branch acknowledgement matters. It proves that the customer submitted a request and gives the bank a starting point for tracing the internal process.
A bank’s confirmation that Aadhaar appears in its core banking system is not enough to prove that the mapper is active. Ask for the actual status or confirmation the bank can provide for the DBT mapping request. The NPCI mapper seeding failure guide explains why this distinction matters.
What NPCI does and does not do
NPCI provides the mapper platform for banks to update or remove Aadhaar records according to customer requests. It processes the files submitted by banks and returns responses. But the official process says NPCI does not independently update a customer’s mapper record.
That means a customer who wants a correction normally starts with the bank. If the mapper is not updated after the bank receives complete documents, use the bank’s customer-service cell and escalation matrix. If a further escalation is necessary, keep the bank-acknowledged consent form.
Do not pay a person who claims to have a private NPCI activation panel. There is no safe reason to share an Aadhaar OTP, banking password, PIN, or app login with an intermediary who promises to update the mapper.
How to change the mapped bank account
Use the consent form’s mapping option or the bank’s current process when moving DBT mapping from one bank to another. The official process says the customer should identify the bank from which the Aadhaar mapping is being moved. This helps the new bank understand that the request is a change, not a first-time seeding.
Only one account can be active for the relevant Aadhaar-based mapping at a time. If a customer gives consent to multiple banks, the last seeded bank with active mapper status becomes the receiving bank under the official process. Check the active bank before making another request.
If Aadhaar status is inactive, the official process directs the customer to visit the bank branch and submit the duly filled consent form. A private online form cannot force an inactive mapper status to change.
The Aadhaar already linked to another account guide covers the multiple-bank error pattern. Do not close the old account until the new mapping is confirmed if that would leave the benefit without a working destination.
What to do if the mapper does not update
First, check whether the bank actually accepted the consent form. If it did, keep the acknowledgement and ask for the mapper status. If the bank says the Aadhaar is linked in its core system, ask whether the mapper file was submitted and whether a response was received.
If the status remains inactive or missing, raise a complaint with the bank’s customer-service cell and follow the escalation matrix. Give the bank the account details, request reference, and acknowledgement. Avoid sending multiple forms to different banks before the first request is resolved.
The official DBT Bharat process places the action with the bank when the Aadhaar is not reflected in the mapper after the customer submits the required information. NPCI can be contacted for an escalation with the bank-acknowledged consent evidence, but the bank remains the party that must correct its mapper submission.
| Problem | Evidence to keep | Next step |
|---|---|---|
| Form rejected | Rejection message or branch explanation | Correct the specific field or document requested by the bank |
| Aadhaar linked but mapper absent | Consent acknowledgement and bank response | Ask the bank to trace the mapper submission |
| Wrong bank mapped | Status result and old-bank details | Request movement or retention through the new bank’s process |
| Inactive mapper | Inactive status and customer-service ticket | Visit the branch if the official process requires physical consent |
The OTP and Aadhaar-seeding troubleshooting guide can help when the form or bank channel fails during authentication.
How the form relates to Annapurna Yojana DBT
Annapurna Yojana uses DBT to the beneficiary’s Aadhaar-linked bank account. The consent form can help the bank establish or change the payment route, but it does not replace the scheme’s eligibility, migration, verification, or sanction process.
Existing Lakshmir Bhandar beneficiaries are migrated subject to prescribed conditions. New applicants use the official Social Registry West Bengal process and provide the information required for enquiry. A bank mapping can be technically correct while the scheme record remains pending.
Use the official scheme name when speaking to a local office. If your issue is the bank route, use this consent-form guide. If it is a scheme or migration issue, use the migration guide. If it is a general Aadhaar-bank mismatch, use the Aadhaar-bank troubleshooting guide.
What to check before submitting any Aadhaar form
Confirm the bank name, branch, account number, and account-holder name. Read the mapping option and select only the choice you actually want. Ask the bank whether it accepts the form physically, electronically, through a business correspondent, or through a specific bank channel.
Keep a copy of the completed form and every document submitted. Obtain an acknowledgement. Ask how the bank will communicate the mapper result. Do not assume that a downloaded file, a typed signature, or an app confirmation completes the process.
Finally, remember what this form can and cannot do. It can record consent for bank-side Aadhaar seeding and mapper action. It cannot approve Annapurna Yojana, guarantee ₹3,000 payment, remove a voter-roll exclusion, or bypass bank verification. The accurate process is slower than a viral shortcut, but it leaves a usable record when something goes wrong.
Frequently Asked Questions
SK Jabedul Haque
Building India's most trusted finance education platform — simplifying news, schemes and market trends so anyone can understand and invest confidently.
Read full bioNever miss an update
Get our clearest explainers on schemes, markets and money — read what matters, without the noise.
Explore more articles