Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsTo revoke an India Account Aggregator (AA) consent, return to the AA app or web portal where you approved it, open Consents or a similarly named management screen, select the lender or other Financial Information User (FIU), check the purpose and data permissions, and choose Revoke. RBI rules also require AAs to support revoking only parts of the information covered by a consent artefact. Revocation stops future fetching under that consent; it does not automatically cancel a loan application or guarantee immediate deletion of data already delivered.
What an Account Aggregator consent controls
India’s Account Aggregator framework lets a person instruct one regulated intermediary to move financial information from a Financial Information Provider (FIP) to a Financial Information User (FIU). A bank, mutual-fund platform, insurer or other institution can be an FIP. A lender, broker, insurer or similar service requesting the information is the FIU. The AA does not use your credentials to let the FIU log in to your bank; it brokers an authorised transfer under a digital consent artefact.
As an Amazon Associate I earn from qualifying purchases.
The consent artefact records the boundaries of that transfer. Depending on the request, it can specify the purpose, the categories of information, the period of historical data, whether data may be fetched once or repeatedly, how often recurring requests are allowed, when the consent expires and how long the FIU may use information it has already received. Those fields determine what a service can ask for and when it must stop asking.
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, including the ability to revoke consent to obtain parts of that information. Sahamati describes the same principle plainly: all consent provided through AA is designed to be revocable. Your AA’s labels and screen layout can differ, but the control should be available in the AA app or web portal used for approval.
#1 Best Overall
Choose the right action: revoke, narrow or wait for expiry
Revoking is not the only way to reduce access. The best choice depends on whether the request is still waiting for your approval, whether the FIU needs another fetch, and whether a live application depends on the data.
| Situation | Usually appropriate action | What to check first |
|---|---|---|
| The request is pending and asks for more data than the service needs | Reject it or edit it to narrower consent values before approving | Purpose, data categories, historical range and fetch type |
| You no longer want the FIU to obtain anything under an active consent | Revoke the entire consent | FIU name, consent identifier, expiry and recent request log |
| You want to stop only one account, category or period | Use the AA’s partial-revocation control, if offered | Which information elements the artefact covers and what replacement artefact is issued |
| The service is almost finished and no further pulls are expected | Allow the consent to expire, or revoke if you want access stopped now | Expiry date and any recurring fetch schedule |
| A loan, insurance or brokerage workflow is still in progress | Ask the FIU what an interruption will do, then revoke or narrow deliberately | Whether the FIU can complete the process offline and what data it has already received |
Expiry is passive: access ends when the recorded end date arrives. Revocation is active and takes effect when the AA processes it. If you are concerned about an unexpected recurring pull, do not wait for expiry; revoke and retain the confirmation.
Step-by-step: revoke an existing consent
The following sequence applies across the RBI/Sahamati ecosystem. Menu names vary by AA, so use the closest equivalent label rather than looking for one universal screen.
- Find the AA you used. Check the approval notification, email, SMS or the lender’s application history. The message normally identifies the AA and may include a consent reference.
- Sign in with the linking mobile number. Use the same mobile number that was verified when the financial account was connected. A different number can open an empty profile even when the consent exists.
- Open consent management. Look for Consents, Manage consents, Consent history or an equivalent item in the account or privacy menu. Sahamati says the AA app should show consents that were given, revoked consents and a log of data requests made by the FIU.
- Select the correct FIU. Match the lender, broker, insurer or other requester, then compare the displayed purpose, consent date, expiry and consent identifier with your notification or application record. Do not revoke a similarly named request by mistake.
- Read the permission details. Expand the consent to see the data categories, historical date range, fetch type, frequency and data-life terms. This confirms whether the concern is a one-time request or recurring access.
- Choose the full-revocation control. It may be labelled Revoke consent, Withdraw or Stop access. Confirm the warning. A successful revocation should produce an on-screen confirmation and an entry in revoked-consent history.
- Save evidence. Download the consent record or data-flow history when available, or capture a screenshot showing the consent identifier, timestamp and revoked status. Keep the FIU’s confirmation as well if it sends one.
- Check the request log later. The log should no longer show new fetches under that consent. A delayed display update is possible; if a new request appears after the revocation time, contact both the AA and the FIU’s grievance officer with the saved evidence.
Revoking through the AA is the primary route because the AA controls the consent artefact. You can also tell the FIU directly. For example, Zerodha states that when a client revokes through the FIU, it must immediately notify the AA and desist from further fetching through that consent. An FIU-side request should therefore be reflected in the AA’s records; verify that it is.
Rank #2
Revoke only part of the information
RBI’s rule is broader than an all-or-nothing switch. Clause 6.6 expressly includes revoking consent to obtain parts of the information covered by the artefact. Depending on the AA and the original request, a partial control may let you remove a linked account, a data category or a portion of the approved period while leaving another portion available.
How partial revocation normally works
- Open the active consent and choose an option such as Edit permissions, Limit access or Revoke selected information.
- Untick the account, information type or date segment you no longer want shared.
- Review the revised purpose, fetch type, frequency and expiry. Removing one element should not silently expand another.
- Confirm the change and record the new consent identifier or revision number.
RBI’s direction says that after revocation, a fresh consent artefact is shared with the Financial Information Provider. In practical terms, the FIP should receive the updated permission boundary rather than continue using the old one. If your AA offers only a full-revoke button, revoke the whole consent and ask the FIU to issue a new request containing only the necessary information; do not assume that deleting an account from a local app list changed an active artefact.
Partial revocation changes future access. It does not retroactively erase a statement or transaction that the FIU already received. Ask the FIU how it handles previously delivered information and check its retention notice for the applicable purpose and legal obligations.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Limit a consent before you approve it
The safest time to reduce exposure is the approval screen. Sahamati’s Fair Use consent attributes identify the fields that should be reviewed. Templates set upper bounds, not targets: an organisation should select lower, more conservative values whenever its service can work with them.
| Consent field | Safer setting when possible | Why it matters |
|---|---|---|
| Purpose | Approve only a clearly stated purpose that matches the service you requested | A vague or broader purpose makes it difficult to judge whether every requested category is necessary. Reject an unexplained purpose. |
| Consent type | Choose profile or summary information instead of transaction-level data when that is sufficient | Transaction data can reveal detailed spending, counterparties and timing. The service may not need that level of detail. |
| Fetch type | Prefer one-time fetching when recurring monitoring is unnecessary | One-time access avoids an open-ended schedule of later pulls. |
| Data range | Set the shortest historical period that supports the application | A two-month income check does not automatically justify years of statements. Inspect the start and end dates before approving. |
| Fetch frequency | Choose the minimum monthly or other interval needed | Lower frequency reduces the number of fresh requests and limits how often changing financial activity is exposed. |
| Consent validity | Set the shortest useful validity and avoid a distant expiry | Validity controls how long the FIU can request data under the artefact, not merely when the first fetch occurs. |
| Data life | Check and minimise the period for which the FIU may use data already fetched | Stopping new pulls does not necessarily end use of information already delivered. This field addresses that separate period. |
Do not confuse an upper limit in a consent template with a requirement. If a lender’s form preselects a long history or recurring frequency, look for an edit control; if none exists, ask the FIU why the wider permission is needed and whether it can issue a narrower artefact.
Example: turning a recurring request into one-time access
Suppose an insurer needs proof of premium payments. If the approval page offers transaction data for 24 months with monthly fetching until a distant expiry, first change the data type to the least detailed option that proves payment, set a short date range, select one-time fetch, and choose a near-term expiry. If the service refuses those values, you can decline the request and ask for an explanation before sharing.
What revocation changes—and what it does not
What stops
- The FIU should not make additional data requests through the revoked consent.
- The AA should record the consent as revoked and show that status in consent history.
- Recurring schedules attached to that artefact should no longer authorise new fetches.
- For a partial revocation, the withdrawn information elements should no longer be available under the revised artefact.
What may continue
- A completed underwriting, onboarding or brokerage decision is not automatically undone. The decision may already have used information lawfully delivered before revocation.
- Revocation does not guarantee immediate deletion of data already delivered. Retention can depend on the service purpose and applicable law.
- The underlying bank or investment account remains open. Revoking AA access is not the same as closing that account or cancelling a product.
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. That may mean providing documents through another channel, changing the assessment path or stopping the application; the result is a matter between you and the FIU. Ask for the practical consequence before revoking a consent that an active application still depends on.
Free tools Windows power users keep installed
One-click scans. No signup required.
Zerodha’s published AA terms illustrate the separation between access and retention: it says it must stop further fetching after revocation, while retaining AA data only as long as necessary for the stated purpose unless law requires longer retention. Other FIUs can have different lawful retention duties, so read the relevant notice rather than assuming one universal deletion deadline.
How to stop repeated checks by a lender
Repeated checks normally indicate a consent with recurring fetch type or frequency. Open the consent detail and look for a schedule, such as monthly access, along with the validity end date. If you no longer want monitoring, revoke the full consent. If you still need the service but not continuous access, use partial controls if available or ask the FIU to replace the artefact with a one-time request.
After confirming revocation, inspect the AA’s data-request log rather than relying only on a push notification. Record the last authorised fetch and the revocation timestamp. A request that was initiated before revocation may appear as a completed transfer; distinguish that from a new request made afterward. For a post-revocation request, send the consent identifier, screenshots and timestamps to the AA and the FIU grievance officer and request a written explanation.
If you cannot find the consent
- Search the original communications. Use the AA name, the FIU name and terms such as “consent” or “data request” in email and SMS search. Check the lender’s application history as well.
- Try the correct identity. Sign in to the AA with the mobile number used during linking. If you changed numbers, follow the AA’s account-recovery process instead of creating a second profile.
- Check every history view. Look under Consents, Manage consents, Consent history, notifications and data-request logs. A revoked item may be filtered out of the active list but remain in history.
- Match the details. Compare the FIU, purpose, dates and expiry. A consent can be easy to miss when the FIU’s legal name differs from its consumer-facing brand.
- Preserve records. Download the consent and transaction or data-flow history where the AA or FIU provides it. Save the consent identifier and the date you attempted revocation.
- Escalate a missing or failing control. Contact the AA support channel and the FIU’s grievance officer, quoting the identifier and date. RBI requires customers to be told of their right to complain when consent is obtained, so use the complaint route shown in the consent or service notice.
If the app reports success but the consent remains active after you sign in again, do not repeatedly approve or edit it. Capture the error, device and time, then request confirmation of the revocation status from both parties. Keep copies until the request log reflects the change.
Revocation versus delinking an account or deregistering from an AA
Revoking a consent is a targeted action: it stops one FIU from obtaining information under one artefact. Delinking a bank or other financial account removes that account’s connection from the AA profile, which can affect future requests involving that account. Deregistration is broader and can involve delinking connected accounts and revoking active consents.
Use full deregistration only when you want to leave the AA service and have checked the effect on every active application. Zerodha’s terms, for example, describe deregistration by delinking connected accounts and revoking active consents, subject to applicable law. A single lender problem normally calls for revoking or narrowing that lender’s consent, not deleting every connection.
Keep a privacy record after changing consent
- Write down the AA, FIU, consent identifier, original purpose, approval date and expiry.
- Save the before-and-after permission details, including data range, frequency and data-life terms.
- Record the revocation time and the confirmation screen or message.
- Review the data-request log for activity after that time.
- Keep any grievance reference number and the FIU’s response.
This record helps separate three events that are often confused: the last fetch authorised before revocation, the point at which future fetching had to stop, and the FIU’s separate retention or deletion duty for information it already received.
How large the AA ecosystem is
The Department of Financial Services’ 2026 progress update reports the following ecosystem counts. They describe live participation at that time, not a guarantee that every provider is available in every AA app or that every account type can be shared.
| Measure | Reported 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 participation and interfaces change, a missing menu or unavailable account type can reflect provider support rather than a permanent loss of your right to revoke. Ask the AA and FIU to identify the consent record and the supported revocation route.
Questions to settle with the FIU before revoking an active application
- Has the FIU already completed its decision using data delivered under this consent?
- What exact step will fail if no further fetch is possible?
- Can you supply the remaining information offline, and through which secure channel?
- What data has already been retained, for what purpose and for how long?
- Will the FIU issue a replacement consent with one-time access, a shorter range or fewer categories?
These questions do not remove your right to revoke. They let you choose between an immediate stop, a narrower replacement or an expiry date with a clear understanding of the service impact.
Limits of what any AA screen can promise
The AA interface can control consent-based fetching, display status and provide records. It cannot by itself reverse a decision already made from lawfully received information, impose one universal retention period on every FIU or guarantee that a separate copy held under a legal duty is deleted immediately. The sources available for this guidance do not establish one universal screen sequence or an immediate deletion deadline for data already delivered. Confirm those details with the specific AA and FIU handling your consent.
The practical rule is therefore precise: use the AA’s consent-management function to stop or reduce future access, use the FIU’s grievance route when a request continues or a workflow is disrupted, and keep the consent and data-flow records needed to prove what changed and when.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →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.
