Plaid Won’t Connect Your Bank? 11 Fixes and Alternatives

Your app uses Plaid to pull in your bank, and one day it just won’t. Usually it’s an authentication mismatch, not a breach. Here are 11 fixes and 6 alternatives.

You open your budgeting or payment app, tap to refresh, and the bank connection spins forever before coughing up “couldn’t connect to your institution.” It is one of the most common and most anxiety-inducing fintech snags, because for a second you wonder if something is wrong with your money. Almost always, nothing is. Plaid sits between your app and your bank, and when the two sides disagree about how you should log in, the handshake breaks. Here is what actually causes it, how to fix each case, and the connectors that keep working when Plaid will not.

Quick Answer

Most Plaid failures trace to a short list of causes: a changed password, a multi-factor setup Plaid cannot handle, a bank that moved to OAuth, an unsupported institution, or a plain outage. Check status.plaid.com first, make sure your phone and email on file at the bank are current, complete any approval your bank app is waiting on, and then remove and re-add the connection. If your bank simply will not cooperate with Plaid, many apps can connect through other aggregators like MX, Finicity, or Akoya, and manual or direct import is always there as a fallback that never fails.

Why Plaid connections break

Plaid is a middleman. It carries your login to your bank, verifies you, and passes read-only account data back to the app you are using. Banks keep changing how they authenticate you, adding device approvals, new multi-factor steps, and OAuth login screens, and every change is a chance for the handshake to fail. That is why a connection that worked for a year suddenly stops: your bank changed something, not you. It is rarely a security incident, which is the first thing worth telling yourself before you work through Plaid’s own connection troubleshooting steps.

11 errors that break Plaid, and the fix

1. A changed or wrong password. If you recently updated your bank password, Plaid is still using the old one. Re-enter your current credentials and reconnect.
2. Incompatible multi-factor authentication. Plaid cannot handle every MFA type, including some that demand a one-time code at every single login or use image-based prompts. Check your bank’s security settings for an app-approval or authenticator option instead.
3. Outdated phone or email for codes. Plaid pulls your contact details from the bank, so if your number is stale, the verification code never reaches you. Update it in your bank’s profile, then retry.
4. An unfinished app approval. Many banks now push an approval to their mobile app. If you did not tap it in time, the flow stalls. Approve the prompt, then immediately reconnect.
5. An OAuth redirect that didn’t complete. Banks on OAuth send you to their own login page in a popup. If it is blocked or you close it early, the link fails. Allow popups, skip incognito mode, and finish the bank’s login screen fully.
6. An unsupported institution. Plaid covers many thousands of banks, but some small banks and credit unions are only partly supported or not at all. If yours is not covered, manual import is your route in.
7. A bank or Plaid outage. Sometimes the problem is not you. Check status.plaid.com and your bank’s status page, and if either is down, wait it out rather than re-trying on a loop.
8. A lockout from too many attempts. Repeated failed connects can trip your bank’s security and freeze the login. Stop retrying, log into your bank directly to confirm you are not locked, then reconnect once.
9. Browser blocking the flow. Ad blockers, strict privacy settings, or blocked third-party cookies can break the connection window. Temporarily relax those or try another browser for the link step.
10. An expired connection. Old links time out and need refreshing. Remove the institution from your app and add it again to mint a fresh connection.
11. A bank limiting aggregator access. A few large banks throttle or restrict third-party access, so certain connections stay flaky no matter what. When that is the case, switch to an alternative connector or fall back to manual import.

6 alternatives that still sync

You usually cannot pick the aggregator yourself, since the app chooses it, but knowing the landscape helps you find an app that connects your bank, or a fallback that always does.

• MX. Uses multi-source aggregation, so it can fall back to another connection method when the primary one degrades.
• Finicity. Owned by Mastercard, with direct agreements at major banks that tend to be more stable than the industry average.
• Yodlee. One of the broadest footprints in the business, useful when your institution is obscure.
• Akoya. A direct, tokenized API backed by banks that shares data without storing your password, which makes it both stable and privacy-friendly.
• Teller or Stripe Financial Connections. Direct-API connectors that skip screen-scraping, so they break less often at supported banks.
• Manual or direct import. The fallback that never fails: download a CSV or statement from your bank and import it, or use your bank’s own export. Less automatic, but bulletproof.

This article is general information, not financial advice, and connection behavior changes over time. Only enter your bank credentials inside your app’s official connection screen, never through a link someone sends you, since fake “connect your bank” pages are a common phishing tactic. When in doubt, contact your bank or the app’s support directly.

Frequently Asked Questions

Why did Plaid suddenly stop connecting to my bank?

Usually because your bank changed something: a new password, a new multi-factor step, or a move to OAuth login. A connection that worked for months can break the moment the bank updates its security, and it is rarely a sign of a breach.

Is it safe to reconnect after an error?

Yes, as long as you do it inside your app’s official connection screen. Never enter bank credentials through a link from an email or message, since phishing pages often imitate the connect flow.

How do I know if the problem is on Plaid’s side?

Check status.plaid.com and your bank’s status page. If either reports an outage or maintenance, the fix is to wait, not to keep retrying, which can lock your account.

What if my bank isn’t supported by Plaid?

Some smaller banks and credit unions are only partly supported or not at all. In that case, look for an app that uses a different aggregator, or use manual CSV import, which works with any bank.

Can I choose a different aggregator than Plaid?

Not directly, because the app picks it. But different apps use different aggregators like MX, Finicity, or Akoya, so switching apps, or using one that offers manual import, can get your bank connected.

Does re-linking delete my transaction history?

Usually not. Most apps keep imported history when you refresh a connection, but check your specific app before removing an institution, and export a backup if the data matters to you.

Final Takeaway

A dead bank connection feels alarming, but it is almost always a login mismatch, not a money problem. Work the list in order: check for an outage, update your bank contact details, finish any approval, clear browser blockers, and re-link once rather than hammering the button. If a stubborn bank keeps refusing Plaid, remember you have options, other aggregators through other apps, and manual import as the fallback that always works. For more on the tools behind your accounts, see our picks for apps to manage your money and how to budget on an irregular income.