Hacker Newsnew | past | comments | ask | show | jobs | submit | guillelopez's commentslogin

I understand your concerns. But let me clarify that this is a secure service. All sensitive information is stored encrypted, all traffic runs entirely over encrypted SSL and all goes through Plaid Technologies, one of the most prominent service provider of banking data. If you would like some more info, you should check: https://plaid.com/security/


....yeah.

SSL libraries never have bugs.

Its a great idea if it could be done without giving you any of my bank credentials beyond what is on a check and basically public knowledge.

https://plaid.com/docs/#add-user

That right there is why I won't use it regardless. No offense to you or Plaid's security. Just the idea I'm going to hand over the same credentials that let me transfer money out of my institution isn't an acceptable solution.


Zach here from Plaid (a bit late in responding). I understand the hesitations around privacy here; however, there's a difference between sharing credentials and account/routing number. SSSaving is using a read-only data feed that is authenticated by username and password. The app has no access to your account/routing data and cannot debit your account.

Your account and routing number are all that's needed to move money in or out of your account. SSSavings does not get these, nor should any application you don't want to debit you. Unfortunately, these numbers cannot be changed without shutting down the account (whereas credentials can be changed quickly).


Account numbers are usually hidden when logging in but are almost always available by downloading a statement or looking for any recently posted check images.

Same with routing numbers, though finding the routing number of a Bank of America account opened in CA, for instance, is just one google search away.

That said, I'm stoked about checking out Plaid sometime soon especially after reading the Yodlee docs (yikes!)


I understand. Banks should implement reading credentials to avoid these problems.


Yeah, if only you could solve that problem instead. ;)


I don't agree with this mindset at all. People should build things they want to build. I agree—I wouldn't hand my bank credentials over to this service (or really any unknown third party), but I don't think we should say that the OP should have spent their time on something else.


Fair enough. However, I'm tired of cleaning up after people who don't care about obvious security issues. Really, really tired.


Working on it :)


Best of luck, let me know if you succeed :)


Well, the service is intended for people who don't do it manually. People who are lazy about their finance.

And the goal is for them to get automatically an email every week or month with basic information about:

— How much did they spent or win last month? — How much savings do they have in all their bank accounts? — How did their finances progressed in the last months? — How much do they normally spend each month? — For how long could they live with their current savings?

About having an API. You should check: plaid.com. That's the API service I am using on sssaving.com to get all data.


Typo fixed. Thanks.


Yes, sorry about that.


That makes sense. We will add that. Thanks for the feedback.


We added tha sample: https://www.sssaving.com/sample


Yes, we might explore the option to add autodeposits. Moreover the idea is to run autonomous.


Sorry about that. Can I ask you which is your bank?


I agree. But probably banks will never get into that business. Meanwhile some companies, like the one I am using for this service, are helping the banks to get this functionality. You should check them: http://www.plaid.com.


Thanks for the feedback. The idea is to provide more information as the service grows.


Yes, sorry about this. Currently it just works with the 7 main banks in the United States.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: