Budgeting App Not Connecting to Bank? Start With Day 90

A budgeting app not connecting to your bank almost never means the app is broken. Nine times out of ten the connection did exactly what the rules tell it to do: it reached the end of its 90-day consent window and stopped pulling data until you said yes again. The app then shows you a stale balance, a half-empty transaction list or a red “reconnect” banner, and it looks like a fault. It is a deadline.

Knowing which of the four possible failures you have got saves you from the thing most people do next, which is delete the connection and start again. That is the slowest fix and it usually loses your transaction history.

The four things that actually break

Work through these in order. They are ranked by how often they are the answer, not by how easy they are.

1. Your 90-day consent expired. The app can see the account but the data stopped on a specific date. Symptom: balances frozen on one day, no error message from your bank.
2. You revoked access at the bank without meaning to. Symptom: the account vanishes from the app entirely, or the app reports access denied straight away.
3. The bank’s authentication handoff failed. Symptom: you tap connect, the screen bounces to a browser or your banking app, and you end up back where you started with nothing changed.
4. The bank’s open banking interface is genuinely down. Symptom: it fails for every app, and direct login to the bank works fine.

The 90-day rule, and what changed in 2022

This is the part most help pages get wrong, so it is worth being precise.

Until 2022, UK open banking made you re-authenticate with your bank every 90 days to keep a budgeting app connected. It was a full login and security check, four times a year, per bank. Drop-out was brutal: one trade body put customer attrition at 20 to 40 per cent at each 90-day mark.

The FCA changed it in policy statement PS21/19, which came into force on 26 March 2022. The rule now lives in Article 10A of the UK SCA-RTS, and it moved the 90-day job from the bank to the app. You no longer log in to your bank every quarter. Instead your budgeting app has to ask you, every 90 days, to reconfirm that you still want it reading your accounts. A yes or no, inside the app. Open Banking Ltd’s summary of the change is here.

Three consequences that explain almost every “it just stopped” complaint:

• If you ignore the prompt, access stops. Not ending the consent, just suspending it. The app must not pull data, but it can keep nudging you, and the moment you reconfirm, data resumes. That is why a connection can sit dead for weeks and then spring back to life without you touching your bank.
• The prompt comes from the app, not the bank. If you have push notifications off for your budgeting app, or the email went to promotions, the first you know is a frozen balance.
• The initial connection still needs full bank authentication. The 2022 change removed the quarterly bank login, not the first one.

The industry’s own consent dashboard standard requires apps to show you, per connected bank, the date reconfirmation is due, the last successful sync, and a status of either Active or Reconfirm. If your app follows it, that screen tells you in five seconds whether day 90 is your problem. Look for it under settings, connected accounts, or data sharing.

Fix it in this order

Step one: read the app’s own connection screen. Find the last sync date. If it is roughly 90 days after you first connected, or 90 days after your last reconfirmation, you have found it. Tap reconfirm and you are done in one screen, with your history intact.

Step two: log in to your bank directly, on its website, not its app. This separates “the bank is having a bad day” from “the link is broken”. If the bank’s own site will not let you in, nothing else you do will work.

Step three: check the bank’s access dashboard. Every UK bank covered by open banking has to show you a list of the third parties reading your data, under a name like “data sharing”, “connected apps”, “third party access” or “manage open banking”. If your budgeting app is missing from that list, the consent was revoked rather than expired, and you need a fresh connection rather than a reconfirmation. Our guide to revoking open banking access has the exact menu path for the major banks, and it works just as well read backwards.

Step four: fix the handoff, not the app. If the connect flow dies halfway, the failure is usually in how your phone hands you between the app and the bank:

• Use Chrome or Safari, fully updated. Some bank authentication screens quietly fail on older or unusual browsers.
• On Android, check that your browser is allowed to open supported links. Settings, then Apps, then your browser, then the setting for opening supported links. With it off, your banking app will not launch when it should.
• Make sure your banking app is installed, updated and already logged in before you start.
• Chase UK connects only app to app. It will not authorise through its website. If the flow tries to open a browser for Chase, that attempt is going nowhere.

Step five: stop trying. Repeated failed attempts can get you temporarily blocked at the bank end, which turns a small problem into a locked door. Two attempts, then leave it a few hours.

Reconnect or remove and re-add?

Reconnect if the app offers it. Removing and re-adding is a last resort, and here is the trade-off nobody warns you about: a fresh connection usually pulls a limited window of history, often 12 or 24 months, and your older transactions, categories and manually split entries may not survive the round trip. Some apps keep the archived data, some do not.

So: reconfirm first, reconnect second, remove and re-add only when the account has actually disappeared from the app or the bank’s dashboard.

One genuine reason to re-add rather than reconnect is an account migration. Halifax customers moved onto Lloyds infrastructure, for example, have ended up with a connection pointing at a bank entry that no longer matches their account. If your account number is right but the bank brand on the connection looks wrong, re-add it under the correct bank.

When it is the bank, not you

If every app fails at the same bank at the same time, the bank’s open banking interface is down and the only fix is waiting. Banks publish availability and performance statistics for their open banking APIs, usually on a developer or open banking page on their own site, and those pages will tell you about planned maintenance windows before you waste an evening on it.

This is also the honest answer to a question worth asking before you pick an app at all: the app cannot be more reliable than the banks it connects to. If your bank is the flaky one, no budgeting app will rescue it. Our rundown of budgeting apps that connect to UK banks covers which ones handle reconnection gracefully.

Frequently asked questions

Why does my budgeting app keep asking me to reconnect every three months? Because UK rules require it. Since March 2022 your app must get your explicit reconfirmation every 90 days to keep reading your accounts. It is one tap inside the app, not a full bank login, and if you miss it the data pauses rather than disappearing.

Will reconnecting my bank delete my transaction history? Reconfirming consent will not. Fully removing the connection and adding it again often will shorten your history, because the new consent typically pulls only a fixed window of past transactions. Always try reconfirm or reconnect before you delete.

My bank is not listed in the budgeting app. Why? Open banking coverage is not universal. Business accounts, some savings and credit products, and smaller providers are often outside the scope your app supports. Check the app’s supported institutions list before assuming a fault.

Is it safe to reconnect a budgeting app to my bank account? Reading access through open banking is read-only and does not let the app move money. You keep a revocation switch at the bank as well as inside the app. The risks are worth understanding properly, which we cover in are budgeting apps safe.

Why did the connection work on my laptop but not my phone? Usually the app-to-app handoff. Your phone either cannot launch the banking app from the browser, or the browser is not permitted to open supported links. On desktop there is no handoff to fail, which is why it works there.

How long should I wait before trying again after a failed connection? A few hours. Consecutive retries can trigger a temporary block at the bank, and that block lasts longer than the original outage would have.