Payment Fraud Reporting Moves to DAKSH from Jan 1, 2023
Current · Source: Reserve Bank of India · RBI/2022-23/158 · issued 26 Dec 2022 · ~2 min read
Quick answerFrom January 1, 2023, all payment frauds must be reported via DAKSH instead of EDSP. Banks, NBFCs, and PSOs must use DAKSH's new features like maker-checker and online reporting. Historical EDSP data will be migrated later.
The rule, in the simplest words
From January 1, 2023, all payment frauds must be reported using DAKSH (a new online system) instead of the old EDSP system.
Banks, NBFCs (companies that give loans but are not banks), and PSOs (companies that handle payments like UPI or cards) must use DAKSH's new features like maker-checker (one person enters data, another checks it) and online reporting.
You cannot report new frauds on EDSP after January 1, 2023, but you can update or close old EDSP reports until December 31, 2022.
Report all payment frauds, even if the fraud didn't succeed (attempted), within 7 calendar days after the customer tells you or you find it yourself.
Before reporting a fraud to DAKSH, check the customer's claim in your own systems to make sure it is real and complete.
How it plays out — a real example
Ravi, a fraud analyst at a bank in Mumbai, gets a call from a customer saying someone used their debit card for a ₹5,000 online purchase they didn't make. Ravi first checks the bank's transaction logs to confirm the fraud is real, then logs into DAKSH on January 2, 2023, and reports the fraud using the online screen-based form, making sure to submit it within 7 days of the customer's call.
What changed
RBI has migrated the payment fraud reporting module from the Electronic Data Submission Portal (EDSP) to DAKSH, effective January 1, 2023. DAKSH offers additional functionalities such as maker-checker, online screen-based reporting, alerts, dashboards, and reports. Entities can no longer report new frauds via EDSP after this date, though they can update and close existing EDSP reports until December 31, 2022.
What it means for you
Banks and payment operators must adapt to DAKSH's interface and ensure compliance with the new reporting process. The enhanced features aim to streamline fraud management and improve efficiency. Historical data from EDSP will be migrated by RBI, so entities should focus on accurate and timely reporting in DAKSH.
What you must do
Ensure your team is trained on DAKSH's maker-checker and online reporting features before January 1, 2023.
Migrate all new payment fraud reports to DAKSH from January 1, 2023, and stop using EDSP for new reports.
Update and close any existing EDSP fraud reports by December 31, 2022, as per RBI timelines.
Validate customer-reported frauds in your systems before reporting to DAKSH, ensuring authenticity and completeness.
Report all payment frauds, including attempted ones, within 7 calendar days of detection or customer reporting.
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
What is DAKSH and why is it replacing EDSP?
DAKSH is RBI's Advanced Supervisory Monitoring System, designed to streamline and automate payment fraud reporting. It replaces EDSP to enhance efficiency with features like maker-checker, online reporting, and dashboards.
Can we still report frauds in EDSP after January 1, 2023?
No, new fraud reports must be filed in DAKSH from January 1, 2023. However, you can update and close frauds that were already reported in EDSP until December 31, 2022.
What are the reporting timelines for payment frauds under DAKSH?
Entities must report payment frauds within 7 calendar days from the date of customer reporting or detection by the entity, as per existing guidelines.
📜 Read the original circular — full text as issued by RBI
RBI/2022-23/158
CO.DPSS.OVRST.No.S1619/06-08-005/2022-2023
December 26, 2022
The Chairman / Managing Director / Chief Executive Officer
Banks, Non-bank Payment System Operators (PSOs) and
Credit Card issuing Non-Banking Financial Companies (NBFCs)
Madam / Dear Sir,
Central Payments Fraud Information Registry – Migration of Reporting to DAKSH
As announced in the Monetary Policy Statement 2019-20 on August 07, 2019 , the Reserve Bank of India (RBI) had operationalised the Central Payments Fraud Information Registry (CPFIR) in March 2020 with reporting of payment frauds by scheduled commercial banks and non-bank Prepaid Payment Instrument (PPI) issuers.
2. To streamline reporting, enhance efficiency and automate the payments fraud management process, the fraud reporting module is being migrated to DAKSH – Reserve Bank’s Advanced Supervisory Monitoring System . The migration will be effective from January 01, 2023 , i.e., entities shall commence reporting of payment frauds in DAKSH from this date. In addition to the existing bulk upload facility to report payment frauds, DAKSH provides additional functionalities, viz. maker-checker facility, online screen-based reporting, option for requesting additional information, facility to issue alerts / advisories, generation of dashboards and reports, etc. The reporting guidelines are mentioned in the Annex .
3. These directions are issued under Section 10 (2) read with Section 18 of Payment and settlement Systems Act, 2007 (Act 51 of 2007).
Yours faithfully,
(P. Vasudevan)
Chief General Manager
(Annex to Circular CO.DPSS.OVRST.No.S1619/06-08-005/2022-2023 dated December 26, 2022)
Annex
CPFIR – Reporting Guidelines
All RBI authorised Payment System Operators (PSOs) / providers and payment system participants operating in India are required to report all payment frauds, including attempted incidents, irrespective of value, either reported by their customers or detected by the entities themselves. This reporting was earlier facilitated through Electronic Data Submission Portal (EDSP) and is being migrated to DAKSH.
The responsibility to submit the reported payment fraud transactions shall be of the issuer bank / PPI issuer / credit card issuing NBFCs, whose issued payment instrument has been used in the fraud.
Entities are required to validate the payment fraud information reported by the customer in their own systems to ensure the authenticity and completeness, before reporting the same to RBI on individual transaction basis.
Entities are required to report payment frauds (domestic and international) to CPFIR as per the specified timelines (currently within 7 calendar days from date of reporting by customer / date of detection by the entity).
Entities may continue to report payment frauds as per the extant reporting format using the bulk upload facility in DAKSH or report individual payment frauds online using the screen-based facility under the Incident Module of the DAKSH platform.
After go-live of payment fraud reporting in DAKSH effective January 01, 2023, entities shall not be able to report any payment frauds in EDSP. Entities may, however, continue to update and close payment frauds that were reported in EDSP until December 31, 2022. Reserve Bank shall subsequently migrate the historical data from EDSP to DAKSH.
The reporting format remains unchanged ( Appendix ).
Though some elements / fields of the Reporting Format are indicated as ‘Optional’, entities shall strive to include them as part of initial reporting itself and only in exceptional cases be reported as updates.
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2022-23/158 · issued 26 Dec 2022. The plain-English explanation above is BankPulse’s own independent summary.
Validate customer-reported frauds in your systems before reporting to DAKSH, ensuring authenticity and completeness.
📜 Compliance
Ensure your team is trained on DAKSH's maker-checker and online reporting features before January 1, 2023.
Migrate all new payment fraud reports to DAKSH from January 1, 2023, and stop using EDSP for new reports.
Update and close any existing EDSP fraud reports by December 31, 2022, as per RBI timelines.
Report all payment frauds, including attempted ones, within 7 calendar days of detection or customer reporting.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are a Compliance officer at a bank this circular applies to (Scheduled commercial banks, Non-bank Payment System Operators (PSOs), Credit card issuing Non-Banking Financial Companies (NBFCs), Non-bank Prepaid Payment Instrument (PPI) issuers), your first concrete step on “Payment Fraud Reporting Moves to DAKSH from Jan 1, 2023” is: “Ensure your team is trained on DAKSH's maker-checker and online reporting features before January 1, 2023.” (RBI issued this 26 Dec 2022).
Circular: RBI/2022-23/158 -- Payment Fraud Reporting Moves to DAKSH from Jan 1, 2023
Issued: 26 Dec 2022
Action required: Ensure your team is trained on DAKSH's maker-checker and online reporting features before January 1, 2023.
Action required: Migrate all new payment fraud reports to DAKSH from January 1, 2023, and stop using EDSP for new reports.
Action required: Update and close any existing EDSP fraud reports by December 31, 2022, as per RBI timelines.
Action required: Validate customer-reported frauds in your systems before reporting to DAKSH, ensuring authenticity and completeness.
Action required: Report all payment frauds, including attempted ones, within 7 calendar days of detection or customer reporting.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 03 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=12431&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.