See the top post on this thread - John Ralls reporting that git only
speaks OFXv2. However many banks only speak OFXv1.
I can confirm that I can download from USAA by speaking OFXv1.0.2.
I can no longer speak OFXv2 to USAA; something has changed on their side.
Sorry John, no workaround yet.
On 3/18/20 3:30 PM, Chris Graves wrote:
Here is what I was thinking were significant differences found in ofx.log.
AQB5 vs git, which should be defaulting to OFX 1.
AQB5:
Sending:
-------------------------------------
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318081757.000
<OFX>...
git:
Sending:
-------------------------------------
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<?OFX OFXHEADER="200" VERSION="220" SECURITY="NONE" OLDFILEUID="NONE"?>
<OFX>...
On Wed, Mar 18, 2020 at 1:23 PM John Ralls <jra...@ceridwen.us
<mailto:jra...@ceridwen.us>> wrote:
That would be because they are XML syntax. OFX V2 is XML.
Regards,
John Ralls
> On Mar 18, 2020, at 1:15 PM, chris graves <mohaveba...@gmail.com
<mailto:mohaveba...@gmail.com>> wrote:
>
> Because I don't see them in the AQB5 ofx.log file and to me they
look like XML syntax. Not being knowledgeable on the subject I
can't say for sure. I thought at v1.6, the syntax was pure SMGL.
But again, I don't know what I don't know.
>
>> On Mar 18, 2020, at 1:12 PM, John Ralls <jra...@ceridwen.us
<mailto:jra...@ceridwen.us>> wrote:
>>
>> And why were you thinking that?
>>
>> Regards,
>> John Ralls
>>
>>
>>> On Mar 18, 2020, at 1:05 PM, chris graves
<mohaveba...@gmail.com <mailto:mohaveba...@gmail.com>> wrote:
>>>
>>> I was thinking that it could be the first two lines of your
file below.
>>>
>>>> On Mar 18, 2020, at 12:40 PM, John Ralls <jra...@ceridwen.us
<mailto:jra...@ceridwen.us>> wrote:
>>>>
>>>>
>>>>
>>>>> On Mar 18, 2020, at 9:33 AM, Christopher Singley
<csing...@gmail.com <mailto:csing...@gmail.com>> wrote:
>>>>>
>>>>> You're sending VERSION="220", which USAA doesn't accept.
You need to send VERSION="200" or VERSION="202". Try that.
>>>>
>>>> No joy, I still get a 400 response, but it does occur to me
that it isn't necessarily an OFX issue, it could be that the HTTP
request itself is malformed.
>>>>
>>>> <?xml version="1.0" encoding="utf-8" standalone="no"?>
>>>> <?OFX OFXHEADER="200" VERSION="202" SECURITY="NONE"
OLDFILEUID="NONE"?>
>>>> <OFX>
>>>> <SIGNONMSGSRQV1>
>>>> <SONRQ>
>>>> <DTCLIENT>20200318122832</DTCLIENT>
>>>> <USERID>XXXXXXXX</USERID>
>>>> <USERPASS>XXXXXXXX</USERPASS>
>>>> <LANG>ENG</LANG>
>>>> <FI>
>>>> <ORG>USAA</ORG>
>>>> <FID>24591</FID>
>>>> </FI>
>>>> <APPID>QWIN</APPID>
>>>> <APPVER>2300</APPVER>
>>>> </SONRQ>
>>>> </SIGNONMSGSRQV1>
>>>> <CREDITCARDMSGSRQV1>
>>>> <CCSTMTTRNRQ>
>>>> <TRNUID>20200318122835</TRNUID>
>>>> <CCSTMTRQ>
>>>> <CCACCTFROM>
>>>> <BANKID>24591</BANKID>
>>>> <ACCTID>XXXXXXXXXX</ACCTID>
>>>> </CCACCTFROM>
>>>> <INCTRAN>
>>>> <DTSTART>20200310000000</DTSTART>
>>>> <DTEND>20200318000000</DTEND>
>>>> <INCLUDE>Y</INCLUDE>
>>>> </INCTRAN>
>>>> </CCSTMTRQ>
>>>> </CCSTMTTRNRQ>
>>>> </CREDITCARDMSGSRQV1>
>>>> </OFX>
>>>>
>>>> Regards,
>>>> John Ralls
>>>> _______________________________________________
>>>> gnucash-user mailing list
>>>> gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org>
>>>> To update your subscription preferences or to unsubscribe:
>>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>>> If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>>>> -----
>>>> Please remember to CC this list on all your replies.
>>>> You can do this by using Reply-To-List or Reply-All.
>>>
>>
>
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
