Sergei P.

[prime ingot]

Hi there 👋 it is not possible to listen to the events fired by the element that will contain sensitive card details, that information is not exposed.

For card brand choice scenarios, you'll need to first create a Payment Method for the card, which exposes what networks the card supports. Then when creating/confirming the Payment Intent to process a payment, you can use the payment_method_options.card.network to control which network the payment is processed over:
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_options-card-capture_method
https://stripe.com/docs/card-brand-choice

If your goal is to outright block a certain type of card and you use Radar for Fraud Teams, then creating a custom Radar rule to block those based on the card_brand would likely be a better fit:
https://stripe.com/docs/radar/rules/reference#:~:text=the card number.-,card_brand,-Case Insensitive String

[vale vigil]

@prime ingot Thanks, I'll check

Radar rules are not our choice, because customers are created dynamically