Three different financial institutions all requested re-authorizations today

clinc

I download transactions almost every day and almost never have FIs required re-authorization. Today, Chase, Charles Schwab, and Capital One all requested re-auth, with error code FDP-350.

It seems rather suspicious. Is this normal?

Quicken for Mac Business & Personal version: 8.1.2

MacOS 15.4.1

Double-A

I had the same problem. When I searched I found this "parallel" thread:
https://community.quicken.com/discussion/comment/20487435#Comment_20487435?utm_source=community-search&utm_medium=organic-search&utm_term=re-authorization+Schwab

Apparently, resetting the account has worked for some. « Edit Account/Online Services/Reset Account »
I will try it myself tonight

clinc

https://community.quicken.com/discussion/comment/20487800#Comment_20487800

Thanks for the link @Double-A. It's good to see that others have reported similar problems. Apparently, resetting the accounts is only a temporary fix.

Quicken Anja

Hello @clinc,

We appreciate you reaching out regarding this issue!

Please be aware that the link @Double-A provided is from a Windows thread.

I took the liberty of reviewing your account and was able to confirm that you are receiving the FDP-350 error internally as well. If you haven't already, please take a moment to review the information and follow the guidance found in this support article regarding error FDP-350.

Hope this helps!

clinc

Hi @Quicken Anja

Thanks for the link to the support article. I know how to re-authorize FI access, but was somewhat reluctant to do so because it seemed suspicious that 3 different FI accounts would all require reauthorization on the same day. I was just checking to see if other users are experiencing the same thing.

Anyway, I've thrown caution to the wind and reauthorized all 3 accounts, and transaction downloads are again working.

Thanks again for your help.

Quicken Anja

Thanks for the update! Glad to hear they are working again. 🙂

clinc

Hi @Quicken Anja

Unfortunately the reauthorization only worked for one day. I tried downloading transactions today and got the same re-auth errors as before. 🙁

Let me know if you'd like me to send any diagnostic data.

Quicken Anja

@clinc Thanks for following up, though I am sorry to hear that the issue has returned.

Yes, please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute to the investigation.

It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue.

We apologize for any inconvenience in the meantime! Thank you.
(CBT-665)

clinc

@Quicken Anja - Problem report and sanitized data file sent.

@Quicken Jasmine - I saw that you had added and removed a comment yesterday which suggested this might be caused by a token issue. If you still think that's a possibility, please let me know how to resolve it.

Thanks to you both!

Quicken Anja

@clinc Thanks for submitting. I will get that added to the ticket.

Thanks again!

Quicken Jasmine

https://community.quicken.com/discussion/comment/20488003#Comment_20488003

Hello @clinc,

Below are the instructions that I originally shared!

It sounds like this may be a token issue. To resolve it, I recommend deactivating all Chase/Charles Schwab/Capital One accounts, unlinking them from Quicken on the Chase website, and then re-adding them in Quicken. Follow these steps in order:

Step 1: Deactivate All Accounts in Quicken

1. Go to Accounts > Hide and Show Accounts and ensure no Chase accounts are hidden.
2. Open each Chase account register.
3. Click the Settings gear in the bottom-right corner.
4. Navigate to the Downloads tab and select Disconnect Account (repeat for each Chase account).
5. Quit Quicken.

Step 2: Remove Credentials from Keychain

1. Open Spotlight (small magnifying glass in the top-right corner).
2. Search for Keychain Access and open the app.
3. On the left panel, select Login, then choose Passwords at the top.
4. Search for Chase/Capital One/Charles Schwab and delete any entries that say "Quicken password for [your insert username] at Blank FI".
5. Quit Keychain Access.

Step 3: Unlink the affected Financial Institutions from Quicken on their Websites

1. Log into your Chase/Capital One/Charles Schwab accounts online. (Note: these instructions are specific to Chase's website, other financial institutions may differ.)
2. Click on the menu bar in the top left corner.
3. Go to Security & Privacy.
4. Click on Linked Apps & Websites.
5. Find and select Quicken, then click Stop Sharing Data.

Step 4: Re-add Accounts in Quicken

1. Reopen Quicken.
2. Go to Accounts > Add Account.
3. Use the search field to locate the financial institutions, then click Continue.
4. Follow the prompts to sign in using your login credentials.
5. If Quicken finds your accounts, use the dropdown menus to link them to the correct accounts in Quicken.

Once you’ve completed these steps, let me know if you're still experiencing issues. Hope this helps!

clinc

Hi @Quicken Jasmine

Thanks for the instructions for resolving a token issue. I've followed them but note that Step 2 doesn't match the instructions:

- The Password app doesn't have a Login selection in the left panel, nor can you choose Passwords at the top. I selected All instead.

- The search for Chase/Capital One/Schwab found only my logins for those FI websites. There were no entries that said "Quicken password for [your insert username] at Blank FI".

 After disconnecting, unlinking, and re-adding all the accounts, the account updates appeared to compete successfully.

I'll try again tomorrow to see if it's still working!

clinc

@Quicken Jasmine Good news - transaction downloads are still working today!

clinc

@Quicken Jasmine Today my Chase account, but not Schwab or Capital One, required reauthorization. I'll report back if there are more reauthorization requests.

Quicken Jasmine

Hello @clinc,

Fantastic, thank you so much for coming back to update us!

Please let me know if the issues return!

Quicken Kristina

Hello @clinc,

To assist with the investigation, please confirm a bit more information. Do you have the problem accounts connected in more than one Quicken file? Did restoring a backup seem to trigger this issue?

I look forward to your replies!

clinc

@Quicken Kristina Yes, I have several FI accounts connected in multiple Quicken files. (I use extra Quicken files for Beta testing). I haven't recently restored any backup files.

Let me know if you need any further info.

Quicken Kristina

Thank you for the additional information,

Sometimes, having accounts that use OAuth (OAuth accounts are the accounts that you have to authorize through the financial institution website during the add account process) connected in multiple files can cause this problem. If the issue returns, please try limiting the problem account(s) to just one Quicken file, and test to see if that resolves the issue.

Thank you!

clinc

@Quicken Kristina Thanks, I'll try limiting OAuth accounts when I can. For Beta testing though, I often need the same OAuth accounts authorized in both my beta test file and my production file.