When Stash is not working, work from the outside in: your phone or browser first, then the app, then your connection, then your account, and only then the company. Most problems are fixed in the first three steps, and writing down what you tried makes the fourth one much faster. Stash is a name used by more than one product, so this article stays with method and does not describe any particular app's screens.
What should you try in the first five minutes?
- Close the app completely and open it again. A frozen screen is often just a stuck session.
- Check you are online by loading any other page or app. If that fails, the problem is your connection, not Stash.
- Switch between Wi-Fi and mobile data once. Some networks block certain services.
- Update the app from your store and restart the phone.
- Try the same login in a browser or on a second device. If that works, the fault is local to the first device.
How do you tell an app fault from an account fault?
| What you see | Likely side | First thing to try |
|---|---|---|
| App opens, then closes at once | Phone or app version | Update, restart, free some storage |
| Spinner that never ends | Connection or server | Change network, try again later |
| Login rejected on every device | Account | Use the app's own reset route, never a link from a message |
| Works on web, fails on phone | App on the phone | Reinstall after noting any unsynced entries |
| Numbers look old | Sync | Pull to refresh, check the last updated time |
What if the data looks wrong rather than missing?
Take a screenshot with the date and time visible, then compare it with your own bank or card statement. Statements are the record you control. If a balance or a transaction differs, note the date, the amount and the reference, because support will ask for exactly those.
Worked example: a log that gets an answer
Say you try to log in at 9:10 pm and see an error. You write: 9:10 pm, Wi-Fi, app version unknown, error text copied. At 9:20 you switch to mobile data, same error. At 9:30 the web version also fails. Three attempts across two networks and two surfaces point away from your phone and towards the service or your account. That is a useful message to send: three attempts, two networks, the exact error wording and the time of each. Compare it with 'it is not working', which gets a standard reply asking you to do those same checks.
Should you keep your own copy of your records?
Yes. Whatever tool you use, keep monthly statements from your bank or card as your own source of truth. If a service goes down, you can still see what happened to your money. If you want a tracker that works from those statements, SpendixAI takes uploaded PDF, CSV or Excel files, with no bank connection and no net-banking login. That is a different approach from an app that links to accounts, so choose the one that suits how you work.
When should you contact the company?
- The same error on two devices and two networks.
- Money has moved but the app does not show it, and your statement confirms it.
- You lost access and the app's own recovery route did not work.
- Include the time, the exact error wording and the transaction reference or amount.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

