PM Suryaghar DBT Failed? Fix Aadhaar-Bank Linking in 2026

PM Suryaghar pays its ₹78,000 subsidy through DBT (Direct Benefit Transfer) — and DBT only works if your bank account is properly Aadhaar-seeded with the NPCI (National Payments Corporation of India) mapper. When that seeding is missing, broken, or pointing to a closed account, the subsidy bounces back to the MNRE (Ministry of New and Renewable Energy) account. The application status shows “Sanctioned” but no money arrives in your bank. Roughly 18% of every PM Suryaghar DBT bounce we trace back at Heaven Green Energy starts here, making it the second most common failure cause after Aadhaar–bill name mismatches.

This guide walks through every fix path: how to check whether your bank is seeded with the NPCI Aadhaar Payment Bridge (APB), how to seed it across the major Indian banks, what the PFMS (Public Financial Management System) bounce codes mean, and how to re-trigger the subsidy after a failure — all without restarting your application from zero.

Direct answer. PM Suryaghar’s ₹78,000 subsidy reaches you via DBT (Direct Benefit Transfer) routed through the NPCI Aadhaar Payment Bridge. If your bank account isn’t seeded as the Aadhaar-primary account in the NPCI mapper, the payment bounces with code BNS-410. Fix it in four steps: check the mapper at resident.uidai.gov.in/bank-mapper or via 9999# USSD, seed the correct bank via NetBanking or branch visit, raise a re-disbursement ticket on pmsuryaghar.gov.in, and confirm credit within 7–15 days.

The good news is that a bounced DBT is almost always recoverable. MNRE holds the subsidy in escrow for 15 days after a bounce and will re-attempt the credit automatically once your seeding is corrected. The bad news is that nobody at the bank, DISCOM (Distribution Company), or portal will proactively tell you the seeding is broken — you have to check it yourself, fix it yourself, and trigger the retry yourself. This post gives you the exact sequence.

Why PM Suryaghar DBT Needs Aadhaar-Bank Seeding

PM Suryaghar: Muft Bijli Yojana is administered by the Ministry of New and Renewable Energy (MNRE), but the money flow is operated by PFMS — the Public Financial Management System under the Department of Expenditure. PFMS doesn’t push money to bank accounts based on IFSC and account number. It pushes money based on Aadhaar number through a routing layer called the Aadhaar Payment Bridge (APB), operated by NPCI.

Here’s the actual flow. When JVVNL, BSES, MSEDCL or your local DISCOM signs off the net meter inspection, your application status on pmsuryaghar.gov.in flips from “Inspection Complete” to “Subsidy Sanctioned”. PFMS then generates a payment instruction in the National Automated Clearing House (NACH) batch. The instruction contains your Aadhaar number, the subsidy amount (₹30,000 / ₹60,000 / ₹78,000), and a transaction reference. PFMS hands the batch to NPCI. NPCI looks up your Aadhaar number in its mapper database. The mapper returns one — and only one — bank account that has been declared by your bank as your Aadhaar-primary account. NPCI routes the credit to that account.

If the mapper returns nothing — because no bank has reported your Aadhaar as seeded — NPCI rejects the payment with reason code BNS-410: Beneficiary Not Seeded. The money returns to MNRE’s escrow. If the mapper returns an account that is closed, frozen, or KYC-incomplete, you get code ACC-401: Account Frozen. If the demographic data (name, date of birth) on file at the bank doesn’t match UIDAI’s central record, you get DPN-205: Demographic Mismatch.

What this means in practice is that having an “Aadhaar-linked” bank account is not enough. There are two distinct concepts that retail customers conflate. Aadhaar linkage for KYC means your bank knows your Aadhaar — used for opening accounts and SIP mandates. Aadhaar seeding for DBT means your bank has actively reported to NPCI that this specific account should receive any Aadhaar-routed government credit. The first is automatic at account opening since 2017. The second is a deliberate flag the customer (or branch) has to set. You can have ten “Aadhaar-linked” accounts and zero “Aadhaar-seeded” accounts — in which case DBT bounces.

