Your email was a bit strong and overstated, but I know you have put a lot of work into a solution as a knowledgeable user. Though I note from other comments that there still appear to be problems that arise.
However, my question was primarily directed at Infinite Kind staff, and concerned with whether discussions with USAA have resulted in any permanent solution at that level. It appears that the answer is no, and IK has been lucky to have you and others provide external solutions in the meantime.
Jenny on 02 Aug, 2021 10:01 AM
You can find the latest update from our lead developer in post 417 of this thread.
I have also included the reply below:
"There have been some great questions recently about our long-term fix for the USAA situation.
In the short term, we're very grateful for Stuart's script and would recommend that people use it for now.
In the medium term, we are working on an update that will make signing up for OFX connections with a web-based flow and authentication much simpler and friendly.
In the long term, we are working on an implementation of FDX which will make use of the web-based authentication flow, followed by a more friendly API which is likely to eventually eclipse the capabilities of OFX.
An official announcement will be coming soon, but The Infinite Kind is now a full member of the Financial Data Exchange (FDX) which is the organization behind the FDX protocol. USAA is possibly the biggest driver of FDX and is one of the most prominent technical leaders. I've been spending the last few days soaking up information and making contacts at their annual summit/conference.
FDX is coming to Moneydance and I'm confident that we'll soon have a solid long-term connection to USAA."
I hope this information is helpful. Please let us know if you have further questions.
Thank you, Jenny. I look forward to the long-term connection with USAA. I still see enough comments re glitches in use of the Stuart script that I am anxiously awaiting an official MoneyDance-USAA solution. If possible, please keep me informed when that happens.
So, after using the workaround for several months, it seems to have stopped working. Suddenly, about 2 weeks ago, it has stopped downloading transactions. I know there are cleared transactions, but none get downloaded for any of the accounts. Is there something new?
I'm no expert on error logs either (you need Stuart, or someone like that to interpret), but I do peg on this line:
---end headers HTTP/1.1 403 Forbidden
From the documentation I wrote on the USAA fix:
HTTP/1.1 403 FORBIDDEN – USAA appears to have more restrictions on who can download OFX transactions. One seems to be “U.S. only” which is odd given USAA is all about the military but let’s move on. If you are outside the U.S., you may encounter this, and must use a VPN to “be in the U.S.”. Another issue that triggers this is connecting too many times quickly. You get banned from connecting, but this appears to be short term, you can try again a few hours later.
So, I have no more answers, but this may give you some insight. Where are you located? Maybe USAA is tightening even further who can connect?
Another thought is to call USAA and ask them to look things over (tell them you are using Quicken, of course, but you can no longer connect, otherwise USAA will blame Moneydance).
Sorry to take so long responding. So, it worked up until I was on vacation at the beginning of September. I am in the US and I use a VPN that is set to Houston, TX. So, that's not an issue. I have also tried it without my VPN turned on and same results.