huncsuga_best-practices

[dawn wolf]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1488440238022856704

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[stiff ember]

Stripe doesn't send a real-time or immediate event when the customer leaves or disconnects from the 3DS authentication process.

Stripe internally has a timer for the 3DS completion. If the customer doesn't complete within the timeout period, a payment_intent.payment_failed will be sent.

Alternatively, your system can also implement your own timer. If the customer didn't complete the within the specified timeframe, your system can send a Payment Intent cancellation request if the status remains in requires_action status: https://docs.stripe.com/api/payment_intents/cancel

[median needle]

Thanks! Could you clarify how long the 3DS timeout period is before the payment_intent.payment_failed event is triggered?

[stiff ember]

We don't have the timeout to share, but it typically takes at least 15 mins or longer.

[median needle]

Just to clarify: if I understand correctly, in cases where the 3DS flow is interrupted (e.g. the user closes the browser or loses connection), once the 3DS timeout expires (e.g. ~15 minutes or more), the payment will automatically transition to failed and a payment_intent.payment_failed webhook event will be sent, right?

[stiff ember]

Yes, that's right!

[median needle]

Thank you very much for the answers.