RBI Rules on Dormant Accounts

By
5 Mins

RBI Rules on Dormant Accounts

Across India, a significant amount of money lies untouched in bank accounts not because it was forgotten forever, but because the account holders stopped operating them. These unclaimed bank deposits arise when savings accounts, current accounts, or fixed deposits remain inactive for extended periods.

To safeguard depositors’ interests and maintain transparency, the Reserve Bank of India (RBI) has laid down clear rules on how banks must classify, manage, and disclose such accounts while ensuring that depositors or their legal heirs can reclaim their money at any time.

 

What Are Unclaimed Bank Deposits?

Unclaimed bank deposits are balances in bank accounts that have seen no customer-initiated transactions for a continuous period of 10 years.

These deposits typically include:

  • Savings and current account balances
  • Fixed deposits that have matured but not been claimed
  • Interest accrued on such deposits

Once this threshold is crossed, banks are required to transfer the funds to a central pool, while maintaining detailed records of the original owners.

 

Inactive vs Dormant Accounts: What’s the Difference?

RBI distinguishes between two stages of inactivity:

1. Inactive Account

An account is considered inactive if there are no customer-initiated transactions for 2 consecutive years.

2. Dormant Account

An account becomes dormant after 2 years of inactivity, triggering:

  • Enhanced monitoring
  • Restrictions to prevent misuse
  • Mandatory customer re-verification before reactivation

Dormant accounts are closely tracked due to their higher vulnerability to fraud and misuse.

 

RBI Rules Governing Unclaimed Deposits

The RBI mandates banks to:

  • Identify inactive and dormant accounts periodically
  • Attempt to contact account holders using available details
  • Publish details of unclaimed deposits on bank websites
  • Transfer eligible deposits to the Depositor Education and Awareness Fund (DEAF) after 10 years

Despite the transfer, banks remain responsible for processing claims and returning funds to rightful owners.

 

What Is the Depositor Education and Awareness Fund (DEAF)?

The DEAF is a fund established under RBI directions to house unclaimed bank deposits.

Key points:

  • Banks transfer eligible unclaimed balances to DEAF
  • Funds remain claimable at all times
  • Interest continues to accrue as per RBI guidelines
  • Banks must honour valid claims even after transfer

The purpose of DEAF is custodianship not confiscation.

 

Why Do Bank Deposits Go Unclaimed?

Unclaimed deposits are often the result of long-term data and identity gaps, including:

  • Change in address or contact information
  • Death of account holder without nominee updates
  • Multiple bank relationships across years
  • Forgotten fixed deposits
  • Poor awareness among legal heirs

In many cases, families are unaware that such accounts even exist.

 

How to Check for Unclaimed Bank Deposits

Individuals or heirs can check for unclaimed deposits by:

  • Visiting bank websites that publish unclaimed deposit lists
  • Using RBI-mandated centralized search facilities
  • Contacting the branch where the account was held

Basic details such as name, last known address, and branch are usually sufficient to begin the search.

 

How to Claim Unclaimed Bank Deposits

The claim process generally involves:

Step 1: Submit a Claim Request

Approach the concerned bank branch with:

  • Valid identity proof
  • Account details (if available)

Step 2: Verification

Banks conduct:

  • Identity verification
  • KYC revalidation
  • Legal heir verification (if applicable)

Step 3: Settlement

Once verified:

  • Funds are released to the claimant
  • Interest is paid as per applicable rules

There is no deadline for making a legitimate claim.

 

Claiming Unclaimed Deposits as a Legal Heir

Legal heirs may need to provide:

  • Death certificate of the account holder
  • Proof of relationship
  • Succession certificate or legal heir certificate (in certain cases)

Banks follow due diligence to ensure funds reach the rightful claimant.

 

Why Dormant Accounts Pose a Risk for Banks

From a systemic perspective, dormant and unclaimed accounts increase:

  • Fraud exposure
  • Compliance burden
  • Reconciliation challenges
  • Identity mismatches across financial systems

This is why RBI places strong emphasis on continuous customer identification and record accuracy.

 

The Bigger Picture: Unclaimed Deposits as an Identity Challenge

