#web40moon

1 messages · Page 1 of 1 (latest)

inner havenBOT
olive walrus
#

hello! To clarify, do you mean you want to block all cards that don't perform 3DS?

livid shore
#

No, I want to block all card that has 3Ds.

#

Only allow simple CC or debit card.

olive walrus
#

why though? Issuers are more and more likely to shift to using 3DS

livid shore
#

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.

olive walrus
#

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

livid shore
#

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

olive walrus
#

you'll need to implement that logic

livid shore
#

So how can we know at the time of add card that, this card has 3DS or not?

olive walrus
#

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

livid shore
#

From test mode?

olive walrus
#

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

livid shore
#

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

olive walrus
#

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.