2 ms·
So the issue is that large banks (I feel like I can speak with a bit of authority as I work at one and know many colleagues who work at others) have no desire t
by carterklein13 6y ago
So the issue is that large banks (I feel like I can speak with a bit of authority as I work at one and know many colleagues who work at others) have no desire to give up user data, and I don't think this problem will be solvable without governments stepping in to force banks to comply. They're in a better position than more traditionally tech-centric companies in this regard because they fall under heavy regulation, and can do all kinds of legal hand-waving to show why their data must remain private.
There are a lot of great APIs that banks provide, but my personal opinion is that they're largely meant to distract from the fact that the vast majority of your data ISN'T accessible through an API. A lot of banks are building genuinely great tools for developers - thinking specifically of JPM's Quorum and Capital One's Cloud Custodian. But these aren't open banking tools.
Plaid and similar services are great, and the best we can currently do, but they have inherent shortcomings in that they face the same restrictions as any other developer trying to get information directly from a bank.
It's largely the same picture in healthcare. The government is trying to force healthcare companies to open up their environment, and healthcare companies are fighting tooth and nail to stop that. The CEO of EPIC Systems got the heads of many, many major hospitals to directly oppose a rule the HHS is trying to pass basically forcing health record companies to open up. For the time being EPIC has their "App Orchard" which... well, go visit apporchard.epic.com and you'll get a picture for how much they care about giving individuals the right to their health data and developers the right to build more systems on top of their own.