Hacker News new | past | comments | ask | show | jobs | submit login

Tracking multiple account balances has gotten less easy as more accounts offer 2-factor. There really ought to be some kind of standard for granting scoped read-only data auth to authorized 3rd parties for financial info, but presumably every business wants to wall their gardens with delusions about consumers not having to work with multiple companies and backwards notions that friction keeps people in instead of driving them out.



I’ve been using a client based tool (Moneydance) for 10+ years and some banks did support special accounts that had read only access to ofx APIs. It was kind of nice as I didn’t have to worry about my passwords as much.

It’s gotten worse over the years as banks have stopped support for open APIs. I guess because of plaid-type integrators that make custom interfaces. I’ll likely quit my bank (usaa) as they got rid of any api access unless you go through third parties.

I’m not willing to give my account credentials to a third party like plaid where the downside is draining most of my liquid assets and investments.


It feels like there should be some libre tool that automates downloading OFX through the web interfaces and keeps up with the breakage, at least for popular banks. Integrate with procmail and the like to deal with snake oil 2FA, etc.


I’ve tried gnucash a few times but it was just too much work for not enough rewards. I’ve contemplated just making my own scrape to database script because all I really want is a ledger I can query.

Moneydance has been decent enough and I think I’ve paid $100-150 in 10+ years for an initial version and then an upgraded one.


The download functionality of Moneydance and GNUCash is via "OFX Direct Connect", which is an older non-HTTPS protocol to download OFX data from a bank. But as web culture took over with things like Plaid, banks have become more wary about serving up a bespoke protocol that (I believe) authenticates in plain text, or at the very least doesn't support snake oil 2FA and the like. For example, Capital One 360 used to serve it up, but they turned it off in the past several years.

Meanwhile, all banks seem to have the functionality to download .ofx/.qfx files through their web interface. I believe this is what Plaid et al retrieve. Of course using Plaid is horrible because not only are you giving out your credentials, but you're also giving away your private financial data to a surveillance company. But you can personally download the OFX files from the web interface for use with Moneydance (etc), and given the way OFX works you don't even need to be careful about overlapping date ranges (eg download the last year of transactions every month).

Of course that becomes a bit tedious and doesn't give Moneydance (or whatever) access to your recent transactions (it would be very convenient to `tail /var/log/bank` rather than having to login manually). So I'm wondering if anyone has written a libre package that aims to do the web scraping approach for various popular banks that don't support Direct Connect.


OFX supports SSL/TLS as the protocol. Doesn’t directly support 2fa, but I don’t care as it’s read only downloads of data.

I still manually download csv or qif files, but that’s much less convenient than automatic imports. I like the idea of an open standard and wish banks would throw them away instead of improving them. OFX was issued in the 90s so the fact it runs at all is at least something.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: