Some apps ask for your net-banking login so they can sign in as you and read your account pages, a method called screen scraping. It is convenient, but it hands the app the same keys you use, and banks commonly warn customers never to give those keys to anyone. A statement you download yourself gets you the same transactions without handing anything over.
What is screen scraping, in plain words?
Picture someone who logs in to your bank on your behalf, opens the pages that list transactions and copies the numbers down. A scraping app does that automatically. To do so it has to know your user name and password, and often the one-time code your bank texts you. In effect, it acts as you.
Why would an app want to work this way?
- It lets the app show transactions without waiting for you to upload anything.
- It avoids building a formal connection with each bank.
- It looks smooth in a demo: type your login once and see your data.
The convenience is real. The question is what you risk in exchange.
What can go wrong when you hand over a login?
| Risk | What it means for you |
|---|---|
| Too much power | A login is not limited to reading. Whoever holds it may be able to do whatever the login allows |
| Storage | The app must store or handle your credentials, and a leak at the app exposes your bank access |
| Code requests | Apps that ask for one-time codes teach you to type them into places other than the bank |
| Dispute trouble | Banks may treat a shared login as a breach of the account terms; check your own bank's terms and what that could mean for a dispute |
| Hard to undo | Changing your credentials fixes it, but you may not know when the exposure began |
Is there a safer way to get the same data into an app?
Yes. Download the statement yourself and give the app the file. You stay in control of what leaves your bank, and the app never touches your login. The trade-off is timing: entries arrive when you upload, not the instant you pay.
How do you download a statement step by step?
- Sign in on your bank's own app or site, typing the address yourself or opening the app you installed from the official store.
- Open the account statement section and pick the account.
- Choose a period. Months are easiest, such as the 1st to the last day.
- Choose a format. PDF reads well for people; CSV or Excel is often easier for an app to import if your bank offers it.
- Download the file, rename it with the account and month, and sign out.
- Upload the file to your tracker, review the rows and save.
Layouts differ between banks, so look at your own statement and your bank's help pages if you cannot find the option.
Some apps blur the line by describing the connection in friendly words, such as secure link or instant sync. Ignore the wording and look at what you are asked to type. If the screen is a bank login that is not your bank's own site or app, or if it asks for a code, you are being asked to give credentials to a third party.
How does SpendixAI handle this?
SpendixAI never asks for net-banking logins and has no bank connection. You upload statements as PDF, CSV or Excel, pick the account first, and review the rows before they are saved. Sign-in is through Google, so there is no separate password to create either.
What if you already typed your login into an app?
- Change your net-banking credentials straight away, through your bank's official option.
- Look through recent transactions for anything you do not recognise.
- Call your bank on a number printed on your card or on its official site, explain what happened and ask what they advise.
- Remove the app's access and delete your account in the app if possible.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

