RBI Plans Account Aggregator Interoperability and Bank Deposits in CAS

By The Indus Pulse Editorial TeamUpdated 3 min read
AI-generated editorial illustration
AI IllustrationCreated for The Indus Pulse with AI tools
⚠️For informational purposes only; not investment advice.

The Reserve Bank of India announced measures in October 2026 to improve the way consumers view and share financial information. The plans include interoperability between registered account aggregators and the inclusion of bank-deposit information in consolidated account statements, which have traditionally focused on securities and mutual funds.

Two changes with different purposes

An account aggregator is a consent-based system through which a customer authorises a regulated institution to share financial data with another permitted recipient. Interoperability aims to reduce fragmentation between aggregator platforms. Expanding the consolidated account statement would instead give consumers a clearer view of balances across types of assets. Neither change authorises unrestricted harvesting of personal financial information.

Implementation questions

Reporting on the RBI announcement points to December 31, 2026, as a target for the interoperability framework. Actual consumer functionality will depend on institutional integration, standards and the choices offered in consent requests. Greater visibility may help families locate forgotten assets and lenders assess borrowers, but it also makes purpose limitation, data security and revocable consent particularly important. Readers should distinguish an announced rollout from a service already available at every bank.

A practical example of the account-aggregator model

Under the consent-based account-aggregator framework, a customer can authorise a regulated financial information provider to share specified data with a regulated user for an agreed purpose. The intermediary facilitates the exchange under the applicable framework; it is not meant to become a free-standing seller of account histories. Consent requests should identify the type of data, duration and purpose, and customers need a way to revoke ongoing permissions.

Interoperability could make these permissions less dependent on which aggregator a bank or service provider uses. But common technical standards, participant readiness and secure authentication determine when that benefit becomes available. Without those conditions, an announcement can precede actual functionality for many customers. Bank-deposit visibility in a consolidated statement solves a different problem: helping savers see holdings that were previously fragmented across securities and banking interfaces.

What users should scrutinise

A more complete financial view can aid budgeting, estate preparation or loan applications, but it can also create richer targets for identity theft if accounts and access are poorly protected. Consumers should check the recipient's identity, the minimum data necessary and the duration of consent instead of accepting blanket permission requests. Rollout timelines need dated RBI or industry documentation. Readers should also distinguish information-sharing consent from consent for a debit or payment: access to data does not automatically authorise money transfers.

The Indus Pulse is committed to accuracy and transparency.
Report a CorrectionEditorial Standards