#basta
1 messages · Page 1 of 1 (latest)
Hi. I wish I could help, but this chat is focused on developers and technical questions. Our support team will be able to assist you better than I can: https://support.stripe.com/contact
Hey @verbal blade, I was hoping for any tips, like using webhooks to add the customer to a blocklist, or things like that. Or ways to invalidate the checkout session and the key that the checkout session page is using.
So far it seems like our only course of action is to stop using Checkout and switch to Elements so that our server sits between the carder and Stripe's API.
The problem is fundamentally that there's no obvious mechanism for programmatically stopping the carder's use of the API once they've reached Checkout
Can you clarify what you mean by 'carding'?
Card cashers are repeatedly attempting to create charges using stolen PANs to test which card details are still valid so they can make fraudulent charges with them.