Official record lookup
Project submission
From payment status to one clear next step.
A Hindi and English guide designed for a PM-KISAN beneficiary who should not have to interpret technical statuses alone—and for the people who help them.
Open the working product No login, API key or personal data required.
Project summary
From a technical status to a clear first step
PM-KISAN pays eligible farming families ₹6,000 a year in three instalments. When one does not arrive, Know Your Status shows the official record after a registration number, CAPTCHA and OTP. Kisan-eMitra answers PM-KISAN questions in several languages. Both are useful, but a farmer may still need to decide which issue to fix first, where to go and what to take or say.
Paisa Kahan Hai fills that action gap. It checks known statuses in a documented order and gives one first action. Built for farmers who are not comfortable using government websites alone and for their helpers, the website uses no beneficiary identifiers. People explore a fictional case or select labels from a status they already have. It never bypasses secure sign-in or looks up a real record.
Each result explains the cause, office, documents, words to say, checked cost or timing, verification and escalation. The Hindi and English guide can be read aloud, printed, saved as a PDF or shared. When a visit is needed, an identifier-free note separates what to take, request and confirm. Round 2 shows how the same checked guidance could work through WhatsApp, one question at a time.
The latest payment reached more than 9.44 crore farmers. Government data separately records lakhs of stopped payments linked to land records, Aadhaar-bank linking and e-KYC. These numbers show the problem's scale—not this prototype's reach. All examples are fictional; no government connection has been built.
Checking a status is not the same as knowing what to do next
Official question answering
Kisan-eMitra
Answers PM-KISAN questionsAvailable in several languages.The remaining gapWhich problem do I fix first—and where do I go, what do I carry and what do I say?
Action guidance
Paisa Kahan Hai
Turns known statuses into one checked first action- 1Fixed, source-backed rules
- 2Web guide or proposed WhatsApp integration
- 3Prepared office visit note
It complements the official services; this prototype does not access government records or replace secure sign-in.
Primary user
A PM-KISAN beneficiary who may use Hindi, an older phone or a slow connection and finds technical payment statuses difficult to act on.
Helping user
A family or community “phone person” helping the beneficiary understand the result and prepare for the right office.
Round 2 demo
From a familiar message to a prepared office visit
This two-minute demo follows the Round 2 brief: the first minute explains the problem and shows the product in action; the second shows one connected improvement, helping a farmer move from familiar WhatsApp-style guidance to a better-prepared office visit.
Round 2 demoProblem, working journey and one connected improvement · 1 min 56 sec
Open the Round 2 videoProblem and working journey
Show the gap after status lookup, then follow one fictional case from technical statuses to one first action.
One connected improvement
Show the proposed WhatsApp route and the office visit note as one handoff—from familiar guidance to a prepared visit.
Performance evidence
Tested for mobile phones and slow connections
The evidence below is dated so it does not pretend to describe every later release. Lighthouse measured the live site on 26 August; a stricter Slow-3G test measured the Round 2 build on 5 September.
100Lighthouse performance · 26 Aug
100Lighthouse accessibility · 26 Aug
0.75 sDiagnosis readable · Slow-3G test, 5 Sep
2.40 sDocument ready · Slow-3G test, 5 Sep
Lighthouse mobile1.6 s
Largest Contentful Paint
Lighthouse mobile40 ms
Total Blocking Time
Measured first load · 5 Sep189 KB
189,113 bytes across 12 requests
Method: Lighthouse 13.4.1 used the live production URL and its mobile profile on 26 August 2026. The Round 2 build was measured on 5 September 2026 using 400 ms latency, 400 Kbps down/up and 4× CPU slowdown, with cache disabled.
Open the complete Lighthouse report ↗Honest limit: the measured 189 KB first load was above this project's internal target of under 100 KB. The target remains recorded as not met.
Scale and potential impact
A large problem—without claiming people already helped
Government figures from 2026 show the scale of PM-KISAN and separately record lakhs of stopped payments linked to conditions this guide explains.
- 9.44+ crore
- eligible farmers received the 23rd instalment
- Scheme-scale context
- 16.52 lakh
- payments stopped under land seeding
- As of 16 March 2026
- 23.54 lakh
- payments stopped under Aadhaar–bank seeding
- As of 16 March 2026
- 32.95 lakh
- payments stopped under e-KYC
- As of 16 March 2026
23rd-instalment release — PIB / Ministry of AgricultureRajya Sabha Question 3226 — stopped-payment conditions
These are problem-space figures, not people reached or outcomes created by Paisa Kahan Hai. The three stoppage categories may overlap and must not be added together as unique beneficiaries. Product reach and comprehension remain unmeasured.
Product / build
The same checked rules decide every result
Start without sharing personal details
Try a fictional case, select status labels you already have, or get help reaching the official lookup.
Find what needs attention first
Fixed rules review the statuses in order, show the first blocker and keep later problems visible.
Prepare the next step
Get the office, documents, words to say, checked cost or timing, verification and an office visit note.
- 23
- fictional scenarios
- 20,736
- guided combinations tested
- 2
- human-reviewed languages
- 0
- personal identifiers collected
Technical government wording
One plain-language cause and one first action
Several problems at once
A fixed order that shows what to address first
An unfamiliar new channel
A website plus a proposed WhatsApp route
Confusion during an office visit
A note covering what to take, request and confirm
Hindi, assisted use or slow data
Reviewed Hindi, read-aloud, print and lightweight pages
Personal-data risk
No beneficiary identifier, login, analytics or server-stored progress
I used Codex to help turn requirements into code, compare sources, prepare bilingual review batches and test the build. I chose the product direction and personally reviewed the Hindi. AI does not choose the farmer's result; fixed rules do.
Evidence and validation
What was checked—and what is not yet proven
- The current journeyI inspected the official Know Your Status entry screen without entering or submitting personal data.
- Where each problem is handledOfficial payment, e-KYC and NPCI guidance confirmed that different blockers require different offices or services.
- How large the problem isPIB and parliamentary records support the scheme and stopped-payment figures, with possible overlap clearly disclosed.
- Every instruction shown to a userA 72-claim workbook tracks the source and wording. Forty-nine claims are verified, and every workbook-backed claim shown in the product is supported by a primary source.
This checks the problem structure and factual guidance. It does not prove that farmers understand the product or achieve better outcomes. No beneficiary or frontline-worker study has been conducted.
A safe path to real use
What a real service would need behind the interface
This is a proposed path, not a claim that government integrations are available. The prototype remains completely outside government systems.
- 01Farmer or helper startsWebsite, WhatsApp, CSC or assisted use
- 02Permission and secure sign-inExplain why access is needed first
- 03Read only what is neededUse the minimum statuses required
- 04Approved government systemsPM-KISAN, payment and state sources
- 05Checked rules and guidanceTraceable Hindi and English output
Data and rules
Agreed status definitions, versioned rules, source history, safe fallbacks and a way to correct errors.
Security and reliability
Encryption, strict access, rate limits, audit logs, misuse monitoring, reliable service and incident response.
People and ownership
Named owners for status updates, bank/CSC/agriculture-office routes, escalation, support and service quality.
Before any real-record use, authorised data access, consent and identity standards, responsible system owners, operational support and a correction process would all need formal agreement.
Transparency
What works, what is mocked and what remains untested
Works in the prototype
- Bilingual status interpretation
- Read-aloud, full-guide sharing and one-page print
- Conditional, identifier-free office visit notes
- Local-only progress tracking
- Mobile, keyboard and no-JavaScript paths
Shown as a mock-up
- All example records are fictional
- Guided inputs are user-selected status labels
- The WhatsApp interface sends no messages
- No example represents a real beneficiary
Not connected
- No government, bank or grievance integration
- No login, database, analytics or SMS
- No real-record lookup or grievance filing
Needed for real use
- Authorised, documented data contracts
- Explicit consent and minimal data
- Authentication, rate limits and audit trails
- Abuse monitoring and human support
Not yet tested with users
- No beneficiary comprehension study
- No frontline-worker workflow study
- No measured reach or outcome improvement
- No physical screen-reader or Android test
Previous-round demo
The original web-guide demonstration
This is the video submitted in the previous round. It is kept here—and at the same direct file URL—so the earlier submission link continues to work. It predates the proposed WhatsApp flow and the office visit note.
Previous-round submissionArchived for continuity; this is not the Round 2 demo.
Open the original video