[GNC] New User-Chase Bank Problems

[Michael Mantei]

I copied an old entry from the OFX LOG. I am using APPVER 2700 and have 
the exact same issue.  I've check my messages with Chase, and there 
aren't any. I don't know that anything is actually being sent to them. 
I've been with Chase for 4 years and have used Quicken with them the 
whole time.  I've never been charged to connect, that I can recall. It's 
always just worked.

Thanks for the feedback anyways.

Mike

On 12/15/2018 5:30 PM, David Reiser wrote:
>> On Dec 15, 2018, at 8:10 PM, Michael Mantei <mantei64 at gmail.com> wrote:
>>
>> I was a user of Quicken for as long as I can remember.  I'm now trying to get serious about my finances and recently installed GNUCash on my Windows 10 system. I simply installed the software, and built my entire account structure manually, to match exactly what I wanted it to be. Now I need to connect to my bank (Chase) and can't do it.
>>
>> I'm using the AQBanking Wizard and have setup a user account and it won't connect.  I started reading lots of messages here then created a new user.  This one has the User Name and User Id set to the same name I used with Quicken. I used an online app to generate a Client UID. I've selected JPMorqan Chase Bank as my bank and took the defaults on the Bank Settings page. For the Application Settings, I have an Application ID of "QWIN". The application version is set to 2700 and the header version is set to 103. When I try to retrieve the account list, this is what I get:
>>
>>
>> 14:06:57 Retrieving SSL certificate
>> 14:06:57 Connecting to server...
>> 14:06:57 Using GnuTLS default ciphers.
>> 14:06:57 TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
>> 14:06:57 Signer not found
>> 14:06:57 Certificate is not trusted
>> 14:06:57 Connected.
>> 14:06:57 Disconnected.
>> 14:06:57 Connection ok, certificate probably received
>> 14:06:57 Operation finished, you can now close this window.
>>
>> The OFX.log file shows this:
>>
>> Sending:
>> -------------------------------------
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:103
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20181214144405.000
>>
>> <OFX><SIGNONMSGSRQV1><SONRQ><DTCLIENT>20181214144405.000<USERID>#NAME REMOVED#
>> <USERPASS>#PASSWORD REMOVED#
>> <LANGUAGE>ENG<FI><ORG>Chase Bank<FID>1601</FI><APPID>QWIN<APPVER>2200<CLIENTUID>4f67a05f-bb69-45a7-ab66-d1f52dc4ef71</SONRQ></SIGNONMSGSRQV1><SIGNUPMSGSRQV1><ACCTINFOTRNRQ><TRNUID>20181214144405.000<CLTCOOKIE>1<ACCTINFORQ><DTACCTUP>19691231</ACCTINFORQ></ACCTINFOTRNRQ></SIGNUPMSGSRQV1></OFX>
>>
>> -----
>>
>> Anyone have any ideas what I am doing wrong? Your help would be greatly appreciated.
>>
>> SciFiGeek
>>
> The ofx log says you set the APPVER to 2200 instead of 2700. That probably matters.
>
> Another thing is that you’re likely to have to do is log into the Chase web site, and check your secure messages for one that asks you if you were the one trying to sign in with a previously unknown app (as identified by the new unique CLIENTUID). Once you’ve followed the steps in the Chase message, you’ll be in better shape. If you have no message yet, there’s a possibility that the Chase system doesn’t think your software is capable anyway (APPVER too low). Change the APPVER, try Aqbanking again, and then check your account messages online again.
>
> I only have Chase credit cards. I don’t know if the procedure is different for checking and savings accounts. Chase does by default charge a fee for checking/savings access via OFXDirectConnect. But since you’ve connected before, I’m assuming that isn’t causing you problems.
>
> I also don’t know if Chase has changed the out-of-band verification steps since the first round two years ago. Good luck.
>
>
> --
> Dave Reiser
> dbreiser at icloud.com
>
>