Why?
AFAIK most big banks have APIs, and it would seem to me the use cases for needing to access an account programmatically are few.
Why?
AFAIK most big banks have APIs, and it would seem to me the use cases for needing to access an account programmatically are few.
2. All ACH transfers, for example, have to clear the Fed, which is done via FTP.
3. The consumer use cases are endless (make payments, analytics, etc). Just look at Mint, Truebill, etc.
4. The commercial user cases are endless (treasury management, AP, AR, etc).
Standardisation of communication protocol can only do so much, especially when the standard is built to accommodate the needs of 100s of airlines using 100s of different host systems.
Also, there is ton of red tape around airlines' APIs as well, I'd say probably as much as in banking.
Disclosure: I work on banking APIs
I don't want to use banking apps and sites daily, they all offer garbage UX that's designed for upselling credit cards, consumer loans and other financial product. What I want is simple API access. I can take it from there, and do a better job than banks do, because my own incentives align better with my own interest.