Topic: TD Bank

I was able to get it going in GNUCash (Version 2.4.9) with the following settings:


General setup for OFX backend:

User Name: <leave blank>
User ID: <your id used to login to online banking>
Customer ID: <left blank>

Bank ID: <number of bank routing code, found on check>  # not sure how important this is


Specific OFX setup:

Bank Settings:
FID: 1001
ORG: CommerceBank
BrokerID <not needed>

server URL: https://ofx.tdbank.com/scripts/serverext.dll

Supports Account List Download, Supports Statement download

No Server Options checked

APPID: QWIN
APPVER: 1800
HEADER VERSION: 102

Hope this helps someone!

Re: TD Bank

For many months, the above worked.

However, now I seem to always obtain a 403 Forbidden HTTP error response.   Problem seems to have occurred mid October.  Perhaps coincidentally, this was exactly the same time frame when TD Bank changed their digital certificate (as confirmed by TD Bank, various blogs, and the SSL failures shown on this website.)

Oddly, I don't believe the digital certificate is the problem since:
   1) GnuCash acknowledges the cert's domain name mismatches, but is otherwise valid & allows me to accept it.
   2) GnuCash clearly sends the OFX message and receives a 403 response from the server (I wouldn't expect GnuCash to even try to send the message if the dig cert was considered invalid).

I suspect something else may have changed on TD Bank's servers beyond the digital certificates.

TD Bank has no answers to date.

Are you or anyone else suddenly having the same 403 problems with TD Bank?

3 (edited by Nicholas_M 2013-01-29 20:03:20)

Re: TD Bank

gubnk wrote:

For many months, the above worked.
now I seem to always obtain a 403 Forbidden HTTP error response (2012-12-xx)
TD Bank has no answers to date.

Same thing.

Re: TD Bank

The FI Url should be updated. Instead of 'onlinebanking' it should be 'ofx' as the first part of the URL. (I can't post links to demonstrate for some reason)


Also - and this is important - requests to this service will be DENIED if the User-Agent header is not found in the request. I believe this problem currently exists in GNUCash, and in PocketSense.py scripts (though it is easily remedied in PocketSense by updated the ofx.py file, and making the following change:

Around line 201, replace:

            p = h.request('POST', selector, query, 
                     {"Content-type": "application/x-ofx",
                      "Accept": "*/*, application/x-ofx"}
                     )

with this:

            p = h.request('POST', selector, query, 
                     {"Content-type": "application/x-ofx",
                      "Accept": "*/*, application/x-ofx",
                      "User-Agent": "httpclient"}
                     )

5 (edited by robler 2016-10-20 13:36:35)

Re: TD Bank

I was able to connect to my TD Bank account without issue until around the beginning of October. After that I keep getting
"The remote server returned an error: (403) Forbidden"

Nothing (that I can find) changed in my code and all my other institution connections work fine.
Anybody else having a problem connecting to TD Bank (USA)?

url:     https://onlinebanking.tdbank.com/scripts/serverext.dll
org:     CommerceBank
fid:      1001
appid:  QWIN
appver: 2500
OFXHEADER:100
VERSION:102

Re: TD Bank

Me Too, also getting 403 forbidden and no transactions, Other accounts working fine. Haven't seen any updated settings for TD at this point.

robler wrote:

I was able to connect to my TD Bank account without issue until around the beginning of October. After that I keep getting
"The remote server returned an error: (403) Forbidden"

Nothing (that I can find) changed in my code and all my other institution connections work fine.
Anybody else having a problem connecting to TD Bank (USA)?

url:     https://onlinebanking.tdbank.com/scripts/serverext.dll
org:     CommerceBank
fid:      1001
appid:  QWIN
appver: 2500
OFXHEADER:100
VERSION:102

Re: TD Bank

There must be some change at the bank. I reverted my software to build where I know the download worked and I get the same error.
Unfortunately getting anyone knowledgeable at TD is difficult. General customer service inquiries are useless.

Re: TD Bank

Using iBank aka Banktivity. Last successful updated from TD is October 12th 2016 - I just noticed now.
Not sure what TD has done but they clearly broke it for everyone ..

9 (edited by robler 2016-11-14 21:14:32)

Re: TD Bank

My communication with TD Bank regarding their OFX service. TD Bank changed the OFX server address and won't release the new one. Yet they maintain that OFX service is running. I have not gotten any further replies:


TD Bank:
We are contacting you in regards to linking your bank account information to third party software.

We have confirmed with our Technology Team that the URL referenced during our call is no longer available for the direct connect option as it is a risk to the company's security. In addition, we have confirmed the OFX connections and files are working without error.

At this time, we recommend working with the third party software developer in order to determine if the information can be linked in another fashion.

We sincerely apologize for the inconvenience this has caused.

If you have any further questions, please contact us via email or call 1-800-493-7562 to speak with a TD Bank On-Line Specialist, 24 hours a day, 7 days a week.

Regards,

Brandon

TD Bank On-Line
Phone Channel Resource Officer


My communication with TD Bank regarding their OFX service:
----------------------------------------------------------

Your Reply:

how is it possible that the ofx address is no longer working but ofx connections are? that makes no sense.

if the ofx connections "work" then relay the ofx server address, FID and ORG parameters. as i explained before, i am the author of the software in question, there is no third-party.

Re: TD Bank

I can confirm that in the beginning of November TD Bank updated their OFX URL to https://ofx.tdbank.com/scripts/serverext.dll (the ORG and FID remained the same). Once I updated the OFX URL (in Banktivity) users were able to connect fine.

Something changed on November 14th whereby users are now seeing either "The remote server returned an error: (403) Forbidden" or "An error occurred while attempting to verify your credentials. Please try again" when attempting to login via Banktivity.

I'll see if I can get any information from the online team at TD Bank.

Re: TD Bank

I was able to get a message to the IT folks at TD Bank and left a phone number and email address for them to contact me. Online support did say that other personal finance software developers have notified them as well. I was told that it could be anywhere from 24-72 hours for them to get back to me.

Re: TD Bank

Thanks nc610. Can you confirm the other OFX parameters. I tried the OFX address you posted but am still getting the 403 Forbidden error. Thanks

Re: TD Bank

Hi robler. I'm still waiting to hear back from TD Bank but prior to yesterday, the other parameters that were working are:

ORG: CommerceBank
FID: 1002
APPID: QWIN
APPVER: 2500
OFXHEADER: 100
VERSION: 102

Up until mid-day yesterday, the OFX URL that was working is: https://ofx.tdbank.com/scripts/serverext.dll

I'll let you know what I hear back from TD just as soon as they contact me.

Re: TD Bank

Thanks nc610.
I tried the configuration you posted with the new URL but still no go on my end; still getting the same error.
Hopefully when/if TD Bank contacts you we'll get the correct parameters.

Re: TD Bank

Good news. It looks like TD Bank resolved the connection issue on their end. Here are the OFX specs that I have confirmed as working:


ORG: CommerceBank
FID: 1002
APPID: QWIN
APPVER: 2500
OFXHEADER: 100
VERSION: 102
OFX URL: https://ofx.tdbank.com/scripts/serverext.dll

16 (edited by robler 2016-11-18 11:57:37)

Re: TD Bank

Hi nc610.
I still can't get in.

The OFX parameters you listed are the same as those posted (on this site) to allow Quicken to connect to TD Bank.  I was using the non-Quicken set which worked till October. The Quicken set never worked for me. I don't know why there are (were) two sets nor why the Quicken params don't allow me access.

Glad you're able to connect though.

Re: TD Bank

Hi Robler.

Hmm, I'm not sure if this helps at all or if you are already aware, but back in October when the connection began failing, a new listing for "TD Bank Online Banking - New" appeared in QWIN (the parameters I posted above). That may explain the two sets of parameters.

Try using APPVER: 2400

18 (edited by robler 2016-11-20 21:07:31)

Re: TD Bank

Finally, I got it to work. I can again download transactions from TD Bank.

I'm using the parameters posted by nc610. Thank you.
The old URL - https://onlinebanking.tdbank.com/scripts/serverext.dll - no longer works
Plus I had to add  a line to my code: httpReqst.UserAgent = "httpclient";
BTW: both APPVER 2400 and 2500 work.

Glad to have this done with!

Re: TD Bank

Excellent!

Re: TD Bank

For the past week or so I've getting 403 Forbidden errors when I try to download from my TD Bank account. My code which has been working for months, hasn't changed at all. Nor I have changed my credentials; I can stiil access the website with my current login/password.

Re: TD Bank

Seems the TD Bank OFX server rejects the connection if I'm in the VS debugger (which is new) but is accepts the connection when running outside the debugger - even if the exe being run was built under debug configuration. Weird.

Re: TD Bank

That is weird. No trouble with TD Bank here fwiw.

Re: TD Bank

NC610, TD Bank accepts your request within your debugger? Is your IDE Visual Studio?

Re: TD Bank

I found the cause. Visual Studio uses a "hosting process" under debug to improve performance. The hp somehow causes the http request to be rejected by the TD Bank server. Turning it off eliminates the issue