How to Link Aadhaar with NPS Account Online (2027 Guide)

A lot of NPS subscribers put this off because they imagine paperwork, office visits and jargon. Honestly? It is mostly logging into a website and verifying with an OTP. No running around, no physical forms — unless you are in government service, where one extra approval step applies (more on that below).

The whole thing runs through the CRA portal — the backend system that tracks all NPS accounts. Protean (formerly NSDL e-Gov) is the largest CRA, and its subscriber login lives at cra.nps-proteantech.in. (The old cra-nsdl.com address now lands on the same Protean platform.)

Here is the flow in plain English:

1. Log in to the CRA portal. Use your PRAN as the username and your I-PIN as the password. Never set an I-PIN? Use the First Time User option to generate one.

1. Find the Aadhaar section. Go to Menu, then Update Details, then Update Aadhaar/Address Details.

1. Enter your Aadhaar details. Type the 12-digit Aadhaar number, or use the 16-digit Virtual ID (VID) from the mAadhaar app if you prefer not to share the actual number.

1. Verify with OTP. A one-time password arrives on the mobile number (or email) registered with UIDAI. Enter it to confirm. If your UIDAI record has an old number, the OTP will not reach you — fix that first.

1. Submit. That is it. Your Aadhaar is now linked to your PRAN. Check your profile to confirm the status.

• Your Aadhaar must be active with a current mobile number or email in UIDAI records. Changed your number? Update it with UIDAI first — online via the mAadhaar app or at any Aadhaar Seva Kendra — then come back to the CRA portal.
• No Form S2 needed. That form covers PAN updates and other corrections. Aadhaar seeding is fully OTP-driven.
• The original deadline (December 31, 2017) has long passed, but the CRA system still accepts Aadhaar updates anytime. Late is far better than never — the alternative is a blocked withdrawal later.
• Government employees, take note: Central Government, State Government and Autonomous Body subscribers need their PAO/CDDO/DTO to authorise the request in the CRA system after submission. All Citizens model subscribers — private individuals who opened via PoP or eNPS — get instant seeding, no nodal office involved.
• Why it matters: without seeding, partial withdrawals, full exits and even e-Sign of routine forms can stall. The CRA's name-match checks compare Aadhaar, PAN, bank and PRAN records — a seeded, accurate Aadhaar is the anchor of all four.

Source: Protean CRA subscriber-maintenance documentation (npscra.proteantech.in); PMLA Second Amendment Rules, 2017.

It helps to know what the ten minutes buys you, because the payoffs are not obvious until something breaks:

• Withdrawals and exits. Both partial withdrawals and full exits run through CRA checks that compare your Aadhaar against your PRAN records. An unseeded account is the classic reason a request bounces back for KYC verification.
• e-Sign. Every online request you sign — withdrawal forms, detail changes — uses Aadhaar e-Sign, and e-Sign succeeds only when the CRA and UIDAI records show the same name. Seeding is what aligns the two.
• Faster grievance handling. When your KYC is complete and current, grievance tickets close on the first pass instead of looping back for document re-uploads.
• Cleaner exit at 60. The exit payout includes a penny-drop verification against your bank account. Your Aadhaar-seeded name, PAN name and bank name all have to agree — sorting this out years in advance is trivial; sorting it out during an urgent withdrawal is not.

If your name differs anywhere — a dropped surname on PAN, an expanded middle name on Aadhaar — fix it at the source first, then seed. Seeding a mismatched name just locks the mismatch into your pension record.

Skipping Aadhaar linkage causes withdrawal delays and profile-update failures later — exactly when you least want friction. Ten minutes today keeps the pension account fully compliant and ready the day you need the money.

Stuck anyway — no OTP, login trouble, or a nodal office sitting on the approval? Raise a ticket through the CRA's Central Grievance Management System (CGMS) on the Protean portal, and check our detailed Aadhaar–NPS troubleshooting guide for the offline route via a PoP branch.

Everything that makes this flow stall can be checked before you log in. Confirm four things:

• Your PRAN and I-PIN are at hand (or use the First Time User option to generate the I-PIN).
• You know the 12-digit Aadhaar number, or you've generated a 16-digit VID in the mAadhaar app.
• The mobile number registered with UIDAI is in your pocket, switched on, and not on Do-Not-Disturb.
• Your name is spelled identically on Aadhaar, PAN and your NPS record. A dropped surname here becomes an e-Sign failure later.

If any of the four fails, fix that item first. The seeding flow itself has almost no friction; every stall I've seen traces back to one of these.

Aadhaar seeding is a KYC mapping, nothing more. Your fund scheme, asset allocation, nominee, contribution history and balance are untouched. The update itself is free — no charge shows up on your statement, because nothing was bought or sold. What changes is that the CRA can now match your identity against UIDAI's records, which is what withdrawals, e-Sign and exit checks all lean on.

All Citizens model subscribers see the seeding apply right after the OTP. If you are a Central Government, State Government or Autonomous Body subscriber, your screen will show the request as submitted but pending — it now sits with your PAO/CDDO/DTO for authorisation in the CRA system. What to expect next: the nodal office sees the request in their queue and approves it, and only then does the seeding complete. If days pass with no movement, follow up with the nodal office directly rather than re-submitting from your side; a duplicate request just adds a second item to the same queue.

None of these are fatal; all of them cost days. The table is worth a skim even if you think you're ready.

It happens: a transposed digit, a family member's number typed in a hurry. The fix follows the same flow — repeat the update with the correct Aadhaar number or VID and verify with the OTP; the latest successful verification is what counts in CRA records. Two variations need more than a re-run: if the portal throws an error on re-submission, or the problem is a name mismatch rather than a wrong number, raise a CGMS ticket with a scan of both the Aadhaar and PAN so the correction lands once, cleanly.

Seeding is a snapshot, not a subscription. If you later change the mobile number or address on your Aadhaar, the NPS record does not refresh itself — the CRA only learns what you tell it. Material changes (a new mobile, a legal name change) should be repeated on the CRA portal so the two systems keep matching. A five-minute re-seed after a UIDAI update is far cheaper than discovering the mismatch during a withdrawal request.

One boundary worth knowing: Aadhaar is issued to residents, so subscribers who joined NPS as NRIs usually won't have one at all, and their KYC rests on the passport and PAN instead. Don't force an Aadhaar update that the UIDAI check will bounce. For NRI-specific KYC updates, the CGMS route is the clean channel — the CRA can tell you exactly which document set your account expects.