Why 9 Crore Farmers Can't Get Their ₹2,000 — And What It Reveals About Identity Tech

About ninety million farmers in India did everything right. They registered for a government cash program. They linked their bank accounts. And then their two-thousand-rupee payment just — stopped. Not because anyone committed fraud. Because they didn't finish an identity verification step many of them never fully understood.

That two thousand rupees is roughly twenty-four U

That two thousand rupees is roughly twenty-four U.S. dollars. For a small farmer in rural India, it's not trivial — it's seed money, it's fertilizer, it's a month of breathing room. The program is called P.M.-Kisan, and it's one of the largest direct-benefit transfer systems on the planet. Three times a year, the Indian government sends cash straight to farmers' bank accounts. But starting in twenty twenty-six, the government made electronic Know Your Customer verification — e-K.Y.C. — mandatory. If that step isn't complete, or if it's expired, the payment freezes automatically. Even if every other detail is correct. Now, you might never have heard of P.M.-Kisan. But if you've ever been locked out of your own bank account because of a verification glitch, this story is about you too. The twenty-second installment alone reached roughly ninety-three million farmers back in March. The twenty-third is expected this summer. And the question running through all of it is simple: when an identity system blocks the people it's supposed to serve, is the problem the technology — or the way it was built?

The most common reason a farmer doesn't receive their payment isn't fraud. It isn't a bank error. According to multiple Indian government and financial services sources, incomplete e-K.Y.C. is the single most frequent cause of frozen installments. Other reasons exist — an Aadhaar number not linked to the right bank account, a mismatch in land records, incorrect bank details. But e-K.Y.C. stands apart because it's the one that trips up the most people. And the way it works matters. Farmers can complete e-K.Y.C. through two paths. One is online, using a one-time password sent to the mobile number linked to their Aadhaar card. The other is offline — walking to a Common Service Centre and doing a biometric scan, usually a thumbprint. Both sound straightforward. Neither is, if you're a sixty-year-old farmer in a village with spotty cell coverage and the nearest service centre is an hour away.

That gap between "technically possible" and "actually completed" is where the real story lives. According to research cited by TechU.K., about seven in ten financial institutions worldwide have adopted e-K.Y.C. solutions to cut onboarding time and reduce identity fraud. That's a massive global shift. But adoption doesn't equal completion. Institutions that use fully integrated, end-to-end identity verification platforms report completion rates two to four times higher than those using patchwork systems. Two to four times. That means the difference between a farmer getting paid and a farmer waiting months often comes down to how well the steps were stitched together — not whether the biometric match was accurate.

And this is where the P.M.-Kisan story connects to something much larger. The same friction patterns show up across agencies and programs around the world. Every extra screen, every additional redirect, every moment where a mobile session drops — each one shaves off a percentage of people who simply don't finish. In a mobile-first journey, and most of India's digital interactions are mobile-first, every interruption is a potential dead end. For compliance teams and investigators, this creates a paradox. K.Y.C. is supposed to be both a security gate and an access gate. It has to stop fraud and let legitimate people through. When the workflow is clunky, it becomes a bottleneck for both — blocking real users while still leaving gaps that sophisticated fraud can exploit. For the rest of us, it means the app that's supposed to deliver your benefit, verify your identity, or unlock your account might be failing you not because the technology can't recognize you, but because the process was never designed for how you actually live.