Create an API connection to bank accounts
There’s no reason this should be manual entry. This is a poor UX pattern imo - there should be a pull from chase to detect. You can start by analyzing statements
There’s no reason this should be manual entry. This is a poor UX pattern imo - there should be a pull from chase to detect. You can start by analyzing statements
Log in to comment and vote
Comments1
Whiskey
Jun 19
I’m not dismissing the idea, but “there’s no reason this should be manual entry” is completely over the top.
Some prefer manual entry
Parsing bank statements isn’t trivial, due to how payments are coded (often lack of subscription cadence or type in bank statements)
Adding a “connect to bank” feature adds a significant amount of complexity to the app
Different countries can use different APIs (plaid, for example, isn’t available everywhere in the world, so the userbase could be split), if a bank connection is down (so not the app’s fault) that creates a support headache with many users pining the blame in the wrong place—and those are just two examples. Even apps that have bank-connecting APIs as part of the core value proposition—like Copilot, or Orgin, or Rocket Money—have had issues because of the flakiness/complexity of those APIs.
The feature would be cool and I’d probably use it, but at the same time there are several good reasons beyond just the ones I mentioned to not do it.