RBI proposes standardised cyber-fraud account holds for banks
RBI’s draft framework would standardise transaction-specific debit holds, monitoring and grievance redressal for cyber-fraud-linked accounts. It proposes a 60-day cap on temporary holds without a statutory order, with public comments due October 2 and implementation scheduled from April 1, 2027.
What happened
Reserve Bank of India · RBI has proposed uniform bank procedures for cyber-fraud-linked accounts, including AI-based monitoring, transaction-specific debit
Key facts
- ₹1,000 minimum suspected mule transaction threshold
- 60-day maximum temporary debit-hold duration without statutory order
- 20-day window for account holder explanation
- 10-day bank review period
- 30-day escalation window to law enforcement
- 30-day grievance-resolution requirement
- ₹22,495 crore cyber-fraud losses in 2025
- ₹22,845 crore cyber-fraud losses in 2024
- 7.1% suspected fraud rate in attempted Indian digital consumer transactions in 2025
- 3.8% equivalent global suspected fraud rate
- ₹50,000 customer-loss threshold for compensation
- 85% of net loss or ₹25,000 maximum compensation, whichever is lower
Why this matters
Fintech and payments platforms with fraud monitoring, case management and customer-support capabilities may become more valuable partners as banks upgrade for standardised hold and redressal requirements.
What to watch
- RBI’s final framework language after the October 2 consultation deadline, particularly scope across banks, payment aggregators, wallets and UPI-linked accounts.
- Clarification of what constitutes a statutory order and the operational process at the 60-day hold expiry.
- Mandated timelines for notifying customers, reviewing holds and resolving grievances.
- Whether RBI requires interoperable fraud-reporting and case-reference standards across banks and cybercrime agencies.
- Bank announcements of new fraud-monitoring rules, merchant payout restrictions or revised payment-partner contracts.
- Changes in payment-failure rates, refund-cycle times, seller settlement delays and COD share in high-risk customer cohorts.
- Any rise in consumer complaints or litigation related to wrongful freezes and delayed access to funds.
- Map exposure to bank-initiated debit holds across refunds, seller settlements, wallet top-ups, subscriptions and marketplace payouts.
- Require payment partners to provide hold reason codes, real-time status APIs, escalation SLAs and documented customer-redress workflows.
- Build customer messaging for fraud-related payment failures that distinguishes a bank hold from merchant-side cancellation or refund delay.
- Create alternate payment and payout paths for affected customers and sellers, including UPI retry flows, secondary bank-account verification and controlled COD options.
- Stress-test peak-event operations for elevated payment retries, delayed seller withdrawals and contact-centre volumes.
- Review fraud-loss and chargeback policies so merchants are not absorbing losses or penalties when regulated holds delay fulfilment or refunds.