Fidelity Reauthorization - Two sets of credentials

System
System Member admin
This discussion was created from comments split from: Quicken requests account re-authorization for Fidelity on every one step update.

Comments

  • Matthew Boone
    Matthew Boone Quicken Windows Subscription Member ✭✭
    edited September 23

    This has become a nightmare. Longtime Quicken user. Since the autherization requirement appeared, I can no longer successfully update both my and wife's long standing fidelity accounts. If I try and authorize her accounts, quicken seems to be unable to download information for mine. If I authorize my accounts, it produces an error trying to download via one step update information for hers. Deactivating each account, and reactivating each one at a time doesn't help. Still takes you through the authorization step, and then doesn't recognize the others during one-step update. [Removed-Speculation]

  • Matthew Boone
    Matthew Boone Quicken Windows Subscription Member ✭✭

    Something has fundamentally become broken since the 'authorization step' just went live.

  • Quicken Alyssa
    Quicken Alyssa Quicken Windows Subscription Moderator mod

    Hello @Matthew Boone,

    Thank you for expressing your concerns and frustrations, I am happy to help.

    Are you and your wife authorized users on each others bank accounts? If so, what could be happening is you are authorizing all of the accounts (both hers and yours) when using your credentials, and/or authorizing all of the accounts (both hers and yours) when using her credentials.

    Basically this would cause an issue because many financial institutions do not allow you to add accounts into Quicken that you are only an authorized user for. To resolve it, you would need to ensure you are only selecting your accounts when authorizing with your credentials. And then doing the same when using your wife's credentials.

    Hope this helps!

    Quicken Alyssa

    Make sure to sign up for the email digest to see a round up of your top posts.

This discussion has been closed.