Unclaimed bank deposits highlight a larger issue fragmented identity records over time.

When identity, contact details, and nominee information are not consistently maintained across institutions, accounts drift into dormancy. Preventing unclaimed deposits requires:

  • Strong identity verification
  • Periodic data updates
  • Better continuity across financial relationships

This is where modern digital public infrastructure plays a critical role.

Conclusion

Unclaimed bank deposits are not lost, but the result of inactivity and gaps in identity or nominee records. While RBI safeguards ensure these funds remain claimable, preventing dormancy depends on timely updates, strong identity verification, and continuity in banking relationships.

FAQs

No items found.
Verified
Build Frictionless
Customer Journeys
Get Started

Related Posts

View All
5 Mins

GDPR vs DPDPA: What Indian Businesses Need to Know

GDPR vs DPDPA: What Indian Businesses Need to Know  

Introduction

With the enforcement of the Digital Personal Data Protection Act (DPDPA) in India, businesses are facing a major shift in how they handle user data. While many are already familiar with the General Data Protection Regulation (GDPR) from the European Union, the Indian DPDPA brings a localized set of expectations that require careful alignment.

If your business operates online, handles user data, or targets customers in India, understanding the similarities and differences between GDPR and DPDPA is crucial to avoid non-compliance penalties and maintain user trust.

What Is GDPR and What Is DPDPA?

GDPR (General Data Protection Regulation) is a comprehensive data privacy regulation that governs the use of personal data of EU citizens. Enforced since 2018, it applies to any organisation inside or outside Europe that processes EU user data.

DPDPA (Digital Personal Data Protection Act, 2023) is India’s data protection law designed to address the digital privacy needs of Indian citizens. While inspired by GDPR, it focuses on Indian legal, social, and operational contexts.

Key Similarities

Both regulations are built on similar privacy principles such as lawful and fair data processing, data minimization, purpose limitation, and user consent. They also emphasize the importance of transparency, giving users access to their data, and ensuring organisations implement strong data security measures.

Important Differences Between GDPR and DPDPA

Despite similarities, there are critical differences businesses must understand:

  • Scope and Applicability: GDPR applies globally to any entity handling EU citizen data, while DPDPA primarily applies to entities processing digital personal data of Indian citizens.
  • Consent: Both require clear and informed consent, but DPDPA introduces the concept of “deemed consent” allowing processing in certain legitimate contexts without explicit permission, such as for employment or public interest.
  • Age of Consent: GDPR sets the age of consent at 16 (with member states allowed to lower it to 13), whereas DPDPA fixes it at 18 across the board.
  • Regulatory Authority: GDPR is enforced by individual Data Protection Authorities (DPAs) in each EU country. DPDPA will be enforced centrally by the Data Protection Board of India.
  • Cross-Border Transfers: GDPR permits data transfers to countries with “adequate” privacy protections. DPDPA allows transfers to countries notified by the Indian government a more discretionary mechanism.
  • Penalties: GDPR can fine up to €20 million or 4% of global turnover. DPDPA fines can go up to ₹250 crore, making it one of the strictest regimes in the APAC region.
  • Data Subject Rights: GDPR grants broad rights including data portability and objection to processing. DPDPA offers rights like access, correction, erasure, and grievance redressal with some differences in implementation detail.

Why GDPR-Compliant Doesn’t Mean DPDPA-Compliant

Many businesses assume that GDPR compliance gives them automatic coverage under DPDPA. But DPDPA’s specific provisions like deemed consent, age requirements, and regional enforcement require a separate layer of localization.

Compliance with GDPR is a strong foundation, but not a full solution for Indian legal obligations.

How Blutic Helps You Navigate Both

Blutic is built to handle both GDPR and DPDPA compliance through a unified, region-aware platform. It helps businesses:

  • Show location-based cookie consent banners
  • Categorize cookies clearly with opt-in controls
  • Record and store user preferences with timestamps
  • Offer granular consent management for specific data purposes
  • Integrate with tools like Google Tag Manager, Shopify, and WordPress
  • Maintain consent logs for audit readiness

