- The PM Surya Ghar subsidy is paid to the customer by DBT after commissioning — so the customer's bank must be seeded.
- A name mismatch across Aadhaar, bank and bill is the #1 disbursement failure; NPCI matching is strict.
- DBT seeding is not the same as Aadhaar linking — an account can be linked for KYC yet not seeded for DBT.
- Fix the weakest record to match Aadhaar, then have the bank seed the active account to NPCI.
- Catch it before commissioning — fixing seeding takes days the customer can use while the install runs.
- NPCI and bank seeding rules and the Aadhaar-authentication mandate change — verify the current process.
You finished the install, passed inspection, filed the claim — and the customer still has not received the subsidy. Nine times out of ten, the money is stuck at the bank, not the portal. The cause is Aadhaar–bank DBT seeding, and a name mismatch is the usual culprit. Here is how EPCs fix it, precisely.
What DBT seeding is
DBT seeding is linking the customer's Aadhaar to their bank account on the NPCI Aadhaar Payment Bridge, so a government subsidy can be paid straight into that account. The PM Surya Ghar subsidy is paid to the customer by Direct Benefit Transfer (DBT) after commissioning and the net meter — not to the EPC, and not as a cheque.
Why the bank is the final gate
Every earlier step — feasibility, install, inspection, net meter, claim — can be perfect, and the money still will not land if the customer's account is not correctly seeded. The bank is the final gate. That is why a "completed" claim can sit for weeks with the customer asking where the money is. The answer is usually seeding.
Who fixes it
The seeding lives with the customer and their bank, but the EPC owns the outcome — an unpaid customer is your problem to chase. The smart EPC treats DBT seeding as part of the job, checks it early, and guides the customer to fix it, rather than discovering it after commissioning.
Why the payout blocks
The payout blocks because NPCI matches the subsidy to the seeded Aadhaar–account record, and any break in that record stops the credit. The most common break is a name that does not match; others include an unseeded account, the wrong account seeded, or an inactive account.
The honest figure
In practice, the subsidy is commonly credited 15 to 30 days after the certificate in theory, but 30 to 90 days or more in the field — and seeding problems are a big part of that gap. Treat these as field estimates, not promises. The payout is not a guarantee with a fixed date; it depends on the claim processing and a clean bank record.
It is not the portal's fault
When a payout fails on seeding, there is nothing more to fix on the National Portal — the portal did its job. Chasing the portal or the DISCOM wastes time. The fix is at the bank. Diagnosing this correctly, early, saves weeks of the wrong follow-up.
Seeding versus linking: the distinction that trips everyone
Aadhaar linking and DBT seeding are different, and confusing them is why "but my Aadhaar is linked" still ends in a failed payout. Linking connects Aadhaar to the account for KYC; seeding registers that account on NPCI as the one to receive DBT money.
An account can be linked but not seeded
A customer can have Aadhaar fully linked for KYC and still not be DBT-seeded. Worse, a customer with several accounts can have Aadhaar seeded to an old account they no longer use, so the subsidy lands somewhere they are not watching. Only one account is the active DBT account at a time.
What to ask the bank
Do not ask "is the Aadhaar linked?" — that gets a misleading yes. Ask the bank to confirm the Aadhaar is seeded to NPCI for DBT and which account is the active DBT account. Get it in writing. Verify the current seeding procedure, because bank and NPCI processes change.
Step-by-step: fix a blocked DBT payout
Work these in order. They move from diagnosis to the bank fix to re-attempting the credit, so you solve the common cases fast and do not chase the wrong party.
Confirm it is a seeding issue, not a claim stage
Check the portal: if the claim shows processed or paid but the bank shows nothing, the problem is almost always DBT seeding, not the application stage.
Check the name across all three records
Compare the customer name on Aadhaar, the bank account, and the electricity bill. NPCI matching is strict, so even a small difference can block the credit.
Verify the account is DBT-seeded, not just linked
Ask the bank to confirm the Aadhaar is seeded to NPCI for DBT (the Aadhaar Payment Bridge), not merely linked for KYC. These are different things.
Fix the weakest record to match Aadhaar
Aadhaar is usually the anchor. Update the bank name or bill name to match Aadhaar exactly, rather than changing Aadhaar, unless Aadhaar itself is wrong.
Re-seed and re-confirm with the bank
Once names match, have the bank seed the correct active account to NPCI and enable DBT. Get written confirmation of the seeded account.
Re-check the portal bank details and re-trigger
Make sure the account number and IFSC on the claim match the seeded DBT account, then follow the portal process to re-attempt the credit. Verify the current re-trigger step.
Failure → cause → fix table
Match the failure to its likely cause and the fix. Treat the causes as commonly reported patterns; confirm the exact bank and NPCI steps with the customer's bank.
Source: commonly reported disbursement experience, MNRE and NPCI DBT rules; verify the current seeding procedure with the bank and NPCI.
The name-mismatch trap
The name mismatch is the number-one disbursement failure because NPCI matching is strict and small differences are everywhere. "R. Kumar" on the bank, "Rajesh Kumar" on Aadhaar, and "Rajesh K." on the electricity bill are three different names to the system.
Where mismatches hide
- Initials versus full name — banks often store initials; Aadhaar stores the full name.
- Maiden versus married name — common when the bank account predates a name change.
- Spelling and transliteration — the same name spelled two ways across records.
- Extra spaces or titles — "Mr", "Smt", or a stray space breaks an exact match.
- Bill in another family member's name — the bill, Aadhaar and account must point to the same beneficiary.
Make Aadhaar the anchor
Pick one source of truth, usually Aadhaar, and bring the bank and bill into line with it. Update the bank's name record to match Aadhaar exactly, rather than changing Aadhaar, unless Aadhaar itself is genuinely wrong. Then make sure the claim and portal details use the same name. This single discipline removes most failures.
Prevention checklist
The cheapest fix is the one you do before commissioning. Check seeding at intake, and you turn a 90-day payout chase into a non-event.
- ✓ Confirm the name is identical on Aadhaar, the bank account and the electricity bill.
- ✓ Confirm the bank account is DBT-seeded to NPCI, not just KYC-linked.
- ✓ Identify the single active DBT account if the customer has several.
- ✓ Confirm the account is active and KYC-complete, not dormant.
- ✓ Complete any Aadhaar authentication the scheme requires.
- ✓ Enter the correct account number and IFSC on the portal, matching the seeded account.
- ✓ Give the customer time to fix seeding during the install, not after.
- ✓ Keep written bank confirmation of the seeded DBT account in the job file.
How SuryaHub helps you catch seeding early
SuryaHub builds the seeding check into customer intake, so a mismatch surfaces before commissioning, not after the customer is chasing the money. The CRM captures the customer's Aadhaar name, bank name, and bill name at the start and flags when they do not match, so your team can guide the customer to fix DBT seeding while the install proceeds. The government-workflow module keeps the portal bank details tied to the job, so the claim uses the seeded account. SuryaHub does not perform the bank seeding — it makes sure you never reach commissioning with a broken record. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and the figures here are scheme facts, not guarantees.
Catch the #1 payout failure at intake
See how SuryaHub flags name and bank mismatches before you commission.
Related guides
Frequently asked questions
Why is my PM Surya Ghar subsidy not credited to the bank?+
A PM Surya Ghar subsidy that is not credited is most often blocked by Aadhaar–bank DBT seeding, usually a name mismatch between Aadhaar and the bank account. The subsidy is paid to the customer by DBT, and NPCI matching is strict. Fix the name and seed the account, then verify the current process.
What is DBT seeding for PM Surya Ghar?+
DBT seeding for PM Surya Ghar is linking the customer's Aadhaar to their bank account on the NPCI Aadhaar Payment Bridge so the subsidy can be paid directly. This is different from KYC linking. A bank account can be Aadhaar-linked yet not DBT-seeded, which blocks the payout, so confirm seeding with the bank.
Does the name on Aadhaar and the bank account have to match for PM Surya Ghar?+
Yes. For PM Surya Ghar, the name on Aadhaar and the bank account should match because NPCI DBT matching is strict, and a name mismatch is the number-one disbursement failure. Make the name identical across Aadhaar, the bank, and the electricity bill, usually by matching the bank to Aadhaar.
How do I make a bank account DBT-enabled for PM Surya Ghar?+
To make a bank account DBT-enabled for PM Surya Ghar, ask the bank to seed the customer's Aadhaar to NPCI and enable it for DBT, not just complete KYC linking. Only one account can be the active DBT account. Get written confirmation, and verify the current seeding procedure with the bank and NPCI.
My PM Surya Ghar Aadhaar is linked but the subsidy still failed. Why?+
A PM Surya Ghar subsidy can still fail when Aadhaar is linked for KYC but not seeded to NPCI for DBT, or seeded to a different account. Linking and DBT seeding are different. Confirm with the bank which account is the active DBT account and that the name matches Aadhaar, then re-attempt.
How does SuryaHub help with PM Surya Ghar DBT seeding failures?+
SuryaHub flags name and bank-detail mismatches early, before commissioning, so the customer can fix DBT seeding while the install proceeds, not after. SuryaHub does not perform the bank seeding. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL.
Sources & references
The Aadhaar-authentication mandate and the NPCI/bank seeding procedure can change. The notes here come from primary government and NPCI sources and commonly reported disbursement experience — confirm the current seeding procedure and mandate wording before you act.
- National Portal for PM Surya Ghar ↗
The official subsidy claim and bank-detail flow — verify the current process.
- Ministry of New & Renewable Energy (MNRE) ↗
Scheme guidelines and the Aadhaar-authentication mandate.
- National Payments Corporation of India (NPCI) ↗
The Aadhaar Payment Bridge and DBT seeding rules.
Written by the SuryaHub team · reviewed against MNRE, NPCI & National Portal sources · updated 19 June 2026.
Method: Seeding failures and fixes are drawn from MNRE and NPCI DBT rules and commonly reported disbursement experience, re-checked every 30 days. Disbursement timelines are field estimates, not guarantees. Confirm the current NPCI/bank seeding procedure and the Aadhaar-authentication mandate. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.
Change log: 19 Jun 2026 — first published.