Fraud Detection metadata comparisons may fail due to mismatched data types.
If you use the =, !=, in, or contains operators to compare a number or boolean with a string, the number or boolean is coerced to a string.
Why does my risk rule metadata comparison fail?
Was this article helpful?
Share
Copy Link
Share via email
Articles in this section
- How to view which user created a risk rule?
- Risk score terminology
- How to reduce fraud from a specific issuer
- Can liability shift if the issuer doesn't support CVV checks?
- How to reduce false positive risk declines
- Why can't I start backtesting?
- Reconciling backtesting with reported fraud
- If I change my live risk strategy after starting backtesting, which strategy is assessed?
- Fraud risk scores on Pro only
- Are there any Fraud Detection webhooks?