Timeline for Collecting banking, credit-card statements from users
Current License: CC BY-SA 4.0
30 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| 2 days ago | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 13 at 8:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 15 at 7:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 17, 2023 at 7:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 19, 2023 at 6:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 21, 2023 at 6:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 22, 2022 at 4:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 24, 2022 at 1:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 26, 2022 at 0:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 26, 2021 at 22:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 28, 2021 at 21:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 30, 2021 at 21:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 31, 2020 at 20:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 2, 2020 at 19:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 5, 2020 at 18:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 6, 2020 at 16:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 8, 2019 at 16:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 9, 2019 at 13:03 | answer | added | dwizum | timeline score: 0 | |
| Aug 9, 2019 at 12:33 | comment | added | dwizum | I think you have two options: 1) Continue with your pdf-stripping approach, but behave in a way that meets industry standards, which ensures there's a clear path of liability (probably the main reason non-merchant vendors handling card data choose to follow DSS). 2) Partner with card issuers to obtain the transactional data directly from them, delivered in a manner that removes the risk altogether (which is what many existing vendors implementing the specific functions you're describing do). | |
| Aug 9, 2019 at 1:32 | comment | added | Gili | @Clockwork-Muse There is too much data to enter manually. Users send me PDF files containing their account statement. I already plan to strip away privacy-sensitive information the second I receive it, but there is no guarantee that someone won't hijack the server and get at the information before I strip it out. Even if I were able do this in the browser, someone could still use XSS and other browser exploits to get at this information. The minute the user hands over this data, they are at risk. Period. I'm trying to act in good faith but I honestly can't think of a better way to do this. | |
| Aug 8, 2019 at 20:25 | comment | added | Clockwork-Muse | @Gili - Could you just not even upload the data? How is it getting uploaded? If this is manual entry, for example, could you just truncate all but the last four digits of the card? | |
| Aug 8, 2019 at 20:08 | comment | added | Gili | @Clockwork-Muse Sadly, my credit card statements contain the full number. | |
| Aug 8, 2019 at 18:52 | comment | added | Clockwork-Muse | ...Do the credit card statements actually contain the full number? Virtually everything I've seen in the last few years only has the last 4, which aren't considered secure. | |
| Aug 8, 2019 at 11:40 | comment | added | Peteris | This question needs specifics about jurisdiction; laws regarding credit cards and financial data are sufficiently different to make a difference here. E.g. if it's EU, then GDPR would become relevant. | |
| Aug 8, 2019 at 11:34 | answer | added | withoutfire | timeline score: 0 | |
| Aug 7, 2019 at 22:58 | history | edited | Gili | CC BY-SA 4.0 |
deleted 1 character in body
|
| Aug 7, 2019 at 16:05 | answer | added | Ghawblin | timeline score: 0 | |
| Aug 7, 2019 at 15:02 | answer | added | Hugo | timeline score: -1 | |
| Aug 7, 2019 at 15:01 | history | edited | Gili |
edited tags
|
|
| Aug 7, 2019 at 14:09 | history | asked | Gili | CC BY-SA 4.0 |