Account aggregators explained: sharing bank data with a lender
Borrower guides

Account aggregators explained: sharing bank data with a lender

  • RupeeMatch Editorial Team avatar
    Written byRupeeMatch Editorial Team
Reading time:
9 minutes
Published:
15.11.2026
Last updated:
15.11.2026
2

What an RBI-registered account aggregator does when a lender asks for your bank statement, how to read the consent before you approve it, how to revoke it, and what never to share.

Key points

  • An account aggregator (AA) is a company registered with the RBI as an NBFC-AA. It moves your financial data, such as a bank statement, from your bank to a lender only with your explicit consent.
  • AAs are governed by the RBI’s Account Aggregator Directions, 2025, issued on 28 November 2025, which replaced the 2016 Master Direction.
  • None of your financial data may stay with the AA. It travels encrypted between your bank and the lender.
  • An AA may not ask for or store your net-banking password or PIN. The OTPs in the process are ones you type into the AA app yourself.
  • Every request shows who is asking, why, which data, the period covered, how often and until when the lender can fetch, and how long it may use the data.
  • You can reject a request, and pause or revoke a consent at any time. Revoking stops future fetches; it does not erase what the lender already has.
  • Sahamati, recognised by the RBI in June 2026 as the AA sector’s self-regulatory organisation, lists the AAs that hold an RBI operating licence.

What an account aggregator is

An account aggregator is a consent manager for your financial data. When a lender wants your bank statement, your bank sends it to the lender, and the AA takes your consent, carries the data and records what was shared. It is an alternative to downloading PDFs or handing papers to an agent.

AA is a separate RBI licence category. No company may run the business without an RBI certificate of registration, and an AA may do nothing else: it cannot lend or carry out transactions. The rules are in the RBI (Non-Banking Financial Companies – Account Aggregator) Directions, 2025, which repealed the Master Direction of 2 September 2016. That is the version in force as of November 2026; later changes appear on the same RBI page.

The directions define three roles:

RoleWho it can beIn a loan application
Financial Information Provider (FIP)Banks, NBFCs, mutual fund companies, depositories, insurers, the GST Network and others that hold your recordsYour bank, which holds the statement
Account Aggregator (AA)A company registered with the RBI as an NBFC-AATakes your consent and carries the data
Financial Information User (FIU)Only an entity registered with and regulated by a financial sector regulator: the RBI, SEBI, IRDAI, PFRDA or the Department of RevenueThe bank or NBFC assessing your application

Registering with an AA is voluntary, according to the Finance Ministry’s Department of Financial Services. App names you may see include Anumati, Finvu and OneMoney, which Sahamati lists as products of Perfios Account Aggregation Services, Cookiejar Technologies and FinSec AA Solutions. We name them only so you recognise them, and recommend none.

What happens when a lender asks you to share through an AA

AAs and lenders had to implement an RBI standard for this journey by 31 October 2026. It runs like this:

  1. The lender hands you over to an AA: its app, its website or an AA module inside the lender’s app. The screen must show the AA’s own name and logo.
  2. You sign in with your mobile number. The AA must use two-step verification, such as an OTP plus a PIN, password or fingerprint you set for the AA account. You get an AA handle, much like a UPI ID.
  3. The AA finds your accounts using your mobile number, optionally with your PAN or date of birth. Your bank sends its own OTP to confirm the account is yours. Linking an account shares nothing by itself.
  4. You pick the accounts to include. The boxes must not be pre-ticked.
  5. You approve or reject. Both buttons must be the same size, and approve must not be the default.
  6. Your bank sends the data. It checks the consent, digitally signs the information and sends it, encrypted, through the AA to the lender. If the data ever differs from the bank’s books, the bank’s records count.

The AA should confirm by SMS or email and send a monthly summary of your active consents and data fetches.

The RBI requires every consent to name you, the data requested, the purpose, the recipient and the expiry date. ReBIT, the technical body named in the directions, sets the fields the screen must show:

FieldWhat it meansWhat to check
Data requestor (FI-U)The organisation that will receive the dataThe bank or NBFC you are applying to
PurposeWhy the data is wantedAssessing your application and monitoring your account after the loan are different purposes
FI types and accountsKinds of data, such as deposits, mutual funds or insurance, and the specific accountsA bank statement request that also covers investments is wider than you were told
Consent typeProfile (name, mobile, PAN), summary (balance, account type) or transactions (date, mode, amount)Which parts of your data will go
FI data rangeThe past period the data coversThe period the lender told you it needs, for example the last 6 months
Fetch type and frequencyOne-time, or periodic with a maximum number of fetches per hour, day, month or yearA periodic consent lets the lender come back for fresh data
Consent start and expiryThe window in which the lender may fetchHow long that access lasts, especially on a periodic consent
Consent mode and data lifeWhether the lender only views the data or stores it, and for how long it may use it for this purposeReBIT notes the lender may still keep records under its own policy and the law, so data life is not a deletion date

