#xjojix
polar oriole
dim vale
Is there a reason you need to know the difference? Are you trying to write a custom radar rule to check that 3ds was done?
dusky shadow
yes, I want to require 3ds for all the cards
dim vale
The best way to do that would be to modify the 3ds rule we provide here (https://dashboard.stripe.com/test/settings/radar/rules?startDate=2023-01-11&endDate=2023-07-11) and enable it for all three conditions
dusky shadow
enable it all three? not just "supported"?
what would happen to the card which 3ds is not supported?
dim vale
If 3DS isn't supported for the card there's no way to require it
dusky shadow
I want to block it
to be spefic, my rule is like this
:transaction_type: = 'setup_intent' and not(:has_liability_shift: and :is_3d_secure_authenticated:)
and I want to know the difference "is_3s_secure" and "_authenticated"
the goal here is to prevent people using other people's cards.
dim vale
is_3s_secure represents whetehr 3ds was attempted for the card
and is_3d_secure_authenticated is only for IF 3DS was attempted whether it was successful or not
dusky shadow
so i shouldn't change my rule to is_3d_secure
attempted and fail would still return true for is_3d_secure correct?
or even user has not yet registered 3ds on there card.
dim vale
Yes, attempted and failed would return is_3d_secure true
if 3ds is not suported then it'd be false
if you haven't already you should read this section as well (https://stripe.com/docs/radar/rules#request-3d-secure)
dusky shadow
in the example rule
:is_3d_secure: and :is_3d_secure_authenticated:
can't it just be :is_3d_secure_authenticated?
dim vale
Most folks also want to know if 3DS is supported which is why they check both (just to be sure)
dusky shadow
oh, yeah, they want to check if 3ds is supported in the first place.
thanks for the support @dim vale i understand better now
dim vale
👍