Topic: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

I'm pretty much having the same problem as smalldognet, but with different financial institutions.

I'm trying to connect to Suntrust and Chase.

I used the fi_url's I found on this site:
https://www.oasis.cfree.com/2801.ofxgp (Suntrust)
https://www.oasis.cfree.com/1601.ofxgp (JPMorgan Chase)

And I kept getting the 15500 error from both of them.

I later found different url's for both institutions and I no longer get errors when I send a request to them. So I think these are the correct ones:
https://www.oasis.cfree.com/fip/genesis/prod/02801.ofx (Suntrust)
https://www.oasis.cfree.com/fip/genesis/prod/01601.ofx (JPMorgan Chase)

But no matter what request I send to those url's, I always get a profile response saying, "Please contact your financial institution to enroll."

Like smalldognet, I have tried calling my financial institutions as well and pretty much got the same response they did...both places had no idea what I was talking about.

Does anyone know how to fix this problem?

And as for the fi_url's, I found the two that I'm using from this list:
http://moneydance.com/synch/moneydance/fi2004.dict

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

I am having a similar problem:

I am trying to connect to OFX Direct connect with chase and amex.  I built my own php script using curl and followed ofx specifications but before debugging that, I at least wanted to get a successful call going!

So I downloaded quickbooks's OFX client available here:
fi.intuit.com/ofximplementation/dcsteps/index.cfm?view=dcdevelop

Doing a call to chase I know is a bit confusing because they have their credit card endpoint, and the main bank endpoint, and the bank endpoint seems to be provided by CheckFree which I'm not even sure exists anymore.

So in terms of the request here is what I'm doing (minus login credentials):

<OFX>
  <SIGNONMSGSRQV1>
    <SONRQ>
      <DTCLIENT>20130312231807</DTCLIENT>
      <USERID>xxx</USERID>
      <USERPASS>xxx</USERPASS>
      <LANGUAGE>ENG</LANGUAGE>
      <FI>
        <ORG>Chase Bank</ORG>
        <FID>1601</FID>
      </FI>
      <APPID>QBW</APPID>
      <APPVER>1800</APPVER>
    </SONRQ>
  </SIGNONMSGSRQV1>
  <BANKMSGSRQV1>
    <STMTTRNRQ>
      <TRNUID>YUq2as56746s123fuU</TRNUID>
      <STMTRQ>
        <BANKACCTFROM>
      <BANKID>xxx</BANKID>
          <ACCTID>xxx</ACCTID>
      <ACCTTYPE>CHECKING</ACCTTYPE>
        </BANKACCTFROM>
        <INCTRAN>
          <INCLUDE>Y</INCLUDE>
        </INCTRAN>
      </STMTRQ>
    </STMTTRNRQ>
  </BANKMSGSRQV1>
</OFX>

For the server, I've tried the following:

oasis cfree /1601.ofxgp - 400 error
https ofx.chase.com - 400 error
oasis cfree /fip/genesis/prod/01601.ofx - XML response with only meaningful message being "Please contact your financial institution to enroll." - I'm sure I enrolled this account because quickbooks directconnect works fine.


I've even tried amex with similar syntax to above using:
online american express /myca/ofxdl/desktop/desktopDownload.do?request_type=nl_ofxdownload

But get a 503 Server not available error.

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

Sorry for the weird hyperlinks but the forum only allows one url, so hopefully my meaning is clear

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

I have two initial recommendations:

1) Try different  combinations of APPID and APPVER.  QWIN and 1900 have worked well for me.

2) Try accessing your account information, first.  Something like this will work:

<SIGNUPMSGSRQV1>
<ACCTINFOTRNRQ>
<ACCTINFORQ>
<DTACCTUP>19700101000000
</ACCTINFORQ>
</ACCTINFOTRNRQ>
</SIGNUPMSGSRQV1>

Jesse

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

Thanks for the suggestion Jesse.

I have tried both these things in the past and just tried again now.  I'll use QWIN 1900 since you have success with it.  I also just now tried your exact example above.  Actually, I also tried experimenting with sending a totally invalid request of just random keyboard strokes not in any XML and still I get the exact same response, which is (had to get rid of some of the urls in the response due to posting restrictions):

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

