News for hackers. Stuff that matters.
Re:Stripe charged me $714 for duplicate transactions within ... by edwinwee on Wednesday February 12, 2020 @04:13PM (#22312877)
Agree with the other comments on idempotency. If you need help with that, please let me know.

(Also: Stripe‘s Payment Intents API is asynchronous, which means no double charges. I’d recommend looking into it! https://stripe.com/docs/payments/payment-intents)

I’d love to take a closer look at exactly what happened if you email me at [email protected].

Re:Stripe charged me $714 for duplicate transactions within ... by newsbinator on Thursday February 13, 2020 @08:03AM (#22317375)
Big thank you to Edwin for emailing & helping me solve the issue.
Re:Stripe charged me $714 for duplicate transactions within ... by leto_ii on Wednesday February 12, 2020 @04:21PM (#22312945)
Just out of curiosity, does the idempotency guarantee cover deliberate shopper actions, or just retries due to network errors?

Shouldn't high velocity + high amount purchases be treated as potential (friendly) fraud and blocked by some fraud system somewhere?

Re:Stripe charged me $714 for duplicate transactions within ... by edwinwee on Wednesday February 12, 2020 @04:41PM (#22313103)
Idempotency doesn't. It's meant to prevent duplicate actions.

For what you're talking about, that fraud system is already built into Stripe! Stripe's fraud shield detects high velocity (along with hundreds of other signals)[1]. You can also tune Stripe Radar[2] to block purchases with amounts that would be abnormally high for your business.

[1] https://stripe.com/docs/radar/risk-evaluation#high-risk

[2] https://stripe.com/docs/radar/rules

Re:Stripe charged me $714 for duplicate transactions within ... by leto_ii on Wednesday February 12, 2020 @05:06PM (#22313336)
Thanks for the reply :)