> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://ixopay.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://ixopay.ferndocs.com/_mcp/server.

# CreditcardBinLevel

Matches transactions whose card-BIN level is (or is not) in a configured list. Shown as "Credit card: BIN Level" in the condition catalogue. Level values such as `PLATINUM`, `PREMIUM`, `CORPORATE`, `BUSINESS` or `STANDARD` are illustrative — the available values are data-derived and not guaranteed.

## Parameters

| Field        | Type             | Required | Allowed values                                                  |
| ------------ | ---------------- | -------- | --------------------------------------------------------------- |
| `levels`     | array of strings | yes      | One or more level identifiers (e.g. `["PREMIUM", "CORPORATE"]`) |
| `comparator` | string           | yes      | `"in"` or `"notin"`                                             |

## Example

```json
{
  "constraint": "CreditcardBinLevel",
  "params": {
    "levels": ["PREMIUM", "CORPORATE"],
    "comparator": "in"
  }
}
```

## 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 set of level values is derived from card BIN data and can change over time. Use [List routing constraints](https://documentation.ixopay.com/api/provisioning/list-routing-constraints) to discover the values currently available.
* If no BIN data is found for the card (or the BIN source does not report levels), `"in"` conditions do not match; `"notin"` conditions match when no BIN entry was found at all. For transactions without card data (or when the BIN lookup fails), rule evaluation stops and the default connector is used.