Account Aggregator interoperability means common technical standards are designed to let participating financial institutions exchange customer-authorized data through different Account Aggregators. It does not guarantee that every NBFC-AA works with every bank, account type or lender. Compatibility depends on each institution’s participation and onboarding, and the customer must authorize the specific data-sharing request.
What does interoperability mean in the Account Aggregator framework?
An Account Aggregator (AA) is an RBI-regulated non-banking financial company that acts as a consent-based intermediary for sharing financial information. A Financial Information Provider (FIP), such as an institution holding financial data, can send information to a Financial Information User (FIU), which uses it for a permitted purpose, after the customer instructs and consents to the transfer.
As an Amazon Associate I earn from qualifying purchases.
The Reserve Bank of India’s November 8, 2019 circular set out common technical specifications intended to make data movement among ecosystem participants secure and compatible. The RBI’s 2025 Directions refer regulated participants to ReBIT’s technical specifications, as updated. ReBIT’s API specifications define common financial-information formats and representations. Together, these standards provide a technical basis for interoperability across systems; they are not a promise that every participant is connected to every other participant.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteThe Department of Financial Services describes the consent principle this way: “No financial information of the customer is retrieved, shared or transferred by AA framework without the explicit consent of the customer.” Registering with an AA is voluntary, and registration alone does not link every account or make every institution available.
Can you use any Account Aggregator with your bank?
Not necessarily. Common technical specifications help participating systems exchange information, but the specific bank or other FIP, the intended FIU, the account type and the chosen AA must also be available and operational in the flow you want to use.
Sahamati said on February 13, 2025, that technical interoperability had been achieved through standardized protocols, while practical 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 describes Sahamati’s work and aims; it is not an RBI guarantee that all institutions have completed onboarding or that all integration friction has ended.
Rank #2
In practice, check the institution and account types shown in the AA app or service you plan to use, and confirm that the intended FIU is supported in that particular flow. Review the data requested, purpose, duration and other consent details before approving a request. Do not assume that a lender’s availability through one AA means it will appear through every other AA.
Recommended Free Tools
What does this change for customers?
Common formats and interfaces are intended to reduce technical incompatibilities when a participating institution sends data through the AA ecosystem. For customers, that can make consent-based data sharing more workable across systems. It does not make data sharing automatic: the customer initiates or approves a consent flow, and the connection must be available for the relevant institutions and account.
Rank #3
The practical questions to check are:
- Compatibility: Does the AA flow support the relevant FIP and FIU?
- Availability: Is the particular institution and account type listed and operational?
- Consent: What information is requested, for what purpose and for how long?
- Controls: What notifications, authentication and consent-management options does the flow provide?
What customer protections are expected under the 2026 standard?
ReBIT’s “Account Aggregator – Standard to enhance Customer Protection and User Experience,” published April 30, 2026, covers onboarding, account discovery and linking, consent management, user experience, technical security and integration. It addresses legible consent fields, customer control over consent operations, simpler AA app design, timely notifications, two-factor authentication, SIM and device binding, and secure AA–FIU integration.
The notice says NBFC-AAs and FI-Us must adopt the standard by October 31, 2026. As of October 7, 2026, that deadline is still in the future; the standard should not be described as already implemented by every covered entity.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How large is the Account Aggregator ecosystem?
Department of Financial Services figures attributed to Sahamati, as of March 31, 2026, report 179 financial institutions live as FIPs and 989 live as FIUs. The same update reports more than 2.88 billion financial accounts enabled to share data, and 284.6 million accounts linked by users.
Those figures describe different measures: accounts enabled to share data are not the same as accounts users have linked. They are ecosystem-wide counts, not evidence that a particular customer’s bank, account or preferred AA will be available in a given transaction.
Best Value
What the RBI interoperability claim does—and does not—establish
The documented framework supports technical interoperability through common specifications and consent-based data exchange. The available evidence does not establish a blanket RBI permission guaranteeing that every customer can use any NBFC-AA with every financial institution. A claim of a newly issued, broader permission would need to identify the specific RBI circular that created it.
For the individual customer, the relevant test remains the live consent flow: whether the chosen AA offers the required institution and account, whether the intended FIU is available, and whether the consent request matches what the customer is willing to share.
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.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
