←back to thread

1134 points mtlynch | 5 comments | | HN request time: 0.476s | source
Show context
jsf01 ◴[] No.22937965[source]
The most effective anti-fraud solution would be a major privacy violation just by the nature of anti-fraud itself. So, since the stripe user is the one being charged for disputes anyway, giving them control over how much more privacy to give up in exchange for better protection is completely obvious. Even if the default is to be extremely pervasive as Stripe’s anti-fraud measures are now, the option to reduce that tracking is a must.
replies(2): >>22938181 #>>22939209 #
1. Ensorceled ◴[] No.22938181[source]
Who do you mean as “the stripe user”? As a customer of a website using Stripe, I have very little concern for fraud, MasterCard and Visa protect me quite well. As a website operator who has somebody use a stolen credit card on my site, MC and Visa protect the owner of the stolen credit card quite well. Stripe is protecting both the website operator and the real owner of the credit card.
replies(1): >>22938193 #
2. jsf01 ◴[] No.22938193[source]
The person responsible for paying for the dispute. The user who goes to create an account on stripe.com to allow them to sell stuff on their site.
replies(2): >>22938406 #>>22939046 #
3. ◴[] No.22938406[source]
4. Ensorceled ◴[] No.22939046[source]
Having done some anti-fraud work in the past... that is Not something I would turn off for some over wrought privacy concerns. There is a reason for the GDPR exemptions for this.
replies(1): >>22939393 #
5. luckylion ◴[] No.22939393{3}[source]
What GDPR exemptions are you referring to?