#Arkalezard-help

1 messages · Page 1 of 1 (latest)

light path
#

Hello, how can we help you?

sullen moon
#

On production, my users are encoutering an error I want to reproduce to investigate and fix it

#

It's link to 3DSv2

#

The error they are receive is
Class
com.stripe.android.exception.APIException
Message
Error encountered during 3DS2 authentication request. Code: 402, Detail: Acs is Timed out, Description: Transaction Timed-out, Component: D"

#

The second message error I need to test and ifx is
Class
com.stripe.android.exception.APIException
Message
Error encountered during 3DS2 authentication request. Invalid 3DS2 authentication response

#

I need help to simulate these behavior and optimize the user experience

light path
#

Thanks for the detail. Looking in to this and will get back with what I can find

sullen moon
#

Thanks 😄

#

For your information, when there error are happening. 3DS validation is failing but the transaction is working on Stripe.
I able to share you examples of these transaction if it can help you

light path
#

Yes please if you can

sullen moon
#

But the error is happening between 3DS and my app so I don't what you'll see

#

We refunded manualy all these transactions because user was unable to see that the transactions were working

light path
#

Gotcha. And thank you. I can actually see the issues on our side it looks like the API Exception is the result of us responding to you on a 3DS authentication call

#

Looking in to how one may react to this and how you can test this yourself

sullen moon
#

great

#

you'll be back to me on this thread?

light path
#

Yes I will

#

Still looking in to this. Unfortunately it doesn't look like there is a good way to recreate this error. I am seeing what info I can get on how to react to it

#

Like what will indicate if a 3DS error means the customer needs to retry vs if it will succeed like this

sullen moon
#

There are others errors not only 402 in my dashboard but there are the most common

#

In term of stat, its the top 2 in APIException

#

See you soon 😉

light path
#

Hey thank you for you patience. So unfortunately this is a bug in our Android SDK. The SDK should not be throwing an exception to you here it should be handling the error itself. I have raised an issue about this internally and there will be a fix in a later version.

#

Unfortunately I am not sure what might be a good workaround in the meantime. You can listen to webhooks to tell when these PaymentIntents have actually succeeded and can provision/notify the user on that if that is appropriate but I get that that is not a great flow in your app

sullen moon
#

Do you have a github issue to track it?

#

Hi, and thanks for the update

sullen moon
#

Did you already release the fix?