Hate to argue, but I agree that Plaid's connection to SVB is indeed unusuable. I've been trying to use them for over a year and we ended up dropping SVB just this month. Chase is on OAuth and WAY better if you need TXN data.
A partnership for ACH is more related to importing stable routing and account numbers, then enabling initiating ACH transfers. Scraping transaction data is a completely different integration that seems to have been forgotten.
Sadly, I'd even wager SVB-Plaid data won't improve any time soon. Remember that SVB doesn't even yet allow external bank transfers on their own bank portal.
We are building recurring bank transfer routines between accounts into our subscription manager service (US only). It'll send fixed amounts or percent of deposits on a schedule.
It's not core to the mission (so it will be free after normal security checks), but we were already building a bank transfer system, and I'm tired having to manually move money between savings and checking or set it aside for taxes. It goes live to site in 2-3 weeks... and then the 'finances-on-autopilot' bliss!
A partnership for ACH is more related to importing stable routing and account numbers, then enabling initiating ACH transfers. Scraping transaction data is a completely different integration that seems to have been forgotten.
Sadly, I'd even wager SVB-Plaid data won't improve any time soon. Remember that SVB doesn't even yet allow external bank transfers on their own bank portal.