iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To revoke an India Account Aggregator (AA) consent, open the AA app or web portal where you approved it, go to the consent-management area, select the consent for the relevant Financial Information User (FIU), check its purpose and scope, and choose Revoke. You can also revoke only parts of the information covered by a consent artefact. If the request is still pending, limit the purpose, data type, date range, fetch frequency, validity period and data-life settings before approving it.
Revocation stops future fetching under that consent. It does not automatically cancel a loan or card application, and it does not establish that data already delivered has been erased immediately. The lender or other FIU may need to continue the process offline, while retention remains subject to the stated purpose and applicable law.
What an Account Aggregator consent controls
India’s Account Aggregator framework lets an individual instruct one financial institution to share financial information with another through a consent artefact. The institution holding the information is the Financial Information Provider (FIP); the lender, broker, insurer or other requester is the Financial Information User (FIU); and the AA presents the request, records your choice and facilitates the exchange.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A consent is more specific than a general permission to “see your bank account.” Its artefact can describe the requester’s purpose, the categories of data, the historical period, how often data may be fetched, when the consent expires and how long the FIU may use information it has already received. Those values determine whether the request is a one-time statement retrieval or continuing access for repeated checks.
#1 Best Overall
The scale of the ecosystem is substantial. A 2026 Department of Financial Services progress update records the following figures:
| Measure | Figure | Qualification |
|---|---|---|
| Financial Information Providers live | 179 | Department of Financial Services progress update, 2026 |
| Financial Information Users live | 989 | Department of Financial Services progress update, 2026 |
| Financial accounts enabled to share data | More than 2.88 billion | Department of Financial Services progress update, 2026 |
| Accounts linked by users | 284.6 million | Department of Financial Services progress update, 2026 |
Because the AA is the place where the permission is represented, changing a bank’s password or deleting a lender’s app does not revoke an AA consent. You must change the consent in the AA service, or use an FIU-provided revocation route that notifies the AA.
How to revoke an existing consent
Labels differ between AA providers, but the sequence is consistent. Use the mobile number and account profile that you used when linking your financial accounts.
- Open the AA service that displayed the approval. Launch its app or sign in to its web portal. If you do not remember the name, search the lender’s emails, SMS messages and application history for the consent notification or AA name.
- Open consent management. Look for Consents, Manage consents, Consent history or an equivalent menu. Sahamati says the AA app should show consents that were given, revoked consents and a log of data requests made by the FIU.
- Identify the correct request. Match the FIU name, stated purpose, data categories, date range, fetch frequency and expiry. If several requests exist for the same lender, use the consent identifier and dates rather than revoking by name alone.
- Review the effect. Confirm that you are acting on the consent for the account and service you intend to change. A lender may have separate artefacts for different applications or products.
- Choose Revoke. Confirm the action when the AA asks. RBI Master Directions clause 6.6 requires an AA to provide a function to revoke consent to obtain information made accessible by a consent artefact.
- Save the confirmation. Keep the revocation timestamp, consent identifier and any confirmation screen or message. Download the consent and data-flow history if the AA offers those options.
RBI’s requirement expressly includes partial control: “An Account Aggregator shall also provide its customers a functionality to revoke consent to obtain information that is rendered accessible by a consent artefact, including the ability to revoke consent to obtain parts of such information.” That means the available control may be a whole-consent revocation, a category-level choice, an account-level choice or another partial selection defined by the artefact.
How to revoke only part of the information
Use the consent detail screen to see whether the AA exposes individual information elements. Depending on how the artefact was created, you may be able to remove a particular account, data category or other portion instead of cancelling everything.
Rank #2
- Open the active consent and select Edit, Limit, Revoke selected information or the equivalent control.
- Clear the account or information categories you no longer want the FIU to obtain.
- Read the revised scope and check that the remaining purpose, date range and frequency still match the service.
- Confirm the partial revocation and save the resulting record.
RBI’s directions require that, after revocation, a fresh consent artefact is shared with the FIP. In practical terms, the data provider receives an updated permission rather than continuing to rely on the old scope. If your AA shows only a single Revoke all control, contact that AA and the FIU to ask what partial revocation options their implementation supports; do not assume that deleting a linked account has the same legal effect.
How to limit a consent before approving it
If the request is still waiting for your approval, narrowing it is usually cleaner than approving a broad permission and revoking it later. Treat every field as a boundary, not a target. Sahamati identifies these as Fair Use consent attributes and says its templates set upper bounds; organisations should select lower, more conservative values when their purpose allows.
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 →| Consent field | Safer choice when possible | Question to ask before approving |
|---|---|---|
| Purpose | Reject an unclear or broader-than-necessary purpose | Does this explain the exact service I requested? |
| Consent type | Choose profile or summary data instead of transaction data when that satisfies the service | Does the FIU really need individual transactions? |
| Fetch type | One-time fetch where recurring monitoring is unnecessary | Is a single statement enough to complete the task? |
| Data range | The shortest history that supports the decision | How far back does the FIU actually need to look? |
| Fetch frequency | The minimum monthly or other recurring frequency needed | What event requires another pull, and how often? |
| Consent validity | The shortest useful validity period | When should this permission end if I take no action? |
| Data life | The shortest period the FIU may use data already fetched | How long does the organisation need to retain or use the delivered data? |
For example, a service that needs one recent income statement does not automatically justify transaction-level access, a long historical range or recurring monthly fetches. If the FIU cannot explain a field in plain language, pause the approval and ask what decision depends on it.
What revocation changes—and what it does not
It stops future consent-based fetching
Once the AA records the revocation and communicates the changed consent state, the FIU should not continue fetching through that consent. Sahamati describes revocation as cutting off access to the data covered by the permission. A regulated FIU example, Zerodha, states that it must immediately notify the AA when a client revokes through the FIU and desist from further fetching through that consent.
It does not automatically reverse a completed decision
Revocation is not a universal “undo” button for underwriting, brokerage onboarding or another decision already made using data that was validly supplied. Sahamati says that if an individual revokes before a loan cycle is complete, the lender needs to engage with the borrower offline to find a remedy. Ask the FIU whether it can complete the application using documents or another verification method, and request that answer in writing.
It does not establish immediate deletion of delivered data
Stopping a future pull and deleting information already received are separate questions. The available guidance does not establish one universal deletion deadline for every FIU. Retention can depend on the original purpose and applicable law. Zerodha’s terms, for example, say AA data is retained only as long as necessary for the purpose, except where law requires otherwise. Read the FIU’s privacy and retention terms and ask how your already-fetched data is handled.
Will revoking consent cancel a loan or card application?
Not automatically. The application’s status depends on the FIU’s process and on whether the required verification has already been completed. Revocation prevents additional AA fetching, but an FIU may still have enough information to decide, may ask for documents, or may be unable to finish the automated workflow.
Before revoking an active application, use this sequence:
- Record the application number, the FIU, the consent identifier and the consent’s current status.
- Ask the FIU which step still requires AA data and whether one-time documents can replace a future fetch.
- Ask whether revocation will pause, decline or merely move the application to manual handling.
- Keep the FIU’s response and any document-submission instructions.
- Revoke in the AA only after deciding whether the privacy benefit outweighs the possible interruption, unless you are revoking because the request is unauthorised or materially broader than agreed.
If you revoke during a loan cycle, Sahamati’s stated position is that the lender must engage with you offline to find a remedy. That does not guarantee approval or a particular turnaround time; it means the lender should provide a path that does not depend on continuing access under the revoked consent.
How to verify that a lender has stopped fetching
Do not rely only on a toast message or a closed application screen. Verification should use the records the AA and FIU make available.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Reopen the consent list and confirm the status is Revoked or equivalent, with a timestamp.
- Check the AA’s data-request or transaction log for requests made before and after revocation.
- Look for a new consent artefact if you made a partial change; the old scope should not remain the active permission.
- Ask the FIU to confirm that it has stopped fetching under the consent identifier.
- Save screenshots or downloads showing the consent, revocation and subsequent data-flow history.
A later request may be legitimate if you approve a new consent artefact with a different identifier. Compare the new purpose and scope rather than assuming every request is a continuation of the revoked one.
What to do when you cannot find the consent
- Search the originating messages. Check email, SMS and the lender’s application history for the AA name, consent notification, purpose or identifier.
- Use the original mobile number. Sign in to the AA profile used during account linking. A different number can open an account with no matching history.
- Check every consent view. Review active consents, history and revoked consents; labels vary by provider.
- Match details before acting. Compare the FIU, purpose, expiry and data categories so that you do not revoke an unrelated application.
- Preserve records. Download or capture the consent and request history where offered.
- Escalate with identifiers. If the request is missing or revocation fails, contact the AA and the FIU’s grievance officer. Quote the consent identifier, date, FIU name and the error you saw.
RBI requires customers to be told of their right to complain when consent is obtained. If support does not resolve the issue, use the grievance route identified in the AA or FIU’s consent and privacy information and retain the complaint reference.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choosing between revoke, narrow and expiry
The right action depends on whether access is still needed and how much exposure you are willing to leave in place.
| Choice | Use it when | Main effect | Check first |
|---|---|---|---|
| Revoke entire consent | You no longer want the FIU to obtain any further information under the artefact | Stops future fetching for the whole consent | Whether an active loan or service workflow will move offline |
| Revoke part of consent | You still need the service but no longer accept one account or information category | Removes the selected portion and leads to a fresh consent artefact | Whether the remaining scope still satisfies the FIU’s stated purpose |
| Narrow a pending request | You have not approved the request yet | Creates a smaller permission from the start | One-time versus recurring access, historical range, validity and data life |
| Let it expire | The service is nearly complete and you are comfortable waiting for the stated end date | Access ends at expiry under the artefact’s terms | Whether the date is too distant and whether recurring pulls continue until then |
Evaluate six questions in order: does the requester need one-time or recurring access; how much historical data is necessary; how often will data be fetched; how long should the consent remain valid; how long may the FIU use information already fetched; and could a revocation interrupt an active workflow?
Recommended Free Tools
Provider-specific handling and deregistration
Some FIUs provide their own revocation control in addition to the AA interface. Zerodha’s published terms say a client can access consent and subsequent data-flow records, raise a grievance with its grievance officer, revoke any consent and deregister by delinking connected accounts and revoking active consents, subject to applicable law. This is an example of one regulated FIU’s process, not a universal screen sequence for every AA participant.
If you use an FIU-side control, confirm that it identifies the same consent artefact and that the AA status changes. If you want to leave the AA service entirely, deregistration may require both delinking accounts and revoking active consents; complete those actions only after checking whether another service still relies on a separate, valid consent.
Record-keeping and privacy checks
A short record makes disputes and support requests much easier. Keep:
- the AA name and the mobile number used for the profile;
- the FIU name, application or service purpose and consent identifier;
- the approved data categories, account scope, date range, fetch frequency and expiry;
- the date and time of full or partial revocation;
- screenshots or downloaded consent and data-flow history;
- the FIU’s retention explanation and any grievance reference.
Store these records securely because they can contain account identifiers or sensitive financial context. Do not send complete statements or screenshots to an unverified support address; use the AA or FIU contact details shown inside the authenticated service.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Important limits of the process
India’s AA ecosystem is implemented by multiple providers, so menu names, login flows and the granularity of partial revocation can differ. The sources describing the framework do not establish one universal screen sequence or an immediate deletion deadline for information already delivered. Confirm those details with the AA and the FIU involved.
The durable rule is narrower: an AA consent is designed to be revocable, and RBI requires the AA to support revoking the whole consent or parts of the information made accessible by its artefact. Use the AA’s consent and request records to confirm the change, and treat any effect on an active financial application as a separate conversation with the FIU.
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.
