This discussion was created from comments split from: CIBC US not connecting.
Related to CIBC US - Since Monday, October 27 when I attempt to update 5 accounts in Quicken I receive "We were unable to connect to CIBC Bank USA - Personal Banking Care Code: FDP-163"
Over past month received emails from CIBC stating" In order to get everything ready for our new Digital Banking experience, Netbanking and CIBC US Mobile Banking app will be offline starting tonight, October 24 at 8pm CT. Once the new digital banking experience is live on October 27, you'll be able to dive into our new and more seamless platform"
Any chance this is a server-side issue?
Hello @tuber,
Thanks for reaching out!
I’ve gone ahead and split your comment into a separate thread since you’re using Quicken Classic for Mac, and the discussion you commented on was specific to Windows users.
Upon checking internally, I was able to confirm that you are currently receiving the FDP-163 error with CIBC Bank USA – Personal Banking.
For context, FDP-163 falls under a group of Known FDP Errors in Quicken for Mac. These errors occur when Quicken’s financial data platform is temporarily unable to connect to your bank to download recent transactions—most often due to changes or issues on the bank’s end.
Since CIBC recently completed a major digital banking upgrade, it’s very likely that this connection error is a server-side issue related to that update.
Per our official guidance, please:
Here’s the support article for reference:Known FDP Errors in Quicken for Mac
Thank you!
I'm in the same boat. I did have to update my sign-in today, so I'll try again tomorrow before I open a support ticket.
Hello @Jeff26@,
Thanks for sharing your experience. I understand how frustrating it can be when your accounts aren’t updating after a recent sign-in change.
If the issue continues after waiting 24 hours, then please do proceed with contacting Quicken Support for further assistance and possible escalation.
CIBC Bank online updated their website Nov.1 and now Quicken Deluxe cannot connect. I get the error message and suggests I contact Support, which is elusive, to say the least.
Hello All, Thank you for taking the time to report this issue! We will be forwarding this issue to the proper channels to have this further investigated. However, we request that you please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute to the investigation.
It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.
While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better. We apologize for any inconvenience in the meantime! Thank you. (CBT-911)
I've had the same issue for a couple of weeks, trying to fix my connection with "CIBC Bank USA - Personal Banking" 1. I waited 24 hours and tried to reconnect. I got a "Care Code: FDP-163" error. 2. I deleted my connection and tried to reconnect. I got a "Care Code: FDP-163" error. 3. I sent an error report to support. 4. I upgraded Quicken to the latest version. 5. I started Quicken and tried to reconnect. I got a "Care Code: FDP-163" error. Is there anything else I could/should try? I'd really like to get this fixed.
-Kevin
Hello @kevin-atx,
Thank you for the detailed rundown of the steps you’ve already tried—that’s really helpful.
At this time, the FDP-163 error with CIBC Bank USA – Personal Banking is a widespread issue. It has already been escalated internally, and there is an active ticket open with our teams. We don’t have an ETA available at this time, but the investigation is in progress.
To help contribute to the ongoing investigation, please submit your log files by navigating to:
We appreciate your patience while this gets worked on.
Hello All,
We now have an open Community Alert for all of you to follow. While we don't have an ETA on resolution, any and all available updates and information will be posted within the Alert.