nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Coastal Credit Union OSU broken

bmbass

Coastal Credit Union recently updated their security procedures and the Express Web Connection is no longer working. OSU tells me my log in information is incorrect and even when I "correct" this, I still get the failures. When I tell Quicken that I have NOT recently changed my password, it offers me to "Update Now", which always shows SUCCESS, but nothing is downloaded and next OSU, I get the same "your log in information is wrong" message. Any suggestions? Is there a ETA of when the EWC connection will be fixed?

Find more posts tagged with

Online Banking

Windows

Comments

Quicken Anja

Hello @bmbass,

Thanks for the details. I checked your connection status on our side, and it’s currently returning an internal FDP-103 (CC-503) error, which indicates the financial institution is rejecting the credentials during the download attempt.

Please refer to this support article regarding this error.

The article covers key things that typically resolve this. Since Coastal recently updated their security, it’s likely something on their login/security side that still needs to be confirmed or allowed for third-party access.

If you go through the steps outlined in that article and the issue still continues, the next step is to contact Quicken Support so they can review your logs and escalate if needed.

Thank you!

Olderman

I am having similar problems but quicken is still able to connect when I do an update. However, when I try to reconcile, it is showing entries that go back in time. For the meantime, since I backup every week, i am going to revert to the backup prior to cu's update and go manual.

bmbass

@Quicken Anja

Anja, thanks for the help with my problem. Using the support article I was able to get the downloads working again. However, I do believe I have uncovered a BUG in the Quicken software. Let me list the steps and where I believe the BUG exists:

Quicken said my password was incorrect and failed the OSU
I selected FIX IT and am given two options: Update Now or Change Password
I originally selected Change Password and Quicken accepted this new password and said everything was OK
Next OSU, I am again told my password was incorrect and I am again given two options. This time I selected Update Now, since I had already changed my password and Quicken gave me the Success result.
Next OSU, I am again told my password was incorrect. I tried to change my password using Tools → Password Vault → Add or Edit Passwords, but since Coastal uses EWC, the password field is marked Not Required and I am not allowed to change the password from this screen.
Finally, using the Support Article, I tried to Reset my account and during these steps, I am given a screen that shows my Coastal User ID and Password. When I look at the password Quicken pre-filled, it is my OLD password! So, even though I "changed" my password during the FIX IT steps and was told that was successful, the actual password being saved by Quicken was still my original password which explains why each subsequent OSU failed with incorrect password.
It seems, since Coastal uses EWC, changing the password during the FIX IT steps allowed that set of steps to "pass", but the BUG is not saving this new password in the vault. The only way to get Quicken to actually save the password was during the RESET steps. I would ask the software team to look at the FIX IT password update and EWC accounts and make sure that updated password actually gets saved in the vault. It seems in my case, it never was.

Quicken Anja

@bmbass Thank you for taking the time to share these detailed findings—that’s helpful. It definitely sounds like you uncovered what was happening behind the repeated credential prompts, and your step-by-step breakdown will be valuable for anyone running into the same situation.

I’m glad to hear you were able to get things working again by following the steps in the support article, and I appreciate you sharing your experience here!