Not sure if this is the proper channel, but USAA Federal Savings Bank has
deprecated older QWIN OFX support.
I have confirmed with the bank this occurred on 27 Jan 2021.
Using a trial subscription for Quicken for Mac, I have an OFX log for new
syncing sequence with USAA.
Here's a snippet:
20
Thanks, John,
Not mentioned in your emails is the response from USAA: A webpage reporting a
server error instead of the usual 50x HTTP response code.
I do see a 400 in the Online Banking Transaction Window when attempting to
download transactions in GNC:
AqBanking v6.2.5.0stable
Sending jobs
The Quicken web interface is I think different from OFX Direct Connect. If it's
OFX Web Connect then it handles authentication differently and that's probably
at least part of the problem.
I found a quicken community discussion that suggests that Quicken for Windows
used IE to connect, so
I can confirm the redirect to USAA for creds is a one-time issue.
You also need a CUSTOMUID. I haven’t deciphered if it is generated sever or
client side.
I am away from my Mac at the moment but can upload the OFX log when I get back
to it. Is there someplace to upload to or would attachment
Scott,
Thanks for the shout out.
I just saw the new thread this morning and I want to confirm that the CLIENTUID
is user specific--the one I was given by Quicken differs from the one you
mention.
I also noticed that APPVER has two values [2300, 2400] in the Quicken logs. I can't
decipher whe
Scott,
To expand a bit more on your research, it turns I got myself locked out working
via command line (had a typo in my password,) but I got a new response:
=
HTTP/2 200
date: Mon, 08 Feb 2021 19:21:46 GMT
content-type: application/x-ofx
content-length: 661
vary: Origin
vary: Acce
Scott,
After about 45 minutes on the phone with USAA being transferred to no less than
3 reps it turns out all one needs to do to reset the lock on Quicken access for
USAA is visit:
www.usaa.com/accessid
And resubmit the form.
Also, once unlocked I was able to get two successful requests sub
Martin,
With further curl testing I have discovered that the NEWFILEUID apparently now
requires an actual UUID or the value NONE. You can see my working examples in
my previous post to the list.
Any attempt to use time-based NEWFILEUID, e.g. 20210209212246.000, results in:
Error encountered
Martin,
Bob,
Am 10.02.21 um 04:09 schrieb Bob White via gnucash-devel:
[...]
With further curl testing I have discovered that the NEWFILEUID apparently now
requires an actual UUID or the value NONE. You can see my working examples in
my previous post to the list.
[...]
Thanks, I changed it
Martin,
Thanks. I integrated the 'make clean' and I can now run locally modified code.
It turns out I am getting a 400 on receive from:
aqbanking-cli request --account=00075X --transactions --fromdate=20210120
--todate=20210208
Debug output:
...
= Enter Password =
Please enter t
Martin,
Thanks! Being able to see the header cleared things right up--there was a spurious
"%0A" hanging off the end of the my 'serverAddr' in the user settings file, how
it got there I do not know.
As it turns out, with a proper user config, the current master branches of
gwenhywfar and aqb
I got new USAA OFX download working with GNC 4.4.1.
It's mainly a configuration task.
-- User config --
int uniqueId=""
char backendName="aqofxconnect"
char userName=""
char userId=""
char customerId=""
char country="us"
char bankCode="314074269"
int lastSessionId="0"
data {
backend {
Regards,
Bob
Sent from my iPhonei v
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
13 matches
Mail list logo