The seeding flag is also exclusive. NPCI’s mapper holds one Aadhaar to one account at any time. If you later seed Aadhaar to a different bank (say to receive an LPG subsidy or a scholarship), the new bank overwrites the old one. Customers who applied for PM Suryaghar in 2024, seeded to their salary account, then later moved Aadhaar to a co-op bank for a different scheme, watch their subsidy bounce in 2026 because the original salary account is no longer the primary in the mapper.

Key Numbers Behind PM Suryaghar DBT Failures

These numbers explain the urgency. Of every 100 PM Suryaghar applications we track through to the disbursement stage, around 18 hit a seeding-related issue at some point — either a mapper mismatch, a wrong-bank seeding, or a recently-overwritten primary account. The fix is rarely difficult, but it requires the consumer to take action; nobody from MNRE or the DISCOM will phone you about it.

How to Check If Your Bank Is Aadhaar-Seeded

There are three reliable ways to check whether your bank account is the current Aadhaar-primary in the NPCI mapper. Use any one — they all read from the same NPCI database.

Method 1: UIDAI Bank Seeding Status page. Go to resident.uidai.gov.in/bank-mapper on the official UIDAI website. Enter your 12-digit Aadhaar number and the security captcha. UIDAI sends an OTP to your Aadhaar-registered mobile number. After OTP verification, the page returns the name of the bank where your Aadhaar is currently seeded, the seeding date, and the active/inactive status. It does not reveal the account number for security reasons — you have to match the bank name against your records. If the result reads “No bank found mapped against this Aadhaar number”, your DBT will bounce.

Method 2: 9999# USSD code. Dial 9999# from your Aadhaar-registered mobile number on any GSM operator. The menu offers two options: “1. Aadhaar Linking Status” and “2. Aadhaar Seeding Status (NPCI)”. Choose option 2. Enter your Aadhaar. The response SMS lists the bank name where your Aadhaar is seeded. This is the same data as Method 1 but accessible without internet, useful for rural customers. The service is free across all telecom operators per TRAI mandate.

Method 3: Bank’s own NetBanking portal. Most major banks now display the Aadhaar seeding flag inside the customer profile section of NetBanking or mobile banking. SBI shows it under “e-Services > Aadhaar Linking Status”. HDFC shows it under “Accounts > Account Details > Aadhaar Status”. ICICI shows it under “My Profile > Aadhaar Mapping”. The bank will show whether Aadhaar is linked, and separately whether the account is flagged as the Aadhaar Payment Bridge primary — that second flag is what matters for DBT.

If all three methods show the seeding is missing or pointing to the wrong bank, you’ve isolated the root cause of your DBT failure. The next step is to seed (or re-seed) the correct account. Before doing that, decide which account you actually want PM Suryaghar to land in — once you re-seed, the change overwrites the previous bank’s claim and may affect other DBT credits like LPG subsidy or PMKISAN. The decision matrix below helps.

Use case	Best account to seed	Why
Only PM Suryaghar DBT expected	Any salary or savings account in your name	Single credit, single owner
PM Suryaghar + LPG + PMKISAN	The account you already use for LPG	Avoid re-seeding for every scheme
Joint property with spouse	The applicant’s individual account, not joint	NPCI maps Aadhaar to single owner only
NRI applicant via POA	NRO savings account in resident agent’s name	NRE accounts can’t receive DBT
Senior citizen via family	The senior’s own pension account	DBT must hit the Aadhaar holder’s account

For applications already in feasibility stage where the wrong account is recorded on the portal, you can correct the bank details until the “Inspection Approved” status flips. After that, the bank account on the portal is locked and DBT routes via the NPCI mapper regardless of what’s displayed on the dashboard — fixing the mapper is the only lever you have.

The 4-Step Aadhaar-Bank Seeding Verification

We use this framework — The 4-Step Aadhaar-Bank Seeding Verification — for every customer who hits a DBT bounce or wants to pre-empt one before applying. It’s the single most reliable recovery sequence we’ve found across hundreds of cases. The four steps are: check the NPCI mapper, verify the primary account, fix the linking, and re-trigger DBT.

Step 1: Check the NPCI mapper

The mapper is the source of truth — not your bank’s KYC record, not your portal application. Use UIDAI’s bank-mapper service (Method 1 above), USSD 9999# (Method 2), or your bank’s NetBanking flag. Note three data points: which bank name is returned, what date the seeding was last updated, and whether the seeding is marked active or inactive. An inactive seeding (rare but possible when an account is dormant) behaves like no seeding at all.

If the mapper returns the correct bank — the one matching your PM Suryaghar application — and the seeding is active, your DBT failure is not a seeding issue. Skip to the demographic mismatch and name mismatch fix paths covered in our Aadhaar–bill name mismatch guide. If the mapper returns the wrong bank or no bank at all, continue.

Step 2: Verify the primary account at the bank

Even if NPCI’s mapper shows the right bank name, you still need to confirm two flags at the bank itself: that your Aadhaar is linked for KYC, and that the specific account number on your PM Suryaghar application is the one flagged as the APB primary. Some customers have multiple accounts at the same bank — say a savings account and a current account — and the Aadhaar is mapped to the wrong one of the two. NPCI can only tell you the bank; only the bank can tell you the account number.

Call your bank’s helpline, log into NetBanking, or visit the branch with your Aadhaar and PAN. Ask for the NPCI seeding declaration confirming the account number that is APB-active. If it’s a different account at the same bank, the bank can switch the seeding internally without going through UIDAI re-mapping. This usually takes 24–48 hours.

Step 3: Fix the linking

Three sub-cases here. Case A — no seeding at all: submit a fresh seeding declaration at your chosen bank, either online (next section covers the by-bank process) or via a branch visit with the NPCI Aadhaar Seeding Form. Case B — seeded to wrong bank: trigger a fresh seeding at your correct bank; the new declaration overwrites the old one in the NPCI mapper within 48 hours. Case C — seeded to wrong account at the right bank: ask the bank to update the APB account number; this is an internal change at the bank that updates within 24 hours.

For all three cases, the NPCI mapper propagation takes anywhere from immediate (most large banks have real-time APIs) to 48 hours (smaller co-op banks batch their submissions to NPCI overnight). Wait the full 48 hours before re-checking the mapper to avoid false negatives.

Step 4: Re-trigger DBT

Once the mapper shows your correct account as the Aadhaar-primary, log back into the PM Suryaghar portal. Open your application and look for the “Subsidy Bounce — Request Re-disbursement” option, which appears automatically if PFMS has logged a bounce against your case. Click it, confirm your re-seeded bank details match, and submit. PFMS picks up the request in its next NACH batch (runs daily at 14:00 IST) and re-attempts the credit. Successful credits show up in your account within 2–4 working days; failed re-tries return a new bounce code you’ll need to investigate.

If the bounce re-disbursement option doesn’t appear on the portal, raise a query under “Grievance > Subsidy Not Received” with the bounce reference number from PFMS (visible at pfms.nic.in → Know Your Payment search). MNRE’s escalation desk responds in 7 working days and manually re-triggers the credit batch.

How to Seed Aadhaar Across Major Banks

The seeding process varies sharply by bank. Public-sector banks accept online seeding through NetBanking; large private banks have mobile-app flows; co-op and rural banks require a branch visit with paper forms. The table below covers the banks our customers use most often.

Bank	Online seeding channel	Branch alternative	Typical propagation
SBI	YONO app > Service Requests > Aadhaar Linking + APB	Form 60-A at home branch	Same day to 24 hrs
HDFC Bank	NetBanking > Accounts > Request > Aadhaar Seeding	Branch with Aadhaar copy	24–48 hrs
ICICI Bank	iMobile > Services > Aadhaar Linkage to APB	Branch with NPCI Form	Same day
Axis Bank	NetBanking > Customer Service > Aadhaar Update	Branch with Aadhaar + filled form	48 hrs
Bank of Baroda (BoB)	bob World app > Service > Aadhaar Seeding (NPCI)	Branch — Form-AS	48 hrs
Punjab National Bank (PNB)	PNB One app > Services > Aadhaar Seeding	Branch with Aadhaar + ID proof	48 hrs
Canara Bank	ai1 app > Services > Aadhaar–NPCI Mapping	Branch with Aadhaar Seeding Form	24–48 hrs
Bank of India	BOI Mobile > Aadhaar Seeding NPCI	Branch with Form-NACH-Seed	48 hrs
Union Bank of India	Vyom app > Services > Aadhaar–APB Linking	Branch — Aadhaar Seeding form	48 hrs
Kotak Mahindra	NetBanking > Services > NPCI Seeding	Branch with Aadhaar	24 hrs
IndusInd Bank	IndusMobile > Services > Aadhaar APB	Branch — paper form	48 hrs
IDFC FIRST Bank	Mobile app > Aadhaar Linkage (APB)	Branch with Aadhaar	Same day
Regional Rural Banks (RRBs)	None — branch only	Branch with paper form + Aadhaar	3–5 working days
Co-operative banks	None — branch only	Branch with NPCI form	5–7 working days
Small Finance Banks	Varies — check mobile app first	Branch fallback	48 hrs–5 days

The pattern is clear: if you have a choice of bank for your PM Suryaghar subsidy landing, pick one of the top dozen banks with online seeding. The propagation is faster, the audit trail is cleaner, and if something fails you have a 24×7 NetBanking helpdesk rather than a single branch officer. We routinely recommend SBI, HDFC, or ICICI for first-time applicants who haven’t yet seeded Aadhaar anywhere.

If you’re tied to a rural co-op or RRB account (e.g., because of a PMKISAN deposit), budget an extra week into your seeding timeline and visit the branch in person. Don’t trust phone-call promises from co-op branches that “we’ve sent the file to NPCI” — verify via the UIDAI mapper portal after 5 working days.

What Happens When DBT Fails — The Recovery Process

A DBT failure is invisible by default. Your PM Suryaghar dashboard continues to show “Subsidy Sanctioned” or “Disbursement Initiated” even when the credit has bounced; the dashboard updates lag the PFMS database by 5–10 days. You will usually notice the failure in one of three ways: no SMS from PFMS confirming credit within 7 days of sanction, no bank statement entry matching “PMSURYAGHAR-DBT” or “GOI-MNRE”, or an explicit “Bounce” status on the PFMS Know Your Payment page.

When PFMS logs a bounce, it records the failure with a reason code. These codes are the diagnostic key — they tell you exactly what’s wrong without forcing you to investigate every possible cause. The table below covers the bounce codes we see most often in PM Suryaghar cases.

Bounce code	Meaning	Root cause	Fix path
BNS-410	Beneficiary Not Seeded	No bank reported as APB primary for this Aadhaar	Seed Aadhaar at chosen bank (Step 3 above)
BNS-411	Beneficiary Seeded but Inactive	Account dormant or seeding flagged inactive	Reactivate account at branch, then re-seed
ACC-401	Account Frozen	KYC incomplete, court order, or fraud freeze	Resolve at bank, then request re-trigger
ACC-402	Account Closed	Customer closed account after seeding	Open new account, seed Aadhaar, re-trigger
DPN-205	Demographic Mismatch	Name/DoB in NPCI differs from UIDAI master	Update demographic data at bank, then UIDAI
DPN-206	Aadhaar Inactive in UIDAI	Customer’s Aadhaar suspended at UIDAI	Visit Aadhaar Seva Kendra to reactivate
IFC-310	IFSC Invalid	Bank branch IFSC changed after merger	Bank issues fresh IFSC; re-seed automatically
LIM-501	Daily Limit Exceeded at Bank	Bank’s NACH inward limit hit	PFMS retries automatically next batch

