"Aadhaar Already Linked to Another Account" NPCI Error Fix

What You'll Learn

• What the “Aadhaar already linked to another account” message means at the bank and NPCI layers.
• How to check the active mapped bank before submitting another consent request.
• When to keep the old mapping, request a move, or ask the bank to correct a failed update.
• Why the bank, not a private agent or generic online guide, owns the mapper correction.

The message Aadhaar already linked to another account is not a complete diagnosis. It can appear when a new bank tries to seed Aadhaar while another bank is already active in the NPCI mapper, when a previous request is still unresolved, or when the bank’s ordinary Aadhaar link and mapper record are out of sync.

The safe response is not to ask several banks to seed Aadhaar at once. First identify the bank that is currently mapped, decide where you want DBT to go, and use the receiving bank’s approved consent process. The official DBT Bharat form allows a customer to request a new mapping, keep an existing mapping, or choose not to seed the new bank. [1]

The official West Bengal scheme name is Annapurna Yojana, not Annapurna Bhandar. A successful mapper change does not itself approve scheme eligibility or guarantee the ₹3,000 monthly payment. Scheme records and bank routing are separate layers. [6] [7]

What the “already linked” error actually means

Aadhaar linking in a bank’s customer profile, ordinary KYC linking, and NPCI DBT mapping are related but not identical. A bank may show Aadhaar linked in its core banking system while the NPCI mapper still shows another active bank. Conversely, a mapper request may be submitted while the bank is waiting for a response.

The NPCI mapper associates an Aadhaar number with a bank for Aadhaar-based DBT routing. Under the official seeding process, only one account can be active at a point in time. If two banks receive consent, DBT is credited to the last seeded bank whose status is active in the mapper.

That does not mean the older account must always be “deleted” first. The receiving bank can submit a move request with the name of the bank from which the Aadhaar is being moved. The bank will verify the request and determine the operational correction.

Check which bank is currently mapped

Start with the official Aadhaar bank-seeding status route. UIDAI’s myAadhaar service provides a Bank Seeding Status facility, and UIDAI’s DBT FAQ points readers to official UIDAI and NPCI status routes. Use the official domain and the service’s own authentication flow.

Write down the bank shown as active, the status wording, and the date of the check. Do not post the result publicly. If the result shows the account you want to use, the new bank request may be unnecessary. If it shows an old or unfamiliar bank, take the result to the bank that should receive the new mapping.

A bank employee may also need to check the internal request and mapper response. A screenshot of “Aadhaar linked” in a bank profile is not enough to close the issue because the DBT Bharat process says the mapper update is a separate activity. The Aadhaar-bank link troubleshooting guide explains why the two records can disagree.

Use the official UIDAI Bank Seeding Status service and the UIDAI DBT FAQ before submitting another form.

Decide whether to keep or move the existing mapping

There are two different decisions. If the old bank is the account you still want for DBT, tell the new bank that you do not want to change the existing mapping. If you want the new bank to receive DBT, use the consent form’s change-mapping option and name the existing bank.

Do not choose the move option simply because a new account has better mobile banking. DBT routing should be changed only when the account is active, the bank is prepared to accept the request, and the scheme or payment destination is meant to use that account.

How to request a bank-to-bank mapping change

UIDAI’s public guidance says that changing the bank account for DBT requires visiting the respective bank branch and submitting the mandate and consent form provided by the bank. The DBT Bharat process describes the same bank-led flow.

Take the documents requested by the bank, complete the form with the intended account, identify the bank from which the Aadhaar is being moved, and sign according to the bank record when a physical form is used. Ask for an acknowledgement with a date or reference.

The official form includes a request to change the NPCI mapping to the new bank. It is not a promise that a new mapping appears immediately. The bank may send the request through its central team or IT division and must verify the NPCI response.

Read the Aadhaar-seeding OTP troubleshooting guide if authentication is stopping you before the bank can accept the request.

Why an online or mobile move is not universal

Some banks may provide digital Aadhaar-seeding facilities or expose a BASE-linked flow. That does not mean every customer can delink an old mapping, move the DBT destination, or complete the whole correction online. The available channel depends on the bank, the account, the authentication result, and the request type.

Do not enter your Aadhaar OTP, internet-banking password, debit-card PIN, or full bank details into a private website that promises instant mapper change. A page that copies the NPCI logo is not proof that it is an authorised bank workflow.

