Chase Bank OFX downloads

[updated 12/6/2015]

In hopes of assisting others in the same boat as Ken, I am posting this setup data for those looking to download OFX data from Chase Bank into PocketSense.    Ken has verified that these settings work. Thanks Ken 🙂


SiteName : CHASE
AcctType : BASTMT
fiorg : B1
url :
fid : 10898
bankid : (use appropriate routing #)
brokerid :
appid : QWIN
appver : 2400
mininterval :
ofxver : 103



  1. John Karasch said

    I started running into a problem today getting quotes. The script terminates with the following error messages:

    Traceback (most recent call Last):
    File “C:\….\”, line 225 in quotes.getQuotes()
    File “C:\…..\”, line 234, in getQuote()
    File “C:\…..\”, line 69, in getQuote print self.ticker, quote{1}, quote{2}, quote{3}
    IndexError: list index out of range

    I have not changed anything since starting to use this in March, and it worked flawlessly until today. Any ideas?

  2. ameridan said


    See if this comment helps…

  3. Cheryl said

    The scripts work great for me, but I’m wondering if anyone else has noticed that while the ‘bank balance’ and date in the Account List are correctly recorded when I import using the scripts, the “Updated” column on the “Home” page (which only shows Favorite accounts) is now blank. It used to show the ‘last update’ date.

    I’m using Money 2007 version

    Is that normal?

  4. ameridan said

    Yes, that is normal. The OFFLINE scripts do not mimic the MSN servers, but they do most of the same functions. You’ll also notice that you can’t update your stock quotes throughout the day like you could online – your first quote run for the day is the only one that Money uses.

  5. ameridan said


    If you think the bankid (routing number) might be common for Chase Bank OFX downloads as you found it to be for Capital One, what number did you use, so I can fold it into the “database” thread?

  6. Hung Le said


    For Chase, did you have to pay the “Activate Direct Access through the PFM service ($9.95/month)” fee?

    I am able to connect to the Chase ofx URL but I am getting the following message back: “USER NOT AUTHORIZED TO ACCESS THE SYSTEM WITH THIS APPLICATION”

  7. Hung Le said

    Regarding value of BANKID. One way to find out is use the OFX’s ACCTINFOTRNRQ request which is suppose to return a list of all accounts available. For bank, part of the account’s info should have the value of BANKID.

    If you’d like to see a sample of ACCTINFOTRNRQ request, send me email.

  8. Cheryl said

    Is anybody else having trouble with Chase after the 7/15/2011 brief site outage? I’m getting errors, but the files in .xfr are empty. Other sources like Schwab & Vanguard continue to work fine…

  9. Cheryl said

    Ah, never mind. It looks like their site outage lasts most of the weekend and includes different functionality at different times. Sorry for posting before researching more thoroughly!

  10. Mike said

    Speaking of Chase … I have been using Chase’s Credit Card Web download up until this month. It no longer imports into Money without an error. Chase reps say Chase decided as of June 2011 to no longer support Money downloads.

    Anyway around this?

    Will Pocketsense work with Credit Card accounts? If yes, is it still working? Is the setup information different than what is used at the beginning of this thread?

    My wife is going to enter them in manually this month, but …


  11. ameridan said

    What are the options? If Quicken QFX files are offered, that’ll work. See the green box text in for more on that.

    QIF files will import as well, but duplicate transactions won’t filter themselves out, as they do with OFX (and QFX) files.

  12. Mike said

    Perfect, absolutely perfect. Chase calls it a Intuit Quicken Web Connect (QFX) File. Download and run it.

    Thank you so much!


  13. Ken H said

    Chase, in their infinite wisdom, has decided only to allow scripted downloads directly from Quicken and Quickbooks. They instituted a one-time secondary user verification protocol which can only be triggered by being logged into the Chase website while initiating downloads into Quicken/QB. I talked to their online support group and they were unable to override the protocols and allow me scripted access. They even said that buying Quicken to unlock access wouldn’t allow a different program access. There must be some token they’re using to identify users who meet their requirements.

    If anyone figures out a way around this I’d be very interested in hearing about it. Otherwise I’ll have to sign into my online Chase accounts and download the data. Not the end of the world but definitely more time consuming.

  14. ameridan said

    Ken H,
    I don’t have a Chase account, and hearing of your experience will probably keep me from signing up for one. It probably wouldn’t hurt to keep trying Pocketsense anyways, since the Intuit site reveals that many Quicken users themselves are having difficulties getting their Chase downloads to work properly. Also try changing appver to 2300 and 2400 for the heck of it.

  15. Cheryl said

    If anyone figures out a workaround for this, I’d be grateful. I’ve tried appver 2300 and 2400, to no avail.

    On a side note, does anybody know any banks who still work, i.e. don’t have this stupid restriction? I will close my Chase accounts if so. I have no allegiance to these jerks.

  16. ameridan said

    PNC Bank works fine.

  17. ameridan said

    For those reading this thread, Humble Pie found the solution and I’ve I’ve added the Chase credit card settings to my OFX download settings page as well as this page for Chase Bank settings.

    • Cheryl said

      This is beautiful, thank you Humble Pie. I used the new values for non-credit card Chase accounts, like checking and savings, and it works for them, too. Huzzah!

  18. Ashok said

    Thanks to Humble Pie, I am again able to download my chase statements to Money.

  19. derekf said

    Jerks. The first time I called Chase PC support about this, they walked me through disabling and re-enabling online access. The second told me that there was an issue they were working on with downloads and I should be patient.

    Had I not done one final search, I’d be looking for a new bank this week.

  20. Andy said

    Anyone else having issues with Chase ofx issues again? All Chase ofx’s in the xfr directory have this again: “Please verify your identity within the next 7 days. Using your desktop computer, go to your bank’s website and visit the Secure Message Center for instructions.” I compared my ofx settings to what Humble Pie listed a while ago and everything looks good.

  21. ameridan said


    I remember reading somewhere* that Chase and other banks requiring clientUID via ofx 103 have been not requiring the email / website verification during a transition phase, but sometime around February 15th, they were going to require this step in order to honor data requests.

    [updated 2/20/2016]
    * Here is the excerpt from the gnucash forum written by Dave Reiser with more information…

    The current change results from Chase implementing Multi Factor Authentication for DirectConnect sessions by insisting that any Quicken-like software be able to supply a tag as part of the login attempt. Martin supplied the capability in aqbanking by the end of 2008, but Intuit wasn’t providing any public help about how they were implementing it. The FAQ above provides enough of that information to get Gnucash reconnected to Chase accounts.

    The key features are that aqbanking has to use “103” as the Header Version for its ofx connections, and it has to send a ClientUID.

    The Header Version is on the Application Settings tab available while editing a User definition in an AqBanking Setup session accessed from Gnucash’s Tools>Online Banking Setup… menu.

    The Client UID entry box is in the User Settings tab in the same Edit User dialog in banking setup. It has been a long time since I set up a new bank account for aqbanking, but reading some of aqbanking’s git log messages, aqbanking may offer the option of generating a ClientUID while you’re defining the user in the first place. For established accounts, it’s probably easier to find any old UUID generator and paste the results into that box in the Edit User dialog.

    Because Intuit specifically says that Quicken sends a 32 character ASCII representation of a hexadecimal number, I’m almost certain that you have to delete the customary hyphens that show up in most uuidgen output. I also made my ClientUID lower case for any of the letters, based on someone else’s observations that their bank was requiring lower case. I have no idea if lower case is required, but it worked for me.

    What happens with the connection is that the first time Chase sees an ofx header version 103 connection with a ClientUID that hasn’t been associated with your account, it will let you download transactions, but it fires off the ‘action required’ email to the address associated with your account, telling you to visit the Secure Message Area in your account page on the web. For me that outside email appeared approximately 3 seconds after I had connected. In that secure message, there’s a link that jumps to a verification web page (and Chase has pasted in your one-time authentication PIN) where all you have to do is click Next. There was some kind of successful completion page displayed.

    Since completing the authentication process, I have been able to download transactions from my formerly blocked account from both 2.4.15 and 2.6.9 gnucash versions. They both use the same aqbanking user data, so chase just thinks I’ve logged in from the same app multiple times.

    If I’m reading Chase’s tea leaves correctly, after February 15, you won’t get any grace period — you’ll have to authenticate before you can access any transaction data. It looks like the authentication PINs will expire in 7 days, now and in the future. If you go beyond 7 days (or maybe if you launch several attempts to log in without authenticating) it looks like Chase’s system will keep generating new PINs for each attempted login. Their mail message mentions you have to be sure to use the most recent PIN if you have received several secure messages regarding authentication.

    The FAQ mentions that DirectConnect servers have to be at version 103 in order to implement MFA via ClientUID. In the Quicken realm all versions that haven’t been locked out of DirectConnect for failure to pay Intuit’s upgrade tax already use header version 103. Servers using version 103 are not required to use ClientUID, but 102 and earlier server versions are unable to use UIDs.

    If you have already logged into a Chase account with Quicken and authenticated your ID, you might have to call Chase and have them clear your authentication. Intuit suggests that banks allow at least 2 valid ClientUID’s per account. But the banks can do what they want. Intuit also suggests that implementation of ClientUIDs be invisible to the user (#ChaseFail). Quicken stores the ClientUID in the data file, and at least in Quicken 2013 provided no way to see the number. The ClientUID was also redacted from the Quicken ofx logs, at least when I looked. Because the ClientUID is stored in the data file, you don’t have to update your authentication when you upgrade Quicken. The good news there is that GnuCash users might be able to use their authenticated ClientUID essentially forever (at least until Quicken’s potential new owner changes something else).

    I hope I’ve found a general solution to the problem.

  22. Andy said

    ameridan –

    Thank you for the quick reply!

    What would I do to fix this on my end? Is there an ofx adjustment needed? I’ve signed into my Chase accounts, so not sure if I missed something.

  23. ameridan said

    Easiest solution might be to erase the clientUID at the bottom of your sites.dat file so that a new # is generated and the verification process is reinitiated.

  24. Andy said

    It appears that worked for 1 out of 5 Chase accounts but then when attempting it again, it returned the same errors. Any ideas as to how to import multiple accounts this way? Looks like it might be manual downloads going forward due to this change. 😦

  25. ameridan said

    Andy, see this comment for a solution to the multiple accounts aside from creating 5 different folders to run Pocketsense in. It involves manually editing a couple of the Python scripts in Pocketsense though – if you wait, Robert may come out with an official update to Pocketsense to accommodate multiple accounts (via multiple clientUIDs) perhaps using code similar code to John’s.

    You’ll find a nice explanation in this comment above as to why the Chase accounts behave this way now.

RSS feed for comments on this post

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: