Suddenly, Problems With Manual Download For Chase Visa
I have been having issues recently with online banking. Just see all of my recent posts/threads. I am not sure if this new issue is somehow related or not.
For years and years, I have gotten transaction data daily via MD/OFX from Chase for this card. Some time ago, Chase quit their OFX server (like so many others) and I have had to go to their website and trigger the qfx downloads manually. It is a pain, but it works. While I recently tried MD+/Plaid, I only tried it for one account - which failed miserably - and it was NOT at Chase. I terminated the MD+/Plaid trial.
Another recent change has to do with changes made by a Heritage Bank's OFX server. This forced me to disable/re-enable its OFX setup in MD. But again, this had nothing to do with Chase.
Suddenly this morning, when I did the same manual trigger as I have always done, I get shown this dialog in the attached screenshot. I have seen something like this before - when I first started doing the manual downloads from Chase. But once done, I have not been re-prompted. And in this case, the account number looks really hosed-up. So I cancelled the process. I tried again and it would not really do anything until I existed both MD and my browser session at Chase. After restart of both, I tried again and got exactly the same, bogus-looking result.
In the console window, I see the following:
mdwin, handling parameters: "C:\Users\davidw\Downloads\Chasenull_Activity20260414-1.QFX"
mdwin, handling parameters/files: "C:\Users\davidw\Downloads\Chasenull_Activity20260414-1.QFX"
Imported book: Combined root: Combined
20260414-08:20:58.838 Setting size of window dialog3 to location (745, 394) and size (431 x 292) on display \Display0 with bounds java.awt.Rectangle[x=0,y=0,width=1920,height=1080]
20260414-08:21:13.080 Was asked to re-open same account book: Combined
no-op'ing
I have compared the file results of two different (but seemingly identical) download failures . The contents of the QFX files are identical. They contain the following:
<ACCTID>8xxxxxx91-null
Which matched the name of the downloaded file.
Something is way off here and it looks like the problem is from Chase. Can anyone comment or provide a fix?
Thanks
-
Capture.JPG 20.2 KB
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Jenny on 14 Apr, 2026 04:32 PM
Hi,
I'm sorry to hear you've been having further problems.
The account name that's displayed in your screenshot is the account name that's associated with the file you are importing.
It is most likely that Chase has made a change to the file format at their end, and this has caused the issues you've encountered.
Do you have a copy of an older QFX file you downloaded from Chase before these problems started, so that we can compare it?
Would you feel comfortable sending me a copy of the QFX file so I can check the file contents? This will allow me to check if the QFX file still adheres to the OFX specifications that are required for Moneydance (and other software) to read the file correctly.
This discussion is private, so your replies and attachments can only be viewed by the support team.
You should check if this account number has been associated with a Moneydance account.
To do this, open Moneydance and select Online > Match Online Accounts.
This will open the window shown in this article.
Your account numbers are displayed on the left.
The associated Moneydance account is displayed on the right.
Do you see an account named '8xxxxxx91-null' in the column on the left?
--
Jenny, Infinite Kind Support
2 Posted by whitedavidp on 14 Apr, 2026 05:56 PM
Thanks!
1. In the Match Online display, there is nothing with a -null in it. That is clearly not a legitimate account number anywhere. As a programmer, I can tell you that seeing null in this situation indicates something is awry at Chase.
2. Sadly, I am quite anal about deleting these files once I am done with them. I do NOT like my computer cluttered with them. So it is doubtful I would be able to find an old one. And that is too bad, I agree.
3. Additionally, to send you a current one, I would have to re-do the download. I can do that. But I looked at it and it seemed quite reasonable other than the file's name and the embedded account number.
I really doubt that IK can do much here - except to contact Chase and ask "what the heck is this?" And I doubt that will happen. I was hoping that a public message might bring out others who have seen this sort of thing.
Support Staff 3 Posted by Jenny on 14 Apr, 2026 06:10 PM
Ah apologies. I had assigned your discussion as private so that you could send me a copy of your file securely. You can mark this discussion as public or create a new thread to ask if anyone else has experienced this.
I haven't seen any other recent posts where this has been discussed, but if it is due to a recent change, it may simply be a matter of time before we receive other reports of this problem.
In the past, we've tried to contact banks about issues, but we have found that they are much more keen to speak with and listen to their customers. As a small company, we have very little influence with the banks, and they are much more receptive to the requests of their customers. I would be happy to try to contact them about this, but it is most likely that we will not hear back.
--
Jenny, Infinite Kind Support
4 Posted by whitedavidp on 14 Apr, 2026 06:12 PM
In looking at the Match Online, I do see the attached - which mostly matches the account shown in the screenshot already posted. The only difference is -null vs -6915.
These numbers do not match the credit card number. And that did change perhaps a couple months ago. There are 2 cards on the same account - both with different numbers. But like I said, all of this worked just fine as of the download on 4/12 - only 2 days ago.
Also, we have a checking account with Chase that I must handle the same way. That account has no problems.
Strange!
5 Posted by whitedavidp on 15 Apr, 2026 04:40 PM
I decided to go ahead and simply accept the strange-looking account number and matched it to the proper MD account. It seemed to work fine. I guess I am being uber-paranoid these days...