Skip to content
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

Closed
christianfindsen opened this issue Jan 23, 2025 · 3 comments
Closed

Increase in 3DS2 failure #1974

christianfindsen opened this issue Jan 23, 2025 · 3 comments
Labels
Not applicable Indicates that issue could not be handled within this repo or publicly

Comments

@christianfindsen
Copy link

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

  1. Server-side integration: Advanced flow
  2. Client-side integration: Components
  3. SDK version: 5.7.0
  4. Android version(s) where issue occurs: All versions from 5 -15
@christianfindsen christianfindsen added the Bug report Indicates that issue has been marked as a possible bug label Jan 23, 2025
@araratthehero
Copy link
Contributor

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:

  • Can you confirm if this is indeed the SDK you are using? If so, what version are you using?
  • The error message "Error starting challenge" originates from our Android SDK when it handles the 3DS2 action. Could you double-check this?
  • Is the issue happening on the native or the redirect 3DS2 flow?
  • Is the issue consistently reproducible?

Additionally, it would be helpful if you could describe your implementation in detail and provide code snippets:

  • Could you share the steps in your 3DS2 flow?
  • If you’re using our components to manage the 3DS2 action, how do you pass the action to the component? If not, how are you handling it?
  • How are you handling redirects?

@christianfindsen
Copy link
Author

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.
I can't reproduce locally unfortunately .

When the backend are sending us a state that requires something from the user it contains the payload from Adyen.
That payload gets deserialized into an Action object that we do a when statement on,
So depending on the action type we send it to the component that should handle that type.
3DS2 will go to the 3DS2 component, RedirectAction will go to redirect ect ect

@araratthehero
Copy link
Contributor

Hi @christianfindsen,

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!

@araratthehero araratthehero added Not applicable Indicates that issue could not be handled within this repo or publicly and removed Bug report Indicates that issue has been marked as a possible bug labels Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Not applicable Indicates that issue could not be handled within this repo or publicly
Projects
None yet
Development

No branches or pull requests

2 participants