<OFX>
  <SIGNONMSGSRSV1>
    <SONRS>
      <STATUS>
        <CODE>0
        <SEVERITY>INFO
      </STATUS>
      <DTSERVER>20130313121429
      <LANGUAGE>ENG
    </SONRS>
  </SIGNONMSGSRSV1>
  <PROFMSGSRSV1>
    <PROFTRNRS>
      <TRNUID>0
      <STATUS>
        <CODE>0
        <SEVERITY>INFO
      </STATUS>
      <PROFRS>
        <MSGSETLIST>
          <SIGNONMSGSET>
            <SIGNONMSGSETV1>
              <MSGSETCORE>
                <VER>1
                <URL>https://www.oasis.cfree.com/test.ofxgp
                <OFXSEC>NONE
                <TRANSPSEC>Y
                <SIGNONREALM>ChaseRealmA
                <LANGUAGE>ENG
                <SYNCMODE>FULL
                <RESPFILEER>Y
              </MSGSETCORE>
            </SIGNONMSGSETV1>
          </SIGNONMSGSET>
          <SIGNUPMSGSET>
            <SIGNUPMSGSETV1>
              <MSGSETCORE>
                <VER>1
                <URL>
                <OFXSEC>NONE
                <TRANSPSEC>Y
                <SIGNONREALM>ChaseRealmA
                <LANGUAGE>ENG
                <SYNCMODE>FULL
                <RESPFILEER>Y
              </MSGSETCORE>
              <OTHERENROLL>
                <MESSAGE>Please contact your financial institution to enroll.
              </OTHERENROLL>
              <CHGUSERINFO>N
              <AVAILACCTS>N
              <CLIENTACTREQ>N
            </SIGNUPMSGSETV1>
          </SIGNUPMSGSET>
          <BANKMSGSET>
            <BANKMSGSETV1>
              <MSGSETCORE>
                <VER>1
                <URL>
                <OFXSEC>NONE
                <TRANSPSEC>Y
                <SIGNONREALM>ChaseRealmA
                <LANGUAGE>ENG
                <SYNCMODE>LITE
                <RESPFILEER>Y
              </MSGSETCORE>
              <INVALIDACCTTYPE>CREDITLINE
              <CLOSINGAVAIL>N
              <XFERPROF>
                <PROCDAYSOFF>SATURDAY
                <PROCDAYSOFF>SUNDAY
                <PROCENDTM>165959[-5:EST]
                <CANSCHED>N
                <CANRECUR>N
                <CANMODXFERS>N
                <CANMODMDLS>N
                <MODELWND>0
                <DAYSWITH>0
                <DFLTDAYSTOPAY>0
              </XFERPROF>
              <EMAILPROF>
                <CANEMAIL>Y
                <CANNOTIFY>N
              </EMAILPROF>
            </BANKMSGSETV1>
          </BANKMSGSET>
          <CREDITCARDMSGSET>
            <CREDITCARDMSGSETV1>
              <MSGSETCORE>
                <VER>1
                <URL>
                <OFXSEC>NONE
                <TRANSPSEC>Y
                <SIGNONREALM>ChaseRealmA
                <LANGUAGE>ENG
                <SYNCMODE>FULL
                <RESPFILEER>Y
              </MSGSETCORE>
              <CLOSINGAVAIL>Y
            </CREDITCARDMSGSETV1>
          </CREDITCARDMSGSET>
          <BILLPAYMSGSET>
            <BILLPAYMSGSETV1>
              <MSGSETCORE>
                <VER>1
                <URL>
                <OFXSEC>NONE
                <TRANSPSEC>Y
                <SIGNONREALM>ChaseRealmA
                <LANGUAGE>ENG
                <SYNCMODE>FULL
                <RESPFILEER>Y
              </MSGSETCORE>
              <DAYSWITH>0
              <DFLTDAYSTOPAY>4
              <XFERDAYSWITH>0
              <XFERDFLTDAYSTOPAY>0
              <PROCDAYSOFF>SATURDAY
              <PROCDAYSOFF>SUNDAY
              <PROCENDTM>235959[-5:EST]
              <MODELWND>30
              <POSTPROCWND>180
              <STSVIAMODS>N
              <PMTBYADDR>Y
              <PMTBYXFER>N
              <PMTBYPAYEEID>N
              <CANADDPAYEE>Y
              <HASEXTDPMT>Y
              <CANMODPMTS>Y
              <CANMODMDLS>N
              <DIFFFIRSTPMT>N
              <DIFFLASTPMT>N
            </BILLPAYMSGSETV1>
          </BILLPAYMSGSET>
          <EMAILMSGSET>
            <EMAILMSGSETV1>
              <MSGSETCORE>
                <VER>1
                <URL>
                <OFXSEC>NONE
                <TRANSPSEC>Y
                <SIGNONREALM>ChaseRealmA
                <LANGUAGE>ENG
                <SYNCMODE>FULL
                <RESPFILEER>Y
              </MSGSETCORE>
              <MAILSUP>Y
              <GETMIMESUP>N
            </EMAILMSGSETV1>
          </EMAILMSGSET>
          <PROFMSGSET>
            <PROFMSGSETV1>
              <MSGSETCORE>
                <VER>1
                <URL>
                <OFXSEC>NONE
                <TRANSPSEC>Y
                <SIGNONREALM>ChaseRealmA
                <LANGUAGE>ENG
                <SYNCMODE>FULL
                <RESPFILEER>Y
              </MSGSETCORE>
            </PROFMSGSETV1>
          </PROFMSGSET>
        </MSGSETLIST>
        <SIGNONINFOLIST>
          <SIGNONINFO>
            <SIGNONREALM>ChaseRealmA
            <MIN>4
            <MAX>4
            <CHARTYPE>ALPHAORNUMERIC
            <CASESEN>Y
            <SPECIAL>N
            <SPACES>N
            <PINCH>Y
            <CHGPINFIRST>Y
          </SIGNONINFO>
        </SIGNONINFOLIST>
        <DTPROFUP>20030512
        <FINAME>Chase Manhattan Bank
        <ADDR1>300 Jericho Quadrangle
        <CITY>Jericho
        <STATE>NY
        <POSTALCODE>11753
        <COUNTRY>USA
        <URL>
      </PROFRS>
    </PROFTRNRS>
  </PROFMSGSRSV1>
