QuickBooks Error 179 -- Bank Feeds Login Rejected

QuickBooks Error 179 blocks Bank Feeds when your bank rejects cached credentials; our engineers walk through clearing the mismatch and reconnecting.

QuickBooks Error 179 interrupts a Bank Feeds session when the financial institution's website refuses the login QuickBooks is attempting on your behalf. The error halts downloads and updates until the credential mismatch is resolved and the connection is re-established.

What the Error Message Says

The message typically appears as:

"QuickBooks Error 179: Your financial institution's website is temporarily unavailable or has rejected your login."

In some Bank Feeds modes the wording is shorter — "Error 179: Please try again later" — but the underlying cause is the same: the bank side of the handshake failed.

What the Code Means

Error 179 is a Bank Feeds authentication failure. QuickBooks stores a token or cached credential set for each connected account and uses it to silently sign in to your bank's download portal. When the bank rejects that credential — because the password changed on the bank site, a session expired, or the cached token became stale — QuickBooks surfaces Error 179 rather than prompting for a fresh login.

What Triggers It

• Password changed on the bank website. You updated your online banking password outside of QuickBooks, so the cached credential no longer matches.
• Bank-side security challenge. The bank is requiring a one-time passcode, security question, or CAPTCHA that QuickBooks cannot answer automatically.
• Expired or revoked session token. The bank timed out the persistent login or you manually revoked third-party access from the bank's security settings.
• Account lockout. Repeated failed silent logins triggered the bank's fraud protection and temporarily locked the account.
• Bank maintenance or outage. The download portal is down, but QuickBooks interprets the non-response as a login rejection.
• Multiple accounts under one bank profile. One account credential changed while others remained unchanged, confusing the Bank Feeds refresh cycle.

How to Fix It

Scenario 1 — Password changed on the bank website (most common)

1. Open a browser and sign in to your bank's website manually using the new password. Confirm you can reach the account dashboard without any security prompts.
2. In QuickBooks, go to Bank Feeds > Bank Feeds Center.
3. Select the affected account and click Edit > Edit Account Information.
4. Re-enter your bank username and the new password.
5. Click Update Now to trigger a fresh sign-in and download.

Scenario 2 — Bank-side security challenge

1. Log in to the bank website directly and clear any pending alerts, messages, or required security acknowledgements.
2. If the bank offers a "remember this device" option, enable it for the computer running QuickBooks.
3. Return to the Bank Feeds Center and click Update Now.
4. If the bank requires step-up authentication each session, switch that account to Direct Connect or Web Connect downloading as a workaround.

Scenario 3 — Expired or revoked session token

1. Sign in to the bank's website and navigate to the security or connected-apps settings page.
2. Confirm that QuickBooks or the bank's data service is still listed as an authorized application. Re-authorize if necessary.
3. In QuickBooks, deactivate Bank Feeds for the account (Edit > Preferences > Checking > Company Preferences > Deactivate).
4. Reactivate Bank Feeds and walk through the connection wizard, entering credentials fresh.

Scenario 4 — Account lockout

1. Attempt to log in to the bank website. If the account is locked, follow the bank's unlock procedure (typically a password reset or callback verification).
2. Wait for the lockout period to clear if the bank imposes a timed hold.
3. Once access is restored, update credentials in QuickBooks as described in Scenario 1.

Scenario 5 — Bank maintenance or outage

1. Check the bank's status page or support line for planned maintenance.
2. Wait until the bank confirms service is restored.
3. Retry the Bank Feeds update. No QuickBooks-side changes are needed.

Scenario 6 — Multiple accounts under one bank profile

1. In the Bank Feeds Center, review each account tied to the bank.
2. Update credentials for every account that shares the changed login, even if only one account is erroring.
3. Send a single combined update for all accounts under that financial institution.

How to Prevent It Recurring

• Whenever you change your bank password, update the credential in QuickBooks the same day before the next scheduled download.
• Avoid enabling aggressive multi-factor prompts on the bank profile for the machine that runs QuickBooks; use trusted-device settings where available.
• Run Bank Feeds updates at least weekly so session tokens stay active and do not expire from inactivity.
• If your bank frequently challenges logins, consider switching to Web Connect (downloading a QBO file from the bank website and importing it manually) to bypass the silent-login cycle entirely.