What Welfare eKYC Screens Must Explain Before Asking for an OTP

One field, one person, one reason

Maharashtra's official Ladki Bahin eKYC flow begins with the beneficiary's Aadhaar authentication. It can continue with a husband or father's Aadhaar authentication, followed by caste category and family declarations. Each step has a different person, consent boundary and OTP.

The label beside an Aadhaar field should identify whose number is required and why. “Enter Aadhaar” is not enough when two people can appear in the same flow. The interface should name the beneficiary step and the husband/father step separately.

Success must name the completed stage

“Success” is too broad for a multi-system welfare service. A better message says: “Aadhaar authentication submitted successfully.” It then explains that eligibility, application status and payment are checked separately.

Without that sentence, a citizen can read eKYC success as a payment promise. When the bank credit does not appear, the same identity step gets repeated even though the unresolved issue can sit with the scheme record, bank readiness or payment file.

Record	What it proves
eKYC result	The visible result of the Aadhaar-authentication step.
Scheme status	The application or beneficiary record held by the programme.
Bank readiness	Whether the destination account is ready for the relevant DBT route.
Actual credit	The transaction shown by the passbook, statement, bank app or SMS.

Error messages must point to the owning record

An OTP failure and an “Aadhaar not in eligible list” result are different failures. The first belongs to authentication. The second belongs to the scheme record. Presenting both as a red error without an owner or next step wastes citizen time and helpdesk capacity.

A useful message contains	Why it matters
What failed	The citizen does not have to guess from a colour or generic label.
Which system owns it	Authentication, scheme and bank issues go to different records.
Last recorded event	A date and reference make the result traceable.
Official next action	The user avoids lookalike sites and unnecessary repeat submissions.

Evidence must survive escalation

Every completed or failed step should produce a reference that the helpdesk, grievance authority and information officer can recognise. Screenshots help the citizen, but a stable reference connects the same event across systems.

If the department later gives no clear recorded reason, RTI can seek existing records such as the eKYC date, the recorded hold or rejection reason, grievance action and any payment reference. RTI is not a substitute for correction or payment processing.

Privacy guidance belongs beside the action

“Do not share your OTP” should sit beside the OTP field, not in a distant footer. Where the flow requires a second person's authentication, the warning must apply again. Citizens should never be asked to send either OTP to an agent, caller or social-media account.

The practical Marathi Ladki Bahin eKYC guide explains the current sequence, common portal messages, evidence checklist, grievance route and record-focused RTI questions. The English guide covers the same official process for a wider audience.

RTI Wiki is built and operated by Big Helpers as an independent citizen resource. The government portal performs the official transaction. RTI Wiki explains the citizen workflow. Big Helpers documents the design pattern so the same discipline carries into websites, apps, CRMs and automation.

Frequently asked questions

Does eKYC Success prove a Ladki Bahin payment was credited?

No. It confirms an authentication step. Scheme status, bank readiness and the actual credit are separate records.

Where should a beneficiary complete eKYC?

Use only the official ladakibahin.maharashtra.gov.in portal and follow the current eKYC screen.

Should an OTP be shared with an agent?

No. Each OTP belongs only in the corresponding authentication field on the official government page.

What can RTI obtain after an unresolved grievance?

RTI can seek existing records such as the eKYC date, recorded hold or rejection reason, grievance action and any payment reference. It cannot sanction the benefit.

Last reviewed: 31 August 2026.