Q-Cyber Magazine
India's Account Aggregator framework: Consent as a control
RBI's Account Aggregator directions make the aggregator a consent-bound conduit: it may not treat customer financial information as its property, and it may not store the credentials used to reach financial information providers.

India's Account Aggregator system is sometimes described as open finance. The legal design is narrower and more interesting: a licensed conduit that may retrieve and present financial information, but only with the customer's consent, and never as the owner of that information.
A conduit, not a new data lake
The directions are built on a refusal. The aggregator exists to move information that already belongs to the customer, at the customer's request, to the customer or to a user the customer has authorised. It does not acquire the information as an asset. It may not use or access customer information except to perform the aggregator business the customer has explicitly requested.
That rule is reinforced by a credential ban. The aggregator may not ask for, or keep, the passwords, PINs or private keys that would allow it to authenticate to a financial information provider as if it were the customer. Access is to be based on consent-based authorisation. The customer must also be able to see a record of the consents given and of the financial information users with whom information has been shared.
These are security and privacy controls written as licensing conditions. They are also a design pattern that other data-sharing arrangements in India, including under the DPDP framework, will be measured against: purpose-specific consent, no secondary use, no standing credential, and an auditable record.
Exhibit 1
Core legal constraints on an NBFC Account Aggregator
| Constraint | What the directions require |
|---|---|
| Legal instrument | Master Direction DNBR.PD.009/03.10.119/2016-17, 2 September 2016, updated 6 September 2024 |
| Permitted business | Retrieve or collect specified financial information; consolidate, organise and present it to the customer or a specified financial information user |
| Ownership of data | Customer financial information shall not be the property of the Account Aggregator and shall not be used in any other manner |
| Credentials | The aggregator shall not request or store customer credentials such as passwords, PINs or private keys |
| Basis of access | Consent-based authorisation only |
| Customer visibility | The customer shall be able to access a record of consents and of the users with whom information has been shared |
| Use limitation | No use or access of customer information except to perform the aggregator business explicitly requested by the customer |
| Regulatory layer | An NBFC Account Aggregator remains in the Base Layer of RBI's scale-based structure |
Source: Reserve Bank of India, Master Direction – Non-Banking Financial Company – Account Aggregator (Reserve Bank) Directions, 2016, updated 6 September 2024.
What fintech builders should take from the design
Product teams sometimes treat consent as a screen the user ticks once. The directions require something closer to a control system: a consent that can be recorded, reviewed and, in the framework's wider practice, withdrawn; a technical path that does not depend on borrowed passwords; and a business model that does not rely on quietly reusing the data. When those conditions are met, the aggregator can be a useful pipe. When they are not, it is simply another holder of sensitive financial data, which is the outcome the licence was written to prevent.
Implications
- Design for consent artefacts, not standing credentials.
- Prohibit secondary use in both policy and engineering, including analytics that the customer did not request.
- Give customers a complete consent history, including downstream users.
- Assume DPDP duties sit alongside the licence when personal data is processed.
What this means for fintech
The Account Aggregator framework is one of India's most precise public designs for data sharing. Firms that copy its constraints — consent, no credential reuse, no silent secondary use — will be building on a standard the regulator has already written, rather than inventing a weaker one.


