Two Rivers Bank not syncing transactions unable to log in. CC-503

Options
Shredder52404
Shredder52404 Member ✭✭

I was getting a successful account sync message after logging in to quicken with all my bank accounts; however, I just noticed that no new transactions were being pulled in since 6/9/23 and there were discrepancies. I attempted to reset my account which has now prompted me to log i with my credentials, but it is not accepting my credentials that i know to be accurate on the website. I do know that Two rivers have recently updated their banking system, so I feel like that may be related.
The error i get is "Oops. Did you mistype your login CC-503"

Comments

  • UKR
    UKR SuperUser ✭✭✭✭✭
    Options

    Have you tried this yet?

    If your bank recently changed their website or password requirements please read and follow instructions here:

    For online billers please see if you can manage (remove and re-add or repair) the online biller, to see if their profile has already been updated.

    If that doesn't resolve the issue:

    • It is the bank's or biller's contractual obligation to notify their Quicken download service provider, Intuit Inc., of any changes to their websites and download functions in a timely manner before the change is implemented. Intuit needs a sufficient amount of lead time to review, change and test their programs, to adapt to the changes the bank makes.
    • The bank also needs to notify their customers of this change in a timely fashion and detail any actions that might be required by the customer to regain access after the change was introduced.
    • If they didn't do that, complain to your bank's or biller's office of the president.
    • Also contact Quicken Support via Chat or Phone at https://www.quicken.com/support#contact-support during posted hours of operation and report this as an Online Banking issue, so that Quicken Support can escalate this issue to Intuit Inc. Ultimately, however, the bank or biller must initiate the call and work together with Intuit on solving this update issue.

    Please let us know if you were able to get this issue resolved (or not).

This discussion has been closed.