#hellotika
1 messages ยท Page 1 of 1 (latest)
Hello
No that's not really possible. You can see the supported attributes here: https://stripe.com/docs/radar/rules/supported-attributes
That said you can always use metadata to create arbitrary rules: https://stripe.com/docs/radar/rules/reference#metadata-attributes
is it applicable to metadata to the PaymentIntent entity?
the adding arbitrary rule by metadata approach
i try this and it won't take my arb rule
๐ hopping in here
i got it it's single quote
๐
but it didn't request3ds for my test card 4000000000003055 with that md
on payment intent
Can you share that payment intent ID so I can take a look?
pi_3NpwlkHFPm42d8Jm1qDaZwSB
maybe i need to use a different test card
tried 5555555555554444 also didn't prompt
pi_3NpwxUHFPm42d8Jm1d7mb4QM
i got front end working for 3ds cards
Did you actually add that radar rule to your account? I don't see it on the accuont tied to pi_3NpwlkHFPm42d8Jm1qDaZwSB
after adding that rule, it navigate me to "review new rule" but there is no further save/enable button on that page
oh, i have to click on the "add rule" AGAIN
yup! (I'll flag that the flow is a bit confusing to the team to hopefully improve it in the future)
5555555555554444 have 3ds attempt but succeeded right away, the bank 2fa pops up and disappear
4000000000003055 also does not trigger 3ds
the radar condition added does not seem to do anything
Do you have a new Payment Intent I can take a look at? For the new attempts with the 3055 and 4444 test cards?
i disabled the radar rule but still get 2fa with this card pi_3NpxLHHFPm42d8Jm06kGIal0
4000000000003055
As far as I can tell the radar rule is still enabled
getting to know the radar pages now
everything needs doubel confirm
so i can really only test this radar rule using 3ds supported sample card that radar don't request by default, i.e. 4000000000003055?
is there other test cards ito use or go through
do u have an idea where canadian credit card belongs most in terms of 3ds/2 required, 3ds/2 supported - OK, Error or Unenrolled?
Let's back up for a minute here - what specifically are you trying to accomplish with this rule?
using the rule to allow incoming request to charge to indicate whether to request3ds via metadata on payment intent
i played with the request3ds field on payment method but this only possible with paying via a payment method not via a payment intent
using a radar rule to trigger 3ds when md exists also allow us to make use of dashboard to enable/disable at runtime
Ah gotcha - was going to ask why you didn't just request 3DS on the payment intent itself (https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_options-card-request_three_d_secure)
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
but that won't work if you want the ability to enable/disable it at will
yeah we want to leverage that enable/disable upon demand in case we see a high regections
Yeah if you want to be sure your rule is working then I'd actually suggest disabling all the other 3DS rules (like the one that requests 3DS if it's required) and then try some of the test cards from this section (https://stripe.com/docs/testing#three-ds-cards).
there is no field anywhere to indicate if the card has 3ds supported BUT it's unenrolled right?
As far as I know there isn't