Fraud response for banks
Once your bank is connected to the I4C's interface, ICCCC receives its fraud reports, guides your desk through the lookup, the lien and the reply, and keeps two officers on every decision that touches customer money.
Built around
ICCCC is a product of Picar. It connects to the published interface for banks of the I4C (Indian Cyber Crime Coordination Centre) and is not an I4C product.
The console
Reports, deadlines, liens and replies side by side. Shown here with sample data.
Report queue
Once your bank is connected, reports arrive around the clock. Each one starts its response clock the moment it lands, and shows who has to act next.
Two-officer approval
An officer proposes a lien; a different Approver confirms it. Nobody approves their own work.
Core banking lookup
Check the holder's details and record what was found, with the lookup itself on the record.
Audit trail
Every view of sensitive data, every proposal and every reply is written to an audit trail you can show.
Built around the I4C API for banks, for desks of a few people, in English and Hindi.
Once your bank is connected, receives fraud reports over the I4C interface, accepts every record and reports faults back, and sends status updates once your desk has acted.
Every report shows its deadline. Late work rises to the top of My tasks, and the home page shows what needs someone now.
Bank rules decide when a lien is suggested. An officer proposes it, an Approver confirms it, and the record says who, when and why.
Find the account behind a report, check the holder's details, and record what was found, with the lookup itself on the record.
Lien thresholds and where each kind of report goes are set in plain forms, in rupees and days, and changed only with a second person's approval.
Every screen your bank's staff use, including the system's own messages, in English or Hindi. Each person picks their language. Picar's own platform console is English only.
4
steps from report to reply
2
people on every money decision
3
clear roles for a small team
2
languages in the bank's console
How it works
Once your bank is connected, I4C sends the complaint. ICCCC accepts it, starts its clock and puts it in the queue.
The officer finds the account in core banking and records what was found.
If your rules say so, the officer proposes a lien and an Approver confirms it.
Once replies are switched on, the status goes back to I4C, and the whole case stays on the record.
Made for small teams
Fraud desk officer
Handles reports, looks up accounts, proposes liens and replies.
Approver
Approves liens, rule changes and switching replies to I4C on, with a code from a phone app.
IT administrator
Creates your bank's staff accounts, gives each a role, and manages the I4C connection. Cannot approve money decisions.
Security
Account numbers and personal details are encrypted, every look at them is recorded, and no single person can move customer money.
Sensitive fields are encrypted in the database and shown only on request, and the request is recorded.
Liens, rule changes and switching replies on each need a second person.
Every user signs in with a password and an authenticator app. No one at your bank can switch it off, and sessions end after inactivity.
A practice mode for testing, so nothing reaches I4C until your bank switches it on.
No. ICCCC runs as a hosted service. Your staff use it in a web browser at your bank's own address.
No. Liens and replies to I4C need two people from your bank. Picar's staff can stop sending if something goes wrong, but cannot start it or approve anything for you.
Account lookups can be recorded by hand from the start. Whether a direct connection to your core banking system is possible depends on that system; we will tell you plainly.
Yes. Every screen your bank's staff use is available in English and Hindi, and each person chooses their own. The platform console that Picar's operators use is English only.
Book a demo. We show the console with sample data and walk through a report from arrival to reply.
Tell us about your bank and we will set up a walk-through with sample data.