> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://ixopay.ferndocs.com/developer-hub/documentation/reference/features/provisioning/connector-routing/rule-conditions/risk-score/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ixopay.ferndocs.com/_mcp/server.

# RiskScore

Matches transactions whose risk-engine score satisfies a numeric comparison against a configured threshold. Shown as "Risk Score" in the condition catalogue.

## Parameters

| Field        | Type    | Required | Allowed values                                  |
| ------------ | ------- | -------- | ----------------------------------------------- |
| `riskScore`  | integer | yes      | A score threshold                               |
| `comparator` | string  | yes      | `"="`, `"<"`, `"<="`, `">"`, `">="` |

## Example

```json
{
  "constraint": "RiskScore",
  "params": {
    "riskScore": 50,
    "comparator": ">"
  }
}
```

## Notes

* **Availability:** might not be included in your platform package — if this condition is missing from the catalogue returned by [List routing constraints](https://documentation.ixopay.com/api/provisioning/list-routing-constraints), contact your Customer Success Manager to have it activated.
* Requires a risk profile to be configured on the meta-connector. If a risk score has not (yet) been computed for a transaction, the score is treated as `0` in the comparison.
* If the transaction has no customer attached, rule evaluation stops and the default connector is used.
* Also available in multi-method routing documents.