← All news and guides
Data protection

Account Aggregator Consent and DPDP: Where the Two Consent Systems Meet

Account Aggregator consent and DPDP consent are two systems. What the RBI consent artefact covers, what the data user still owes under DPDP, and what to build.

Mono Team ·

A sealed envelope resting on a brass tray beside a rubber stamp on a polished wooden counter in a quiet bank branch, morning light through a high window.

Short answer: Account Aggregator (AA) consent and DPDP consent are two different instruments, and the first does not replace the second. An AA consent artefact authorises one defined movement of financial information, from a Financial Information Provider (FIP) through the Account Aggregator to a Financial Information User (FIU). It is governed by the RBI's NBFC - Account Aggregator Directions, 2025. DPDP consent, under Section 6 of the DPDP Act, is one of the two grounds on which the FIU may process that personal data once it arrives. The artefact is a strong record and a good starting point. But the FIU still needs its own DPDP notice, a ground for its own use, withdrawal handling and erasure rules. The core DPDP duties start on 13 May 2027.

This post is for lenders, wealth and insurance firms, and the SaaS teams that build for them. It covers what each consent does, where they overlap, and what to build so that one customer journey satisfies both. It is engineering guidance, not legal advice. How the two regimes interact for your business goes to counsel.

Which RBI text governs Account Aggregators?

As of 20 November 2026, the governing text is the Reserve Bank of India (Non-Banking Financial Companies - Account Aggregator) Directions, 2025, RBI/DoR/2025-26/368, dated 28 November 2025. Paragraph 61 repeals the earlier Account Aggregator directions. If a policy, vendor contract or audit file still cites the 2016 Master Direction as the current text, update the reference.

The Directions are issued to NBFC-AAs, the non-banking finance companies registered with the RBI to do the business of an Account Aggregator. They apply in addition to other laws, not in place of them (para 63). That matters here, because the DPDP Act also says it is in addition to other laws (Section 38(1)).

Who is who in an Account Aggregator flow?

A row of wooden pigeonhole mail slots in an old sorting cabinet, one slot holding a folded envelope, soft side light, the background out of focus.

Paragraph 8 of the Directions defines the roles. The DPDP role is our analysis and your counsel should confirm it.

RoleWhat the Directions sayLikely DPDP role (analysis)
CustomerWhat the Directions say: A person who has contracted with the NBFC-AA for its service (para 8(6)). 'Person' includes companies, firms and HUFs, so the customer is not always an individual.Likely DPDP role (analysis): Data Principal, where the customer is an individual. DPDP covers personal data of individuals only. Sole proprietors and GST return data need a closer look.
NBFC-AAWhat the Directions say: Retrieves, consolidates and presents financial information, only on the customer's explicit consent. No financial information 'shall reside with the NBFC-AA' (para 14(7)). It must not request or store customer credentials (para 30(2)).Likely DPDP role (analysis): Data Fiduciary for what it does hold, such as customer identity and consent records. Not holding the financial information shrinks its footprint.
Financial Information Provider (FIP)What the Directions say: A bank, NBFC, asset manager, depository, insurer, GSTN and similar entities. Verifies the artefact and shares the data in real time (paras 22 to 26).Likely DPDP role (analysis): Data Fiduciary for the records it holds. It already has its own DPDP duties.
Financial Information User (FIU)What the Directions say: An entity registered with and regulated by a financial sector regulator (para 8(12)). Receives the data under the artefact.Likely DPDP role (analysis): Data Fiduciary for the data it receives and uses. This is where most DPDP work lands.
Your vendorsWhat the Directions say: Not a defined AA role. A SaaS tool, LLM API or analytics provider that touches the data on the FIU's behalf.Likely DPDP role (analysis): Data Processor, under a valid contract (Section 8(2)). The FIU stays responsible (Section 8(1)).

One consequence: a software vendor is not itself an FIU, because an FIU must be regulated by a financial sector regulator. If you sell to lenders, you sit behind the FIU as its processor, and the FIU's purpose limits flow down to you.

