bhaal22

[flint cobalt]

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.

• bhaal22-pm-on-destination-py, 22 hours ago, 36 messages
• bhaal22, 5 days ago, 27 messages
• bhaal22, 6 days ago, 20 messages

[compact cove]

hi, what's the question exactly?

[hazy holly]

hi

could you have a look at this sequence please ? https://dashboard.stripe.com/payments/pi_3OWlv7Gn3FuAFiGU0OlJUYVo

[compact cove]

I could. What question do you have about it?

[hazy holly]

does it mean I try in this particular sequence to confirm an already confirmed Payment Intent?

i wonder why it would happen only in that case

in such a 3ds sequence

[compact cove]

yes

[hazy holly]

the confirm can be done out of my flow?

[compact cove]

not sure, what have you found from your code investigation so far?

I would start by trying to replicate the issue in test mode and go from there

[hazy holly]

is there a way to replicate this sequence?

[compact cove]

maybe you have a "pay" button in your frontend page that can be clicked twice and is not marked as disabled after it's used, could be many things.

[hazy holly]

do you have test cards with sequence :

• 3ds failed

• 3dsv2 frictionless?

in any case, I can always be safe by checking pi_ status before confirming

[full carbon]

👋 https://stripe.com/docs/testing#regulatory-cards

[hazy holly]

do you know which one?

this one maybe?

[full carbon]

Not sure, I'd recommend just trying them out one at a time

[hazy holly]

ok

ty !

anyway I will check first the status of the pi

before confirming

if he is already sucess I keep continue