Downloading transactions from USAA

Charlie Morrison sail43 at
Sun May 10 08:44:26 EDT 2015

On 05/09/2015 07:44 PM, David Reiser wrote:
>> On May 9, 2015, at 4:44 PM, John Ralls <jralls at> wrote:
>>> On May 9, 2015, at 1:00 PM, David Reiser <dbreiser at> wrote:
>>>> On May 9, 2015, at 2:25 PM, Charles B. Cameron <Charles.B.Cameron at> wrote:
>>>> I have been able to download transactions into GnuCash from USAA for several years, but this stopped working on April 24.  What could account for this unwelcome and unexpected change in behavior?  Here is a log showing what happens now:
>>>> 14:22:08 Sending request...
>>>> 14:22:08 Connecting to server...
>>>> 14:22:08 Resolving hostname "" ...
>>>> 14:22:09 IP address is ""
>>>> 14:22:09 Connecting to ""
>>>> 14:22:09 Connected to ""
>>>> 14:22:09 Connected.
>>>> 14:22:09 Sending message...
>>>> 14:22:09 Message sent.
>>>> 14:22:09 Waiting for response...
>>>> 14:22:09 Receiving response...
>>>> 14:22:10 HTTP-Status: 400 (Bad Request)
>>>> 14:22:10 Operation finished, you can now close this window.
>>>> Any help would be gratefully accepted.
>>> You might have run afoul of Intuit’s sunsetting rules at the bank. Check to see that AqBanking is sending a current-enough version number for the connection software.
>>> In Tools>Online Banking Setup…
>>> Click Forward
>>> Click Start AqBanking Wizard
>>> pick your USAA user from the list of users in the next window, and click Edit User
>>> select the Applications Settings tab in the next dialog
>>> and make sure the Application Version is high enough.
>>> 2300 works for me, but I don’t think that’s this year’s Quicken version. But anything that is newer than 3 years old ought to keep USAA’s server from complaining (if that’s the problem with your connections).
>> I’m not able to connect today either, though everything worked fine last Monday. I’m getting much further than Charles, though: An error 2000 after completing authentication and approving the certificate. Changing the Application Version number from 2200 to 2300 didn’t make a difference. The USAA website gives instructions for Quicken 2010-2013, FWIW.
>> Regards,
>> John Ralls
> The only other thing I can think of is if USAA/Intuit are now requiring the ClientUID from direct connections. After crying wolf on this subject several times a couple years ago, I don’t know how to even verify the possibility. You can enter a ClientUID in AqBanking, but I have no idea how you confirm to the bank that that UID is you and not someone else. The OFX spec tells how to include a ClientUID, but absolutely nothing about how the negotiation is supposed to establish authenticity.
> Dave
> --
> Dave Reiser
> dbreiser at
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
It wasn't working yesterday but today is back to download as usual. 
Might have been a problem at USAA.

More information about the gnucash-user mailing list