Whether you're an Indian business expanding to Europe or a global company entering India, Blutic ensures you're compliant, user-friendly, and future-proof.

India’s DPDPA reflects a maturing digital landscape, demanding accountability from businesses handling personal data. While it borrows foundational elements from GDPR, it introduces its own framework and enforcement style. Understanding these differences and acting early is the key to risk-free, trust-centric operations.

Blutic helps Indian businesses confidently navigate this evolving space by simplifying compliance without compromising user experience.

5 Mins

How Fintechs Can Reduce KYC Onboarding Drop-Off Caused by Form Fatigue

Why KYC Onboarding Still Struggles to Convert

In fintech onboarding, intent is rarely the issue. Users begin the journey willing to complete identity verification, yet a significant number never reach the end. Industry-wide, KYC and identity verification stages consistently see the highest abandonment especially when users are required to manually enter the same information multiple times across forms and document uploads. User patience hasn’t decreased. Expectations have increased.

The Cost of Form Fatigue in Fintech Onboarding

Repetitive onboarding flows introduce friction at the most sensitive stage of the user journey.

This typically shows up as:

  • Long forms asking for identity and address details  
  • Document uploads that repeat already-entered information  
  • Multiple steps validating the same data  

Each repetition adds effort. Each added step increases the likelihood of drop-off.

For businesses, this friction results in:

  • Higher acquisition costs with lower activation rates  
  • Delayed customer onboarding  
  • Increased operational effort to follow up on incomplete applications  

Form fatigue affects both conversion and efficiency.

Why This Problem Exists Across the Industry

Many onboarding systems were designed around verification completeness, not user effort minimisation.

As a result:

  • Data capture and verification operate as separate stages  
  • Document uploads don’t meaningfully reduce form length  
  • Users are asked to provide the same information in different formats  

When verification workflows are layered on top of forms instead of integrated into them, redundancy becomes visible—and frustrating.

What Efficient Onboarding Looks Like

Effective onboarding follows a simple principle:
Do not ask users to manually enter information that already exists in a verifiable form.

Instead:

  • Verified data is reused within the onboarding flow  
  • Forms are shortened wherever possible  
  • Users confirm details rather than re-enter them  

This keeps onboarding focused on validation, not repetition.

How ProfileX Supports This Approach

ProfileX, built by Neokred, supports onboarding flows where verified data is used to reduce unnecessary manual input.

ProfileX enables:

  • Real-time verification of identity and address  
  • Support for both individual (KYC) and business (KYB) onboarding  
  • Validation of company registrations, tax IDs, licenses, and regulatory documents  

The emphasis is on reducing redundant user effort while maintaining structured verification processes.

Automation Without Disrupting the User Journey

ProfileX supports automated KYC and KYB processes through configurable workflows that reduce manual intervention.

This helps:

  • Maintain onboarding continuity  
  • Limit repeated user actions  
  • Keep the experience consistent across channels  

Automation is applied to simplify the flow not to add complexity.

Fraud and Risk Signals During Onboarding

Onboarding is also a critical point for early risk detection.

ProfileX includes fraud and risk signaling using device intelligence, which:

  • Analyses device behaviour during user interaction  
  • Identifies anomalies such as emulators, bots, or tampered devices  
  • Detects multiple accounts associated with the same device  

These signals integrate into existing risk workflows and operate without interrupting genuine users.

Reducing Drop-Off Starts with Removing Repetition

Onboarding failures are rarely caused by lack of intent. They are more often caused by users being asked to repeat themselves.

By shortening forms, reusing verified data, and integrating verification directly into the flow, fintechs can reduce onboarding drop-offs without weakening compliance requirements.

What to Review in Your Onboarding Flow

If drop-offs consistently occur midway through onboarding, it’s usually a process signal.

Look for:

  • Fields users have already provided elsewhere  
  • Uploads that don’t reduce manual effort  
  • Steps that validate the same data twice  

That’s where friction starts and where improvement has the most impact.

5 Mins

Why Soundbox Devices Are Becoming Essential for Indian Merchants

Why Soundbox Devices Are Becoming Essential for Indian Merchants

