Find Connected Apps First
Open banking consent revocation usually starts where connected accounts are listed, either in the payment app or bank dashboard. Review active permissions, identify the app, and choose revoke or disconnect. The bank may ask for confirmation, then remove access tokens and stop data sharing. Some systems require logging into the bank portal, especially when consent was granted through a regulated interface. After revocation, pending payments or scheduled transfers may still complete if already authorized, so check transaction status before assuming everything stops. Save confirmation messages, because support teams may need evidence if an app continues requesting data.
Also worth reading: How Do AI Agent Payment Policy Controls Protect Everyday Wallets? · What Is the Best Stablecoin Payment Processor for Everyday Merchants in 2026? · How Do You Build an Offline Seed Phrase Backup That Survives Everyday Payment Use?
Next, remove the app’s stored credentials and unlink saved cards or accounts in its settings. Revoke recurring payment mandates separately if the app created them, since data consent and payment authorization are often separate. Monitor bank alerts for a few days and contact support if new requests appear. If reconnecting later, expect fresh consent screens and stronger authentication. On shared devices, sign out everywhere and update passwords. Keeping a simple record of connected apps helps prevent forgotten access and speeds future cleanup.
Check Consent Scope Details
Open banking consent revocation usually begins inside the payment app, where users review connected accounts, data permissions, and active payment mandates before choosing to withdraw access. The app should clearly show which services stop, whether pending payments remain, and how long cached transaction data may be retained. If the app cannot complete revocation directly, it should route the user to the bank or consent dashboard with a clear explanation of what changes and what does not.
After revocation, users should confirm that recurring payments, account aggregation, and third-party data sharing have actually stopped, then monitor statements for unexpected activity. Good apps provide confirmation messages, audit trails, and support paths for disputes. Because rules vary by market, consumers should check local open banking requirements, bank terms, and app privacy notices before relying on a single button. Keeping screenshots and revocation timestamps can help if a merchant or provider later claims consent remained active.
Revoke Access In App
Open banking lets payment apps pull account data or initiate payments only after you grant explicit consent. To revoke it, start inside the app: open settings, find connected accounts or data sharing, and remove the bank link. Most apps stop new data pulls immediately, though pending transactions may still settle. Also check your bank's portal, where many institutions list third parties with access and let you cut them off in one tap. Doing both ensures neither side keeps a stale token.
If the app ignores your request, contact the provider in writing and ask for confirmation that consent is revoked and data deleted where required. Regulators in several markets now expect dashboards that make this process obvious, with firms honoring revocation within a short window. Keep screenshots and confirmation emails, because disputes about lingering access are easier to resolve with proof. Treat consent like a subscription: review it quarterly, revoke what you no longer use, and never assume deleting an app alone ends the connection.
Confirm Removal In Bank Dashboard
Open banking consent revocation usually begins inside the payment app or the bank dashboard, where a user selects the connected service and confirms removal. The app may show which accounts, scopes, and recurring permissions are affected, then send a revocation request to the bank or aggregator. Some providers require an additional identity check, such as biometric approval or a one-time code, before the link is disabled. Users should review pending payments, scheduled transfers, and saved payees because revocation can stop future access without canceling transactions already initiated.
After confirmation, the bank should display a clear status showing the connection is removed, and the app should no longer retrieve balances or initiate payments. If the dashboard still lists the service, refresh the page, sign out, or contact support rather than assuming the link is gone. Keep screenshots or confirmation numbers, especially when switching wallets or closing an account. Reconnecting later usually requires fresh consent, so treat revocation as a deliberate reset of data sharing rather than a temporary pause.
Monitor Future Payment Requests
Open banking consent revocation usually begins inside the payment app that holds your permission. Look for connected accounts, data sharing, or permissions settings, then remove the bank link, pause access, or delete the consent. The app should stop requesting new data or initiating payments after that change. Also check your bank’s connected apps or security settings, because some providers require a second confirmation before the link fully closes. Save confirmations and note the date, since revocation may not cancel pending transactions or scheduled payments immediately.
If a payment is already processing, revocation generally affects future requests, not completed transfers. Review recurring subscriptions, wallet top-ups, and merchant checkout links separately, because each may use its own consent token. For shared accounts, make sure every authorized user understands the change so no one reauthorizes the same app. When uncertain, contact both the app and your bank, and ask whether residual permissions, cached tokens, or backup access paths remain active. Treat revocation as a process to verify, not one button press, especially when money movement is involved.
Revocation Methods Compared
| Step | Action | Result |
|---|---|---|
| 1 | Open the app's connected-accounts settings | View active bank connections and scopes |
| 2 | Select the bank connection to revoke | App sends revocation request to bank API |
| 3 | Confirm in app or bank portal | Consent token invalidated; sharing stops |
| 4 | Verify in bank's consent dashboard | No residual access remains |