</OFX>

FORMATTING SERVER RESPONSE
HTTP Header Block:
##HTTP/1.1 200 OK
Date: Wed, 13 Mar 2013 16:14:29 GMT
Server: Apache
Pragma: no-cache
Content-Length: 3792
Expires: Mon, 01 Jan 1990 01:00:00 GMT
Content-Type: application/x-ofx

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

There is not much I can help with at this point.  The server is returning valid OFX data and that's the extent of what I can do on my end.  I would still recommend checking with your bank to make sure account access is enabled.  Even though the quicken software can access the data it does not mean you can.  Quicken may have a special arrangement in place.

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

Yo dudes.

I'm just learning OFX, so I'm not a definitive source, but here's what I think is going on...

oasis cfree com/1601.ofxgp (JPMorgan Chase) - refers to the actual OFX server
oasis cfree com/fip/genesis/prod/01601.ofx - refers to the FI *PROFILE*

Azhao, I'm seeing the "contact your institution to enroll" message too, but if you notice, it's contained within the "signup" response - and what the "enrollment" is referring to is for *new customer* enrollment for signing up to chase.com...NOT whether the user has activated the OFX service on their existing account. Does that make sense?

Junk2, that would be the reason you're also getting the same response over and over: you're sending your request to
oasis cfree com/fip/genesis/prod/01601.ofx

which, like I said, just returns the FI profile info and doesn't actually handle any requests...it probably doesn't even read the string you send.

I don't know if I'm correct, but as I'm getting a 400 error and also getting the same response when I use the 2nd url as well, I'm sort of in the same boat. Azhao and junk2, hope that helps.

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

thebulll,

Your insight that oasis cfree com/fip/genesis/prod/01601.ofx refers to the FI profile is really helpful.

At least I know where to concentrate my efforts.

But... regardless... we are all stuck getting a 400 error.

Any other ideas anyone?

Re: FI_URL's and Trouble Connecting to Suntrust and JPMorgan Chase

Has anyone gotten this to work? I have been trying every possible way and only get error 400. GNU Cash returns  Signon invalid (Code 15500, severity "ERROR").  It's making me crazy!