The KYC notice that isn't the bank's
The RBI's caution on frauds in the name of KYC updation: the urgent message that borrows a genuine bank process - what re-KYC actually looks like, and the route that settles a suspicious request.
The SMS sounds like housekeeping: your KYC is incomplete, your account will be frozen by the end of the week, update now at this link. The Reserve Bank of India cautioned the public about frauds in the name of KYC updation in September 2021, repeated the caution in February 2024 "in the wake of continuing incidents", and was still printing the warning on financial-literacy leaflets in 2026. The scheme survives because it borrows something real: banks genuinely must update customer KYC from time to time, and they genuinely send reminders. The fraud's whole job is to stand next to that real process and look like it.
What the RBI says the fraud looks like
The modus operandi, as the central bank describes it, begins with an unsolicited call, SMS or email urging the customer to update KYC. The message manufactures urgency - a deadline, a threat that the account will be frozen, blocked or closed - and supplies the remedy: a link to click or an application to install. What it is after, the RBI's releases say, are account and login details, card information, PIN, password or OTP, typed into a page or an app the bank does not run; once a customer shares these, the fraudsters gain access to the account and defraud them. Note what a click does and does not settle. Clicking alone does not establish whether compromise occurred: the RBI-described harvest needs the customer to type the details or install the rogue application, and a phishing page captures whatever is submitted to it; separately, malicious software or an exploited vulnerability can cause compromise without either. The message is the lure; what is typed, installed or run decides the harm.
What genuine KYC updation looks like
This is the part the fraud counts on you not knowing: re-KYC is routine, and most of it is simple. The RBI's FAQs on its Master Direction, updated in June 2025, describe the shape of it: every regulated entity must keep customer records current, repeating KYC at least once every two years for high-risk customers, eight for medium-risk and ten for low-risk. On that FAQ's account, the bank must intimate you in advance and send reminders after the due date; if nothing has changed, a self-declaration is enough, delivered through your registered email or mobile number, an ATM, the bank's own internet banking or mobile application, or a letter; any branch of your bank can take the update, and the bank must acknowledge whatever you submit; an account can be closed only after due notice. The Master Direction is amended from time to time, so its current text governs the detail. Two things follow. A KYC message is not automatically fake, because banks really do send them. And the genuine process finishes through channels the bank already runs, not through an app you have never seen.
The line that separates real from fake
Since the content can be copied, the tell is the route. A genuine request survives being handled through the bank's own channel; a fake needs you to stay inside its message. So the test is not reading the SMS harder - it is leaving it. Open the bank's app or website yourself, or call the number on the bank's official site or the back of your card - the RBI's first "do" is to take the contact number only from official sources - and ask whether KYC is due. If it is, complete it right there. If nothing is due, you have just caught the fraud. The RBI's own FAQ on links inside KYC messages is blunt: exercise utmost caution before clicking them.
The habits the RBI lists
The 2024 caution ends with a short list. Do not share account login credentials, card details, PINs, passwords or OTPs with anyone; do not hand KYC documents to unidentified people or organisations; do not type sensitive data into unverified websites or applications; do not click suspicious or unverified links. On the positive side: contact the bank directly when a KYC request arrives, take its contact details only from the official website, ask the branch which update modes are available to you, and inform the bank at once if you suspect a fraud. None of this requires reading headers or tracing domains; it requires only that the conversation move to a channel you chose.
If you already shared something
Speed matters more than certainty. Call the bank on its official number and say exactly what was shared - an OTP, a password, card details - so access and cards can be blocked; change passwords from a device the caller never touched. If money moved, call 1930, the national financial-fraud helpline, immediately - the RBI's release directs exactly this - and report the incident at cybercrime.gov.in, keeping the message, the sender's number and any transaction references. Neither the bank nor the helpline can promise recovery; what they can do is shorten the fraudster's window.
The shape worth remembering
Re-KYC is a real errand, which is why it works as a costume. The fraud does not need to invent a task; it only needs to own the route the task arrives by. Take the route back and the costume falls off: the bank's own app, its own site, its branch, its published number. A genuine reminder will wait for you there. The fake one cannot follow.
Sources: the RBI's press releases of 13 September 2021 and 2 February 2024 cautioning against frauds in the name of KYC updation; the RBI's FAQs on the Master Direction on KYC (updated June 2025) on how genuine periodic updation works; the RBI's 2026 financial-literacy leaflet on KYC fraud. Fraud reporting: 1930 and cybercrime.gov.in.
Frequently asked questions
My bank genuinely sends KYC reminders. How am I supposed to tell?
You do not have to tell from the message. Periodic updation is real - under the RBI's KYC rules, banks intimate customers in advance and send reminders - so a KYC SMS can be genuine. The safe move works either way: ignore the link and the number inside the message, open the bank's own app or website yourself, or call the number on its official site, and ask. A genuine request will still be waiting; the fake one depends on you answering through its own route.
The caller knew my name and part of my account number. Isn't that the bank?
No. Names and partial numbers circulate widely after data leaks and are cheap to guess, and the RBI's caution describes exactly such unsolicited calls. Treat every unexpected contact as unverified and continue through the bank's published channel. What a caller knows about you says nothing about who they are.
I shared an OTP before it felt wrong. What now?
Call your bank immediately on the number from its official website and report what was shared, so cards and access can be blocked; change your passwords from another device. If money moved, call 1930 at once and inform the bank, and file the incident at cybercrime.gov.in with the message and number preserved. Recovery is never guaranteed, but minutes matter for freezing a transaction in transit.