If your bank gives you an official digital option, use it through the bank’s own website or app and save the acknowledgement. If the option is absent or fails, follow the branch and customer-service process. The article must not turn one bank’s optional facility into a national guarantee.

What the bank does after receiving consent

The DBT Bharat process says bank officials verify the form, documents, and customer authenticity, then accept the request and provide an acknowledgement. The branch links Aadhaar to the account and updates the NPCI mapper through the bank’s central process.

The branch may not directly upload the mapper file. The bank’s central team or IT division can perform the update, and response files from NPCI must be checked. This is why a branch saying “Aadhaar is linked in our system” does not by itself prove that the active DBT mapping has changed.

If the mapper is not updated after a complete request, the bank is responsible for finding the root cause and taking corrective action. Do not accept a vague instruction to contact NPCI without a bank acknowledgement and complaint reference.

What to do if the old account is closed or inactive

An old account can remain associated with a mapping even when you no longer use it. Do not assume that closing the account automatically removes the NPCI record or transfers DBT to a new bank.

Take the old bank name and the current mapped-bank result to the new bank. Use the form option that requests a move from the old bank. If the old bank must correct its own record, ask that bank for its closure and mapper-escalation process as well.

If the status is inactive, the official process directs the customer to visit the respective bank branch and submit the duly filled consent form. No universal 72-hour or 3-7 working day completion promise is supported. Keep the acknowledgement until the new active mapping is visible.

What if multiple banks have received consent

The official DBT Bharat document says a customer can link only one account with Aadhaar at a time. If consent is given to multiple banks, DBT is credited to the last seeded bank whose status is active in the NPCI mapper.

This makes repeated form submissions risky. A second bank may become active while the customer is still checking the first account. Before requesting another move, identify the currently active bank and decide which account should receive all relevant DBT payments.

The active mapping does not settle scheme eligibility. A mapped bank can receive a payment only if the beneficiary is approved and the Annapurna DBT record is ready for the implementing authority to generate the relevant payment instruction.

How ordinary Aadhaar linking differs from DBT mapping

Ordinary bank linking may be used for KYC or customer-service purposes. NPCI mapping associates the bank with Aadhaar for the Aadhaar-based DBT route. The bank’s internal record and NPCI response must both be considered.

Ask the bank two separate questions: “Is Aadhaar linked in the account?” and “Is the NPCI mapper active for this bank?” A “yes” to the first question does not answer the second. This distinction is often the reason that an online bank screen and the DBT status result appear to disagree.

For a wider payment diagnosis, read the Annapurna payment-not-received guide. It separates scheme approval, bank validation, mapper status, payment-file processing, and returned transactions. For scheme-side context, read the Lakshmir Bhandar migration guide.

What the error means for Annapurna Yojana

The mapping error affects the payment route, not automatically the scheme decision. Annapurna Yojana has its own eligibility, migration, verification, and payment-file stages. A correct bank mapping cannot remove a scheme exclusion, and a valid scheme record cannot fix a failed bank mapper.

Use the official scheme channel for beneficiary questions and the bank channel for mapper questions. If the payment record shows a returned or failed transaction, ask for the exact reason and whether the scheme or bank must reprocess it.

Do not describe Annapurna as “Annapurna Bhandar” in an official complaint. The old phrase may remain in a URL or search query, but the government scheme name used in current guidance is Annapurna Yojana.

How to escalate a mapper problem

Start with the bank’s customer-service cell and follow its escalation matrix. Include the acknowledged consent form, bank name, date, account reference permitted by the bank, mapped-bank result, and exact error message. Keep full Aadhaar and account details out of public posts.

If you write to NPCI, the DBT Bharat process says the acknowledged consent copy should be provided so the issue can be taken up with the concerned bank. NPCI provides the platform and processes bank files, but it does not independently update customer mapper records.

A good escalation asks the bank to confirm whether the request was accepted, whether the mapper file was submitted, whether NPCI returned a response, and what corrective action is being taken. Avoid an agent who promises a private override.

Final checklist before submitting another request

Check the active mapped bank. Decide whether to keep or move it. Use the receiving bank’s consent form. Name the bank from which the Aadhaar is being moved when requesting a change. Keep the acknowledgement. Ask the bank to confirm both its internal Aadhaar link and the NPCI mapper response. Then verify the mapped result before changing any scheme or bank record again.

Do not treat the “already linked” message as a reason to panic or to submit unlimited forms. It is a signal to identify the active destination and use the bank-led correction path. A mapping change can be appropriate, but it must be recorded and confirmed through the responsible institution.