Altrollique-Android-3DS

[forest moat]

Hi 👋 can you share the error that you're encountering?

[hexed frost]

here the picture of what happens

1. I give the card info
2. 3d secure opens
3. it close with this error

[forest moat]

Thank you for that. I noticed that the card number shown there doesn't seem to be one of our test card numbers, does this mean that you're replicating this in live mode with an actual card that requires 3DS to be completed?

[hexed frost]

yes exactly. I'm on production build, with my personal credit card (CCV is changed before screening) it's a credit card that work perfectly otherwise

[forest moat]

Do you have the ID of the associated Payment Intent from one of these attempts that you can share so I can pull that up on my side?

[hexed frost]

Customer is cus_Ha3ysnnW8ci3Da
setup intent ID seti_1L8mMbIx0RS0Ub2TO5iyDrc0

here I follow the process described in this doc
https://stripe.com/docs/payments/save-during-payment-cards-only?platform=react-native

[forest moat]

Thank you

[hexed frost]

I can also give you code from the screen and the bit I call to get the client secret on API side.

here is the code from the screen

here is a part from our api but show basically what I do to fetch client secret

[forest moat]

Thank you again. I've taken a closer look at that from my side, and what I'm seeing is that the authentication failed, but I'm not seeing details on why.

When it comes to the 3DS challenges we only provide the popup/modal for content to be displayed in, but the actual content and associated challenge flow is provided and controlled by the issuer of the card.

Are you seeing this for a wide range of cards, or just a small subset? If the latter, I would recommend that you reach out to those issuers to see if they can help identify why their authentication flow failed.

[hexed frost]

we have this issue from a wild range of card. For the moment I can tell we have 5 or 6 different bank listed with the issue.

I have a different error to share you. It comes from when a user attempt a payment

for this we use a WebView provided with the uri given in response from the payment_intent

<WebView
    onLoadStart={() =>  {
        setVisible(true)
    }}
    onLoad={() => {
        setVisible(false)
    }}
    onError={error => {
        dispatch(errorOccured(error))
    }}
    style={{flex: 1}}
    source={{uri: uri}}
    hidesWhenStopped={true}
/>   

[forest moat]

Thank you for the details. I've been conferring with my teammates about this and think this is something we'll need to pull into a support ticket so we can take a closer look. Would you mind summarizing your findings so far and writing into our support team with that. Please reference my name when you do.
https://support.stripe.com/?contact=true

[hexed frost]

Is there anyway I can continue with you. I've been loosing my day with stripe support, I've been in contact with like 8 different ppl and I had no follow up on my issue. I would be the 4th ticket I create for this issue as I never get solution or even response to tell me the someone is working on it.
I got more deeper in the problem in 1h with you than the rest of the day from the support

[zinc dove]

👋 sorry for the delay. If you write into support and mention toby in your email then my team will grab that support ticket and correspond with you directly over email.

We just won't be able to debug this effectively further over this chat so we need to move over to email to do so, but you will still correspond with the same folks you have been talking to on discord.

As an alternative, if you want to DM me your email that you have contacted Support with, we can grab one of your tickets where you have already written in.

[sturdy fossil]

You can check our ticket reference : 26076904 . Email address : [e-mail]

[zinc dove]

I'm sorry you are having this issue. We will follow up via email.