#sasa.sekaric-payments
1 messages · Page 1 of 1 (latest)
Give me a second to copy and hide customer details...
ah well that one is just a weird edge case, the payment failed because of a card testing(https://stripe.com/docs/card-testing) rate limiter
I saw this before and basically if the charge fails in one of those limiters they don't generate an outcome . We raised that feedback to the product team last month. They say they can't change it, because there is no actual charge to the banks(we block the charge before then). The API doesn't actually guarantee that outcome has to not be null, it just usually isn't.
OK, but how we can support this customer. What we should do? We can't say it's because some Stripe limiter 🙂
So, it's something about the card that this customer is using?
This customer tried 2 times with the same card, and both times got same error. So it must be something with the card.
yep it means they've tried using that card too much in one day so we suspect it as fraud
probably not just on your account but maybe other Stripe accounts
you want to talk to https://support.stripe.com/?contact=true about this, not here since it's not an API question