Citi Connection updated - Now all transactions hit wrong account

tyeee

I updated yesterday. No Issues. It started working for me again a few days prior to the update. So, I don't know what changed. All I know is that it my Citi Card updates OK.

Dean P

Yeah worked for me. Updated to R54.16, then went back to a prior saved version of data, updated and all worked. However I did end up with a bunch of accounts from a single institution that I had previously closed. The process to delete them was cumbersome, but worked. All back to normal now (but took an immediate backup just in case).

Long time Quicken user

Richard Kutnick

NO CHANGE AFTER UPDATING TO R54.16—when I sign in to Citibank in Chrome (my default browser—so don't get me started!) after inserting my Username & PW, I STILL am greeted with a blank screen in Chrome and in Quicken the arrow just spins and spins!! The Quicken screen then times out with the message, "Sign into Citibank bank failed. Try again. Sorry, the sign in failed due to time out or connection error. Select Sign in to authenticate via your web browser" This is verbatim. Below that is another Sign In requester box. I am NO further ahead than where I was weeks ago with this fiasco!!

…AND, YES, I did copy the authorization URL and pasted it into Edge and Firefox, which both resulted in the same error screen!!

Is there really no end in sight? Why can't all of these brilliant engineers figure this out? Is this more complicated than rocket science? Surely if they put a man on the moon (sorry ladies) they can figure this "minor" problem out, no??

Did I say "HELP!!!"

Richard Kutnick

Dean P, your method did not work for me either. Trying yet again to reauthorize, when I refreshed Chrome after letting it sit for about 30 seconds or so, I received this failrure tex on the page: "Your Request Has Failed
Please note, your request has failed due to an internal error or an error with the server. Please try again later.

Any other ideas, ANYONE??!!

Richard Kutnick

As suggested in another thread, why not try Edge and first clear the cache? So going the Edge browser route, Citi stated that I had the wrong credentials! So I thought, why not clear my CHROME cache and try to update—VOILA, THAT DID THE TRICK!

Quicken Kristina

Hello @Richard Kutnick,

The issue you describe is different from the issue this thread is discussing. This issue in this thread was that people were going through the reauthorization process and their account(s) were getting linked to the incorrect nicknames in Quicken. The update corrected that issue. The issue you describe is still a known issue and is discussed in a different thread. Here is the link:

https://community.quicken.com/discussion/7945755/citibank-reauthorization-failure-webpage-citibank-consent-is-blank

I hope this helps!

moevalois

54.16 didn't fix the issue for me.

Quicken Kristina

Hello @moevalois,

If updating to R54.16 did not correct the issue with Quicken trying to relink your accounts to the incorrect nicknames in Quicken, I recommend that you reach out to Quicken Support directly for further assistance as they can walk you through troubleshooting steps in real-time and escalate the situation as needed.  The Quicken Support phone number can be found through this link here. Phone support is available from 5:00 am PT to 5:00 pm PT, Monday through Friday.

I apologize that I could not be of more assistance!