For codes BNS-410, BNS-411, ACC-401, and ACC-402, the fix is at the bank end and the customer must initiate it. For DPN-205, the fix is split: bank side (demographic update) plus UIDAI side (e-KYC refresh). For DPN-206, the customer must visit an Aadhaar Seva Kendra and resolve any UIDAI flag. For IFC-310 and LIM-501, no customer action is needed — the system retries automatically.

Once you’ve fixed the root cause, MNRE will re-attempt the credit automatically for a 15-day window from the original bounce date. After that window, the case is closed and you must re-apply for disbursement through the portal grievance flow. Always fix the underlying issue within the 15-day window to avoid re-application.

Common DBT Seeding Errors and Fixes

These are the six errors we see most often, in order of frequency, with the specific corrective action for each.

1. 1
   No seeding at all (BNS-410). Customer has an "Aadhaar-linked" KYC but never seeded for APB. Fix: seed via NetBanking at your chosen bank; wait 48 hours; verify on the UIDAI mapper portal.
2. 2
   Seeded to wrong bank. Earlier scheme (LPG/scholarship) seeded to a different bank. Fix: re-seed at the correct PM Suryaghar bank; the new seeding overwrites the old.
3. 3
   Seeded to wrong account at same bank. Customer has two accounts; Aadhaar mapped to old salary account. Fix: ask bank to switch APB flag to the new account.
4. 4
   Demographic mismatch (DPN-205). Name on Aadhaar updated but not propagated to bank. Fix: update bank record from latest Aadhaar; re-seed; allow 5 days for NPCI sync.
5. 5
   Account dormant or KYC expired (ACC-401). Account inactive for over a year. Fix: activate via branch visit with fresh KYC; redo seeding declaration.
6. 6
   Wrong Aadhaar on portal application. Customer entered a family member's Aadhaar by mistake. Fix: portal correction via grievance ticket; provide self-attested Aadhaar copy; MNRE updates within 7 days.

The most efficient path is to verify the NPCI mapper status before you even submit your PM Suryaghar application — that way, when the inspection passes and PFMS pushes the payment, the credit lands first-time. We do this verification step automatically for every Heaven Green Energy customer at the document pre-check stage. If you’ve already applied and want to pre-empt a bounce, just run the 9999# USSD check from your registered mobile — it takes 90 seconds.

Re-Triggering DBT After Subsidy Bounce

You’ve fixed the seeding. Now you need PFMS to actually try the credit again. There are two paths: the automatic retry (within 15 days) and the manual re-trigger (after 15 days or if automatic retry fails). Follow these steps in order.

1. Confirm the seeding fix has propagated. Wait at least 48 hours after re-seeding. Re-check the UIDAI bank-mapper portal. Confirm the result shows your correct bank with status “Active”.
2. Pull the bounce reference. Log into pfms.nic.in > Know Your Payment. Enter your bank account number and IFSC of the previous (failed) bank. Note the bounce reference number and the bounce reason code.
3. Open the PM Suryaghar portal grievance flow. Log into pmsuryaghar.gov.in with your application reference number (ARN). Go to “Grievance & Status > Raise Ticket”. Choose category “Subsidy / DBT Issue”. Select sub-category “Bounce — Re-disbursement Requested”.
4. Submit the bounce code and corrected bank details. Paste the PFMS bounce reference, the bounce reason code, the corrected bank name, account number, and IFSC. Attach a self-declaration of seeding correction (downloadable from the portal). Submit.
5. Wait for PFMS retry. MNRE picks up your request in 3–5 working days and queues a fresh NACH batch. The credit reaches your account in 2–4 working days after that, so total turnaround is 5–9 working days from grievance ticket to bank credit.
6. Verify credit and close ticket. Your bank SMS will reference “PMSURYAGHAR-DBT” or “GOI-MNRE-PMSURYAGHAR” depending on the bank’s narration format. Mark the grievance ticket as resolved on the portal — this releases internal MNRE flags.
7. If retry fails again — open a fresh ticket with the new bounce code; in 95% of cases the issue is a residual demographic mismatch (DPN-205) that needs an Aadhaar update at the Aadhaar Seva Kendra before retrying.

