#ds-dev_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ 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/1509158468865495152
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
hey there ๐ are you referring to the payment timeline when viewing a specific payment in the dashboard?
hello, yes
I am referring to the visual timeline inside the Stripe Dashboard when viewing a specific PaymentIntent.
Our billing team looked at this specific timeline and pointed out that "3D Secure attempt failed" and "authentication_required" appear right before the successful capture. Because of this, they are concerned that our 3DS integration might be misconfigured or broken.
Could you please review this flow and confirm if everything is working as intended from Stripe's perspective?
ah I see what happened here - an initial 3DS attempt was triggered in our system because the Subscription Creation request included payment_settings.payment_options.card.request_three_d_secure: "any"
https://dashboard.stripe.com/acct_1Sx2OYGuSPnuZ91P/logs/req_A7TzbEClIZrMgh
then, when the PaymentIntent was confirmed on the client-side, that cancelled the in-flight 3DS attempt, and triggered another one:
https://dashboard.stripe.com/acct_1Sx2OYGuSPnuZ91P/logs/req_Kadm4Amn34GbSg
so technically it's true that there was a failed 3DS attempt, due to the way that your subscription creation call requested 3DS authentication
but then 3DS was successfully completed right afterwards, and the payment succeeded
so yes, this is safe to ignore, since the payment went through and was successfully authenticated with 3DS
That explains it perfectly, thank you!
Just one quick follow-up question so I can fully explain this to our billing team: why does this timeline sequence only appear for some transactions and not all of them?
Are some subscription creations bypassing that initial server-side 3DS trigger, or does it depend on the customer's bank card type?
no worries! if you can share an example of a payment that has a different timeline sequence I'd be glad to take a look and check what the difference is
๐ Hi there! I'm taking over for my colleague. Let me take a look
Hi! Thanks for jumping in. Take your time to review the logs and history above. Let me know what you think! ๐
Thanks for the example. What does the timeline look like on the Dashboard for that one?
timeline looks good on last examples
Yeah, I don't see any clear difference between the two scenarios.
Hi @vivid lake ๐ Thanks for joining the thread! Looking forward to your insights on why this flow happens only for certain transactions.
Hey! Taking over for my colleague. Let me catch up.
Hi there! No problem at all, thanks for taking over. Take your time to catch up on the history above. Let me know what you find! ๐
I think this is a display issue in Dashboard, I invite you to reachout to Stripe Support, they handle Stripe dashboard questions/issue better than us
this channel is for technical integration questions mostly
https://support.stripe.com/contact
(use the email option)