Paragraph 17 says the consent obtained by the NBFC-AA must be a standardised consent artefact. Paragraph 21 says an electronic artefact must be capable of being logged, audited and verified. Here is what it holds, and the DPDP idea each field sits next to.

Artefact content (para 17)What it doesNearest DPDP concept
Identity of the customer and optional contact informationWhat it does: Ties the consent to a personNearest DPDP concept: Data Principal identity in your consent record
Nature of the financial information requestedWhat it does: Limits what can be fetchedNearest DPDP concept: Data limited to what is necessary (Section 6(1))
Purpose of collecting the informationWhat it does: Sets what the data may be used forNearest DPDP concept: Specified purpose (Sections 5 and 6)
Identity of the recipients, if anyWhat it does: Names who may receive itNearest DPDP concept: Disclosure to other fiduciaries or processors
URL for notification each time the artefact is usedWhat it does: Gives a trail of every accessNearest DPDP concept: Visibility through logs (Rule 6)
Creation date, expiry date, and the NBFC-AA's identity and signatureWhat it does: Time-boxes the consent and proves who issued itNearest DPDP concept: Proof of consent (Section 6(10))
Any other attribute the RBI prescribesWhat it does: Allows changeNearest DPDP concept: Not applicable

Before asking, the NBFC-AA must tell the customer these attributes and their right to complain to the relevant authorities if a grievance is not resolved (para 19). That notice is the AA's. It does not satisfy the FIU's own DPDP notice.

No. Both are 'consent', and both are specific and revocable. But they answer different questions. The artefact answers: may this information move from this FIP to this recipient, for this purpose, until this date? DPDP consent answers: may this business process this person's personal data for this specified purpose?

QuestionAA consent artefactDPDP consent
Legal sourceAA consent artefact: RBI Directions 2025, paras 14 to 21, 28DPDP consent: DPDP Act Sections 4 to 6 and Rule 3
Who asks and records itAA consent artefact: The NBFC-AA, through its own app and screensDPDP consent: The Data Fiduciary, in its own journey
Notice before consentAA consent artefact: AA tells the customer the artefact attributes and the complaint right (para 19)DPDP consent: Standalone notice with an itemised description of data, specified purposes, and how to withdraw, use rights and complain to the Board (Section 5, Rule 3)
What it authorisesAA consent artefact: One defined retrieval and sharing of financial informationDPDP consent: Processing of personal data for the specified purpose
WithdrawalAA consent artefact: Revoke in full or in part. A fresh artefact then goes to the FIP (para 20)DPDP consent: Withdraw as easily as it was given (Section 6(4)). Fiduciary and its processors must cease within a reasonable time (Section 6(6))
RecordAA consent artefact: Must be loggable, auditable and verifiable (para 21). Customer can see the consents and recipients (para 35)DPDP consent: Fiduciary must prove notice and consent if challenged (Section 6(10))
Use limitAA consent artefact: No use or disclosure except as specified in the artefact (para 28)DPDP consent: Processing only for the specified purpose (Section 6(1))
StatusAA consent artefact: In force from the day the Directions were placed on the RBI website (issued 28 November 2025)DPDP consent: Core duties start 13 May 2027

So the artefact governs the data flow. The FIU's own processing still needs a DPDP ground. The two usual candidates are consent under Section 6 and a certain legitimate use under Section 7. Section 7(a) covers data a person voluntarily provided for a specified purpose, where she has not said she does not consent. Whether Section 7(a) fits a given AA journey is a question for counsel. Until you have that answer, design for Section 6 consent, because it forces you to build notice, withdrawal and proof, and those controls help under either ground.

No, not on anything we have found. An NBFC-AA is registered with the RBI. A DPDP Consent Manager is a person registered with the Data Protection Board under Rule 4 and Section 6(9), acting for the individual across Data Fiduciaries. They are separate registrations under separate regulators.

Using an AA does not make you use a DPDP Consent Manager, and the reverse is also true. Section 6(7) makes a Consent Manager optional for the individual. When we last checked on 19 November 2026, the Board's register showed none registered. Our registered Consent Managers tracker records any change.

One more item for the file. Sahamati, the Account Aggregator industry alliance, says the RBI recognised it as the Self-Regulatory Organisation for the AA ecosystem on 5 June 2026. We could not confirm this on rbi.org.in, so treat it as Sahamati's statement. Check the RBI's site before you cite it in a policy.

What does the FIU still owe under DPDP when the artefact is valid?

A valid artefact lets you fetch the data. It does not discharge your DPDP duties on the data you now hold. Here is what remains, with the duties starting on 13 May 2027:

  • Your own notice. Section 5 and Rule 3 require a notice that stands alone, with an itemised description of the data and the specified purposes. The AA's screen is not your notice. Present yours in your journey, before you send the consent request to the AA.
  • A purpose that matches the artefact. If the artefact says 'loan underwriting', your notice and your use must say the same. Paragraph 28 bars use or disclosure beyond what the artefact specifies.
  • Accuracy where you decide on it. Section 8(3) requires completeness, accuracy and consistency of data used for a decision that affects the person. Paragraph 14(11) says the FIP's own record prevails if a statement differs from it. Keep the fetch time and FIP reference, so you can refetch and compare.
  • Reasonable security safeguards, including access control, logs and processor clauses (Section 8(5), Rule 6).
  • Breach intimation to the Board and affected people (Section 8(6), Rule 7).
  • Erasure when consent is withdrawn or the purpose is no longer served, unless a law requires you to keep it (Section 8(7)).
  • Processor control. Anyone who handles the data for you needs a valid contract (Section 8(2)), and you stay responsible for them.

Lending flows also meet the RBI's digital lending rules and KYC retention. Our post on DPDP for digital lending apps shows how those stack with DPDP.

A glass hourglass on a worn wooden desk with most of the sand in the lower bulb, soft window light, the background blurred.

Each event below leaves a different mark on your systems. Plan each one before you launch.

EventWhat it stopsWhat you must still do
Artefact reaches its expiry dateWhat it stops: Further fetches under that artefactWhat you must still do: Decide retention for data already fetched. Expiry does not erase anything. Ask for a fresh artefact only if you still have a purpose and the person agrees.
Customer revokes the artefact at the AA (para 20)What it stops: Further fetches. The AA sends a fresh artefact to the FIPWhat you must still do: Receive the revocation, stop jobs that use the artefact, and record the event. Then decide what happens to data already held (see below).
Customer withdraws consent in your appWhat it stops: Your processing for that purpose (Section 6(6))What you must still do: Revoke the artefact at the AA too, or fetches may continue. Tell your processors to stop.
Customer closes the account or the purpose endsWhat it stops: Your need for the data (Section 8(7))What you must still do: Erase, unless a law requires you to keep it. Record the legal hold and its end date.

The hard case is data already fetched when consent is revoked. DPDP erasure under Section 8(7) is subject to retention that other laws require. Credit records, KYC and audit duties may justify keeping some of it. Do not keep it by default. For each data class, write down the law that requires retention, the period, and who may access it during that time. Our consent log engineering guide shows how to structure the record.

What should an FIU build so one journey satisfies both?

The design goal is one consent record that links the DPDP notice, the AA artefact and every use of the data. A workable build looks like this.

  • One consent ledger, two kinds of event. Store each DPDP consent event with person, purpose, notice version, timestamp and channel. Add the AA artefact reference, its purpose, its expiry date, and its status (active, revoked, expired). Link the two.
  • Notice first, then the AA redirect. Show your Rule 3 notice, capture the person's agreement, and only then raise the consent request to the AA. Save the notice version shown.
  • Ask for the minimum. Request only the financial information types and the date range you need. This helps Section 6(1) and keeps you inside the artefact's stated nature of information.
  • Tag every record with its source. Mark data from AA flows with the artefact reference, FIP and fetch time, so a revocation, a refetch or an erasure request can find all of it, including copies in your data warehouse and feature stores.
  • Bind purposes in code. Let each downstream use, such as underwriting, fraud checks or marketing, check the artefact purpose before it reads the data. A marketing job should fail on data fetched for underwriting.
  • Handle revocation in both directions. Process the notification from the AA, and also call the AA to revoke when the person withdraws in your app. Test both paths.
  • Keep an evidence trail. Keep the artefact record, the notification receipts, the fetch logs and the erasure log. Rule 6 expects logs to be kept, and a bank, auditor or the Board will ask for them.