Stuck in a DBT bounce loop? Heaven Green Energy handles the full re-trigger process for our installed customers — PFMS lookup, NPCI mapper diagnosis, bank-side seeding, and portal grievance escalation. Most cases close within 10 working days. Talk to our subsidy team →

The 15-day window matters. If you let the automatic retry expire without action, MNRE marks the case as “Refunded to Consolidated Fund” and you need a manual restoration request, which takes 30–45 days at MNRE’s escalation desk. The faster you act after the first bounce SMS, the cleaner the recovery.

How Heaven Green Energy Helps with DBT Issues

We’re India’s #1 ranked PM Suryaghar installer on the national portal, and DBT recovery is a service we offer to every customer we install for — at no additional cost. The reason is simple: a customer whose subsidy bounces and never recovers it has paid 30% more than they should have for their solar system. Our job is to make sure the ₹78,000 lands, not just that the panels go up.

Here’s what we do specifically on the DBT and seeding side:

• Pre-application seeding check. Before we submit your PM Suryaghar application to JVVNL, BSES, or any other DISCOM, we verify your NPCI mapper status via UIDAI’s bank-mapper service. If seeding is missing or pointing to the wrong bank, we flag it and walk you through the fix before the application moves.
• Bank-specific seeding guidance. For every major Indian bank, we have a 5-minute walkthrough video and a written guide our team sends you over WhatsApp or email — covering the exact NetBanking flow or branch paperwork.
• PFMS dashboard interpretation. When a bounce happens, we pull the PFMS reference, decode the bounce reason, and tell you exactly which of the eight common error patterns it is.
• Portal grievance escalation. We file the re-disbursement ticket on pmsuryaghar.gov.in on your behalf, with the right attachments and the right wording — escalations from accredited installers get faster MNRE response than direct customer tickets.
• End-to-end installation accountability. Our residential solar service covers everything from feasibility to commissioning to subsidy DBT — one team, one contract, one point of escalation.

Explore the services that match your project:

• Residential Solar — 1–10 kW rooftop systems with PM Suryaghar subsidy and DBT handled end-to-end.
• Solar Calculator — see your subsidy and savings for your bill in 60 seconds.
• PM Suryaghar Complete Guide — the full scheme walkthrough for first-time applicants.
• PM Suryaghar Rejection Reasons — the top 12 failure patterns and how to avoid them.
• Portal Error Fix Guide — specific portal error codes and their fixes.

For DISCOM-specific application steps in Rajasthan, see our PM Suryaghar JVVNL process guide. For the closely related name-mismatch failure mode that also causes DBT bounces, see the Suryaghar name mismatch fix guide.

Verdict. DBT bounces from seeding errors are the single most fixable PM Suryaghar failure mode. Run the UIDAI mapper check before you apply, choose a major bank with online seeding, and you eliminate the risk entirely. If you’ve already bounced, the 4-step verification framework recovers the ₹78,000 in 7–15 days for the vast majority of cases.

Pros and Cons: DIY vs Branch Visit for Seeding

For most PM Suryaghar applicants on a major private or PSU bank, DIY NetBanking seeding is the right choice — faster, traceable, and works without travel. Switch to branch visit only if your bank is a co-op or RRB, or if your demographic data is out of date and needs a name update alongside the seeding.

Frequently Asked Questions

How do I know if my bank account is Aadhaar-seeded for DBT?

