Chase OFX downloads


Having just set up multiple Chase accounts to work with Pocketsense, here are my findings:

  • Quicken downloads are offered on the web, but only to the primary account holder, and only after you have logged onto the web, click on top left button and then click on Profile & Settings > Manage Account Security > Desktop apps > activate Quicken.  Otherwise, you will only be offered pdf downloads.
  • Then clear you account credentials (if any): Pocketsense > Setup > Delete Account
  • Add your Chase account:  Pocketsense > Setup > Add Account
  • For each account user (sites.dat entry), after running Pocketsense > Setup > Test Account, you will get an error informing you that you have a secure message requiring your verification.  Logon to your web account, click on top left button and then click on Secure Messages and then click on the link within your most recent message to activate downloads.
  • Now you will be able to test once again, and you should have a successful download that you’ll need to Send to Money, so that you can match with the appropriate account in Money.
  • Test each account individually and match to Money accounts before running the regular combined downloads.

sites.dat settings



     SiteName : CHASE 
     AcctType : BASTMT     #bank accounts 
     fiorg    : B1 
     url      : https://ofx.chase.com 
     fid      : 10898 
     bankid   : #use appropriate routing number 
     brokerid : 
     appid    : QWIN
     appver   : 2400
     ofxVer   :    103
     mininterval : 
 

  
     SiteName : CHASE CREDIT CARD  
     AcctType : CCSTMT     #credit card  
     fiorg    : B1 
     url      : https://ofx.chase.com  
     fid      : 10898
     bankid   : 
     brokerid : 
     appid    : QWIN
     appver   : 2400
     ofxver   : 103
     mininterval: 
Advertisements

12 Comments »

  1. Pablo said

    Could you send me the same for Charles Schwab. I have pocketsense, but it does not work anymore. Thanks, Pablo Tricci

  2. ameridan said

    Pablo, see this article.  Nothing else has changed with Schwab.

  3. Norm Coltri said

    Sorry. I can’t seem to find were to start a new topic.

    I use OFX download from banks sites rather then PocketSense script. Find it easier than trying to keep up with the changes.
    All was working weel until TD BANK went online with there new WEB site. The site maintained an OFX export option, however the file is not in the proper format.

    I have a TD BANK OFX file from before Feb 9 and the current OFX file. Vastly different in construction and headers. Both claim to be OFX, but only the pre Feb 9 file will import. Other banks ( Everbank, CapitalOne, GinnieMay) all have OXF exports the work just fine.

    Anyone else experiencing this issue. How do we approach TD BANK fro a fix when that will probably say that they do not support obsolete software?

    • julie oconnor said

      i download it as a quicken format file, save it on my computer and change name to ofx then click on it and it works

    • Norm Coltri said

      Thanks for your response!
      I also found a work-a-round for TDBank. Tried to contact the bank about the defective OFX file to no avail. The OFX standard requires a file header. The new TDBank download is missing the required header.
      I download the OFX file, open in Wordpad and add the required header. Then import into Money without any issues, including the new ability to download multiple accounts simultaneously.
      The header for OFX version 1.2 is:

      OFXHEADER:100
      DATA:OFXSGML
      VERSION:102
      SECURITY:NONE
      ENCODING:USASCII
      CHARSET:1252
      COMPRESSION:NONE
      OLDFILEUID:NONE
      NEWFILEUID:NONE

      Place this before the /OFX in the TD download and it works. The new OFX version 2 requires a different header. Not sure if that will work in Money, but TDBank didn’t use any header. Maybe, some day, the programmers at TDBank will realize that their OFX download is defective according to the published standard.

  4. ameridan said

    OFX file format is standardized, so I’m not sure what you mean when you say “the file is not in the proper format”. Pocketsense makes use of a scrubber routine for getting rid of OFX tags that Money doesn’t know what to do with, and so you may have to do that manually to each download, once you determine what tags Money doesn’t like. For instance, Schwab uses {correctaction} tags that Money doesn’t like and the scrubber eliminates those. By comparing the two TD Bank files, you need to determine what is different and look for new tags.

    • Norm Coltri said

      I understand your comments. Really want to continue with manual OFX downloads.
      I analyzed the new TDBank OFX file and found that the header was missing:
      OFXHEADER:100
      DATA:OFXSGML
      VERSION:102
      SECURITY:NONE
      ENCODING:USASCII
      CHARSET:1252
      COMPRESSION:NONE
      OLDFILEUID:NONE
      NEWFILEUID:NONE

      When I paste the header on the OFX file, imports correctly. All of the other banks I use have this header. Suspect that TDBank overlooked the header in their new implementation of OFX. Now to convince them…

  5. Sam said

    I have been downloading transactions from Chase Credit Card for years. All of a sudden couple of weeks (6/4) ago, i got an error. I did not pay attention. I tried to download transactions again today and same problem. When I look at the error, I have not seen anything like this (see below)

    I deleted the account and recreated it. Reset the connections. No joy! I called Chase to see if i was still authorized to download and they said yes. And ofcourse they were helpful but gave me the standard disclaimer that they do not support anything other than Quicken

    I do have another account with Chase which works just fine. Any suggestions?

    502 Bad Gateway

    502 Bad Gateway

    nginx

    • ameridan said

      Try downloading recent transactions for that account as a QFX file from their web page, and studying the file to see if that offers a clue. That will also verify that your web account has access rights.

  6. Sam said

    Tried it. Was able to download and import into Money without any problems

  7. JB said

    I too have been unable to directly download Chase Credit card ofx data using PocketSense since about early June. Error message is:

    ** An ERROR occurred sending POST request to ofx.chase.com
    Exception type :
    Exception val : [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
    (_ssl.c:726)

    Chase downloads worked fine before that, all my other banks continue to download fine, and I don’t think anything changed on my machine.I updated Python and PocketSense – no change. Chase website reports that I am still authorized to download. I find that I can manually download the qfx file from the Chase website, but I would like to get the automatic retrival working again.

    I’ve run out of ideas (perhaps an SSL cert change on thier end, requiring an update to PocketSense)? Any thoughts would be greatly appreciated…

    Thanks
    John

  8. ameridan said

    I found out the hard way that downloads only work for the primary account holder, even though the non-primary can get web downloads. But, it sounds like your issue is different. Can I ask what version of Python you upgraded to? That error message you recited was resolved for me by upgrading to 2.7.14.

RSS feed for comments on this post · TrackBack URI

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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: