#tarantino-47_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/1468084765252128820
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- tarantino-47_unexpected, 5 hours ago, 39 messages
hello Alex this is the archived thread #1467969446302711871 message
I can now provide you with the link to reproduce
hmmmm, from what I see from the previous conversation, this can only be replicated in livemode right?
yes
also, we have the same issue on mobile app!
we are using stripe sdk for RN
RN might be using iframe for 3ds as well
If it can only be reproduced in livemode, and specifically with Discover cards, I'm going to need to request that you keep your livemode site alive if possible, and I'll share with you a link to create a ticket. We don't have a Discover card on hand right now, so we're going to need to get someone else to test.
Hello @modest iris, we have sent you a direct message, please check it at https://discord.com/channels/@me/1357399963889307770
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
but give me a second to look at the PaymentIntent example you previously shared first
From what I can see from that PaymentIntent you shared, it just looks like the 3DS was rejected from the issuer
Did you try reaching out to the issuer to ask about why the 3DS was rejected?
hm, im not sure if it's possible? we have a bunch of failed transactions of our users
There's not much that we can help with if the issuer is rejecting the 3DS authentication. What happens is that Stripe will send a request to the issuer to request for authentication, but the issuer is rejecting it at this point, which is why it never gets to showing the 3DS modal. There's not much that we can help with here because we have no insight into why the issuer is rejecting 3DS.
If you have tried this yourself, with your own Discover card, can you reach out via that link, share the specific PaymentIntent ID, and I can share a ID which you can include when reaching out to the issuer to check on why the authentication was rejected
⛔️ Stripe developers have stepped away for a short while
Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.
thank you Alex, but I’m a bit confused. Since Stripe is the party initiating the 3DS authentication request, is there really nothing Stripe can do?
does this also mean that all Discover payments requiring 3DS are currently failing on Stripe for all Stripe merchants?
ping to keep the thread opened
do you have any thoughts on the questions above?
👋 Taking over this thread, catching up now
From the integration perspective, the flows look fine to me. This channel is for technical questions such as API integration with Stripe. I'd recommend writing to Support https://support.stripe.com/contact, so that they can check with the relevant team if there is any further action that Stripe can do, or if these are the genuine rejections from the banks issued these Discover cards