Law / India

RBI NBFC Account Aggregator Directions, Consent and Sharing of Financial Information

RBI (Non-Banking Financial Companies - Account Aggregator) Directions, 2025, paras. 14, 15, 20, 22, 28 and 30

In force since .

A data subject rights rule binding private bodies.

Private right of action
No
Instrument type
a binding direction issued under an act
Obligation class
Consent, Data subject rights

What it requires

  • This binds a non-banking financial company undertaking the business of an Account Aggregator, a Financial Information Provider (a bank, non-banking financial company, asset management company, depository, insurance company or another entity the definition names) and a Financial Information User, an entity regulated by a financial sector regulator (reached by declaring that you hold a financial-services licence).
  • If you are an Account Aggregator, provide services only on the customer's explicit consent and retrieve, share or transfer no financial information of the customer without it (paragraphs 14(1) and 15).
  • If you are an Account Aggregator, obtain consent through a standardised consent artefact that states the customer's identity, the nature of the information, the purpose, the recipients and the expiry date, and tell the customer of those attributes and of the right to complain when you obtain consent (paragraphs 17 and 19).
  • If you are an Account Aggregator, give customers a functionality to revoke consent, including consent to obtain parts of the information, and share a fresh consent artefact with the Financial Information Provider on revocation (paragraph 20).
  • If you are a Financial Information Provider, share the customer's financial information with the Account Aggregator on being presented a valid consent artefact, after verifying the validity of consent, the specified dates and usage and the Account Aggregator's credentials, digitally signing the information and keeping a log of the requests (paragraphs 22 to 26).
  • If you are an Account Aggregator or a Financial Information User, use or disclose the financial information only as the consent artefact specifies, and let no financial information accessed from the providers reside with the Account Aggregator (paragraphs 14(7) and 28).
  • If you are an Account Aggregator, do not request or store the customer credentials used to authenticate the customer to the Financial Information Providers (paragraph 30(2)).

These lines are LexLint's reading of the law's text.

Who enforces it

Enforcement body

The Reserve Bank of India, which issues these Directions under section 45JA of the Reserve Bank of India Act, 1934.

Settledness

As of

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Paragraph 3 applies the Directions to non-banking financial companies undertaking the business of an Account Aggregator. Paragraph 14(1) requires an Account Aggregator to provide services to a customer based on the customer's explicit consent. Paragraph 15 bars an Account Aggregator from retrieving, sharing or transferring a customer's financial information without the customer's explicit consent.

Paragraph 20 requires an Account Aggregator to give its customers a functionality to revoke consent, including consent to obtain parts of the information. Paragraph 22 requires a Financial Information Provider to share a customer's financial information with an Account Aggregator on being presented a valid consent artefact. Paragraph 28 bars an Account Aggregator and a Financial Information User from using or disclosing the financial information except as the consent artefact specifies.

Paragraph 14(7) provides that no financial information accessed from the financial information providers shall reside with the Account Aggregator. Paragraph 30(2) bars an Account Aggregator from requesting or storing the customer credentials used to authenticate the customer to the Financial Information Providers. Paragraph 2 brings the Directions into force on the day they were placed on the website of the Reserve Bank.

When LexLint raises it

When your app profile says your app provides financial services.

Back to the example  ·  Lint your app

Page updated .