#sasa.sekaric-payments

1 messages · Page 1 of 1 (latest)

tribal bronze
#

do you have an example pi_xxx PaymentIntent with that issue?

broken cedar
#

Give me a second to copy and hide customer details...

tribal bronze
#

I only need the ID

#

pi_xxx , nothing else

broken cedar
#

Ah, OK, just a second.

#

pi_3LKTx4FPqRZZsGpW0xFcViVI

tribal bronze
#

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.

broken cedar
#

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.

tribal bronze
#

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