Aadhaar and your bank account: KYC linking is not DBT seeding

Aadhaar bank linking and NPCI seeding are two different things

When a bank says your Aadhaar “is linked”, and when a subsidy portal says your Aadhaar “is not seeded”, both can be true at the same time. That is not a contradiction and nobody is lying to you. They are describing two different records, created by two different acts, for two different purposes.

The first record is the bank’s own. When you give your Aadhaar number to a bank as part of opening or updating an account, the bank verifies it — by e-KYC authentication with UIDAI, by offline verification, or by looking at the document — and records it against your customer profile. That is know-your-customer: it establishes who you are to that bank, and nothing more. Nothing about it tells the government where to pay you.

The second record is NPCI’s. NPCI runs the Aadhaar Payments Bridge, the system through which government departments send direct benefit transfers using the Aadhaar number as the address. Its mapper is a table that pairs each Aadhaar number with one bank. When a scheme pays you by Aadhaar, the payment goes to whichever bank the mapper names. Getting your number into that table is called seeding, and NPCI defines it plainly: “Seeding means updating the Aadhaar number in NPCI mapper.”

NPCI’s standard operating procedure for banks draws the line itself. Banks are to keep “distinct fields in their CBS for updating the Aadhaar number submitted for KYC purpose and Aadhaar for seeding purpose”, and “under no circumstances the Aadhaar number submitted as a part of KYC be seeded in NPCI mapper. The seeding should only be subject to explicit written consent from customer for receiving the Direct Benefit Transfer related credits.” So a bank that did your KYC with Aadhaar has, if it followed the procedure, deliberately not seeded you.

Is it mandatory to link Aadhaar with a bank account? What the Supreme Court held

In 2017 rule 9 of the Prevention of Money-laundering (Maintenance of Records) Rules, 2005 was amended so that an individual opening an account had to give the bank an Aadhaar number, existing customers had to do so by 31 December 2017, and an account whose holder did not would “cease to be operational” until the number was produced. That rule is what made “link your Aadhaar or your account will be frozen” a thing everybody heard.

The Supreme Court’s Aadhaar judgment of 26 September 2018, K. S. Puttaswamy (Retd.) v. Union of India, Writ Petition (Civil) 494 of 2012, struck it down. In the majority opinion, written by Justice A. K. Sikri for himself, Chief Justice Dipak Misra and Justice A. M. Khanwilkar, paragraph 429 says the rule “does not meet the test of proportionality and is also violative of right to privacy of a person which extends to banking details”. Paragraph 433 adds that deactivating an existing account until it is seeded “amounts to depriving a person of his property”. Paragraph 434 notes that the banks were already using “alternative methods of KYC”. Paragraph 436 concludes: “We, thus, hold the amendment to Rule 9 … in the present form, to be unconstitutional.” Paragraph 447, answering issue (8), repeats the holding.

The bench was not unanimous on this point, and it is worth knowing how it split. Justice D. Y. Chandrachud, who dissented on the Act as a whole, reached the same result on the bank rule: his conclusion (18) is that the 2017 amendments “fail to satisfy the test of proportionality”. Justice Ashok Bhushan would have upheld the rule. So the rule fell four to one. What the same judgment upheld, by contrast, was the linking of Aadhaar with PAN — which is why one is compulsory and the other is not.

Parliament then rewrote the position rather than leaving the struck-down rule in the air. Section 11A of the Prevention of Money-laundering Act, inserted in 2019, lets a bank verify identity by Aadhaar authentication, by Aadhaar offline verification, by passport, or by any other officially valid document — and sub-section (3) says “the use of modes of identification … shall be a voluntary choice of every client … and no client or beneficial owner shall be denied services for not having an Aadhaar number.”

How Aadhaar seeding in the NPCI mapper actually works

UIDAI’s own answer is short: “visit the bank branch where you have opened the account and request the bank to link your Aadhaar with your account by filling up the mandate and consent form of the bank. This account will be seeded with NPCI-mapper by the bank to operate as DBT enabled account.” NPCI’s published guidance adds that the consent may be given “either in physical or electronic form as per the facility provided by his / her bank” — so a bank may offer it online as well, and if yours does, the online form is the same mandate.

Behind the counter there are two steps and they are not the same step. The branch links the number in its core banking system; then the bank’s central team or IT division uploads it to the mapper. NPCI’s guidance says it in so many words: “By linking the Aadhaar number to the account the branch is not updating the mapper.” The mapper sends back a response file saying which records it accepted and which it rejected, and a rejection — an invalid number, a mandate dated earlier than an existing one, a missing previous-bank code — is fixed by the bank, not by you and not by NPCI.

NPCI is explicit that the mapper belongs to the banks. “The activity of updating or removing an Aadhaar number from mapper can be performed only by the banks. NPCI on its own does not update the mapper records.” That single sentence explains most of the frustration people run into: when the mapper is wrong, NPCI cannot correct it, UIDAI cannot correct it, and the scheme department cannot correct it. Only a bank can.

Not every account can be seeded. NPCI tells banks to refuse seeding for accounts that cannot receive the credits, and gives NRE accounts, loan accounts, PPF accounts, blocked or frozen accounts and inoperative accounts as examples — the list is described as “only indicative”. It also tells banks to de-seed an account that is closed, whose holder has died, that is under litigation, or that is blocked or frozen, and says customer consent is not needed for that. A temporarily frozen account is meant to be re-seeded automatically when it is reactivated; in practice, if a subsidy stops after a freeze, re-seeding is the first thing to ask about.

1. 1You fill in and sign the bank’s Aadhaar seeding consent form, ticking the option to seed a specific account for DBT. NPCI’s specimen form carries four options: seed this account; move my existing DBT mapping from another bank to this one; keep my mapping where it is; or do not seed at all.
2. 2The bank verifies the form and your signature, and gives you an acknowledgement. Keep it: NPCI’s guidance treats that acknowledgement as the evidence in any later dispute.
3. 3The branch links the Aadhaar number to the account in its core banking system, in the seeding field rather than the KYC field.
4. 4The bank’s central team uploads the number to NPCI’s mapper, and checks the response file for rejections.
5. 5Once accepted, the mapper records your Aadhaar number against that bank, and Aadhaar-routed government payments go there from then on.
6. 6The bank is meant to tell you by SMS or email. NPCI’s procedure asks for a message with the seeding date on success and the reason on failure; UIDAI’s 2017 notification requires a bank to tell you within 24 hours that it has sent a mapping request.

Several bank accounts, and not knowing which one gets the subsidy

You can have Aadhaar recorded for KYC at every bank you use. You can have it seeded at only one. UIDAI: “You can receive DBT benefits only in one account as per your choice which has been mentioned by you while submitting the mandate and consent form to your bank.” NPCI: “Customer can link only one account with Aadhaar at any point of time.”

When more than one bank has sent a seeding mandate, the mapper does not ask which you prefer. It keeps the latest. NPCI’s procedure gives its own example: an Aadhaar number seeded by bank A on 5 May 2017 and by bank B on 15 June 2017 is routed to bank B, and “all the transactions will be routed to bank ‘B’ only”. The customer-facing version: “If customer gives consent to multiple banks then subsidy will be credited to the last seeded Bank with which the status is active in NPCI mapper.”

That is how people lose track. A consent form signed years ago when opening a second account, a payments-bank account opened in the course of some other errand, a form filled in at a camp — any of them can have moved the mapping, and the money has been going there since.

Two further details matter when the accounts are at the same bank. First, the mapper records a bank, not an account: NPCI describes the Aadhaar Payments Bridge as disbursing “based on the mapping of Aadhaar number to the Institution Identification Number (IIN) of the beneficiary’s bank”. So a status check can point you to the bank but cannot by itself tell you which of your accounts there will be credited — that is decided inside the bank’s own system, by whichever account carries the seeding. Second, NPCI’s specimen consent form asks you to name one account number to seed, while separately asking consent to link Aadhaar to “all my existing/new/future accounts” for identification. If you hold two accounts at one bank, ask the branch which of them holds the seeding, and have it put in writing on the acknowledgement.

How to change the bank account that receives DBT

UIDAI’s answer: “To change the bank account for receiving DBT funds, please visit the respective bank branch and submit the mandate and consent form provided by your bank.” The respective branch is the new one — the bank you want the money to go to — not the one it is currently going to.