Sahamati’s fair-use templates, which cap these fields per use case, have separate templates for processing a loan application, monitoring a borrower’s repayment capacity and monitoring overdue accounts. If you are only applying and the request is periodic and runs well past the decision, ask the lender why, or reject it. An approved consent cannot be edited; any change needs a fresh request.

Can the AA read your data?

No. The RBI’s directions say that:

  • no financial information fetched from your bank may reside with the AA;
  • the data is not the AA’s property, and it may use customer information only for the service you asked for;
  • the AA may not request or store your bank passwords, PINs or other credentials;
  • the AA may not support transactions, so it cannot move money out of your account.

ReBIT’s specification encrypts the data end to end between the bank and the lender, and Sahamati’s FAQ says the AA cannot view what passes through it.

The lender does read your data, but may not use or disclose it beyond what the consent allows. For digital loans, the RBI’s lending rules add that data collection must be need-based, that you can refuse consent for specific data, withdraw consent and, if required, ask for deletion, and that the lender must publish how long it keeps customer data.

Every AA must let you revoke a consent, in whole or in part, and show you a record of your consents and who received data. Under the RBI’s standard you can also pause and resume consents from a consent dashboard.

  1. Open the AA app or website directly, not through a link in a message.
  2. Find the consent on the dashboard by the lender’s name.
  3. Choose pause or revoke and confirm. The AA should notify you by SMS or email.

Revoking stops future fetches only. Data already received falls under the data life and the lender’s retention policy; for a digital loan you can ask the lender to delete it. If you revoke mid-application, Sahamati says the lender has to take it up with you outside the AA.

Each AA must publish its grievance officer’s contact details; Sahamati collects them on one page. The AA has one month to resolve a complaint, after which you can take it to the RBI. A complaint about how the lender used your data goes to the lender first; our guide to complaining to the lender and the RBI Ombudsman covers that route.

How to check that an AA app is genuine

  • Check Sahamati’s list. Sahamati, which the RBI recognised on 5 June 2026 as the AA sector’s self-regulatory organisation, publishes the AAs with an RBI operating licence and the company behind each app. It listed 16 when we checked in November 2026.
  • Install from a verified link. Sahamati’s AA apps page links to each listed AA’s web sign-up and its Android and iPhone apps where available. Ignore links sent by SMS, WhatsApp or a caller.
  • Look for the name and logo, which the RBI’s standard requires at registration and every login.
  • Check the lender as well. Sahamati’s network participants list shows which banks and NBFCs are live as FIUs, and our guide to checking whether a loan app is RBI registered explains how to verify the lender behind an app.

What to refuse, and the scams to watch for

Because your bank sends the data directly, the only secrets a genuine AA flow needs are your AA sign-in details and OTPs, which you type into the AA app yourself. Refuse if a lender, agent or “helper” asks you to:

  • share your net-banking user ID or password, card PIN or UPI PIN, or read out any OTP;
  • install a screen-sharing or remote-access app so they can “complete the AA step” for you;
  • send screenshots of your net banking, or forward statements to an individual on WhatsApp or email;
  • open an “AA consent” link from an unknown number, or sign in to an app you cannot match to Sahamati’s list.

The RBI warns that fraudsters chase login IDs, passwords and OTPs and get people to install apps that can read everything on the phone; its advice is never to share these details with anyone, even bank staff. The AA rules agree: the AA itself may not ask for your bank credentials, and remote access to AA mobile apps must be disabled. Nor is there any reason to send net-banking screenshots: through an AA the lender gets data signed by your bank, while a screenshot can show far more than it needs.

If you have already shared a password or OTP, contact your bank at once and change your net-banking password, then report it on the cyber crime helpline 1930 or at cybercrime.gov.in. Revoke any consent you did not mean to give.

Frequently asked questions

Is it safe to share my bank statement through an account aggregator?

The statement goes from your bank to the lender encrypted, the AA may not keep it, and you see what will be shared before you approve. Most of the risk sits around the process: look-alike apps and people asking for passwords or OTPs.

Do I have to use an account aggregator to get a loan?

Registering with an AA is voluntary, according to the Department of Financial Services. Lenders set their own document requirements, so if you would rather not use one, ask the lender which other ways it accepts.

Are Anumati, OneMoney and Finvu the same thing?

They are apps of different RBI-registered account aggregators, all on Sahamati’s list and all bound by the same RBI directions and ReBIT consent format. What the lender receives depends on the consent you approve, not on which AA carries it.

Will the lender delete my data when I revoke consent?

Not automatically. Revoking stops new fetches, while data already received is covered by the data life on the consent and the lender’s retention policy; for a digital loan you can ask the lender to delete it and complain to its grievance officer if it refuses.

Home
Blog
Account aggregators explained: sharing bank data with a lender