A Head of Risk at a mid-sized NBFC walks into the Monday standup with a number on a sticky note: 23 percent. That is the share of their personal-loan applications where the underwriter is still parsing PDF bank statements by hand. The rest are coming through their Account Aggregator (AA) integration. The question on the wall behind her is which AA they should add as a second source so that 23 percent gets cut in half by the next quarter.
A Financial Information User (FIU) is choosing among 17 Reserve Bank of India (RBI)-licensed entities. A wrong pick costs developer weeks. A right one cuts loan turnaround time by days.
The 2026 Indian AA Landscape in 60 Seconds
The Account Aggregator framework is India’s consent-driven open finance layer, regulated by the RBI as an NBFC-AA license category. It is the rail through which a customer’s bank statements, mutual fund portfolios, insurance records, and tax data move from where they sit to where the customer wants them to go, all under explicit, time-bound consent.
Ecosystem at a Glance
According to Sahamati’s official directory, there are 17 operational Account Aggregators in India as of 2026. The broader ecosystem now includes 179 Financial Information Providers (FIPs), 955 Financial Information Users (FIUs), and over 999 financial entities live on the rail.
The lending side has crossed a meaningful threshold. Sahamati’s Credit Reimagined H1 FY26 report shows AA-facilitated lending reached ₹1.47 lakh crore across 1.5 crore loans in the April–September 2025 half-year. The monthly run-rate of ₹24,000 crore is up 71 percent from roughly ₹14,000 crore monthly in H2 FY25. AA now accounts for 7.7 percent of total sector lending by value and 10.8 percent by volume, with approximately one in every ten personal loans facilitated through the framework.
AA is no longer a sandbox-phase rail. The infrastructure is live, the volumes are real, and the decision for an FIU is which provider to trust with the consent layer that underwriting depends on.
What an Account Aggregator Actually Does (And Doesn’t)
An Account Aggregator is a consent-driven data-plumbing layer. It is not a credit bureau, a lender, or a data analytics company. The AA holds no financial data of its own. It moves data from FIPs (banks, mutual fund houses, insurers, depositories, the Goods and Services Tax Network) to FIUs (lenders, wealth platforms, account aggregators of aggregated services) under a customer-issued consent artefact.
The model is tripartite: customer, FIP, FIU, with the AA in the middle as the consent broker. For a deeper view, our explanation of the RBI Account Aggregator framework walks through the architecture and what each role actually does.
The 6 Questions to Ask Before Picking an AA
A clean selection process answers six questions in order. Each one eliminates options. By the end you usually have one or two AAs left, and the choice between them comes down to commercial terms.
1. Which FIPs Do You Actually Need?
Map your FIU use case to the FIP coverage you need. A consumer-credit lender mostly needs banking and credit-bureau data, so banking FIP coverage is the priority. A wealth platform needs depositories (Central Depository Services Limited, National Securities Depository Limited), Asset Management Company registrars (CAMS, KFin), and the Goods and Services Tax Network for self-employed customers. An MSME lender needs all of the above plus the GSTN for revenue evidence.
Coverage varies dramatically across AAs. According to publicly reported integration data, top AAs by live FIP coverage as of early 2026 are roughly Anumati at 80-plus FIPs, CAMS AA at 70-plus, OneMoney at 65-plus, Finvu at 60-plus, and NADL at 60-plus. Four AAs (Upmint, Cygnet, PB Financial, Scoreme) currently have zero live FIP integrations despite holding RBI licenses. The license is not the same as a live, production-ready integration.
The implication is operational. Most large FIUs end up integrating with two or three AAs, not one, because no single AA covers every FIP a complex underwriting flow needs.
2. What Is the Developer Experience?
Sandbox quality, documentation completeness, error-message clarity, and test-FIP availability for end-to-end user acceptance testing. These sound like soft factors. They are not. A poor sandbox costs an integration team six to eight weeks of hidden work that nobody scoped at the start.
Specific questions to ask the AA’s solutions team:
- Is there a test FIP that returns realistic-shape data for every FI type you intend to pull?
- Are error responses standardized to the ReBIT (Reserve Bank Information Technology) specification, or are they vendor-specific?
- Is there an SDK in your engineering team’s primary language, or is it raw REST?
- What is the median time-to-first-successful-pull for a new FIU integration?
Get answers from a current customer, not just the AA’s sales deck.
3. What Is the Consent UX?
The consent screen is the customer’s window into the entire AA experience. It is also the screen where most AA flows lose customers.
Pre-built consent screens versus build-your-own is the first decision. Pre-built ships faster but constrains how you brand the experience. Custom screens give brand control but require careful adherence to the consent-display rules in the Master Direction.
Mobile SDK availability matters because most AA-driven lending and wealth flows happen on mobile. So does localization. Hindi plus eight to ten major regional languages is the operational standard. If the AA’s SDK only renders in English, you are leaving conversion on the table for tier-2 and tier-3 cities.
The AA’s documentation should also explain which consent artefacts are stored where, and how revocation flows back to the FIU. This is the part that becomes painful at audit time.
4. What Is the Pricing Tier?
Three pricing models dominate. Per-pull (you pay per consent fulfilled), subscription (a flat monthly or annual fee with a volume cap), and hybrid (subscription plus per-pull above the cap).
The break-even between these depends on volume. At low volumes (under a few thousand pulls a month), per-pull wins. At high volumes (over fifty thousand pulls a month), subscription wins. The hybrid model fits institutions whose volumes are growing and predictable.
Two specific questions to ask: what is the price per data category (banking pulls usually cost more than mutual-fund pulls), and what is the volume discount curve at the tier you expect to operate in twelve months from now? The first answer changes the unit cost. The second answer prevents a renegotiation when you scale.
5. What Is the Support Model?
AAs distribute through Technology Service Providers (TSPs) and through direct relationships. Both are valid. The choice depends on what kind of support you need.
A TSP relationship gets you a buffer that handles integration questions and absorbs FIP outage incidents on your behalf. The downside is one more contract and one more margin layer. A direct relationship gets you closer to the AA’s engineering team for production incidents but requires more in-house technical depth.
The questions worth asking on either path: what is the SLA for FIP outage incidents, what is the on-call escalation path, and is there dedicated account management at the FIU-tier you operate at? Production AA outages are rare but real. When they happen, the time to resolution is the difference between a customer drop-off event and a quiet recovery.
6. Are They Certified, and on Which Standards?
Sahamati certification status is the table-stakes check. ISO 27001 for information security and SOC 2 Type II for operational controls are the next layer. Data residency is the third. The Master Direction requires that AA data residency stays within India; verify this contractually, not just on the marketing page.
Worth one final ask: is the AA on the latest ReBIT specification version, or are they still on a prior version? A lagging spec means missing features and longer integration cycles when ReBIT updates.
The Active Indian AAs at a Glance
Below is a working comparison of the seven Indian AAs with meaningful market traction as of early 2026. The remaining ten licensed AAs either operate at small scale, are still in sandbox, or have not announced live FIP integrations.
| Account Aggregator | Parent / operator | Approx. live FIPs | Best-fit FIU profile |
|---|---|---|---|
| Anumati | Perfios | 80+ | Lending FIUs needing breadth across banking, GST, and depositories |
| CAMS AA (CAMSFinServ) | CAMS | 70+ | Wealth management and mutual-fund-heavy use cases |
| OneMoney | FinSec AA Solutions | 65+ | Early ecosystem footprint, broad FIU adoption |
| Finvu | Cookiejar Technologies | 60+ | AA-only focus, broad partner network |
| NADL | NeSL Asset Data | 60+ | Information Utility-backed, debt instrument depth |
| Setu AA | Agya Technologies (Pine Labs) | Mid-tier | Developer-experience-led, fintech-friendly stack |
| Protean SurakshAA | Protean (formerly NSDL e-Gov) | Mid-tier | Retail-friendly, leveraging Protean’s consumer reach |
FIP counts are approximate, drawn from publicly reported integration data, and shift quarterly as new partnerships go live. Validate the current count with the AA directly during evaluation.
Brief Profiles
Anumati ships with the broadest FIP coverage among the active AAs and is operated by Perfios, whose lending-data heritage reads through into the AA product’s underwriting orientation. Best-fit for FIUs whose use case spans banking, GST, and depositories simultaneously.
CAMS AA brings the deepest mutual-fund coverage by virtue of CAMS’s role as the largest registrar in Indian asset management. Wealth platforms and lenders cross-selling investment products tend to short-list CAMS first.
OneMoney was one of the earliest licensees and has accumulated a broad ecosystem footprint across both lending and wealth FIUs. Solid all-rounder with reliable production performance.
Finvu is AA-pure-play, operated by Cookiejar Technologies, with a broad partner network and a focus on the consent layer rather than ancillary services. Strong for FIUs that want a focused AA partner without bundled services.
NADL is backed by the National e-Governance Services Limited Information Utility infrastructure, which gives it depth in debt-instrument data. Best-fit for FIUs in the debt-recovery and credit-monitoring use cases.
Setu AA is operated by Agya Technologies, part of the Pine Labs group, and is known among the engineering community for its developer experience, sandbox quality, and SDK ergonomics. The fintech founder community tends to short-list Setu first when developer cycles are the bottleneck.
Protean SurakshAA is operated by Protean (formerly NSDL e-Governance), with strong consumer reach and PAN/Aadhaar adjacency. Useful for FIUs whose customer base skews toward retail and tier-2 markets.
If you want a different angle on the same shortlist, our walkthrough of how to choose the right financial Account Aggregator goes through the criteria from a buyer’s checklist perspective.
Implementation Reality: What the Marketing Pages Skip
Three things consistently catch FIU teams by surprise after they sign with an AA. Naming them upfront is part of why this article exists.
The FIP Fragmentation Problem
Your customer might have their salary account at HDFC, their mutual funds with CAMS-registered AMCs, and their insurance with LIC. If you have integrated with one AA that covers HDFC and CAMS but not LIC, you have a hole in your data picture for that customer. The next customer’s hole is somewhere else entirely.
There is no universal interconnection across the AA ecosystem. FIPs join AAs one by one through bilateral integrations. The practical implication is that a serious FIU integrates with two or three AAs to get to ninety-percent-plus FIP coverage for their customer mix.
For a mid-sized lender, this means budgeting for two to three AA integration projects, not one. For a single-product wealth platform, one AA is often enough if their FIP coverage covers the AMC list you actually need.
What’s Still Missing in 2026
Joint accounts are excluded from AA pulls under the current Master Direction. This affects MSME and family-business lending more than retail lending, but it is a real gap.
Bonds and certain non-deposit instruments are still in proposed status rather than live. Investment data tilts heavily toward mutual funds and depository holdings.
Some smaller cooperative banks and regional rural banks have not yet onboarded to any AA. If your FIU’s target segment overlaps with co-op bank customers, expect a period of parallel manual collection.
When the AA Pull Is Not Enough
For underwriting decisions that need three to six months of cash-flow analysis, the AA pull gives you the raw bank-statement data, but the analytics layer on top is a separate problem. Our breakdown of automated bank statement analysis covers what the analysis side looks like once the AA hands you the data, and our bank statement analysis software guide covers the buying criteria for that adjacent layer.
Income evidence for self-employed and gig customers is the other place AA needs help. The AA gives you the bank inflow data; turning that into a confident income number is what income validation for lending is about. Our walkthrough on how to verify income covers the practical steps once you have AA-pulled bank data in hand.
Where Account Aggregators Sit in the Broader Onboarding Stack
The AA decision is one of three or four that shape modern customer onboarding for an FIU. Identity verification (the KYC layer covering the standard components of KYC), bank statement analysis (the underwriting layer), and document verification (DigiLocker and physical document capture) are the others.
Our DigiLocker API integration covers the document-pull side that complements the AA-pull side, and our credit underwriting overview covers how AA data translates into a lending decision. For the bigger picture of how all of this fits together inside a credit ops workflow, Underwriting 2.0 is the platform layer that orchestrates AA pulls, document analysis, and decision logic in one stack.
Picking the AA is not the end of the buildout. It is the first decision in a chain of four or five that determines how fast and how confidently you onboard customers. Our piece on the customer onboarding process covers the broader workflow for FIU teams designing this chain end-to-end. We also wrote up the comparison of manual tracking vs Account Aggregators for FIU teams still running parallel paths, and a deeper look at how Account Aggregators are reshaping financial data sharing.
A Short Note for FIUs Operating Outside India
The “Account Aggregator” framework is India-specific terminology. The same workflow exists in other jurisdictions under different names: open banking in the United Kingdom and the European Union, the Consumer Financial Protection Bureau’s 1033 framework in the United States, and Plaid, Yodlee, MX, Finicity, and Akoya as the dominant Western data-aggregator platforms.
These are adjacent layers, not direct equivalents to the Indian RBI-regulated AA framework. If you operate across India and other markets, the AA selection question above applies to your India footprint specifically. The cross-border equivalent is its own selection exercise with its own vendor list, governed by a different regulatory framing, consent architecture, and provider-user model.
Putting It Together
The right AA for an FIU is the one whose FIP coverage matches your customer mix, whose developer experience does not eat your engineering quarter, whose pricing model fits your volume, and whose support model fits your in-house technical depth. Two AAs short-listed is usually better than one. The first quarter of integration is what separates the AAs that ship cleanly from the ones that consume more time than they save.
If your team is building or refactoring the data and identity stack around AA integrations and you want to see how the AA pull, document verification, bank-statement analysis, and KYC remediation fit together in a unified flow, book a walkthrough with our team. Our identity and Account Aggregator orchestration page covers how the consent pull connects to the rest of an onboarding journey.
FAQs
Who are the top Account Aggregators in India?
The active Indian AAs with meaningful market traction are Anumati (Perfios), CAMS AA, OneMoney, Finvu (Cookiejar), NADL (NeSL), Setu AA (Agya/Pine Labs), and Protean SurakshAA. Anumati leads on Financial Information Provider coverage with 80-plus live FIPs. CAMS AA is strongest for mutual-fund-heavy use cases. Setu is preferred for developer experience.
How do I choose an Account Aggregator?
Answer six questions in order: which FIPs do you actually need, what is the developer experience, what is the consent UX, what is the pricing tier, what is the support model, and are they certified. The first question eliminates the most options. Most large FIUs end up integrating with two or three AAs to cover their full customer mix.
Is Setu an Account Aggregator?
Yes. Setu AA is operated by Agya Technologies, part of the Pine Labs group, and is a Reserve Bank of India-licensed Account Aggregator. It is known in the developer community for sandbox quality and SDK ergonomics, and is often short-listed by fintech teams where developer cycles are the bottleneck.
What is the difference between Finvu and OneMoney?
Finvu, operated by Cookiejar Technologies, is an AA-pure-play with a broad partner network. OneMoney, operated by FinSec AA Solutions, is one of the earliest licensees with a broad ecosystem footprint across both lending and wealth FIUs. Both have sixty-plus live FIPs as of early 2026. The choice usually comes down to support model, pricing, and which one’s FIP coverage best matches your customer mix.
Are Account Aggregators safe?
Yes, when used correctly. AAs are RBI-regulated NBFCs operating under the Master Direction, with consent-based data sharing as the architectural foundation. They cannot read or store the data they move; they only facilitate the consent-driven transfer between FIP and FIU. Customers can revoke consent at any time. Verify ISO 27001 and SOC 2 Type II certifications when selecting a provider.
How much does it cost to integrate an Account Aggregator?
Pricing varies by AA and pricing model. Per-pull pricing is common for low-volume FIUs and ranges from a few rupees to tens of rupees per consent fulfilled, depending on the data category. Subscription pricing fits high-volume FIUs and starts in the lakhs per month. Integration cost (one-time engineering effort to go live) typically runs four to twelve weeks of engineering time, depending on the AA’s developer experience and the complexity of your onboarding flow.
What is the role of Customer Due Diligence in an AA integration?
The AA pull does not replace customer due diligence. It feeds it. The AA provides verified financial data, but the FIU still runs its own KYC, AML screening, and risk classification on the customer. CDD is the regulatory wrapper around how that AA data gets used in onboarding and ongoing monitoring.
What happens if a customer’s bank is not yet on AA?
The fall-back is parallel manual collection: the customer uploads their bank statement, the FIU runs OCR and bank-statement analysis on the upload, and the underwriting flow continues. Most FIUs design their integration to gracefully fall back to manual when the AA does not cover a specific FIP. As FIP coverage grows, the manual fall-back rate falls. Our piece on KYC remediation covers the broader pattern of bringing back-book customers up to current standards as coverage expands.
