> 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/bin-range-regexp/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ixopay.ferndocs.com/_mcp/server.

# BinRangeRegexp

Matches transactions whose card BIN matches (or does not match) a configured regular expression. Shown as "BIN Range matches RegExp" in the condition catalogue.

## Parameters

| Field        | Type   | Required | Allowed values                                                                       |
| ------------ | ------ | -------- | ------------------------------------------------------------------------------------ |
| `regexp`     | string | yes      | PCRE-style regular expression (without delimiters), applied to the card's BIN digits |
| `comparator` | string | yes      | `"eq"` (matches) or `"neq"` (does not match)                                         |

## Example

Match Visa BINs starting with 4 followed by any 5 digits:

```json
{
  "constraint": "BinRangeRegexp",
  "params": {
    "regexp": "^4[0-9]{5}",
    "comparator": "eq"
  }
}
```

## 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.
* The expression is applied to the card's BIN digits — these may be 6 **or 8** digits, so avoid `$`-anchored 6-digit patterns. Backslashes inside the pattern must be JSON-escaped.
* If the transaction has no card or the BIN is empty, rule evaluation stops and the default connector is used.