#Gilson-PaymentIntent
1 messages · Page 1 of 1 (latest)
No AFAIK. Could you give me an example request id of cancelling taking too slow? I can give a quick check
when I say taking too long is because sometimes I need to cancel something like 100 abandoned payments, and for every payment intent cancel request, can take up to 2..3 sec, so that list of 100 abandoned payments will take a fair amount of time to be processed
I see
It's totally out of curiosity but I wonder what business scenario is that you need to cancel 100 abandon Payments?
in the end I am afraid the answer is no, unfortunately we don't have such an API
well, in order to display the apple or google pay, I have to create the payment intent in stripe
But if that's a batch processing, then maybe you can build a queue and call the Cancel API subsequently
when the users see the "confirm payment" and they do not confirm, they leave the page or go to somewhere else, those payment will be marked as incomplete forever
as we sell some tickets such as a raffle ticket, we cannot hold those things forever we kind of cancel them as that batch can release the "on hold" ticket to the next guest can buy it
how long an payment intent can be "incomplete" like forever?
Forever