Ralls
>>
>>
>>> On Mar 18, 2020, at 1:05 PM, chris graves
mailto:mohaveba...@gmail.com>> wrote:
>>>
>>> I was thinking that it could be the first two lines of your
file below.
>>>
>>>> On Mar 18, 2020, a
18, 2020, at 12:40 PM, John Ralls wrote:
On Mar 18, 2020, at 9:33 AM, Christopher Singley 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
HTTP 400.
The problem may be larger than AqBanking...
On 3/18/20 2:40 PM, John Ralls wrote:
On Mar 18, 2020, at 9:33 AM, Christopher Singley wrote:
You're sending VERSION="220", which USAA doesn't accept. You need to send VERSION="200"
or VERSION="202". Try th
You're sending VERSION="220", which USAA doesn't accept. You need to
send VERSION="200" or VERSION="202". Try that.
On 3/18/20 11:31 AM, John Ralls wrote:
Interesting. USAA can't parse the OFXv2 that AQBanking 6.1.2 emits.
Unfortunately it just returns an HTTP 400 response, no details.
Thanks. Just, y'know, keep it cool on the profile scanning... each one
spams a lot of requests.
Your bank's server has an OK parser... standards-compliant OFXv1.0.3
(what Quicken sends). Sadly no OFXv2 support.
On 3/18/20 10:50 AM, Chris Graves wrote:
ofxtools -- nice toolset!
Here are
