Wave switched integrators from Yodlee to Plaid. Not sure why they did that since Yodlee works with Capital One, but Plaid does not. This was not a wise decision. Hopefully Wave can go back to using Yodlee. If not, I will have to jump ship as I have several businesses and use Capital One cards with most. I just tried Cheqbook and it is importing Capital One just fine. They use Yodlee.
Hi there, thank you everyone for reaching out to voice your feedback on this. I understand Bank Connections are an important part of your business so I'm sorry you are being impacted by this issue. We do not have any further updates about the Capital One connection at this time.
The reason connections are not working for Capital One currently is because we have changed our bank data provider. The decision to switch to a new data provider came about because of the demonstrated increased connection stability, transaction update frequency, and generally wider bank coverage with the update. While we realize the new data provider currently does not support a Capital One connection, we can confirm they are currently in ongoing conversations to try and get a connection established.
In the meantime we can continue to suggest using Wave Connect or our CSV uploader to import your data manually.
Look @EmmaP and the rest of the team at Wave: Let's dispense with the corporate speak.
You were forced to switch data providers. You failed to do you due diligence and now a great number of your users are adversely affected. It's not a showstopper by any means, but Capital One being a huge bank and have a large client base, this should have been on your mind prior to the switchover, and the top of your priority now. If it's not a severity 1 issue, it's definitely severity 2. Literally people cannot use the platform you've built.
I'm one of those affected. I'm not happy with the situation nor your positioning. Capital One didn't make any changes. It only broke AFTER you switched to the new data aggregator. Your team has admitted as much. Take responsibility, and stop making your clients do your legwork to make your own product work.
I don't understand why you switched to a new data aggregator fully knowing a portion of your clients will be completely blocked from using your platform. Wasn't there a bridge solution where you can use your existing data aggregator for some accounts? The fact that you did a rolling rollout of your new aggregator shows that a progressive transition plan was possible, but you simply decided it wasn't worth your time.
Just own it. Tell your clients you screwed up, and stop blaming others. If you have no plans on supporting Capital One, just say so so we can find an alternative.
I've started looking around. I suggest others do so until Wave can be honest about how they plan to support their users.
Wow, and I even tweeted your little pre-made tweet to Cap1. Shame on you guys. I'm switching to Xero.
Any ideas on when Capital One Sync connections will work again?
@jennye I moved your comment over to our discussion about Capital One. Our data aggregator is still experiencing issues with Capital One. The conversations between them and Capital One are still ongoing but at this time, we don't have an ETA for a resolution.
We recommend using our CSV uploader and our Google Sheets add-on, Wave Connect to do direct bulk uploads at this time.