The detail that decides whether the change actually happens is the previous bank. After the 2017 complaints about mappings being overridden without consent, UIDAI directed that NPCI should allow an override “only if it is accompanied by the name of his current bank on the APB mapper” and confirmation of consent, and NPCI’s mapper now rejects a move that does not carry the previous bank’s code. NPCI’s guidance to customers is to “provide the name of the bank from which the Aadhaar is being moved”, and its specimen form has a line for exactly that. So before you go, check the status and note which bank the mapper currently names. A form that leaves that line blank is the commonest reason a change silently fails.

Moving the mapping does not close the old account, and it does not move any payment that has already been made. For an LPG subsidy, NPCI’s guidance is that oil marketing companies are to be approached “for reinitiating the failed transactions to last seeded bank account”; for other schemes the route is the scheme’s own.

What “seeded”, “active” and “inactive” mean on the status check

You can check the seeding yourself, without asking anyone. UIDAI’s DBT FAQ gives two places: myAadhaar, where the answer “is fetched from the server of National Payment Corporation of India (NPCI)” — UIDAI adds that it “is not responsible for its correctness” and stores nothing — and NPCI’s own seeding-status page. Because the answer comes from NPCI either way, the two should agree; if they do not, the NPCI page is the source.

The words you will meet are NPCI’s, and they mean something narrower than they sound. “Seeded” means your Aadhaar number is in the mapper against a bank. “Active” means that mapping is live and payments will route to it. “Inactive” means the mapping exists but will not receive payments — typically because the bank de-seeded the account after a closure, a freeze or a death, or because the record needs to be re-seeded. NPCI’s instruction for an inactive status is short: “customer to visit respective bank branch in person and submit the duly filled customer consent form.”

NPCI’s own look-up facility for banks uses four answers — enabled for DBT, disabled for DBT, never enabled for DBT, and cancelled by UIDAI — and a failed payment comes back to the paying department with a return reason. You may see those phrases on a scheme portal. The reader below translates each one.

Why a subsidy is not received even though Aadhaar is linked

Most “subsidy not received” problems sit in one of four places, and the fix depends entirely on which. Working out which is the job of the troubleshooting flow on this page; this section explains why each exists.

The scheme. A payment is released by the department only if you are an approved beneficiary in the scheme’s own records. UIDAI points out that a name in Aadhaar that differs from the name in the scheme’s database is a common reason, and that a person whose fingerprints fail authentication is covered by the exception-handling provisions in the scheme notifications rather than simply refused. If the scheme has not released a payment, nothing at the bank will help.

The mapper. If your Aadhaar is not seeded, or is seeded to a different bank, or the mapping is inactive, an Aadhaar-routed payment either fails or goes where the mapper says. This is the case the status check answers.

The account. Even with the mapping right, the receiving bank can return the credit because of the account itself. NPCI’s return reasons include account closed, account inoperative, dormant account, KYC documents pending, account blocked or frozen, a credit limit the bank has set on the account, and an account type that cannot take the credit. Each is fixed by putting the account right, not by re-seeding.

The link between the two inside the bank. NPCI’s procedure records that “practically many banks return the transactions with the reason ‘Aadhaar number not mapped to account number’” — the bank put your number in the mapper, but its own system cannot find which account it belongs to when the payment arrives. That is wholly the bank’s to fix, and NPCI tells branches so: “The customer should not be told that NPCI has not updated the Aadhaar number.”

What an Aadhaar update does — and does not do — to your bank records

Changing your address, mobile number or date of birth in Aadhaar does not change anything at your bank, and does not touch the mapper. The bank holds its own copy of your details captured at KYC; the mapper holds only your number and a bank. The Aadhaar update page covers the update itself and lists the bank among the records you have to go and fix separately afterwards.

Two knock-on effects are worth knowing. The RBI’s Directions require a bank opening an account by Aadhaar OTP e-KYC to send alerts only to the mobile number registered with Aadhaar — so a changed Aadhaar mobile number is something to tell a bank that onboarded you that way. And if an update leads UIDAI to deactivate or cancel a number, NPCI’s look-up returns “cancelled by UIDAI”, and the mapping stops working until the underlying Aadhaar problem is resolved.

Where the escalation route lives

This page does not carry a complaints procedure. Where the fault is the bank’s — and for anything in the mapper, NPCI says it is — the route runs through that bank’s grievance process and then the RBI Ombudsman, which has a page of its own on this site. Where the fault is the Aadhaar record, the UIDAI complaint page covers it. Neither is repeated here.

Worked examples