#georgew

1 messages · Page 1 of 1 (latest)

spring sleetBOT
dire saddle
#

Error on requires action will block all cards requiring 3DS. I think you want the other way, right?

patent dust
#

yes, sorry I didn't mean to paste that 😛

#

I know that this is possible with Radar for Fraud Teams using custom rules, but I'm wondering if there's a way to do this purely in the API (my client is not ready to commit to Radar just yet)

dire saddle
#

I'm not aware of a mechanism that would allow the payment to fail during confirmation if 3DS was not requested.

patent dust
#

The problem we have is that we want to guarantee that a challenge is given to certain customers.

If their card doesn't support 3DS (which is rare, I know) then we can't enforce this logic can we?

dire saddle
#

No I don't think so.

#

There isn't a corresponding error_on_not_requires_action flag

patent dust
#

One idea we have is to proceed but with manual capture. And if it went straight to requires_capture without any challenge then we'd cancel it. But that seems pretty hacky :\

dire saddle
#

That would actually be the best option currently.

patent dust
#

Ah, we could look at the payment method object to see whether 3DS is supported. And then cancel out before creating any Payment Intent.

#

ok thank you