Page 2 of 2
Re: Download transactions fails
Posted: Tue Feb 09, 2016 9:10 pm
by RLebeau
MechCAD just now closed my support ticket as "resolved":
RAM-1YP-D3V2: Download Chase transactions is broken
But it doesn't say whether the problem was actually fixed and Chase transactions will be downloadable again, or if they can't fix the problem due to Chase's changes and will be moving forward without Chase support.
Re: Download transactions fails
Posted: Fri Mar 18, 2016 12:32 pm
by jmihalich
I am having the exact same issue btw. Mechad's tech support is like non existent. I opened a couple of tickets, also one of which was marked as resolved. The other one i asked a question about when the next release is going to be with all these fixes they're supposedly making. I got no response.
The last release of this software was June 2015, so maybe they do yearly releases in June...sigh.
And btw, Chase's tech support was mostly useless, as i went through them too trying to get them to tell me why i can't connect anymore after connecting for years.
Joe
Re: Download transactions fails
Posted: Mon Mar 21, 2016 5:48 pm
by RLebeau
I contacted Chase and got some more info. See the following discussion on the AceMoney Yahoo group for details:
Problem downloading transactions from Chase
In a nutshell, due to security changes on Chase's end several months ago, users have to re-authenticate their financial apps. When an un-authenticated app tries to login to Chase's system, Chase is
supposed to generate an authentication code and send it to the user, who then has to append the code to their existing password in the app, login, and then remove the code. Then the app will be able to continue using the system as before.
The problem is, after several months, Chase's system is
still broken and not generating those necessary codes. So apps like AceMoney are not able to login anymore. Chase is aware of the issue, but has yet to fix it.
Re: Download transactions fails
Posted: Mon Mar 21, 2016 6:06 pm
by jmihalich
Yeah, the main issue is that i did not get the email in my secure inbox that we were supposed to get. They apparently can't force the system to generate it.
Joe
Re: Download transactions fails
Posted: Wed Mar 23, 2016 3:47 pm
by RLebeau
jmihalich wrote:the main issue is that i did not get the email in my secure inbox that we were supposed to get.
Nope, and I have already complained to them about it. All they say is to call their tech support phone number for further help, but I have not had time to do so yet.
Re: Download transactions fails
Posted: Wed Jun 29, 2016 2:08 pm
by RLebeau
Latest info from the AceMoney Yahoo group:
Here is a very interesting tidbit I just found on the issue forum of the open-source OFXClient project (
https://github.com/captin411/ofxclient) regarding this exact same Chase issue:
https://github.com/captin411/ofxclient/issues/17
"Chase has made a recent change that breaks ofxclient. They are now requiring that users perform a verification step through their website. The symptom is that download fails and the response is:
<OFX><SIGNONMSGSRSV1><SONRS><STATUS><CODE>15510<SEVERITY>ERROR
<MESSAGE>Please verify your identity within the next 7 days. Using your desktop computer, go to your bank<92>s website and visit the Secure Message Center for instructions.</STATUS><DTSERVER>20151203063424.779[-5:EST]<LANGUAGE>ENG<FI><ORG>B1<FID>10898</FI></SONRS></SIGNONMSGSRSV1><CREDITCARDMSGSRSV1><CCSTMTTRNRS><TRNUID>49048ca8d87a43dd8a6bac3f093984f6<STATUS><CODE>15500<SEVERITY>ERROR</STATUS><CLTCOOKIE>4</CCSTMTTRNRS></CREDITCARDMSGSRSV1></OFX>
The verification in the "Secure Message Center" is not triggered by the existing request. Based on my experiments, the request has to be an OFX 2.1.1 request that includes the new CLIENTUID element in order to trigger the verification step.
...
Indeed, changing ofx_version [from 102] to 103 allowed transactions to download and triggered the verification, so I'm closing the issue."
AceMoney is still using OFX 1.0.0 ! It does not send a CLIENTUID when signing in to a bank.
According to the official OFX specifications (
http://www.ofx.net), support for multi-factor authentication was added in OFX 1.0.3, 2.0.3, and 2.1.1, and error code 15510 is classified as a "CLIENT UID invalid" error.
So, if MechCAD updates AceMoney to at least OFX 1.0.3 with MFA support, we might regain the ability to download Chase transactions in AceMoney again.
Re: Download transactions fails
Posted: Fri Jul 15, 2016 4:46 am
by RLebeau
Latest info from the AceMoney Yahoo group:
I spent a few hours writing some test code and was finally able to get Chase to generate the secure message needed to grant access to my test app so it can login to Chase's OFX server and download my credit card transactions! I have posted my findings on my ticket on MechCAD support, hopefully MechCad will now be able to update AceMoney to download transactions from Chase once again:
http://support.mechcad.net/ticket.php?t ... M-1YP-D3V2