Table of Contents
- What is screen scraping in banking, step by step
- Screen scraping vs. a bank-approved connection
- Why some apps still ask for your bank password
- The risks, in plain terms
- How to tell which method an app is using
- If you have already shared your bank password with an app
- The limits of this article
- Frequently asked questions
What is screen scraping in banking? It is the method where you type your real online-banking username and password into a third-party app, and that app then uses automated software to sign in to your bank as you and copy what it sees, such as balances and transactions. Your bank did not build the connection and often cannot tell the app apart from you. It works, which is why some apps still use it, but it leaves a full copy of your banking login outside your bank.
If an app has ever asked for your actual bank password and it felt wrong, that instinct was worth listening to. This article explains what screen scraping is, how it differs from newer permission-based connections, why it has not disappeared, and how to tell which method the app in front of you is using. It is general information, not advice about your own accounts.
What is screen scraping in banking, step by step
The name describes the method quite literally. The app reads your bank's screens the way a person would, only automatically.
- You enter your bank username and password, and sometimes the answers to your security questions, into a login form inside the third-party app.
- The app, or a data company working behind it, stores those details.
- Software signs in to your bank's website on your behalf, as if it were you at a keyboard.
- It reads the pages that load, picks out the numbers and text it wants, and copies them into the app.
- It repeats this on a schedule, which is why the app keeps your login rather than using it once.
To your bank, that session can look like you logging in. That is the core of the issue: the app is not using a door the bank built for it. It is using your door, with your key.
Screen scraping was not invented by scammers. It was the practical way early budgeting tools, account aggregators and some lenders' affordability checks got hold of bank data before banks offered anything better. Legitimate companies used it, and some still do. The problem is structural, not a question of whether a particular company means well.
Screen scraping vs. a bank-approved connection
The alternative is a connection through an API (application programming interface), a controlled channel the bank itself provides. Under that model you are sent to your own bank to sign in, the bank asks you to approve specific access, and the app receives a limited permission rather than your password. The practical differences look like this:
| Question | Screen scraping | Bank-approved (API) connection |
|---|---|---|
| Where you type your bank password | Inside the third-party app | Only on your bank's own website or app |
| Who holds your login afterward | The app or its data provider, as well as you | Only you |
| What the app can see | Anything you can see when logged in | The data you agreed to share |
| How you stop it | Change your password and ask the app to delete what it stored | Withdraw the permission, often from your bank's settings |
| Does your bank know an app is involved | Often not | Yes, the app identifies itself |
| What happens when you change your password | The connection breaks | Usually nothing, because the app never had it |
The last row explains a lot of everyday frustration. If an app "disconnects" every time you update your banking password or your bank redesigns its website, there is a good chance it relies on scraping, because it depends on your exact login and on the layout of your bank's pages.
Why some apps still ask for your bank password
If a safer method exists, why does anyone still ask for credentials? There are a few reasons, and none of them requires the app to be a scam.
Your account type may not have an approved connection. Open-banking rules usually cover particular kinds of accounts. In the European Union and the UK, the second Payment Services Directive (PSD2) requires banks to give authorized third parties a compliant way into payment accounts, typically an API, and those third parties must identify themselves with a recognized certificate. Accounts outside that scope, such as some savings, investment or pension accounts, may have no bank-built connection at all, so an app that wants to show them may fall back on scraping.
Your country may not have a finished framework yet. In Canada, the Department of Finance says on its Budget 2025 page on consumer-driven banking, which we read on September 24, 2026, that "about nine million Canadians currently share their financial data by providing their confidential banking credentials in a process known as screen-scraping." The same page says a prohibition on screen scraping will come into force once the new framework is fully operational, with the timeline still under consultation.
In the United States, the Consumer Financial Protection Bureau's page on reconsidering its personal financial data rights rule, read the same day, shows the Bureau issued an advance notice on August 22, 2025 seeking comment on how its section 1033 data-access rules should work. The rulebook there is still being settled. Australia offers a contrast: its Consumer Data Right, described by the Australian Competition and Consumer Commission, lets banks transfer data to accredited recipients with the customer's consent, with the customer choosing what to share and for how long.
Older integrations are slow to change. Some services built their connections years ago and move to newer methods one bank at a time. An app can use approved connections for one bank and scraping for another, and you may not be told which is which unless you look.
The honest summary: screen scraping shrinks where regulators have built an alternative, and it persists where they have not, or where an account type falls outside the rules.
The risks, in plain terms
The risk is not that every scraping app will misuse your data. It is what the arrangement creates, whatever the app intends.
A second copy of your full login. Your banking credentials now live in two places, and you control only one. If the app or its data provider is breached, the leaked item is not an app password. It is the key to your bank account. That is the same logic behind keeping your banking password unique and stored somewhere safe, which is what a password manager for banking protects: every extra place your real credentials live is another target.
Access you cannot narrow. Logging in as you means seeing everything you can see. There is no way to tell a scraping app "balances only."
A possible effect on your fraud protection. Canada's Department of Finance, on the page cited above, says people sharing credentials "face increased security, liability, and privacy risks and may be left without recourse if something goes wrong." Your own bank's account terms may include rules about sharing your security details, and whether sharing affects a claim depends on those terms and on your country's rules. The reliable answer is in your account agreement or from your bank.
A habit criminals can exploit. Once people are used to typing their bank password into any screen that asks, a fake "connect your bank" page becomes easier to fall for. Criminals who collect banking logins this way can use them for account takeover fraud, where someone else controls your account using details you handed over.
How to tell which method an app is using
This is the part most explanations skip, and it is the most useful thing you can check. It takes no technical knowledge, only attention to where things happen.
- Where does the login box appear? If you are sent to your bank's own website or your bank's own app to sign in, that is the pattern of an approved connection. If the password field sits inside the third-party app, even with your bank's logo on it, that is the pattern of credential sharing.
- What exactly is being asked for? An approved connection asks you to confirm access on your bank's side. A request to type your password into the app, to answer your bank's security questions for the app, or to pass along a one-time code is a different arrangement.
- Is there a consent screen from your bank? Approved connections usually show you, on the bank's side, what is being shared and for how long.
- Can you see the connection afterward? Many banks list approved third-party connections in their settings so you can remove them. A scraping app will not appear there, because to the bank it is simply you.
- Does the app say so? Some apps state which method they use for each bank. If the help pages and privacy policy are silent, the app's support team can be asked directly.
One firm rule sits above all of these: a request for your bank password or a one-time security code that arrives by call, text or email, rather than inside a process you started yourself, is not how either method works. That pattern belongs to fraud. One-time codes exist to prove it is you, and our guide to two-factor authentication for banking explains why passing those codes to anyone undoes the protection.
If you have already shared your bank password with an app
This is common and not a reason to panic. What comes next depends on whether you still trust and use the app.
If the app is a service you chose and still use, reasonable questions include whether it now offers an approved connection for your bank, what its privacy policy says about how it stores credentials, and what your bank's terms say about sharing them. If you no longer use it, people commonly close their account in the app, ask the company to delete stored data, and change their banking password so any stored copy stops working. Your bank can tell you how it treats credential sharing on your specific account.
If you shared your details with something you now suspect was not genuine, such as a fake app, a caller, or a website reached through a link, treat it as a possible compromise rather than a privacy question. Our guide on what to do if you gave your bank details to a scammer walks through the first steps, starting with contacting your bank through a number you find yourself.
The limits of this article
FinMateMastery is not an authority, and this is general information, not financial or security advice for your situation. Open-banking rules differ by country and are changing, so the position where you live is set by your own financial regulator and your bank's terms, not by us. Where we quote an official source, we give the date we read it, because that date is part of the answer.
Frequently asked questions
Is screen scraping illegal?
Not as a general rule. Screen scraping has long been a common way for apps to collect bank data with a customer's permission. Some places restrict it or plan to: Canada's Department of Finance says a prohibition will take effect once its consumer-driven banking framework is fully operational, and EU and UK payment rules require third parties accessing payment accounts to identify themselves to the bank. Your bank's own terms may also limit sharing your login.
Is screen scraping the same as open banking?
No. Open banking usually means regulated, permission-based data sharing where you sign in with your bank and the app receives limited access without your password. Screen scraping is the older method it is designed to replace, where the app holds your password and logs in as you.
How can I tell if an app uses screen scraping?
The clearest sign is where you type your password. If the login field is inside the third-party app, the app is likely storing your credentials. If you are sent to your bank's own site or app to approve access, and the connection later appears in your bank's settings, that is the pattern of an approved connection.
What happens if I change my bank password after using a screen-scraping app?
The app's stored copy stops working, so the connection breaks until you enter the new password again. Whether that is what you want depends on whether you still use the app and whether it offers a safer connection method for your bank. If you suspect the app or the request was not genuine, your bank is the place to call, using contact details you find yourself.