Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Account Aggregator (AA) interoperability means common technical standards are designed to let participating financial institutions exchange customer-authorized financial information through different AA systems. It does not guarantee that every bank, account, lender, and AA app is connected to every other one. Customers still need to check that the institutions and account types in their intended flow are available, and they must approve the consent request before information is shared.
What interoperability means in the Account Aggregator framework
India’s AA framework uses a consent-based intermediary to move financial information between institutions. A Financial Information Provider (FIP) holds the information; a Financial Information User (FIU) seeks it for a permitted purpose; and the AA handles the customer’s instruction and consent. The AA is not the lender and does not own the customer’s financial information.
The Department of Financial Services says registration with an AA is voluntary and that “No financial information of the customer is retrieved, shared or transferred by AA framework without the explicit consent of the customer.” In practice, interoperability concerns the systems and data formats used by participating institutions. It is not automatic access to every account merely because someone registers with an AA.
Technical compatibility is not universal availability
RBI’s November 8, 2019 circular set out common technical specifications so data could move among ecosystem participants in a “secured, duly authorised, smooth and seamless” way. RBI’s 2025 Directions refer RBI-regulated participants acting as AAs, FIPs, or FIUs to ReBIT technical specifications, including updates. ReBIT’s API specification describes common definitions and a uniform representation for financial information.
#1 Best Overall
Those standards provide a basis for technical compatibility. A specific customer flow can still depend on separate operational steps: whether the relevant FIP and FIU have joined and completed onboarding, whether the account type is supported, and whether the chosen AA app offers that connection. Sahamati said on February 13, 2025, that standardized protocols had achieved technical interoperability, while integrations still involved bilateral agreements, compliance requirements, and separate onboarding. It described SahamatiNet and a Router as initiatives intended to reduce repetitive onboarding; that statement is not a guarantee that every institution is now connected.
Can you use any AA with your bank or lender?
Not necessarily. Common standards make interoperability possible, but they do not establish that every AA can connect to every FIP and FIU for every account. Nor do they require you to use the same AA as a lender in every case. The available choice depends on the specific institutions, account types, and flow you are trying to use.
Rank #2
- Check the intended connection. In the AA app or institution flow, confirm that your financial institution and the relevant account type are listed and available.
- Read the consent request. Check which information is requested, the purpose, the period or frequency of access, and the recipient before approving.
- Review the controls shown in the app. Look for how the service presents consent, notifications, and options to manage or revoke consent.
How widely the ecosystem was connected as of March 31, 2026
The Department of Financial Services’ progress update, which attributes its figures to Sahamati, reported these ecosystem counts as of March 31, 2026:
| Measure | Count | What it describes |
|---|---|---|
| Financial institutions live as FIPs | 179 | Institutions holding financial information |
| Financial institutions live as FIUs | 989 | Institutions using financial information for permitted purposes |
| Financial accounts enabled to share data | More than 2.88 billion | Accounts enabled in the ecosystem; not the same as accounts linked by users |
| Accounts linked by users | 284.6 million | Accounts actually linked by users |
These figures show substantial participation, but they do not tell you whether a particular account is available through a particular AA app or usable by a particular FIU.
Recommended Free Tools
Customer-protection standards and the October 2026 deadline
ReBIT’s “Account Aggregator – Standard to enhance Customer Protection and User Experience,” dated April 30, 2026, covers onboarding, account discovery and linking, consent management, user experience, technical security, and integration. Its requirements include legible consent details, customer control over consent operations, simple AA application design, timely notifications, two-factor authentication, SIM and device binding, and secure AA–FIU integration.
The standard’s notice says NBFC-AAs and FI-Us must adopt it by October 31, 2026. As of October 7, 2026, that deadline is still upcoming; it should not be read as confirmation that every covered entity has already completed adoption.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
