- Sep 1, 2022
- 955
- 305
Hey guys!
I'm using stripe to accept payments on my SMM related business.
Today i got hit with about 10-20 $20 transactions (via stripe) that were very obviously fraud. They were all made from an Iraq IP address, with the cards being in USA, as well as majority of them being declined and 10-20 being successful.
I sorted it out manually with a bit of a monetary loss, but wondering how I can prevent this in the future from happening again?
Does enabling 3DS in the radar settings totally eliminate this risk? Seeing as on the payment information, it states:
'3D Secure was attempted for this payment, but the customer hasn’t been verified by their bank. This payment is still protected from being disputed for fraud.'
With that link refering to this page:
'Payments that have been successfully authenticated using 3D Secure are covered by a liability shift. Should a 3D Secure payment be disputed as fraudulent by the cardholder, the liability shifts from you to the card issuer. These types of disputes are handled internally, do not appear in the Dashboard, and do not result in funds being withdrawn from your Stripe account.
Liability shift can also occur when the card network requires 3DS, but it isn’t available for the card or issuer. This can happen if the issuer’s 3DS server is down or if the issuer doesn’t support it, despite the card network requiring support. During the payment process, the cardholder isn’t prompted to complete 3DS authentication, because the card isn’t enrolled. Although the cardholder didn’t complete 3DS authentication, liability still shifts to the issuer.'
I'm using stripe to accept payments on my SMM related business.
Today i got hit with about 10-20 $20 transactions (via stripe) that were very obviously fraud. They were all made from an Iraq IP address, with the cards being in USA, as well as majority of them being declined and 10-20 being successful.
I sorted it out manually with a bit of a monetary loss, but wondering how I can prevent this in the future from happening again?
Does enabling 3DS in the radar settings totally eliminate this risk? Seeing as on the payment information, it states:
'3D Secure was attempted for this payment, but the customer hasn’t been verified by their bank. This payment is still protected from being disputed for fraud.'
With that link refering to this page:
'Payments that have been successfully authenticated using 3D Secure are covered by a liability shift. Should a 3D Secure payment be disputed as fraudulent by the cardholder, the liability shifts from you to the card issuer. These types of disputes are handled internally, do not appear in the Dashboard, and do not result in funds being withdrawn from your Stripe account.
Liability shift can also occur when the card network requires 3DS, but it isn’t available for the card or issuer. This can happen if the issuer’s 3DS server is down or if the issuer doesn’t support it, despite the card network requiring support. During the payment process, the cardholder isn’t prompted to complete 3DS authentication, because the card isn’t enrolled. Although the cardholder didn’t complete 3DS authentication, liability still shifts to the issuer.'