Account Aggregator in India: How the AA Framework Works (2026 Guide)

Account aggregator is a new class of RBI-licensed NBFC that enables consent-based sharing of financial data between institutions in India. In simple terms, it lets borrowers share their bank statements, tax records, and investment data directly with lenders—without downloading, uploading, or handling any documents.

In fact, the growth has been remarkable. As of September 2025, the AA ecosystem had processed over 269 million customer consents. Moreover, 780+ financial institutions are now live on the framework. Additionally, loans worth ₹1.6 lakh crore have been disbursed using AA data across 1.8 crore loan accounts.

This guide explains how the account aggregator framework works in India. It covers the three key participants (FIP, AA, FIU), the consent flow, use cases in lending, and why AA adoption matters for NBFCs and fintech lenders building modern credit underwriting workflows.

What Is an Account Aggregator? Definition and RBI Context

An account aggregator is a consent manager for financial data. The RBI created this category through its Master Directions in 2016. Specifically, AAs operate as a new class of NBFC licensed to facilitate data sharing between financial institutions.

Here is the critical distinction. An account aggregator does not store, read, or process user data. Instead, it is “data-blind.” It acts as a secure pipe that transfers encrypted financial information from one institution to another—but only after the customer gives explicit consent.

Notably, the framework emerged from an inter-regulatory decision involving the RBI, SEBI, IRDAI, and PFRDA through the Financial Stability and Development Council (FSDC). As a result, the AA framework covers not just banking data. It also includes investments, insurance, pensions, and tax information.

Currently, 16 RBI-licensed account aggregators hold operating licenses in India. For example, these include entities like CAMS Finserv, Anumati, Setu, OneMoney, and Finvu. Each AA must meet strict technical and compliance requirements before going live.

How the Account Aggregator Framework Works: FIP, AA, and FIU

The AA framework has three participants. Therefore, understanding each role clarifies how data flows through the system.

Financial Information Provider (FIP)

The FIP is the institution that holds the customer’s data. For instance, the customer’s bank holds their transaction history. Similarly, their mutual fund depository holds investment data. Their insurance company also holds policy details. As of 2025, over 155 FIPs participate in the AA ecosystem. This includes all major public and private banks.

Account Aggregator (AA)

The AA sits in the middle. Specifically, it receives the consent request from the FIU, presents it to the customer, captures explicit consent, and then facilitates the encrypted data transfer from FIP to FIU. Importantly, the AA never sees or stores the actual data. It only manages the consent and the data flow.

Financial Information User (FIU)

The FIU is the institution that needs the data. In lending, for example, this is typically the bank or NBFC processing a loan application. The FIU sends a consent request through the AA. Once the customer approves, the FIU receives the data directly from the FIP. Currently, over 475 FIUs are live on the framework.

The Consent Flow: How Data Moves Through an Account Aggregator

The consent flow is the backbone of the entire account aggregator framework. Here is how it works step by step:

• Step 1: The FIU (lender) sends a consent request to the AA. This request specifies what data is needed, from which FIP, for what purpose, and for how long.
• Step 2: The AA presents this request to the customer through an app or web interface. The customer sees exactly what data will be shared, with whom, and for what duration.
• Step 3: The customer approves or rejects the consent. No data moves without explicit approval.
• Step 4: Once approved, the AA notifies the FIP. The FIP then encrypts the requested data and sends it through the AA to the FIU.
• Step 5: The FIU receives the encrypted data and decrypts it using keys that only the FIU holds. The AA cannot read this data at any point.

The entire process takes seconds. Moreover, the customer can revoke consent at any time through the AA app. This gives borrowers full control over their financial data.

What Financial Data Can an Account Aggregator Share?

The RBI has defined 16 categories of financial information that can flow through the AA framework. These include:

• Bank account details: Deposit accounts (savings, current, fixed, recurring), transaction history, and balance information.
• Investment data: Mutual fund holdings, equity and debenture holdings from depositories (NSDL, CDSL), and government securities.
• Insurance data: Policy details from insurance repositories.
• Pension data: NPS account information from pension funds.
• Tax data: GST returns filed with GSTN and income tax data from the Income Tax Department.

For lenders, the most relevant data types are bank transaction history and GST returns. Together, these provide a comprehensive view of the borrower’s income, cash flow, and tax compliance. Additionally, the data arrives in structured JSON format. This eliminates the need for OCR-based extraction from PDFs.

How Lenders Use Account Aggregator for Credit Decisions

