As of 4/13/2022, Quicken is no longer connecting, (Express
Web Connect), to Pacific Service Credit Union, (PSCU). When attempting to log in to PSCU, I receive
no 2nd factor authentication “send to” request nor does any 2nd
factor entry point appear, as had been expected. Instead, the One Step Update, (OSU), Summary shows
error code CC-502, for my two accounts from this Financial Institution, (FI).
When I looked at the Quicken Users Forum this morning, I see
that @Quicken_Anja added a new alert on this issue: NEW
4/14/22 Pacific Service Credit Union - 502/102. Thank you, Anja.
My experience is using Quicken for Windows, Home &
Business, Build 27.1.39.23, of the Subscription software. This on an LG gram 17, Model
17Z90N-R.AAC8&1 computer, 16 GB RAM & a 2TB Samsung EVO SSD, running
Windows 10 Pro, Version 21H2, Build 19044.1645,
Experience Pack 120.2212.4170.0.
PSCU downloads were working without issue through
4/9/22. My “One Step Update Summary”
shows the last online balance downloaded on 4/9/22. The “Account List” shows the “last download”
as 2:41 PM on 4/10/22. This error has
been observed during OSUs on 4/13, 4/14, and 4/15. Repeated requests to update just the PSCU
accounts, from either of the two accounts, does not result in a download or resolve
the issue.
Note that the 2nd factor login step was added
within the last year or so, but has been working OK since then, until now. The user enters a “second factor” code into a
drop down box, and that information is presumably used to grant the user’s
request to login to their account and download data. I have not seen the expected
request for a phone number or location to send the code to, nor the code send
request, nor have I had any opportunity to respond to a 2nd factor
authentication step, since last Sunday, 4/10/2022.
I called PSCU at 888-858-6878 on 4/15/2022 @ ~ 10:30 AM, and
spoke to William. He indicates that they
have had no calls of similar problems from others. William asked that I call back if Quicken is
unable to resolve this issue directly. I
asked him to escalate the issue and he asked me to work with Quicken again.
Thanks to Anja’s post, it is clear that this
issue is generic and not specific to me.
Please let us (users) know if there is anything further we can do to help
resolve this issue, which appears to be related to a change/failure in the process
to log in through Quicken.