Unable to relate supported brand with the supported paymentMethodVariant in the web drop-in onBinLookup

[shadowtje1990]

Is your feature request related to a problem? Please describe.
I am using the onBinLookup from the web-component https://docs.adyen.com/payment-methods/cards/web-component/ to identify what type of brand and paymentMethodVariant the card is. This works fine as long as the card does not have a duo brand.

As example when I use this test card
4035 5014 2814 6300 | Visa Debit / Cartes Bancaires

Now there is no way to associate what paymentMethodVariant to use for the brand that I have and is supported.

Describe the solution you'd like
I would like to be able to associate what paymentMethodVariant to use for the brand that I have and is supported from the onBinLookup in the web-component.

Describe alternatives you've considered
The paymentMethodVariant is only available in 2 situations

1. After a payment. (sadly this is not an option for us because we need this for our costEstimation and we need this before a payment)
2. in the onBinLookup from the web-component but this has this limitation as explained above.

[sponglord]

@shadowtje1990 Can you please explain what you mean by

Now there is no way to associate what paymentMethodVariant to use for the brand that I have and is supported.

It's not clear what you mean, or what you would like to be working differently

thanks

[shadowtje1990]

Hi @sponglord,

I'll do my best to explain this more clearly.

When you input a card number, it triggers the onBinLookup call. This call retrieves information about the entered card, such as the brand and paymentMethodVariant. From my understanding, the paymentMethodVariant is linked to a brand and provides more specific details about the card type.

However, for cards with multiple brands (e.g., 4035 5014 2814 6300 | Visa Debit / Cartes Bancaires), you receive an array of paymentMethodVariants for both brands, but there's no clear indication of which paymentMethodVariant corresponds to which brand. I would like a way to correlate the paymentMethodVariant with the brand from this call without needing to manually map the entire payment method variant list (which isn't even complete, as noted on the page).