The Account Aggregator system is a consent-based way for financial institutions in India to share your financial data with another institution or app, but only after you approve a specific request. Instead of handing over a login or emailing a file, you say yes to a defined set of data, for a stated purpose, for a limited time.
This article stays at the idea level. Details such as which institutions take part and what exactly is shared change over time, so check the current position with the provider you are dealing with.
What is the basic idea?
Think of it as a go-between that carries data only when you approve. A lender or app that wants to see your bank details makes a request. You get asked to approve it, you see what is requested, and the data moves from the institution that holds it to the one that asked, with the go-between passing it along. Your login stays with you.
What does a consent request usually spell out?
- Who is asking and who holds the data.
- What kind of information is requested, for instance deposit account transactions.
- The period the data covers.
- The purpose, such as a loan assessment.
- How long the permission lasts and how often the data can be fetched.
- How you can withdraw it.
Read these items before you tap approve. They are the difference between a narrow, time-limited view and an open-ended one.
How does it differ from sharing a password?
A password gives the app everything the login allows and is not tied to a purpose. A consent request is limited to the data and the purpose you approved, you can see it and you can withdraw it. The institution that holds your data decides what to release, so you are not typing your bank credentials into a third party.
How does it differ from sharing a statement file?
| Aspect | Statement file | Consent-based data sharing |
|---|---|---|
| Who produces the data | You download it from your bank | The institution releases it after you approve |
| What you control | Dates, which accounts, who gets the file | The scope and duration you approve |
| What can go wrong | The file lingers or is forwarded | A broad or long-running consent forgotten |
| Effort | Download and upload each time | Approve once, then data can flow within limits |
Is every app that mentions it using it properly?
No. Some apps say they offer secure access but still ask for logins. Check what the app actually asks you for. If it asks for your net-banking user name or a code, it is using a different route. Also check which provider or provider it connects through, how it stores what it receives and how to delete it, because the app may hold a copy once it has the data.
What are the questions to ask before you agree?
- Is this request for the data I expect, and for the period I expect?
- Is the purpose clear, and does it match what I am doing?
- How long does the permission last, and can the app keep fetching data?
- How do I see and withdraw my approvals later?
- What does the app do with the data once it has it?
A good mental image: a password is a spare key to your house, a file is a photocopy you hand over, and a consent request is a visitor pass for one room and one afternoon, issued by the building's front desk. The pass can be cancelled, and it says what the visitor may look at.
Where does SpendixAI fit?
SpendixAI works from statements you upload as PDF, CSV or Excel. It has no bank connection and never asks for net-banking logins, so for now it sits on the file side of this comparison, and what you share is what you choose to upload.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


