#donb-risk_score
1 messages · Page 1 of 1 (latest)
hello, so full disclosure, I'm not an expert on this part of the API but my read of the API ref is that either of those fields is not present or parsed into the risk_score property on the Charge object, presumably cause there was some error on the Radar evaluation on that Charge.
that is what I think it is, but let's start here, do you have a Charge ID that ran into this, I can look it up and get a better picutre
py_3JX9x4Bg9hxzNH6K1lQ2MCFC
ah gotcha thanks so here's what I understand, this was an ACH debit payment, my understanding is that this wouldn't have a risk_score field at all, and that is why risk_level is not_assessed
going off of the explanation in the docstring: https://stripe.com/docs/api/charges/object#charge_object-outcome-risk_level
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Ah ok, that makes sense. Thank you!
so you can first check if the Charge is a card Charge and has a risk_score field / property and then access it
So if the Charge is a card charge but it doesn't have a risk_score field. We'd consider that an error right?
you wouldn't consider the whole thing an error, just that the Radar Evaluation could have faced an error, the actual Charge might have succeeded or declined
Gotcha, in those cases is there a way for us to retry the radar evaluation, or check again to see if it's succeeded later?
Let me check on that - I would assume there isn't, but I'm not sure
What'd you find?
Sorry for the very very long wait - I don't see anything that says we retry and eventually change the radar evaluation after the initial charge. I assume you would need to actually retry the whole charge to get a new evaluation
Ok, we probably wouldn't want to do that since this is triggered off of the charge.succeeded webhook. It happens infrequently enough that we can do a manual investigation if/when it fails again and figure out the edge case