Why Bank Connections Break (and What Plaid Actually Does)

Every app that shows you your own bank data — Seven Financial included — sits on top of an aggregator, and the most widely used one is Plaid. Understanding what that layer does explains both why linking is safe and why connections still break routinely. The short version: breakage is your bank ending a session, and the only real danger is an app that hides it from you.

What Plaid actually is

Plaid is a connection service that sits between apps and roughly twelve thousand financial institutions. When you link a bank, you authenticate with the bank — either on the bank's own login page (OAuth, the modern path) or in a Plaid-hosted form. The app you're using never sees your username or password. What it receives is an access token: a credential that can read balances and transactions for the accounts you approved, and do nothing else.

Read-only is a property, not a promise

"This app can't move your money" isn't a policy statement — it's what the token is capable of. A read-only Plaid token has no ability to initiate payments, trades, or transfers, no matter what the app that holds it does. That's the correct security posture for a tracking tool: the worst-case outcome of a compromise is that someone sees your data, not that someone drains your accounts. It's also why you should be suspicious of any tracking app that asks you to type bank credentials into its own screens.

Why connections break anyway

• You changed your bank password — every session dies, including Plaid's.
• Your bank demanded a fresh MFA challenge that only you can answer.
• The consent you granted had an expiry date (common with OAuth banks) and it lapsed.
• The bank changed something on its side, and the connection needs to be re-established.

None of these are errors, exactly — they're your bank doing its job. A linked account is a session with your bank, and sessions end. Expect a reconnection every few months per institution and it stops being alarming.

The failure that actually matters: stale data served as fresh

When a connection breaks, syncing stops, but the last-known balances are still sitting in the app's database. The dangerous behavior is displaying them as if they were current. You glance at the app, see a comfortable checking balance from nine days ago, and make a decision on it. For a finance app, silently serving stale data is the worst failure mode there is — strictly worse than showing an error.

So the thing to demand from any tool in this category is loud staleness: a visible banner the moment a connection breaks, a timestamp on the data, and a one-tap path to reconnect. Seven Financial tracks the health of every connection on every sync, tells you the moment one needs attention — including a push notification, since a broken link means your alerts are flying blind too — and keeps your history intact when you relink. Connections breaking is routine. Not being told is the bug.