Cyber Complaint Filed on 1930 or NCRP but No Action? How to Escalate in Kerala

A 12-digit NCRP number and a “status: pending” screen are not the end of a cyber complaint in Kerala — they are the point where many files stall. The national pipeline that actually moves a financial fraud case is 1930 / NCRP (CFCFRMS hold + routing to State/District cyber cell) → written complaint / FIR at the jurisdictional police / district Cyber Police Station → investigation and possible court application for frozen money. When that middle step is missing or silent, the file needs escalation — and escalation is a paper chain, not a phone follow-up: Superintendent / Commissioner in writing → CPGRAMS / State Police portal → Magistrate direction under Section 175(3) BNSS.

What happens after you dial 1930 or file at cybercrime.gov.in?

A common gap: the victim files at NCRP and waits, but never files the written, signed complaint at the police station that grounds an FIR. An NCRP reference alone does not always convert into an investigation — the signed written complaint closes that gap.

What does the law require — when must police register an FIR?

The mandatory-FIR rule from Lalita Kumari v. Govt. of U.P., (2014) 2 SCC 1 (Constitution Bench) holds: where the information discloses a cognizable offence, the police shall register an FIR under Section 154 CrPC / now Section 173 BNSS — preliminary inquiry is permitted only for limited categories, and delay beyond 7 days requires reasons. One BNSS caveat: under Section 173(3) BNSS, for offences punishable with three years or more but less than seven years, the officer in charge may, with the prior permission of an officer not below the rank of Deputy Superintendent of Police, conduct a preliminary enquiry to ascertain a prima facie case within fourteen days. Cyber fraud involving cheating under BNS 318(4) (punishable up to seven years) falls outside that three-to-seven-year window, so a victim’s written disclosure of such a fraud triggers the Section 173 duty without discretion to “examine and decide later”; where the facts disclose only IT Act 66C/66D (up to three years), the Section 173(3) preliminary-enquiry option can apply.

Where the offence is non-cognizable (e.g., certain simple intimidation or defamation alone), the police may need a Magistrate’s direction to investigate under Section 174 BNSS.

How should you escalate when the file is silent — the correct order?

Level 1 — Fix the base: a written, acknowledged complaint at the right station

File at the district Cyber Police Station (every revenue district in Kerala has one) or the station whose cyber cell covers the transaction. Hand over a signed representation with: NCRP/1930 numbers, crime-type (e.g., Telegram task scam, UPI phishing), transaction details with UTR/RRN, bank statement with disputed debits highlighted, screenshots with URLs/timestamps (preserved for Section 63 BSA), and a prayer for FIR under Section 173 BNSS where cognizable. Take a dated acknowledgement stamp. The written complaint is not a formality — it is the document later magistrates and SPs call for first.

Level 2 — Written escalation to the district head

If 2-3 weeks pass without FIR or meaningful action despite acknowledgement, send a written complaint to the District Police Chief (SP/Commissioner) under the supervisory chain recognised in Sakiri Vasu v. State of U.P., (2008) 2 SCC 409 — which treats inaction on a complaint as amenable to supervisory direction, and now maps to BNSS Chapter XIII supervision. Send by registered post + email, enclosing the NCRP number, the station’s acknowledgement, and the earlier complaint. Ask for: registration under Section 173 where cognizable, transfer to the district cyber cell where needed, and progress intimation under Section 193(3)(ii) BNSS (IO shall inform progress to informant/victim by any means including electronic communication).

Level 3 — CPGRAMS / State Police portal (supervisory, not judicial)

File a grievance on CPGRAMS (pgportal.gov.in) and the Kerala Police complaint portal citing the same numbers. CPGRAMS routes to the State nodal and creates a tracked timeline. Treat it as a parallel supervisory push, not an investigation trigger — it helps where the file is stuck between desks, not where FIR registration itself is refused after acknowledged disclosure of a cognizable offence.

Level 4 — Magistrate direction under Section 175(3) BNSS

Where registration or investigation is still refused despite acknowledged written disclosure of a cognizable offence, move the jurisdictional Magistrate (JMFC/ACJM where the victim resides or where part of the cause occurred, per Zero-FIR logic under Section 173(1) BNSS) for a direction under Section 175(3) BNSS (successor to Section 156(3) CrPC). The Court may:

• call for a status report from the SHO,
• direct registration and investigation where cognizable offence is disclosed,
• or, where the complaint discloses only a non-cognizable offence or the facts already constitute a complaint case, treat it as a complaint under Section 223 BNSS (old 200 CrPC) and proceed accordingly.

Attach the full chain: NCRP/1930 references → station acknowledgement → SP/CP representation with postal proof → CPGRAMS ID → preservation file. The petition’s strength is not drafting flair but proof that the police were given the chance to act and did not.

Scope note: Section 175(3) BNSS itself requires the application to be supported by an affidavit (made under Section 173(4)), and the Magistrate considers the police officer’s submission before ordering investigation. File the affidavit with documents; do not rely on an unsworn transmission.

What records actually move a file in Kerala practice?

The bundle that both a supervising SP and a Magistrate look for is the same:

1. Identifiers: NCRP acknowledgement, 1930 reference with date/time, FIR/complaint number if any, and the bank’s CFCFRMS lien/UTR numbers.
2. Money trail: Bank statement (highlight disputed debits), UPI transaction details with UTR, beneficiary name/UPI ID, and — for P2P or task-scam layers — the exchange/P2P order book (see crypto P2P guide) or task-app screenshots.
3. Evidence preserved for Section 63 BSA: Original-device exports with hash, not forwarded copies — hash + certificate will be needed if the case proceeds.
4. Chronology: Dates of NCRP, written complaint, acknowledgements, and escalation letters — a one-page dated timeline.

A repeated mistake is quoting only a cybercrime.gov.in ticket in escalation with no signed station complaint — the ticket is a routing number, not an FIR predicate.

What this escalation does not do

• It does not convert a civil debt recovery into a cyber crime. Where money was lent voluntarily and recovery is the real dispute, the FIR track is misused — use the civil or consumer route (how to respond to a legal notice; civil-consumer practice).
• It does not guarantee an arrest or immediate refund. Investigation and arrest follow the BNS/BNSS standards; the refund of lien-marked money is a separate Magistrate application under Sections 497-505 BNSS (see UPI fraud guide).

Primary sources

• BNSS, 2023 — Sections 173, 174, 175(3), 193, 35, 94, 503; BNS, 2023; IT Act — Sec 78
• Lalita Kumari v. Govt. of U.P., (2014) 2 SCC 1 (FIR mandatory for cognizable); Sakiri Vasu v. State of U.P., (2008) 2 SCC 409 (supervisory route)
• Satender Kumar Antil v. CBI line on Section 35/41A and physical service (21 Jan & 16 Jul 2025 orders; the 16 Jul 2025 order is 2025 INSC 909)
• I4C / NCRP at cybercrime.gov.in and 1930 helpline (Ministry of Home Affairs)
• BSA, 2023 — Section 63; Constitution — Articles 21, 226