If you use AI on this data, for example to extract features from bank statements or to summarise cash flow with an LLM, treat the model call as another use. It must fall within the artefact's purpose. A third-party API is a processor and a possible cross-border transfer, so it needs a contract and a data-flow record. Training a general model on AA data is a different purpose from underwriting one customer. Raise it with counsel before you do it. Record these AI uses in your AI governance file too.

What evidence should you have ready for a bank, investor or auditor?

EvidenceWhat it shows
Consent ledger extract for a sample customer, with notice version and artefact referenceWhat it shows: You can prove notice and consent (Section 6(10))
Purpose map from artefact purposes to systems and jobsWhat it shows: Data stays within what the artefact specifies (para 28)
Revocation test results, in both directionsWhat it shows: Withdrawal reaches the AA, your systems and your processors
Retention schedule, with the law behind each periodWhat it shows: Erasure follows Section 8(7), with documented exceptions
Processor list with contracts and data categoriesWhat it shows: You control who touches the data (Section 8(2))
Access and fetch logsWhat it shows: Reasonable safeguards under Rule 6 can be demonstrated

Mono does not certify AA or DPDP compliance, and no government certificate exists for DPDP. We build the controls and the evidence. Your partner law firm signs off the legal reading. Our BFSI DPDP page covers banks and NBFCs more broadly, and our consent management service builds the ledger, notices and withdrawal flows described above.

Sources: Reserve Bank of India (Non-Banking Financial Companies - Account Aggregator) Directions, 2025, RBI/DoR/2025-26/368, 28 November 2025 (paras 8, 14, 15, 17, 19 to 21, 28, 30, 35, 61 and 63). Digital Personal Data Protection Act, 2023, Sections 4 to 8, 38. Digital Personal Data Protection Rules, 2025, Rules 3, 4, 6 and 7. Sahamati press release, 5 June 2026. Data Protection Board of India register, checked 19 November 2026. Last reviewed 20 November 2026.

FAQ

Does Account Aggregator consent satisfy DPDP consent?

No. An AA consent artefact authorises one defined movement of financial information between a provider and a user. The user, as a Data Fiduciary, still needs its own DPDP notice and a ground for its own processing, either consent under Section 6 or a legitimate use under Section 7. The artefact is useful evidence, and its purpose limit in paragraph 28 of the RBI Directions also shapes what the user may do with the data.

Is an Account Aggregator the same as a DPDP Consent Manager?

No. An NBFC-AA is registered with the RBI under the Account Aggregator Directions, 2025. A DPDP Consent Manager is registered with the Data Protection Board of India under Rule 4 of the DPDP Rules. They have different regulators and different roles. When we last checked on 19 November 2026, the Board's register showed no registered Consent Manager.

What does an Account Aggregator consent artefact contain?

Under paragraph 17 of the RBI Directions it holds the customer's identity and optional contact details, the nature of the financial information, the purpose, the identity of the recipients, a URL for notification on each use, the creation and expiry dates with the NBFC-AA's identity and signature, and any attribute the RBI prescribes. Paragraph 21 requires it to be capable of being logged, audited and verified.

What happens to data already fetched if the customer revokes AA consent?

Revocation stops further fetches. It does not by itself delete data you already hold. Under DPDP, withdrawal of consent leads to erasure under Section 8(7) unless a law requires you to keep the data. Decide for each data class what law requires retention and for how long, and erase the rest. Record the decision.

Who is responsible for DPDP compliance in an Account Aggregator flow?

Each party is responsible for the data it holds and uses. The Financial Information User is generally the Data Fiduciary for the data it receives and uses, and its software and AI vendors are processors under a valid contract. The Account Aggregator and the Financial Information Provider have their own duties. Counsel should confirm the roles for your set-up.

Map your Account Aggregator and DPDP consent flows before 13 May 2027.