India’s digital payments scale has exposed a gap that software alone cannot solve: real-time, unambiguous payment confirmation at the physical point of sale. Soundbox devices have emerged not as accessories, but as operational infrastructure for merchants handling high-frequency UPI transactions.

The Real Problem Soundboxes Solve: Payment Ambiguity at Scale

UPI works exceptionally well at the system level. The friction appears at the merchant execution layer.

In busy retail environments, merchants deal with:

  • Simultaneous customers
  • Multiple payment apps
  • Network latency or delayed app notifications
  • Human error during verification

The result is payment ambiguity situations where a customer claims success, but the merchant cannot instantly verify receipt. Soundbox devices eliminate this ambiguity by becoming a single source of truth at the counter.

Why Smartphone-Based Verification Fails in Real-World Conditions

Most merchant apps assume ideal conditions: one device, one transaction, one operator. Indian retail rarely works this way.

Operational limitations include:

  • Shared phones across staff
  • Battery drain and device downtime
  • Notification overload
  • App switching delays during peak hours

Soundboxes offload payment confirmation from smartphones to dedicated hardware, improving reliability without adding complexity.

Impact on Transaction Throughput and Queue Economics

In high-volume environments, even a 2–3 second delay per transaction compounds quickly.

Soundbox devices:

  • Remove the need for manual checks
  • Enable continuous transaction flow
  • Reduce verbal confirmation loops with customers

For merchants processing hundreds of payments daily, this translates to:

  • Shorter queues
  • Higher throughput
  • Better staff productivity

This operational efficiency directly affects revenue during peak periods.

Dispute Reduction and Operational Risk Control

UPI disputes are rarely about fraud they are about timing, visibility, and confirmation.

Soundbox devices help reduce:

  • “Paid but not received” arguments
  • Accidental double payments
  • Missed transactions during rush hours

By announcing only confirmed credits, soundboxes introduce determinism into an otherwise probabilistic verification process.

Trust Signaling in Semi-Formal Retail Environments

In many Indian retail settings, trust is built in real time.

Audio confirmation:

  • Signals transaction success to both parties
  • Reduces dependency on visual proof
  • Reinforces merchant legitimacy

This is particularly important in:

  • Cash-heavy neighborhoods
  • First-time digital payment users
  • Tier-2 and tier-3 markets

Soundboxes quietly reinforce confidence in digital payments without requiring user education.

Integration with POS, QR, and Merchant Workflows

Modern soundbox deployments are no longer standalone.

They are increasingly:

  • Linked to dynamic QR systems
  • Integrated with POS terminals
  • Synced with merchant dashboards and settlement systems

This integration ensures consistency across:

  • Payment modes
  • Transaction records
  • End-of-day reconciliation

Soundboxes are becoming part of a cohesive merchant payments stack, not an isolated device.

Uptime, Connectivity, and Hardware Dependability

In payments, reliability is not a feature — it is a baseline requirement.

Soundbox devices are designed for:

  • Continuous power availability
  • Low-bandwidth connectivity
  • Always-on operation

This makes them more dependable than consumer smartphones in retail environments, especially during long operating hours.

Soundboxes as Enablers of Merchant Digitization

Beyond confirmation, soundbox adoption has second-order effects:

  • Encourages full digital acceptance
  • Reduces cash handling
  • Creates cleaner transaction records
  • Supports future credit and analytics use cases

For small merchants, soundboxes act as a gateway device into structured digital commerce.

Strategic Importance in India’s Payment Infrastructure

India’s payment growth is not constrained by consumer adoption it is constrained by merchant-side execution.

Soundbox devices solve a uniquely Indian problem:

  • Extremely high UPI volume
  • Highly fragmented merchant base
  • Real-world retail constraints

This is why soundboxes have moved from optional add-ons to core infrastructure.

Soundbox devices are not about convenience. They are about clarity, speed, and operational certainty at the moment money changes hands.

For Indian merchants operating at scale, soundboxes are no longer a nice-to-have — they are becoming essential to running digital-first commerce reliably.

Ready to take your customer experience and product to next level with Neokred