USAA Checking Stopped Working - OFX service
Hello all,
Today my USAA stopped downloading transactions. I followed the instructions for the new and depreciated method via the Toolbox extension here: https://infinitekind.tenderapp.com/kb/online-banking-and-bill-pay/c.... I go through the setup for my accounts and receive the below error:
There was an error communicating with your financial institution. The details of this error are below.
Bank Name: USAA Custom Profile (ofx_create_new_usaa_bank_profile_custom.py)
The error code reported by the server was: 2000
General error
According to Step 4 in the instructions, I am supposed to make a post asking for help. Here is what I'm getting from the Console as well.
HTTP response headers:
date: [Sun, 21 Aug 2022 15:39:42 GMT]
content-length: [505]
expires: [0]
vary: [Access-Control-Request-Headers]
x-frame-options: [DENY]
x-cdn: [Imperva]
x-iinfo: [10-1369782-1369786 NNNN CT(32 33 0) RT(1661096376713 92) q(0 0 0 -1) r(57 57) U6]
pragma: [no-cache]
strict-transport-security: [max-age=31536000 ; includeSubDomains]
x-content-type-options: [nosniff]
x-xss-protection: [1; mode=block]
content-type: [application/x-ofx]
connection: [close]
cache-control: [no-cache, no-store, max-age=0, must-revalidate]
Reading message from https://df3cx-services.1fsapi.com/casm/usaa/access.ofx
>>>>>>>>
OFXHEADER:100
DATA:OFXSGML
VERSION:103
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:NONE
<OFX><SIGNONMSGSRSV1><SONRS><STATUS><CODE>0<SEVERITY>INFO<MESSAGE>SUCCESS</STATUS><DTSERVER>20220821103937.057[-4:EDT]<LANGUAGE>ENG<FI><ORG>USAA Federal Savings Bank<FID>67811</FI></SONRS></SIGNONMSGSRSV1><SIGNUPMSGSRSV1><ACCTINFOTRNRS><TRNUID>1661096375836-3<STATUS><CODE>2000<SEVERITY>ERROR<MESSAGE>General Error</STATUS></ACCTINFOTRNRS></SIGNUPMSGSRSV1></OFX>BEGINRESPONSE>>>>>
<OFX>
<SIGNONMSGSRSV1>
<SONRS>
<STATUS>
<CODE>0
<SEVERITY>INFO
<MESSAGE>SUCCESS
</STATUS>
<DTSERVER>20220821103937.057[-4:EDT]
<LANGUAGE>ENG
<FI>
<ORG>USAA Federal Savings Bank
<FID>67811
</FI>
</SONRS>
</SIGNONMSGSRSV1>
<SIGNUPMSGSRSV1>
<ACCTINFOTRNRS>
<TRNUID>1661096375836-3
<STATUS>
<CODE>2000
<SEVERITY>ERROR
<MESSAGE>General Error
</STATUS>
</ACCTINFOTRNRS>
</SIGNUPMSGSRSV1>
</OFX>
<<<<<<<<ENDRESPONSE
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by dtd on 21 Aug, 2022 09:36 PM
just a user - yes USAA seems to be down today (I cannot download my accounts - errors out with 2000 (general error)).
Usually this resolves within a day or so (i.e. maintenance, Sunday, resolve the computer that crashed). There are of course possibilities that something has changed, as has happened before.
Good on you for following instructions that I probably wrote for Stuart/IK. However, I should probably revise it to say more specifically, "if you get a 2000 or 503 error, try again tomorrow. If this continues for 3-4 days, a lot more people will be talking about this."
As it is, redoing things that already work will probably only result in more problems than answers.
2 Posted by refekt on 21 Aug, 2022 09:55 PM
Appreciate it! I'll wait it out. :)
3 Posted by dtd on 21 Aug, 2022 10:46 PM
One of the things I often do is to check Quicken forums. Sure enough, USAA is down for them as well, which usually makes me feel this is just a "normal" maintenance glitch.
4 Posted by dwg on 21 Aug, 2022 11:22 PM
When online banking does not work do not assume it is Moneydance. If you have not changed anything there is no reason to believe the fault it on the Moneydance side. So initially look to see if the bank is the problem, the bank system being offline is often the first thing to investigate, has the bank made any changes, errors being returned to Moneydance may help to indicate this, for example being locked out of your account.
Error 2000 is a general error it is often not very helpful, unfortunately banks often don't set up their systems to give useful information, for example they could set it up to give a 13505 error which is a server undergoing maintenance try again later error.
5 Posted by rdmyers.42 on 22 Aug, 2022 05:57 PM
Its' very intermittent on the 22nd
On 8/21/22 19:22, dwg wrote:
6 Posted by dtd on 22 Aug, 2022 09:59 PM
USAA seems fine for me today.
7 Posted by refekt on 22 Aug, 2022 10:01 PM
Looks good to me now! Thanks!
System closed this discussion on 21 Nov, 2022 10:10 PM.