#tianyouli - radar rules
1 messages · Page 1 of 1 (latest)
Still looking in to when exactly they apply. Are you talking on object creation or when trying to confirm them?
Are you currently not seeing a rule applied when you would expect it to?
We are evaluating if we'd like to use Radar for Fraud teams, so wanna understand when the rules are applied.
in our use cases, setup intents are created at checkout but payment intents are created from the backend after other verification processes. So i'm mostly interested in relevant attributes to apply rules on for our scenarios
Gotcha, so yes you can have radar rules to apply to both scenarios. To allow Radar to apply to SetupIntents as well, you can turn on "Use Radar on payment methods saved for future use" in your Radar settings https://dashboard.stripe.com/test/settings/radar
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
And if you want a rule to only apply to one or the other, you can use the transaction_type attribute to differentiate between PaymentIntents and SetupIntents
using transaction_type to differentiate would only be available in Radar for Fraud Teams , right?