Cannot test 3dsecure 2 credit card without cvc, cannot make CVC not mandatory

[lluishi93]

Describe the bug
We're trying to test different credit card numbers. In the page below, there are some cards listen. We tried to use the one marked in the screenshot:

https://docs.adyen.com/development-resources/test-cards/test-card-numbers#test-3d-secure-2-authentication

But there's one issue: CVC is always mandatory in the dropin, and I could not find any option to make the dropin recognise when the CVC is mandatory or not, or at least make it not mandatory at all. The only option I found is hideCVC, but that's not what we intend to do.

To Reproduce
Steps to reproduce the behavior:

1. Set up the dropin as you would normally do.
2. Fill the fields with the previously mentioned test credit card.
3. Try to submit the dropin.
4. Verify that the CVC field is marked as incorrect

Expected behavior
The dropin should recognise when the CVC is required or not, or at least allow to instantiate the dropin with the CVC not mandatory at front-end level.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• iOS
• chrome
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[sponglord]

Hi lluishi93,
Can you tell me what version of adyen-web you are using?
Because we cannot recreate this issue. This is what we see when we try to pay with this maestro number:

[sponglord]

This was tested with v3.6.1, v3.13.1 & v3.14.1 on both desktop and Chrome in iOS

[lluishi93]

@sponglord we're using the npm package with the following version:

How did you set the CVC to optional?
Maybe you could provide how you instantiated the dropin, posting its config

[lluishi93]

Could it be related with the supported card types? ATM, we do not provide any array with supported cards, and according to documentation:

I see that the Maestro cards are not supported in the default array... could it be related to that?

[sponglord]

Indeed - you are not saying that you support maestro. Therefore we cannot recognise the brand and make decisions about whether the cvc is optional or not.
What happens in this case is we say: "we don't recognise the card brand from this number, but if it validates correctly we'll allow the shopper to try and use it". But then of course we treat it as a "regular" credit card (needs date & cvc)

[lluishi93]

Ok, so we can close this for now then! TY