5 ms·
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
by edwinwee 7y ago
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 https://stripe.com/docs/payments/payment-intents)
I’d love to take a closer look at exactly what happened if you email me at edwin@stripe.com.
- leto_ii 7y agoJust 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?
- edwinwee 7y agoIdempotency 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 https://stripe.com/docs/radar/risk-evaluation#high-risk [2] https://stripe.com/docs/radar/rules https://stripe.com/docs/radar/rules
- leto_ii 7y agoThanks for the reply :)
- newsbinator 7y agoBig thank you to Edwin for emailing & helping me solve the issue.