What’s the simplest way to avoid double-counting related fraud signals in a small Bayesian model?
I’m building a small probability-based transaction decision model, not a production fraud system.
A problem I’ve run into is that some of the evidence clearly isn’t independent.
For example:
- new device
- new IP
- location mismatch
could all be caused by the same underlying thing, like the customer travelling or switching devices.
If I update the fraud probability as though all three pieces of evidence are independent, I’m worried I’ll make the posterior much more confident than it deserves to be.
For a small prototype with limited data, what would you consider the simplest defensible way to handle this?
I’m not looking for the fanciest model - mainly something I can explain and test without pretending the signals are independent when they obviously aren’t.