Difference in drop in challenge behaviour between 3ds checks for instant payment methods and inline card numbers about adyen-web

[sponglord]

@terrymccartan-toast - I'm referring this question to our Authentication team.
I'll let you know when I know more.

In the meantime can you tell us what version of Dropin/Components you are using? And against which version of the CheckoutAPI?

[terrymccartan-toast]

Hi @sponglord - its checkout api version 70 and the drop in component 5.53.3

[sponglord]

Thanks, and can you just confirm that you are setting this:

authenticationData: {
  threeDSRequestData: {
    nativeThreeDS: 'preferred'
  }
}

? re. https://docs.adyen.com/api-explorer/Checkout/70/post/payments#request-authenticationData-threeDSRequestData-nativeThreeDS

[terrymccartan-toast]

Yep confirmed we are setting it on the /sessions request and it seems to have no affect when paying with the google pay instant payment button. The full redirect still occurs.

Our question is whether the redirect is valid or should the challenge window be displayed within the drop in component

Thanks!

[sponglord]

@terrymccartan-toast - do you have a pspReference?

[terrymccartan-toast]

Sure thing. We have a couple

HG6H5C9XXQDG96F6
HDVW438TTVBVDND3
HDVW438TTVBVDND3
P4VTD49RXNXLV3X3

All of these ended up in a full page redirect - where we have seen with cards the challenge window is displayed inline

heres one where we explicitly called out preferred on the initial session
JHDQFKT92WNM9J65 - (session id CSDCDE56F1331F427F)

[sponglord]

@terrymccartan-toast - thanks for the refs

To answer your question the redirect is valid - it's a legitimate flow.
I'm just trying to establish (from our Backend & Authentication teams) if there is anything you can do, via config props, to influence this flow for Instant payment methods, and bring it inline

[sponglord]

@terrymccartan-toast - turns out it was an issue on our side.
The GooglePay component wasn't passing on a property necessary for our backend to decide whether to route the 3DS2 through a native or redirect flow.
This has been fixed in #2690 and will be available in our next release

[terrymccartan-toast]

Fantastic - thanks @sponglord for seeing this through