Home › Dashboards › Account Aggregator (AA)
Account Aggregator (AA) framework — India’s consent-based financial-data-sharing rail
IndicativeFigures on this page are indicative and pending expert verification by Vikram Jain (CA) — not yet admitted to the BankPulse Verified-numbers ledger.
Quick answerThe Account Aggregator (AA) framework lets a customer share their financial data — with explicit, revocable consent — from the institution that holds it (a Financial Information Provider, FIP) to the one that needs it (a Financial Information User, FIU) through an RBI-licensed, data-blind NBFC-Account Aggregator. The AA moves encrypted data but cannot read, store or use it, and the customer is never charged. Created by the RBI’s Master Direction — NBFC-Account Aggregator (Reserve Bank) Directions, 2016 and live since September 2021, the ecosystem now spans roughly 14-16 operational AAs and, on an indicative basis, around 1 billion accounts enabled. Figures are rounded, approximate and indicative.
The chart shows the indicative growth of accounts enabled and cumulative successful consents on the AA rail since 2022. The table below carries the same figures so the page is readable without JavaScript — for accessibility and AI answer engines.
AA adoption (indicative), by period
| As of | Accounts enabled (approx.) | Cumulative consents | Note |
| Mar 2022 | ~5 cr | ~0.4 cr | Early roll-out after the September 2021 go-live with eight banks as the first FIPs |
| Mar 2023 | ~30 cr | ~2 cr | More banks and NBFCs join as Financial Information Providers; lending use-cases scale |
| Mar 2024 | ~100 cr | ~8 cr | Accounts enabled approach ~1 billion; GSTN onboarded as an FIP widens MSME-credit use |
| Sep 2024 | ~115 cr | ~12 cr | Continued growth across banking, securities and insurance data |
| Mar 2025 | ~130 cr | ~16 cr | Indicative / provisional — adoption keeps climbing (pending confirmation) |
All figures are rounded, approximate and indicative; the latest period is provisional. None of these figures is in the BankPulse Verified-numbers ledger pending reviewer sign-off. For exact, current figures see the source linked below.
Ecosystem at a glance (latest, approximate)
| Metric | Value | What it means |
| Operational NBFC-AAs | ~14-16 | RBI-licensed Account Aggregators in operation — each holding a Certificate of Registration as an NBFC-AA |
| Accounts enabled | ~1 billion+ | Cumulative bank / financial accounts discoverable for consent-based sharing across the ecosystem (indicative) |
| Cumulative successful consents | tens of millions | Consent requests fulfilled end-to-end since go-live — growing fast (indicative) |
| FIP / FIU participants | hundreds | Banks, NBFCs, insurers, mutual funds, pension funds and GSTN as data providers; lenders and advisers as data users |
| Cost to the customer | Free | The customer is never charged for sharing data through an AA; consent is explicit and revocable |
| Data handling | Data-blind | The AA transmits encrypted data but cannot read, store or use it — a pure consent intermediary |
Values are rounded and approximate and not in the Verified-numbers ledger pending reviewer sign-off.
The AA framework (RBI)
What the RBI’s framework sets up — the licence, the consent architecture and the data-blind design that make the rail safe and interoperable.
| Element | What it is | Detail |
| Master Direction | NBFC-AA Directions, 2016 | RBI’s Master Direction — Non-Banking Financial Company — Account Aggregator (Reserve Bank) Directions, 2016, issued 2 September 2016, created the AA licence |
| Licence / registration | NBFC-AA CoR | An AA must hold a Certificate of Registration from the RBI as an NBFC-Account Aggregator and meet the prescribed net-owned-fund and fit-and-proper conditions |
| Consent architecture | Explicit, revocable | Data moves only on the customer’s electronic consent artefact specifying the FIU, data types, purpose, duration and frequency — and can be revoked at any time |
| Data-blind role | No read / no store | The AA cannot see the data it routes: it is encrypted end-to-end between FIP and FIU, and the AA only manages consent and the data pipe |
| Technical standards | ReBIT / Sahamati | Common API and data-format standards (ReBIT-defined) with ecosystem coordination by the Sahamati collective make all participants interoperable |
| Regulator coordination | FSDC (RBI / SEBI / IRDAI / PFRDA) | A cross-regulator framework so banking, securities, insurance and pension data can flow under one consent rail |
How a consent flowsA customer with a loan application gives the lender (the FIU) consent through an AA app to fetch, say, six months of bank-statement data from their bank (the FIP). The AA presents a consent artefact naming the FIU, the exact data, the purpose, the duration and the frequency; on the customer’s approval the FIP sends the data encrypted straight to the FIU through the AA, which never sees it. The customer can revoke the consent later. It replaces sharing PDFs, passwords or screen-scraping with a single, auditable, consent-first rail.
The four roles & the consent artefact
Who is who in an AA data flow.
| Role | Detail |
| Account Aggregator (AA) | The RBI-licensed, data-blind consent intermediary that retrieves data from FIPs and delivers it to FIUs strictly on the customer’s consent |
| Financial Information Provider (FIP) | The data holder — a bank, NBFC, insurer, mutual fund / depository, pension fund or GSTN — that shares the customer’s data on a valid consent |
| Financial Information User (FIU) | The data consumer — a lender, financial adviser or other regulated entity — that requests data to deliver a service such as a loan or advice |
| Customer / data principal | The individual or business whose financial data it is; gives, manages and revokes consent through the AA app and is never charged for it |
| Consent artefact | The machine-readable record of exactly what was consented to — FIU, data types, purpose, duration and frequency — the backbone of the framework |
| Financial information shared | Deposits, loans, investments (securities / mutual funds), insurance and GST returns — the data set widens as new FIPs onboard |
Milestones
| Date | Milestone |
| 2016 | RBI issues the Master Direction on NBFC-Account Aggregators, creating the AA licence category and the consent-based data-sharing model |
| Sep 2021 | The AA ecosystem goes live with eight major banks as the first Financial Information Providers |
| 2022-2023 | More banks, NBFCs, insurers, securities depositories and mutual-fund registrars onboard as FIPs / FIUs; consent-based lending use-cases scale |
| 2023 | GSTN onboarded as a Financial Information Provider, opening GST-return-based MSME credit underwriting through the AA rail |
| 2024-2025 | Accounts enabled approach ~1 billion as the AA rail becomes a mainstream channel for consent-based lending and personal finance (indicative) |
What it means for bankers
The Account Aggregator rail reshapes how a bank both sources and shares data. As a Financial Information User, a lender can pull a consented, machine-readable view of an applicant’s bank statements, investments or GST returns in seconds — cutting fraud, speeding underwriting and reaching thin-file and MSME borrowers who could never assemble paper trails; it pairs naturally with UPI and the wider digital-payments stack. As a Financial Information Provider, the same bank must be able to serve its customers’ data on valid consent, to ReBIT standards, which is an engineering and compliance obligation, not an option. Two cautions run through it: the framework is consent-first and data-blind by design, so customer control and data minimisation are the rules, not features; and the headline adoption numbers are indicative — the precise count of operational AAs, accounts enabled and consents fulfilled should always be confirmed on the official source before being quoted. The AA is the consent rail; Jan Dhan and the JAM trinity are the inclusion rails it builds on.
More live dataRelated BankPulse pages: UPI / Digital Payments · RBI Digital Payments Index · Jan Dhan (PMJDY) · NBFC Sector · Financial Inclusion Index.
Account Aggregator (AA) FAQ
What is an Account Aggregator (AA) in India?
An Account Aggregator is an RBI-licensed NBFC (NBFC-AA) that lets a customer share financial data, with explicit consent, from one regulated institution to another. It is ‘data-blind’ — it moves encrypted data between a Financial Information Provider (the institution holding the data) and a Financial Information User (the lender or adviser that needs it) but cannot itself read, store or use it. The customer is never charged, consent specifies exactly what data and for what purpose and duration, and can be revoked any time. The framework runs under the RBI’s Master Direction — NBFC-Account Aggregator (Reserve Bank) Directions, 2016. Figures are rounded and approximate.
Who are the FIP, FIU and AA?
Four parties. The Financial Information Provider (FIP) holds the data — a bank, NBFC, insurer, mutual fund or depository, pension fund or GSTN. The Financial Information User (FIU) consumes it to deliver a service — typically a lender or adviser. The Account Aggregator (AA) is the RBI-licensed, data-blind intermediary that routes data on consent. The customer (data principal) owns the data and gives, manages and revokes consent. Confirm the latest participant list on the official source.
How big is the Account Aggregator ecosystem?
The AA ecosystem went live in September 2021 with eight banks and has grown quickly: roughly 14-16 RBI-licensed Account Aggregators are operational, and on an indicative basis around 1 billion accounts have been enabled for consent-based sharing, with cumulative successful consents in the tens of millions. These figures are rounded, approximate and indicative — confirm current numbers on the official source.
Methodology & sources: see how BankPulse dashboards are sourced, verified & updated · machine-readable Account Aggregator (AA) JSON feed.
Last reviewed by Vikram Jain
Source: RBI Master Direction — Non-Banking Financial Company — Account Aggregator (Reserve Bank) Directions, 2016, rbi.org.in, read with Sahamati ecosystem statistics. The operational-AA count, accounts-enabled and consent figures are rounded, approximate and indicative, the latest period is provisional, and none is in the BankPulse Verified-numbers ledger pending reviewer sign-off. We never reproduce source text verbatim. Reviewed by Vikram Jain. Last updated 22 Jun 2026, 00:11 IST.
The short version: official source on every page · plain English, never verbatim · three-model AI consensus · Chartered-Accountant sign-off · web-grounded verified numbers · public corrections. See the six pillars on how we earn your trust.