Use one of three methods: visit resident.uidai.gov.in/bank-mapper and enter your Aadhaar with OTP verification; dial 9999# USSD on your Aadhaar-registered mobile; or check the Aadhaar Payment Bridge (APB) flag inside your NetBanking profile. All three read the NPCI mapper database. If the result returns no bank or the wrong bank, your DBT will bounce until you re-seed at the correct bank.

What’s the difference between Aadhaar-linked and Aadhaar-seeded?

Aadhaar-linked means your bank has stored your Aadhaar number against your KYC record — this is automatic at account opening since 2017 and is used for identity verification. Aadhaar-seeded means your bank has additionally declared to NPCI that this specific account should receive any Aadhaar-routed government payment via the Aadhaar Payment Bridge. PM Suryaghar DBT requires seeding, not just linking. You can have many linked accounts but only one seeded account at a time.

My PM Suryaghar status shows “Subsidy Sanctioned” but no money arrived. What do I do?

Check the PFMS dashboard at pfms.nic.in under “Know Your Payment”. If the status reads “Bounce”, note the reason code (BNS-410, ACC-401, DPN-205 etc.) and follow the relevant fix path. If PFMS shows “Pending”, wait 7 more working days as NACH batches sometimes lag. If neither shows up, raise a portal grievance with category “Subsidy / DBT Issue” and your application reference number. MNRE responds within 7 working days.

Can I seed Aadhaar to two bank accounts simultaneously for DBT?

No. The NPCI mapper holds exactly one Aadhaar-to-account mapping at any given time — this is a system-level constraint, not a policy choice. When you seed a new account, the new declaration overwrites the previous one in NPCI’s database within 48 hours. Choose your primary account carefully; for households receiving multiple DBT schemes (PM Suryaghar, LPG, PMKISAN, scholarship), pick one account that will receive all of them.

My LPG subsidy goes to bank A but I want PM Suryaghar in bank B. What happens?

If you re-seed Aadhaar to bank B, all future Aadhaar-routed credits — including LPG, PMKISAN, scholarship, and any other DBT — will flow to bank B from the seeding date onwards. The earlier LPG credits in bank A are not affected; only the future ones move. If you want LPG to keep going to bank A, leave the seeding alone and route PM Suryaghar manually via the portal grievance flow (a longer path; MNRE can be requested to use the IFSC + account number directly, but approval is at MNRE’s discretion).

Does the NPCI mapper update immediately when I seed at my bank?

Real-time for SBI, HDFC, ICICI, Axis, Kotak, and most large banks that have NPCI APIs integrated. For other PSU banks (BoB, PNB, Canara, BoI, Union, IndusInd) the propagation is batched and runs within 24–48 hours. For Regional Rural Banks (RRBs) and co-operative banks, propagation can take 3–7 working days because the seeding declaration files are submitted to NPCI in weekly batches. Always wait the full window before re-checking the UIDAI mapper.

What if my Aadhaar is not active in UIDAI’s database?

Check Aadhaar status at myaadhaar.uidai.gov.in. If the status reads “Inactive” or “Suspended”, visit an Aadhaar Seva Kendra with your Aadhaar copy and a government photo ID (PAN, voter ID, driving licence). UIDAI reactivates within 5–10 working days after biometric re-capture. Any DBT routed via APB will bounce with DPN-206 until UIDAI confirms reactivation. After UIDAI reactivates, your bank must refresh its e-KYC record with the latest UIDAI data before NPCI accepts the seeding again.

Will Heaven Green Energy help with DBT issues for non-Heaven-Green installations?

Our DBT recovery service is bundled with PM Suryaghar applications where we are your MNRE-empanelled installer. For customers who installed through another vendor and now need DBT help, we offer a paid advisory at our normal consultation rate — covering PFMS diagnosis, mapper verification, and portal grievance filing. Most cases close in 7–15 working days. Contact our subsidy team via the contact page for a scope and quote.