#yolan.pibrac
1 messages · Page 1 of 1 (latest)
Hi there!
I recommend reading this doc: https://stripe.com/docs/disputes/prevention/card-testing
Thank you, I will do that
After reading the documentation, my question remain. (We followed the guidelines with the recaptcha protection, we provide maximum of data we have on the customer creation, all ou secret keys are fully protected).
But the problem is that the hacker, use our publishable key, to make calls to https://api.stripe.com/v1/payment_intents/***/confirm directly. So we have no control on this because it is on stripe's side.
I can reproduce the attack myself, by calling the endpoint with different payment method, after creating a real payment method.
What possibility can we have to avoid this attack ? Are they lot of companies that experience this kind of attack ?
Have you tried adding a Radar Rule as mentioned in the link I shared? https://stripe.com/docs/disputes/prevention/card-testing#radar