For lending institutions, the account aggregator framework solves three problems at once: specifically, data authenticity, processing speed, and customer experience.

Eliminating Document Fraud

Data shared through an account aggregator carries a digital signature from the FIP (the bank). This signature cryptographically verifies that the data has not changed after generation. Therefore, the risk of tampered or fake bank statements drops to near zero.

Faster Credit Underwriting With AA Data

Traditional loan processing requires borrowers to download bank statements, upload them to the lender’s portal, and wait for manual extraction and review. This takes days. With AA, the same data flows directly from the bank to the lender in seconds. A bank statement analyser then processes the structured JSON data instantly. As a result, loan approval timelines drop from days to under 48 hours for many MSMEs.

Reaching New-to-Credit Borrowers

Millions of Indian borrowers lack formal credit histories. However, they do have bank accounts with transaction data that demonstrates their repayment capacity. The account aggregator framework lets lenders access this data with consent. Consequently, borrowers who were previously excluded from formal credit can now qualify based on their actual financial behaviour.

Account Aggregator vs Manual Bank Statement Upload

Many lenders still rely on manual bank statement uploads. Here is how the two approaches compare:

Factor	Manual Upload	Account Aggregator
Data authenticity	Risk of tampered PDFs	Digitally signed by the bank
Processing time	20–40 min per statement	Under 60 seconds
Data format	Unstructured PDF (needs OCR)	Structured JSON (ready to analyze)
Customer effort	Download, upload, wait	One-tap consent
Fraud detection	Requires separate tamper checks	Forgery risk eliminated at source
Scalability	Proportional to headcount	Unlimited via API

The operational advantage is clear. Specifically, AA-sourced data eliminates three major risks: document fraud, OCR extraction errors, and processing delays. For lenders processing high volumes, these gains compound across every application.

The Account Aggregator Ecosystem in 2026: Scale and Adoption

The AA ecosystem has grown faster than any other open finance framework globally. Here are the key numbers as of late 2025:

• 269+ million customer consents processed since September 2021.
• 780+ financial institutions (155 FIPs and 475+ FIUs) live on the framework.
• 2.12 billion accounts enabled for consent-based data sharing.
• Loans worth ₹1.6 lakh crore disbursed using AA data across 1.8 crore loan accounts.
• 4–5 crore customers have availed a financial service (loan, insurance, PFM) through the AA framework.
• Consent requests grew from 5.5 million in FY23 to 63.75 million in FY24—a 1,059% increase.

The growth trajectory is still accelerating. Sahamati estimates that 15–20% of the Indian adult population will use AA by the end of FY26. Moreover, use cases are expanding beyond lending into insurance underwriting, portfolio management, pension planning, and personal finance management.

For NBFCs and fintech lenders, the implication is straightforward. Account aggregator integration is rapidly shifting from a competitive advantage to a baseline requirement. Lenders who do not adopt AA will face slower processing times, higher fraud exposure, and a narrower reach into new-to-credit segments.

Key Takeaways

• An account aggregator is an RBI-licensed NBFC that enables consent-based, encrypted financial data sharing between institutions in India.
• The framework has three participants: FIP (data holder), AA (consent manager), and FIU (data consumer). The AA is data-blind and never sees actual user data.
• Data shared through AA carries a digital signature from the FIP. This eliminates the risk of tampered or fake bank statements.
• For lenders, AA reduces loan processing time from days to hours. It also removes OCR errors and document fraud risk.
• The AA ecosystem processed 269+ million consents by September 2025. Over ₹1.6 lakh crore in loans have been disbursed using AA data.
• Account aggregator adoption is becoming a baseline requirement for modern credit underwriting in India.

Conclusion

In fact, the account aggregator framework has moved from pilot to production at remarkable speed. Four years after launch, it processes hundreds of millions of consents. Moreover, it powers over ₹1.6 lakh crore in lending. And it reaches borrower segments that traditional document-based workflows could never serve efficiently.

For lenders, therefore, the value proposition is clear. AA delivers verified, structured financial data in seconds—without the fraud risk of manual uploads and without the extraction errors of OCR-based processing. When combined with a bank statement analyser that processes AA JSON data, the result is faster decisions, lower defaults, and a broader addressable market.

Consequently, the question is no longer whether to adopt an account aggregator. Instead, it is how quickly a lender can integrate it into their credit underwriting stack. The framework is live. The institutions are connected. And the borrowers are ready.

Frequently Asked Questions