# Retrieve risk score rules Retrieves risk score rules. Endpoint: GET /risk-score-rules Version: latest Security: SecretApiKey, JWT ## Response 200 fields (application/json): - `isProxy` (object,null, required) - `isProxy.value` (integer, required) Value added to the risk score of the transaction. - `isVpn` (object,null, required) - `isTor` (object,null, required) - `isHosting` (object,null, required) - `hasMismatchedBillingAddressCountry` (object,null, required) - `hasMismatchedBankCountry` (object,null, required) - `hasMismatchedTimeZone` (object,null, required) - `hasMismatchedHolderName` (object,null, required) - `hasFakeName` (object,null, required) - `isHighRiskCountry` (object,null, required) - `paymentInstrumentVelocity` (object,null, required) - `paymentInstrumentVelocity.brackets` (array, required) Risk factor values range with corresponding risk score increment value. First matched bracket is applied. - `paymentInstrumentVelocity.brackets.start` (integer, required) Minimal risk factor value when condition is applied. - `paymentInstrumentVelocity.brackets.end` (integer, required) Maximal risk factor value when condition is applied. - `declinedPaymentInstrumentVelocity` (object,null, required) - `deviceVelocity` (object,null, required) - `ipVelocity` (object,null, required) - `emailVelocity` (object,null, required) - `billingAddressVelocity` (object,null, required) - `isRebill` (object,null, required) - `isRetry` (object,null, required) - `customerLifetimeValue` (object,null, required) - `browserAdBlockEnabled` (object,null, required) - `paymentInstrumentApprovedTransactionCount` (object,null, required) ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.