How to link Aadhaar to your bank account

When a bank records your Aadhaar number in its customer database, it is using Aadhaar as an officially valid document to establish identity. This satisfies the bank's know-your-customer obligations, updates its records, and has nothing to do with the payments system. You can hold this linkage at five banks simultaneously and it creates no conflict.

Seeding is different. It is a request the bank sends to the central mapper operated for the retail payments system, saying: for this Aadhaar number, route Aadhaar-based credits to this account at this bank. The mapper stores one destination per Aadhaar number, and a new request replaces the previous one.

Government departments then pay benefits through the Aadhaar payment bridge. The department's file contains Aadhaar numbers and amounts rather than account numbers and IFSC codes. The bridge looks up each Aadhaar in the mapper and credits whichever account it finds. If the mapper points at a closed account, the credit fails and comes back to the department as a rejected transaction.

This is why 'I have linked my Aadhaar to this account' and 'my benefits will come to this account' are two different statements, and why bank staff and applicants regularly talk past each other. Ask specifically about seeding for direct benefit transfer, not about linking.

The design has an obvious consequence and a less obvious one. The obvious one is that opening a new account and seeding it will silently move every benefit you receive. The less obvious one is that a bank's routine account-opening process may include a seeding consent as part of the standard form, so people move the slot without ever intending to. If a benefit suddenly stops arriving where it used to, the first question is what account you opened recently.

Seeding is voluntary and requires your consent. A bank cannot seed an account into the mapper without a signed consent, and equally cannot refuse to seed one when you ask it to and the account is eligible.

The most direct check is the bank seeding status service on the myAadhaar portal, which shows the position reported by the payments mapper for your Aadhaar number — whether it is seeded, with which bank, and when the status was last updated. It requires an Aadhaar authentication with a one-time password, so the mobile number registered with Aadhaar has to be one you still hold.

Note what that display does and does not tell you. It generally shows the bank, not the full account number, and it shows the mapper's view rather than your bank's view. Where the two disagree, the mapper is what the payment system will act on.

A second route is to ask the branch directly, in writing, for confirmation of whether the account is seeded in the mapper for direct benefit transfer and on what date the request was sent. Ask for it in writing precisely because the verbal answer is frequently about KYC linking instead.

A third check is the scheme's own portal. Most benefit schemes publish a beneficiary or payment status enquiry, and a failed transaction there usually names the reason — account closed, invalid account, name mismatch, or Aadhaar not seeded. That reason code is far more useful than a general enquiry, because it tells you which of the possible failures you are dealing with.

Where a payment is showing as made by the department but has not arrived, the missing money is almost always sitting in a different account of your own rather than lost. Check every account you hold, including old ones and Jan Dhan accounts opened during a scheme drive, before escalating.

Keep in mind that a benefit paid by a department using a normal bank transfer to an account number, rather than through the Aadhaar bridge, is unaffected by any of this. Not every scheme uses the bridge, and the two mechanisms coexist.

Decide which account you actually want. The right answer is usually an active savings account at a branch you can reach, with a working passbook or statement, that is not close to becoming dormant. A joint account can be seeded, but the mapper points at the account, so be clear about who operates it.

Make sure the Aadhaar itself is in order before you start. The name on the Aadhaar and the name on the bank account should match closely; the mobile number registered with Aadhaar must be one you hold, because authentication depends on the one-time password to it; and the Aadhaar should not be one where biometrics have been locked without you being able to unlock them.

Go to the branch where you want the money and ask for the Aadhaar seeding consent form for direct benefit transfer — sometimes called the Aadhaar seeding and consent mandate. Fill it in, sign it, and attach a copy of the Aadhaar with the number masked except the last digits if the bank accepts a masked copy.

State on the form that you want the account seeded in the mapper as the destination for direct benefit transfer, and that any earlier seeding for your Aadhaar should be moved to this account. Ask the branch to give you an acknowledgement with a date. Without an acknowledgement you have no way of showing later that the request was made.

Complete the biometric or one-time password authentication if the branch asks for it. Some banks complete seeding through a biometric device at the counter; others send the request in a batch file.

Wait for the mapper to update, which typically takes a few working days rather than being instantaneous, and then re-check the status on the myAadhaar portal. Do not assume it worked because the branch said it would.

Once it shows as seeded to the right bank, tell the departments that pay you — the scheme portal, the employer, the pension office — only if their systems separately record an account number. Where the scheme pays through the Aadhaar bridge, no further action is needed, and that is the point of the whole design.

Finally, do not seed a second account 'as a backup'. There is no backup slot. The second request simply overwrites the first, and the benefit you were receiving at the first bank stops.

A name mismatch between the Aadhaar record and the bank account is the most frequent cause of a rejected credit. Indian names are recorded differently across documents — initials expanded or contracted, a surname included in one record and not the other, a transliteration that differs. Fixing it means updating whichever record is wrong, and updating Aadhaar is usually the more consequential change because everything else keys off it.

A dormant or inoperative account will reject a credit. Accounts go dormant after a period without customer-induced transactions, and the threshold is set by the bank under the applicable framework. Reactivating requires a visit to the branch with fresh identity documents, and it should be done before the next benefit cycle, not after a payment has failed.

A closed account is worse, because the seeding survives the closure in some cases and the credits simply fail. If you close an account that was seeded, seed a new one immediately rather than waiting to discover the problem.

An out-of-date mobile number registered with Aadhaar breaks almost everything, because the one-time password used for authentication goes to it. Updating the registered mobile requires a visit to an Aadhaar enrolment or update centre in person with the Aadhaar — it cannot be done entirely online — and it is worth doing before any of the rest of this becomes urgent.

Biometric authentication failures affect older applicants and people whose fingerprints have worn through manual work. Where fingerprints fail, iris authentication or a face authentication route is generally available, and the enrolment centre can also record updated biometrics.

Aadhaar records that have not been updated for a long period may be flagged for a document update. This does not by itself stop a payment, but it produces prompts and, in some services, blocks authentication until it is done.

Where the bank is the obstacle — refusing to seed, losing the form, or giving contradictory answers — put the request in writing to the branch manager, then to the bank's grievance redressal officer, and then use the reserve bank's integrated ombudsman scheme for banking complaints. That scheme is free, is filed online, and requires you to have first complained to the bank.

Seeding also enables Aadhaar-based cash withdrawal at a business correspondent — the micro-ATM model in which a customer withdraws money using their Aadhaar number and a fingerprint, with no card and no password. This is genuinely valuable in places with no branch, and it is also the mechanism behind a category of fraud in which biometrics captured elsewhere are used to withdraw from an account.

The countermeasure is built into Aadhaar and almost nobody uses it. Biometric locking, available through the myAadhaar portal and the Aadhaar mobile application, disables biometric authentication for your Aadhaar until you unlock it. Locked biometrics cannot be used for a withdrawal or any other biometric authentication, and unlocking takes a minute when you genuinely need it.

Use a virtual identifier or a masked Aadhaar wherever a full Aadhaar number is not strictly required. The virtual identifier is a temporary revocable number generated from the myAadhaar portal that can be used in place of the Aadhaar number for authentication, and masked Aadhaar is a downloadable copy showing only the last digits.

Check your authentication history periodically. UIDAI provides a record of authentication requests made against your Aadhaar, and an entry you do not recognise is worth pursuing immediately through the helpline and, if money moved, through the cyber crime reporting route and the 1930 helpline.

Never share the Aadhaar one-time password. There is no legitimate circumstance in which a bank employee, a scheme official or a delivery agent needs it. The commonest social engineering script in India begins with a caller claiming a benefit will lapse unless an Aadhaar authentication is completed immediately.

Where money has already been withdrawn fraudulently, report it to the bank in writing the same day and file on the national cyber crime reporting portal. The reserve bank's framework on unauthorised electronic transactions limits customer liability where the customer reports promptly and the loss did not arise from their own negligence, and the timeline for reporting is what determines the outcome.

Aadhaar is not compulsory for opening a bank account. Following the Supreme Court's decision on the Aadhaar framework, banks must accept other officially valid documents for know-your-customer purposes, and a customer may choose not to use Aadhaar. In practice branches sometimes insist; ask for the refusal in writing and it usually resolves.

It is, however, the practical route to receiving benefits under schemes that pay through the Aadhaar bridge, and the enabling legislation permits requiring Aadhaar for benefits funded from the Consolidated Fund of India, with an alternative route for those who do not have one. Where a person genuinely cannot authenticate, the department is expected to provide an alternative rather than deny the benefit outright — that entitlement exists and is worth invoking in writing.

Aadhaar is separately required to be linked with a permanent account number for income tax purposes, which is a different obligation from anything discussed here and has its own consequences for an unlinked PAN.

For a problem with the Aadhaar record itself — a name, date of birth, address, mobile number or biometric issue — the route is an Aadhaar enrolment or update centre, the myAadhaar portal for the changes it supports, and the UIDAI helpline on 1947.

For a problem with the bank — refusal to seed, a failed credit, an unexplained rejection — the route is the branch in writing, the bank's grievance redressal officer, and then the reserve bank's integrated ombudsman scheme.

For a problem with the paying department — the scheme shows the payment as made and it has not arrived, or eligibility has been wrongly rejected — use the scheme's own grievance mechanism first and the central public grievance portal where a central ministry is involved. Quote the transaction reference the scheme portal displays; a grievance with a reference number moves and one without it does not.