CC-503's Rise Again

BereanPK

Anyone else seeing this?

Quicken Classic Windows 11 R62.16 Build 27.1.62.16 (latest as of date of writing), Windows 11 fully updated (just before any Quicken rep asks).

I'm seeing several CC-503's rising when attempting to connect OR RE-connect some accounts - mostly credit cards.

Here's the kicker: One credit card company, I have 3 different branded cards with. Two of those cards interface perfectly and I've never had do deactivate/reactivate. The latest one however, keeps throwing CC-503's even though (again before you ask) I have absolutely verified the correct username/password (particularly because I can successfully log in to the card's site using the same credentials I'm attempting to use with Quicken).

Others include PayPal credit accounts (not Paypal "bank"), that USED to connect to Quicken with no problems but now will not.

I even attempted to try connecting by closing Quicken, restarting my PC (twice), verifying that no weird software that could possibly interfere with Quicken was running, and to test if it was my existing Quicken file, instead created a whole new "test" file with absolutely nothing in it, so I could see if "adding" an account and letting activation go through would work. It didn't. CC-503, folks.

So, all that to say: hey Quicken folks - is there something going on with certain financial institutions right now that's forcing Quicken to throw a CC-503? Or is it a bug that needs worked out?

jtomalley

I've noticed that my accounts that use Express Web Connect (or Quicken Connect in Quicken for Mac) are the ones that are consistently throwing the CC-503 "incorrect credentials" errors. I now have EIGHT accounts that are experiencing this issue.

Discover Card in particular is a problem because they do not offer an option for using Web Connect to Download Transactions as a QFX file from their website, and only one of my two Synchrony accounts have that option.

However my accounts that use Express Web Connect Plus (you are taken from Quicken to the bank's website where, after successfully signing in, a secure token is passed to Quicken and stored by the aggregation service) have no problems.

So it appears that the problem has to do with Express Web Connect (or Quicken Connect in Quicken for Mac).

BereanPK

jtomalley: I agree with your assessment. Somehow something has "broken" the standard EWC.

I just wish that others would call out this issue if they're experiencing it (or if they're not, what they may be doing "differently") so that the Quicken techs would recognize this issue publicly and announce at least that they're working on a fix.

Quicken Kristina

Hello @BereanPK,

Thank you for letting us know you're seeing CC-503 errors. For the financial institution you specified, PayPal credit (PayPal Credit, MasterCard and Crypto), there is a known issue where customers receive CC-501, "not your fault" errors, or CC-503 errors when attempting to connect.

https://community.quicken.com/discussion/7958240/ongoing-1-14-25-paypal-credit-mastercard-and-crypto-cc-501-sorry-not-your-fault-fdp-103

What other financial institutions are you seeing this issue happening with?

I look forward to your reply!

BereanPK

Most of my other accounts that were previously set for EWC/EWC+ are OK. Key Bank, Wells Fargo, and Bread Financial (besides the previously mentioned PayPal credit entities) are all problems.

I have noticed that previously, Quicken would filter the online setup by reaching the financial institution's login page (or modification thereof specifically for authorizing the setup). Obviously "something" happened and all online setups, regardless of the financial institution, are opening a local (Quicken-generated) username/password screen that shows the CC-503 error after entering the correct credentials.

Quicken Kristina

Thank you for your reply,

If you have already followed the troubleshooting from the article on CC-503 errors (to see the article, click here), then I recommend following these steps to further troubleshoot:

1. Navigate to Tools>Account List. If the Show Hidden Accounts checkbox is visible, select it.
   1. If there are any hidden accounts that connect to the problem financial institutions, verify that the accounts are still active on the financial institution side. If they are not, please backup your file and deactivate them in Quicken.
2. Please try temporarily changing your password with the financial institution, then try adding/re-adding the problem accounts in Quicken using the new password.

If the issue persists after you've tried those steps, then I recommend that you reach out to Quicken Support directly for further assistance, as they have access to tools that we on the Community cannot access, and they're able to escalate the issue 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 hope this helps!

jtomalley

Hi Kristina - I have no "hidden" accounts, and currently my accounts throwing the CC-503 error are as follows:

Amazon Store Card (Synchrony), Chevron/Techron Advantage (also Synchrony), AAA Visa Signature (Comenity / Bread Financial), Discover (*recently acquired by Capital One at about the same time this started happening… related?), GAP Visa (Barclay US).

All of these accounts used "Express Web Connect" (or "Quicken Connect" in Quicken for Mac). All of my other accounts that use "Express Web Connect PLUS" are syncing fine.

BereanPK

I agree with jtomalley.

This certainly points to a connection error between Quicken and the Intuit interface; in other words, a technical issue that's arisen in the interface, and not an individual subscriber's file problem that needs troubleshooting.

terry112

I came back from a long vacation on 6/22 and updated quicken deluxe. After, when I updated all accounts (through Direct Connect), ONLY Schwab updated. Ameriprise, Ally Bank, Wells Fargo and Capital One failed to provide updated data, although they did not fail to connect. I had to painstakingly reset all of them. My conclusion is that there was a fundamental change in the Quicken update that caused this problem.

Quicken Kristina

Hello @terry112,

Thank you for letting us know you're seeing an issue. When I check our internal tools, I'm not seeing that you're getting CC-503 errors. If you are not getting CC-503 errors, then please start a separate discussion and provide more details about the exact issue you're encountering, including any error messages/codes you are seeing.

If you are getting CC-503 errors, then please start by backing up your file and following the troubleshooting in this article on CC-503 errors: https://www.quicken.com/support/error-when-updating-accounts-cc-503/ .

@jtomalley & @BereanPK,

Since I'm not seeing any open alerts for CC-503 errors with those financial institutions, and you already tried the troubleshooting steps, I recommend that you contact Quicken Support directly, as they have access to tools that we on the Community can't access, and they are able to escalate the issue 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! 

jtomalley

Hi @Quicken Kristina -

I had a (2 hour) call regarding the CC-503 issue with Quicken support yesterday - it was escalated and I received a ticket number.

HOWEVER… now today the LAST TWO accounts I had that were still successfully syncing via Express Web Connect have failed and are now giving me the same CC-503 error.

I tried resetting the account and then I deactivated them and tried to re-add them, which was when I got that dreaded error again.

So now that means that ALL of my accounts that were previously syncing via Express Web Connect are no longer syncing. They were fine yesterday. Now they're not.

Quicken Kristina

Thank you for the follow-up @jtomalley,

Since the issue has already been escalated, I don't recommend doing further troubleshooting unless the escalated team contacts you (usually by email) with instructions, since the troubleshooting may undermine what they're doing on their end to investigate and resolve the issue. If you haven't already notified the escalated team that the issue is now impacting more accounts, I recommend that you do so by sending a Problem Report with log files attached, and reference the ticket number they provided you in that problem report.

Thank you!