#dan_kres

1 messages · Page 1 of 1 (latest)

hazy geyserBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

twilit ermine
#

Hello

#

Nothing really has to happen...

#

You can create a new PaymentIntent or attempt to confirm that PaymentItntent again

cloud wind
#

It is confusing that the redirect url is returned for this payment intent even though it is invalid

twilit ermine
#

Hmm what happens when you attempt to visit that URL?

cloud wind
#

it is invalid and does not lead anywhere as it is expired

#

user is able to be authenitcated within 15 minutes

twilit ermine
#

Hmm I am a bit surprised that the PaymentIntent did not return to a requires_payment_method state in that case

hazy geyserBOT
twilit ermine
#

But it is possible the issuer just never alerted us to the fact that the 3DS flow expired on their end

#

So we would have no way of really knowing that the URL was not still available

cloud wind
#

okay, how can we find out that the issuer just never alerted you to the fact that the 3DS flow expired on their end

twilit ermine
#

You can't really. Mostly if you are worried about this you should have a limited timeframe that you allow a customer to attempt to confirm a PaymentIntent and then if that is exceeded you would create/confirm a new PaymentIntent instead of handling an old one.

#

Like you shouldn't really expect a PaymentIntent from 6 months ago to still be able to handle 3DS