#Fun_GKC - reject 3DS cards

1 messages · Page 1 of 1 (latest)

tawny dawn
#

Checking in to this. It may be possible via a Radar rule. Can you tell me more about why you are looking to block 3DS cards here?

tawny anchor
#

Thanks for the reply!

I don't want to block all 3DS cards. I only block cards which might require authentication when I charge the card off-session. This allow me to construct a simpler payment flow and the customers don't need to come back to my website every month just to complete the authentication. Not to mention if the customer is charged multiple times every month.

I also evaluated Radar rules. There're two problems.

First, it costs money to use. I could achieve the same thing using the old API but not with new API. I need to pay for a free-to-use feature after the migration.

Second, the Radar block rules don't block when confirming a SetupIntent. It only blocks in the payment stage (PaymentIntent). It means I still have to handle the case which customers need to re-authenticate. It doesn't make the payment process easier for me to implement.

tawny dawn
#

I don't know if it is possible to make that distinction unfortunately. As far as I know, any 3DS card may require authentication any time it is used. They typically don't when set up for off session payments but it is ultimately up to the banks to decide when to ask or not ask

tawny anchor
#

Ok, thanks. Look like I cannot avoid it and need to handle that 😃

tawny dawn
#

And I am stepping out but my colleague hanzo can help you with any followup questions that you may have

tawny anchor
#

I don't use subsciption and invoice. I only use payment_intent. How do I handle payment intent that requires authentication?

final sage
#

👋 Pompey had to step away, give me a moment to catch up here 🙂 thanks