7 ms·
All of these may result in you bringing in less $ overall, so it really depends on how much each fraud case costs you, but you could (off the top of my head): -
by ro_sharp 4mo ago
All of these may result in you bringing in less $ overall, so it really depends on how much each fraud case costs you, but you could (off the top of my head):
- Enable always checking CVV
- Require 3DS
- Ban a card after N disputes
- Ban an email/other identifier after N disputes
- Ban certain payment methods, banks etc
- Add a visible or invisible captcha to fight automated abuse/card testing
I suspect Stripe walks a fine line where they want to help you prevent fraud, but they also want to avoid vendors complaining to them that their customers can’t pay.
Context: I worked on a payments team for a short while.
- gingerlime 4mo agoNone of the technical measures you mentioned are relevant with “friendly fraud”. And that’s exactly the problem that Stripe doesn’t solve. And doesn’t want to help merchants fight against.
- mrguyorama 4mo agoCertain 3DS setups would shift fraud liability to the payment network itself. That is the only payment network solution to an entity that will happily sign off on clearly false chargebacks. Then they would themselves be fighting the institution agreeing to sign off on bad chargebacks.
- gingerlime 4mo agoEven when the consumer claims that they didn’t receive the product?
- mrguyorama 4mo agoActually no, I am wrong, and duh, of course they don't take liability for "Not delivered". The protection against that is the legal system unfortunately.