Holds an account's fraud score band boundaries, and whether blocking is switched on at all. The blockEnabled flag exists so a new rule set can be deployed in watch-only mode: rules run, scores are recorded, but nothing is rejected, which is how a block threshold gets calibrated against real traffic instead of against a guess. Kademi's shipped block threshold is deliberately high, high enough that a hit is very likely fraudulent, because Kademi's own response is only to reject and notify; clients who want stronger action, such as disabling the profile or blocking the IP, configure that in IDP against the fraud score, usually at a lower threshold set to their own appetite for risk.
Properties
| Property | Returns | Description |
|---|---|---|
| blockEnabled | boolean | Whether blocking is switched on for this account. |
| blockScore | int | The score at or above which an operation is rejected, when blocking is enabled. |
| watchScore | int | The score at or above which a fraud event is recorded, even when blocking would not reject it. |
Methods
getWatchScore()
Returns: int
The score at or above which a fraud event is recorded, even when blocking would not reject it.
getBlockScore()
Returns: int
The score at or above which an operation is rejected, when blocking is enabled.
isBlockEnabled()
Returns: boolean
Whether blocking is switched on for this account.
calcBand(int score)
Returns: FraudBand
Works out which band a score falls into. Independent of whether blocking is enabled: a score can be in the block band while blocking is switched off, which is exactly what calibration needs to be able to see.
| Parameter | Description |
|---|---|
score | the score, 0 to 100 |