Why Is Plaid Not Connecting To My Bank? | What Usually Fails

Plaid sits between your bank and the app you’re trying to use. That middle position is handy when it works and maddening when it doesn’t. A failed connection can come from the bank, the app, the Plaid flow, or the account itself. That’s why the same “couldn’t connect” message can mean four different things.

Most readers want one thing: a clear fix. Start here. If your bank login works on the bank’s own site, you finish every security step, and Plaid still won’t link, the snag is often tied to bank-side access rules, a stale consent session, or an account type that the app can’t pull from yet.

Why Is Plaid Not Connecting To My Bank? Common Triggers Behind The Error

The usual causes fall into a small set of buckets. Once you know which bucket you’re in, the fix gets much faster.

• Bank-side changes: the bank changed its login flow, added a fresh security wall, or paused third-party data access for a while.
• Credential trouble: a saved password is old, your bank wants a one-time code, or you need to verify a device before Plaid can pass through.
• Consent trouble: you signed in, but the permission screen was skipped, timed out, or was approved for the wrong account scope.
• Account mismatch: the account exists, but the app may only accept certain account types, owners, or data products.

When The Bank Is The Bottleneck

Banks change things all the time. A new login page, a fresh security question, a short maintenance window, or a tighter rule around third-party access can break a Plaid connection even when your username and password are correct. That’s why the bank site can look fine to you while the app still throws an error.

Some banks also split access by product. A checking account may connect for balance data, yet the same institution may not pass payroll, investments, loans, or business accounts into the app you picked. That can make Plaid look broken when the real snag is narrower than that.

When The Login Or Consent Step Fails

A Plaid connection is not always a plain login. Many banks now send you through a consent page or an outside bank window. If that handoff loops, times out, or drops you back into the app without a clean finish, Plaid may never get the green light it needs. On your screen, that can look like a random failure. In practice, it’s often a half-finished authorization.

You can also hit a dead end when the app requests access to one kind of data and the bank approval screen grants another. The sign-in worked, yet the app still can’t use the account. One clue helps here: if the link dies before account selection, think login or consent. If it dies after account selection, think account class, product scope, or an expired authorization.

Plaid Bank Connection Problems That Keep Coming Back

Connection errors often repeat in patterns. If you match the pattern, you can skip a lot of guessing.

What you see	What it often means	What to try next
“Invalid credentials” after a login that seems right	Your bank password changed, the username format is different, or a saved credential in the app is old	Sign in on the bank’s own site first, then enter the same details again in the app
The bank keeps asking for a code, then returns you to the start	The extra verification step is not finishing cleanly	Approve the code on the same device, avoid switching tabs, and retry from a fresh session
Your bank is missing from search	Plaid may have pulled it from search for a while, or the institution is not available for that app’s setup	Retry later and check whether the app offers manual verification
You reach the bank page, then land back in the app with no linked account	The consent handoff expired or the bank did not return a usable authorization	Close the app, reopen it, and start the link flow again from scratch
Only one account shows up even though you have several	The app may only pull from certain account types or ownership setups	Pick a different eligible account or ask the app which account classes it accepts
The app says the institution is unavailable	The bank connection may be degraded or down for a while	Wait and retry later instead of hammering the same login over and over
A connection worked last month but fails on refresh	The prior consent expired or the bank wants you to reconnect	Use the app’s reconnect flow instead of adding the bank as a brand-new account
The bank links in one app but not another	The failing app may ask for a different data product or have a stale Plaid item on file	Remove the old connection in that app and link again

Plaid’s institution status notes show when a bank connection is degraded. Plaid also explains on its consumer connection page that banks can change login flows, pause access, or disappear from search until the link is stable again. If you’re dealing with one stubborn bank, Plaid’s US and Canada Coverage page can show whether that institution and product pairing is available at all.

Steps That Fix Most Plaid Bank Connection Failures

You do not need ten random retries. A clean sequence works better.

Start At The Bank, Not Inside The App

1. Sign in on the bank’s own website or mobile app first.
2. Clear any alerts there, such as a password reset, a fresh terms screen, or a request to verify your device.
3. Log out of the bank site.
4. Return to the Plaid flow and try again.

This simple reset catches a lot of hidden blocks. If the bank wants you to accept fresh terms or clear a fraud check, Plaid cannot do that part for you.

If The Bank Uses OAuth

Some banks send you to their own page or app to approve access. Stay in that flow until it sends you back. Don’t close the browser midstream. Don’t jump between devices. And if the bank asks which accounts to share, pick the ones the app can actually use. A skipped checkbox can leave you signed in but still unlinked.

Reset The Session And Pick The Right Account

Next, clear out the stale session. Close the app, reopen it, and start a fresh bank link instead of tapping retry five times in a row. If the app already has an old bank item saved, remove that broken link first when the app gives you that choice.

Then check the account itself. Some apps only work with personal checking accounts. Others accept savings, credit cards, or joint accounts. If the app shows one account but not another, that’s a clue that the problem is with account eligibility, not your login.

If the app offers manual bank verification, use it. That path is slower, but it can get you past a bank login flow that keeps failing. It also helps when one data method is down but account and routing details still work.

If this happens	Best next move	When to stop retrying
You get the same bank outage message twice	Wait a few hours and retry once	After that, leave it alone until the bank window passes
Your password works on the bank site but not in the app	Delete the saved link in the app and add the bank again	If the same error returns after a clean relink
The consent page loops back to the start	Retry on the same phone and browser session	If the loop repeats after one fresh attempt
Your bank vanished from Plaid search	Use manual verification or wait for the bank to return	Right away; repeated searches will not force it back
Only business or loan accounts are failing	Ask the app which account classes it accepts	Once you confirm that account type is not allowed

When The Problem Is Not On Your Side

Sometimes you’re doing every step right and the fault still sits elsewhere. Banks can pause outside connections during maintenance. Plaid can mark an institution as degraded. The app can ask Plaid for a data product your bank does not hand over. None of that is fixed by typing your password again.

There are a few clues. If multiple Plaid-powered apps fail with the same bank on the same day, the bank-Plaid link is a likely suspect. If one app fails and another app works, the snag may be tied to the failing app’s setup. If your bank site works, Plaid sign-in works, and only one account class is missing, the app may not accept that account type yet.

• Likely bank-side snag: the bank login works, but several Plaid-powered apps fail.
• Likely app-side snag: the bank links elsewhere, but one app keeps rejecting it.
• Likely account-side snag: your business, loan, trust, or joint account will not appear.
• Likely consent snag: the flow keeps bouncing between the bank page and the app.

When you reach out for help, ask for the exact connection error shown in the app. That wording matters. “Institution unavailable,” “reconnect required,” and “no eligible accounts” point to three different fixes. A screenshot helps too, since one missing line on the error screen can tell you where the break starts.

What To Do Next

Start with the bank site. Clear any password, device, or terms prompts there. Then run one fresh Plaid connection, finish the bank approval flow on the same device, and pick the account type the app accepts. If the bank is down or missing from search, stop retrying and wait. If one app fails while another works, the app’s setup is the better place to push for a fix.

That pattern is the whole story: confirm the bank login, finish the consent flow, match the right account, and avoid endless retries during an outage. Once you sort those four points, most Plaid connection failures stop being mysterious and start looking like a plain routing problem with a plain fix.