In the midst of the launch frenzy, I glanced at our Stripe dashboard. At first, I thought, "Wow, that's a lot of new subscriptions!". T

Handling a Stripe Payment Attack During Our Product Hunt Launch

submited by

Style Pass

2024-11-30 19:30:06

In the midst of the launch frenzy, I glanced at our Stripe dashboard. At first, I thought, "Wow, that's a lot of new subscriptions!". Transactions were pouring in—hundreds within minutes. But my excitement quickly turned to concern.

Upon closer inspection, I realised that thousands of dollars in fraudulent transactions had been blocked in just a few minutes, all originating from the same country. We were under a coordinated payment attack.

According to research by Juniper Research, payment fraud losses are expected to exceed $343 billion globally between 2023-2027. It's a widespread issue that can hit anyone, with fraudsters becoming increasingly sophisticated in their attack methods.

I noticed all the fraudulent attempts were coming from a single country (PK). Using Stripe's Radar rules, I set up a temporary rule to block transactions originating from that country. This immediately reduced the number of incoming fraudulent attempts.

We lowered the risk threshold in Stripe Radar from 75% to 50%. This made our fraud detection more sensitive, catching more suspicious transactions before they could proceed.