#web40moon
1 messages · Page 1 of 1 (latest)
hello! To clarify, do you mean you want to block all cards that don't perform 3DS?
why though? Issuers are more and more likely to shift to using 3DS
Actually we have a huge code that works perfectly with simple CC and debit card but not with 3DS.
So to manage this, We need to change the flow in code. So right now we don't allow users to use 3DS cards.
hmmm okay, but this isn't something which i would configure in Radar. If your app doesn't support 3DS right now, you can probably display an error message if the PaymentIntent is in status=requires_action and ask the customer to provide new card details
you can also disable the rules to request for 3DS as mentioned here : https://stripe.com/docs/payments/3d-secure#three-ds-radar
Can we do like => if the user adds a card to our app at that time we give him the error that the app only allow the non-3d card
you'll need to implement that logic
So how can we know at the time of add card that, this card has 3DS or not?
https://stripe.com/docs/api/cards/create
I checked this, but none of the param helps me to know that it's 3DS or not.
Can you share your account id so that I can take a closer look at how your integration works? It'll looks like acct_123
From test mode?
if you have different accounts for test/live, it should be the livemode one, i'd need to see how your integration is working in livemode
acct_1LpqxrCMBV5MukvB
This is from test mode. Please check if you can.
For live mode, I can't share it now.
Extremely sorry for that
your test account doesn't really have a lot of info on it. All I can see is that you're using Tokens which is very very old and doesn't support 3DS anyway. You should migrate to PaymentIntents asap.
You can test what happens when you try to create a payment with a Card Token with a card that requires 3DS : https://stripe.com/docs/testing#regulatory-cards.