41–50 of 67 posts
I think Facebook or Twitter logins would go s long way to solving credit card issues. A credit card purchase backed by a 10+ friend FB account is unlikely to be a scammer. Legit Facebook accounts probably sell for more than the cc being tested.
Interesting to read about those fraudsters. Really annoying when you're a small business. I remember reading something similar from Gittip[0], and also mentioned on the linked blog post, jsbin[1]. I wonder what other small startups are using to detect / prevent this kind of fraud? Are there any good services in this space? and why won't recurly/stripe et al bundle this in? (or maybe they do, and I just don't know abo…
Granted, we are quite small and our volume of sales is not massive (Hey! Small startup with very little funding and mostly bootstrapped here), but still, I was expecting some kind of issue with this by now. Or at least people trying to get stuff for free.
For the record, we use Stripe and PayPal for payments, don't know if they do anything on their end.
I think Facebook or Twitter logins would go s long way to solving credit card issues. A credit card purchase backed by a 10+ friend FB account is unlikely to be a scammer. Legit Facebook accounts probably sell for more than the cc being tested.
I think someone else mentioned this in another post about this. Thought it was a great idea so I'll repeat it here: To prevent fraudsters from using you to authenticate their stolen credit cards, set it up so that every purchase automatically redirects to a 'order successful' page. After seeing that a few their credit card numbers all seem to work on your site, the fraudster will realize they can't use your site to t…
Scammer cards will pass the Luhn check, so it won't be helpful for them validating cards. But it will catch many customer typos, thus giving them immediate feedback.
The initial post was just a draft I had neglected to make private, and wasn't finished (but thank you xixi for posting). I didn't spend the whole year solely battling CC fraud. I now wrote about other things that happened in 2015 now, so go back and refresh to read that part.
I think someone else mentioned this in another post about this. Thought it was a great idea so I'll repeat it here: To prevent fraudsters from using you to authenticate their stolen credit cards, set it up so that every purchase automatically redirects to a 'order successful' page. After seeing that a few their credit card numbers all seem to work on your site, the fraudster will realize they can't use your site to t…
Would a simple delay in confirmation be enough to dissuade them? e.g. 10 mins? an hour? There's probably some critical threshold where it's not worth it for the criminal/s. Since the candy can't be dispatched instantly anyway, you could arrange it to not affect delivery times. Though of course, delayed confirmation would also put off genuine customers. So you could faux-confirm it instantly, and follow-up later if th…
He was doing things a little differently than my idea, so not sure what success he had in blocking them.
If you have your own merchant account and have implemented the code by hand or through a library, you pay all sorts of fees, sign up fee, fraud chargeback fees, percentage of charge, statement fee, monthly fee, etc. Both Strip and Square offer simple integrations, simpler than Pay-Pal IMHO, and I assume they have the capacity to deal with fraud better.
I think someone else mentioned this in another post about this. Thought it was a great idea so I'll repeat it here: To prevent fraudsters from using you to authenticate their stolen credit cards, set it up so that every purchase automatically redirects to a 'order successful' page. After seeing that a few their credit card numbers all seem to work on your site, the fraudster will realize they can't use your site to t…
Best reply, but... How often is a typo made (1:1000?), how much time for support staff is needed and how many lost orders due to a ~24 hour delay in some orders being placed. Also, easy to flood the system with bad orders that need to be manually sorted, like a fake order DDoS.
Earlier quoted context omitted.
Would a simple delay in confirmation be enough to dissuade them? e.g. 10 mins? an hour? There's probably some critical threshold where it's not worth it for the criminal/s. Since the candy can't be dispatched instantly anyway, you could arrange it to not affect delivery times. Though of course, delayed confirmation would also put off genuine customers. So you could faux-confirm it instantly, and follow-up later if th…
I discussed this with Bemmu & wrote up the idea (in the context of Laravel coding, but the idea is the same) here: http://codebyjeff.com/blog/2015/10/cut-credit-card-thief-cha... He was doing things a little differently than my idea, so not sure what success he had in blocking them.
I know you wrote that it's just "out-running you, not the bear," but you probably won't be outrunning others for very long.
Edit: I have no problem with measures that could help protect against fraud even just a little, but this one also introduces friction for legitimate customers, so it needs to be sufficiently effective to be worth it.