I too have been unable to download Citi Card data with an error 2000. In my case it is not intermittent and the problem has been exhibited for about four days. There's also a message that says to try again in 24 to 36 hours. Am using Moneydance 2019.4(1904) with OS 10.15.4.
Same problem here with two CitiCards accounts, one associated with Costco and one not. Automatic download was broken for a short while last year, then started working correctly again for around 5 months (I think) then stopped working recently with same 2000 error code. I tried deleting the Moneydance workstation application connection on the Citi website, and disabling and resetting the download information in Moneydance, then starting over. The result is the 2000 error code, except now Moneydance isn't even listed on the approved connection list in the Citi website. Uugh. Trying this also on Moneydance 2019.4 beta and that doesn't help. Trying it in Windows 10 and in Ubuntu 20.04, no difference, same problem.
I just reported the problem to Citi. At the very least, it will help them be more aware of Moneydance. I'm hoping that someone at Citi will investigate the problem and either fix the problem directly or offer technical guidance to the Moneydance developers to resolve the problem. Wouldn't that be lovely? Let's see where they go with this.
We've filed a ticket in our ticketing system regarding this issue, and the developers are currently looking into it. This also flags your message as someone who is having this issue, so we'll respond here if we have any updates.
For the time being, the best way to get your transactions into Moneydance is to use a web browser to download files from your bank's web site.
We'd recommend you download using the OFX or QFX file format if available. If not, use the QIF file format. (These files are sometimes referred to as Quicken or MS Money files). You can import the files to Moneydance using File --> Import.
Thank you for your patience and sorry for the inconvenience.
Darrel G Mahann...
on 26 May, 2020 04:19 PM
I spoke with Citi Twice and they claim they do not have a problem.
did everything they and moneydance have suggested including deleting my App Access in my Citi account, resyncing and resetting my Account in Moneydance and disabling and restarting my account in Moneydance.
Everyone says it is the other guys fault.
In the meantime using the cumbersome manual export import process is unacceptable.
Both companies need to get behind your customer and work this out.
I have the same problem. I just spoke with Citi Tech Support. They reauthorized access in my account to no avail. They said that is the most they could do and directed me to Moneydance support. Hoping this is corrected very soon as I don't want to start manually entering, or deal with the duplicate transactions.
My last successful access was on 5/16 at 13:43. I've seen other say that the problem began on 5/17. Something clearly changed between early afternoon (GMT -8) and sometime on 5/17. If these requests pass through Infinite Kind servers, did anything change in that time window? Otherwise, Citi had to have made a change to access on their side.
The Direct Connect protocol is between the Moneydance software on your machine and the bank's servers. Your transaction data goes nowhere near any machine that The Infinite Kind (Moneydance) owns. The Moneydance folks do not have any aggregation servers, nor do they use such services that third parties provide (e.g Yodlee).
Same issue with Citi Cards connection, and have tried all of the things others have mentioned but am still getting the 200 error. I reported to IK yesterday. My last successful connection was 5/13/20. We need this resolved asap!
Collectively for us, Citi posed few or no problems for us for months, and
we didn't change our IK software, yet suddenly the same problem popped up
for many of us. This suggests that Citi changed their automation interface.
Maybe IK can sort this out but the root cause looks like a change made by
Citi has not responded to the question that I submitted to them a few days
ago about this issue. I will try again. And maybe all of us should be
submitting questions to Citi to show this isn't just one customer's issue.
Ethan on 04 Jun, 2020 08:57 PM
Our developers made contact with Citibank's tech people last week, and they appear to have implemented a fix for direct connections as of June 2. For most people this seemed to start working without any changes, but some people had to recreate connections to their bank. To do so, you can follow these steps:
1) Open your bank account register by clicking on it in the left sidebar in Moneydance
2) Select Online->Setup Online Banking from the menu bar
3) Click the Disable button. If you don't see a disable button, continue to step 5.
4) Select Online->Setup Online Banking from the menu bar (again)
5) Click the New Connection button and select your bank from the list of available institutions that pops up. Hit OK. (Make sure you pick the New Connection button, even though your bank is still one of the connection choices after you disable it. Choosing your bank in this way will force Moneydance to reset the connection information, which should then allow you to connect.)
6) Continue with the setup process, entering your username/password
7) Repeat steps 1-6 for any additional accounts from this bank
If you still can't connect after resetting your connection, please open up a separate private thread to contact support with the error message you're receiving, and we'll see what's happening.