#jonas-pfrang_api

1 messages · Page 1 of 1 (latest)

spiral dragonBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1364246711694004264

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

ornate glacier
#

Hello, radar is our anti fraud tool where we can reject or request 3DS based on risk level, metadata, and other factors. That field lets you see the ID of the specific rule that was triggered if relevant
https://docs.stripe.com/radar/rules

#

Can you tell me more about what you are trying to figure out here?

near rune
#

Unfortunately, it has been closed already :-(.

#

I am a bit unsure whether we could maybe use "outcome.rule" for achieving what we would like to achieve. For this, it would be important to know (a) what "rule" means and (b) whether only the rule id is in the response (or maybe also a textual description)?

ornate glacier
near rune
#

Unfortunately, I am currently not having a Stripe account to test it within the test mode. Is there another option or a more detailed documentation?

ornate glacier
#

You can create one for free at Stripe.com and can skip providing a lot of the info that it asks for, not much info is needed to test. I can see if I can find something

near rune
#

This would be great!

ornate glacier
#

It looks like it gives the rule type and the actual text of the rule as well, no text description

rule: {
  id: "ssr_1MJipHJmquaq3LbpkgMNcUqz"
  action: "block"
  predicate: ":email_domain:='block.me'"
}```
near rune
#

OK. And is it possible to add a text description as part of the rule object?

ornate glacier
#

Unfortunately not. You would need to keep a mapping of rule ID -> name on your side

#

I checked and those are the only three fields that the API can expose for rule objects

near rune
#

Perfect! This helped a lot! Thank you so much! Really great and fast support!

ornate glacier
#

Of course! Happy I could find some answers here at least

near rune
#

Just a follow-up question: Is it possible that multiple rules are triggerd and, therefore, would be in the response?

ornate glacier
#

Only one rule will show up here. Each rule will individually effect a payment or not, so even if two rules could have blocked a payment, only the one that is evaluated first will be the one that actually blocks the payment

near rune
#

Ah ok - understood. So only if a payment is blocked, the rule object will not be null?

ornate glacier
#

There are other types of rule as well such as "Allow", "Request 3DS", and "Review". I think by default on your account there will only be block and 3DS ones but that will definitely be something to double check when you have an account https://docs.stripe.com/radar/rules

near rune
#

Ah okay. However, if I am correct "outcome.rule" does nothing have to do with "Stripe Radar’s evaluation of the riskiness of the payment". The riskiness of a payment might be used as a numerical value by a rule to block, etc. a payment. Correct?

ornate glacier
#

Correct, each payment will have a risk score regardless of what other rules may apply here. You'll get a risk score even if no rules trigger

spiral dragonBOT