-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase in 3DS2 failure #1974
Comments
Hi @christianfindsen, thank you for opening a bug report and providing integration details. To better understand the issue, could you clarify a few points? You mentioned using the standalone 3DS2 SDK:
Additionally, it would be helpful if you could describe your implementation in detail and provide code snippets:
|
Yes that is the SDK I'm using. It is on 5.7.0. So the 3DS2 version would be determined by the version you guys bundle it with. Yes it is coming from your Android SDK inside your ActionComponentCallback::onError that I have created. The "Error starting challenge" is coming from the native while the BCMC is on the redirect. When the backend are sending us a state that requires something from the user it contains the payload from Adyen. |
After discussing the issue internally, we believe the best way to resolve this would be to contact our Support team. They are well-equipped to identify the problem quickly and escalate it to the appropriate teams if needed, ensuring a faster resolution. You could reach our Support Team via Customer Area or via email: support@adyen.com. If you need further assistance with the SDK or have additional questions, feel free to get back to us. We're here to help! |
Description
Over the last week, we have been seeing and getting reports from our users, that people are having trouble to complete a payment.
In our tracking that includes messages from the components if anything went wrong.
With the CardComponent:
We can see that the 3DS2 component is throwing an error stating "Error starting challenge". The error is thrown in the
ActionComponentCallback::onError
With the BCMCComponent:
We have gotten reports from our users that they get redirected to the 3DS2 flow and completes but afterwards they are not redirected back into the app with the payload from the 3DS2. The tracking we have in place we can see that the user are redirected and not coming back before the order has timed out.
TL:DR
We have not made any changes to this in a while and we suddenly got a lot of reports where the 3DS2 is failing to either show or navigate back after completion.
We are using the stand alone 3DS2 library, not from inside the payment option component
Integration Information
The text was updated successfully, but these errors were encountered: