1/30: Nationwide Annuity has not worked in Quicken for Mac for several days
Nationwide Annuity download is providing an error. Care Code: FDP-155 (see attached). Have gone to Nationwide site and there is no reference to issue. Any insight?
Also, for several months there are repeated days where downloads show a $0 value. Any insight?
Thank you
Comments
-
Update, please see most recent error message. Thank you.
1 -
Hello @bmilewski82,
We currently have a known issue reported with this financial institution that has been escalated internally, though we do not have an ETA on resolution at this time. While the investigation remains ongoing, please refer to this Community Alert for any and all available updates.
We apologize for any inconvenience in the meantime! Thank you.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
@bmilewski82 I've had the same problem, though I'm able to login to my account via a browser to confirm all is well there.
0 -
Same issue here it hasn't worked for quite some time. When I first set up the account it was completely functional and displayed the correct info. It now says $0 is in the account. For many months, it would connect and update the info once again to $0. Now it cannot connect at all. It has not worked properly for at least a year for me, even though nothing has changed on my end as far as account credentials or anything else. Disappointing.
0 -
Hello - Just spoke with a representative at Nationwide - according the her, Nationwide no longer supports any external access to 3rd party platforms (like Quicken) due to security issues. Is this true? Thank you.
1 -
I believe they told you that, but if true, that's a really poor way to treat customers by pulling this feature without informing them first.
0 -
FWIW, I've been able to connect to Nationwide for the last 3 days now. I haven't seen any updates from Quicken reflecting this on the other thread on this change.
0 -
Thanks! Just checked and it's working again.
1 -
Quicken Jasmine You posted an update on the related thread reporting that this is still a problem, but two of us have reported the issue seems to have been resolved (can't reply to the other thread, so I'm commenting here instead).
0
