ANannexrichmond·Jan 15, 2020Submission
Archive: Privacy/security concerns · Issue #68 · plaid/link
1 points · Open discussionplaid
deprecated-link
Learning & Reference2017–2020
plaid / deprecated-link · Archived
deprecated-link
This repository is now deprecated. To integrate with Plaid, visit the docs.
11Distinct people
12Mentions
0Explicit recommenders
252GitHub stars
What to know before exploring
What it is
This repository is now deprecated. To integrate with Plaid, visit the docs.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year12 dated mentions
Observed mentions: 2017-03-10 16:09:03 UTC to 2020-01-15 01:05:42 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 2 | 6 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
12 sourcesIf you’re referring to the github link, they took it down after several Complaints.
https://github.com/plaid/link/issues/68
In Visa Buys PlaidSince HN doesn’t turn URLs in text submissions into clickable links like it does in comments, here are the URLs given for your clicking convenience.
http://web.archive.org/web/20190415103059/https://github.com...
https://github.com/plaid/link/issues/68
In Plaid Deletes GitHub Issue Exposing Imitation of Bank Login UIsSeems to have happened not because they deleted that specific issue but because they have disabled issues in general for that specific repository. Take a look at https://github.com/plaid/link and see there is no "Issues" tab. When doing that, it removes all existing issues.
In Plaid Deletes GitHub Issue Exposing Imitation of Bank Login UIsPlaid Deletes GitHub Issue Exposing Imitation of Bank Login UIs
Plaid imitates major bank account UIs in their login forms to make users more comfortable submitting their bank credentials to Plaid. This issue was addressed in this Github issue (archived from WaybackMachine): http://web.archive.org/web/20190415103059/https://github.com/plaid/link/issues/68
The Github issue has since been deleted, as shown here: https://github.com/plaid/link/issues/68. I'm hoping this isn't a repost, but this behavior seems ridiculous to me, and I'm hoping to bring it to wider attention (if it isn't already).
Edit: post flagged for some reason. Oh well.
169 points · Open discussionUse at own risk* [1]
[1] https://github.com/plaid/link/issues/68
In Plaid Launches in the UKExactly the point I made about Plaid's login flow-
https://github.com/plaid/link/issues/68#issuecomment-4408942...
For the average Web user, if you don't see a name you trust with an EV cert in friendly green in your address bar, you shouldn't be giving up the keys to your bank account. Plaid and (soon formerly?) Stripe embedding their widgets into the parent page are just training users to get scammed. I'm still beating this drum because it's still a serious problem and nobody seems to care.
In New version of Stripe CheckoutPlaid Privacy/Security Concerns
1 points · Open discussionI haven't heard any reports of Plaid doing bad stuff with user transaction data, so I suspect there's a bit of paranoia in the comments here.
On the other hand, there's an underlying (and valid) concern that handing over bank credentials to a third party is risky and, even assuming good faith from Plaid, they have to store passwords on their servers somehow (probably encrypted).
Since they make money from integrations with startups/big banks, there is definitely a conflict of interest between keeping user credentials safe and growing their revenue.
I think as a whole, relying on a modern company which specializes in authentication is better than trusting that thousands of app developers, some of which might big legacy banks with woefully understaffed IT departments, will keep your credentials safe. I'm aware that I'm more optimistic than
Read the rest
most people in this thread (and on HN) though.
Here's a stackexchange question with some good discussion about Plaid security:
https://security.stackexchange.com/questions/198005/is-plaid...
Here's a github issue on Plaid's repo, showing that they are at least considering oauth on their roadmap:
https://github.com/plaid/link/issues/68
And here's Plaid's page on security, which is frankly short and a bit vague:
https://plaid.com/security/
Reminder that Plaid doesn't know what their doing when it comes to security: https://github.com/plaid/link/issues/68
In Build your own MintPlaid.com API flaw and major security concern
9 points · Open discussion