Regardless of how transaction data is varied to represent different fraud or AML scenarios, the sandbox evaluates the same set of rules and always assigns Typology 000. Shouldn't different transaction patterns trigger different rules, scores and typologies?
Why does the sandbox assign the same typology (Typology 000) to every transaction scenario?
Justus
1
Viewed 7
1 Answers
This is expected behaviour with the default configuration. Tazama's default network map contains a single typology - Typology 000 - which bundles all of the deployed rules together. Every transaction is therefore evaluated against the same rule set and always resolves to that one typology, no matter how the transaction data is varied.
Discrimination between different fraud or AML scenarios requires a multi-typology configuration, where rules are grouped into separate typologies with their own weights and thresholds.
If you are running your own instance and see only Typology 000, deploy a network map and typology configuration that splits the rules across multiple typologies instead of relying on the default single-typology setup.
Related