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

# CreditcardBinLookupStatus

Matches transactions by the status of their BIN lookup — useful for routing differently when BIN data is unavailable or when the lookup failed. Shown as "Credit card: BIN Lookup Status" in the condition catalogue.

## Parameters

| Field        | Type             | Required | Allowed values                                      |
| ------------ | ---------------- | -------- | --------------------------------------------------- |
| `statuses`   | array of strings | yes      | One or more of: `"success"`, `"no_data"`, `"error"` |
| `comparator` | string           | yes      | `"in"` or `"notin"`                                 |

## Example

```json
{
  "constraint": "CreditcardBinLookupStatus",
  "params": {
    "statuses": ["success"],
    "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.
* `success` indicates the BIN was found in the BIN database.
* `no_data` indicates the BIN was not found.
* `error` indicates the lookup itself failed (e.g. due to a timeout).