#Cory

1 messages · Page 1 of 1 (latest)

polar echoBOT
long fiber
#

Hello! Can you provide more details? Not sure I understand your question.

keen shell
#

I have a test rule ":risk_score: > 4 and :distance_between_ip_and_billing_address: > 200"

#

and it's not showing a payment that I can see in the dashboard that falls under this condition

#

Here is the payment

#

pi_2MonMJSeFe0t7sFD0oJq7Yb3

#

As you can see, distance between billing and IP address
834.93 miles,

and risk eval is 5

long fiber
#

Looking...

long fiber
#

I think what happened here is one of your allow rules let this payment go through.

keen shell
#

interesting

keen shell
long fiber
#

That depends on how you define a "new signup". Can you provide more details?

keen shell
#

a new customer subscribing

long fiber
#

But how do you define "new customer"?

keen shell
#

When a person who is not in the system, signs up for our product, a new customer is created in Stripe, and then subscribed to our product - not sure what you mean I guess

#

first one subscription charge, as opposed to a recurring one?

obsidian crag
#

This would be up to you based on the available rules and the logic you want to use. There's no built in rule to catch what you describe, but you could implement something perhaps based on checks against customer metadata

#

ie, after an initial period you set some customer metadata and write rules to check that

keen shell
obsidian crag
#

What is not working? Can you share a specific payment ID and what you expect to happen?

keen shell
#

pi_2MonMJSeFe0t7sFD0oJq7Yb3 should appear

#

I am doing a review rule of, :risk_score: > 4 and :distance_between_ip_and_billing_address: > 200"

#

It should appear

#

and it does not

polar echoBOT
obsidian crag
#

(sorry got lost digging into this)

obsidian crag
#

@keen shell Are you potentially mixing up accounts you're making requests with and editing rules on?

keen shell
#

no

keen shell
obsidian crag
#

For the account used to create the subscription related to that payment, I'm not seeing any rule like the one you describe

keen shell
keen shell
brave wadi
#

To the dashboard's landing page?

#

In that case would you mind clicking on the person icon in the upper right of that page, clicking on "Profile" and then scrolling down to the bottom of the page. That should tell you what account you are currently on

keen shell
#

acct_1ntwSeFe0t7sFDQdm8KK

brave wadi
#

Did you set the rule :risk_score: > 4 and :distance_between_ip_and_billing_address: > 200" ? I am not currently seeing it on that account? Was this a review before setting the rule?

keen shell
#

I am using the "test review"

polar echoBOT
urban seal
#

Hi stepping in here and taking a look. Can you confirm what the outstanding question is here?

keen shell
#

Well I have another question relatd to this

#

if I use metadata, how can I check if the metadata exists at all?

#

For example, I set a value in metadata to true, but I want to check if false or doesnt exist at all since all rpevious customers will not have metadata attribute

#

nvrmuind I found is missing

urban seal
#

You can check the metadata by retrieving the specific object you passed that metadata to.

keen shell
#

my previous q1uestion didnt seem to be answered, but that;s okay. Do you not have access to the previous conversaation?

urban seal
#

Glad to hear this one is resolved.

#

Can you summarize the ask here again?

brave wadi
#

Apologies, I can summarize, they are trying to set the rule :risk_score: > 4 and :distance_between_ip_and_billing_address: > 200" but aren't seeing pi_2MonMJSeFe0t7sFD0oJq7Yb3 which they believe should appear. The risk score on that intent is 5 but I was having trouble figuring out what was calculated for distance_between_ip_and_billing_address

urban seal
#

Thank you, taking a look

#

Cory, I recommend that you reach out to Stripe support as they have folks who have more expertise with how Radar rules apply here.