• Registered: 2012-01-24
  • Posts: 1

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!

  • gubnk
  • New member
  • Offline
  • Registered: 2012-12-29
  • Posts: 2

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 Reply by Nicholas_M (edited by Nicholas_M 2013-01-29 20:03:20)

  • Registered: 2013-01-29
  • Posts: 1

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.