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

# IbanRegexp

Matches transactions whose customer IBAN matches a configured regular expression. Shown as "IBAN matches RegExp" in the condition catalogue.

## Parameters

| Field        | Type   | Required | Allowed values                                                                   |
| ------------ | ------ | -------- | -------------------------------------------------------------------------------- |
| `regexp`     | string | yes      | PCRE-style regular expression (without delimiters), applied to the customer IBAN |
| `comparator` | string | yes      | `"eq"` (matches)                                                                 |

## Example

Match IBANs from Germany:

```json
{
  "constraint": "IbanRegexp",
  "params": {
    "regexp": "^DE",
    "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 customer IBAN as a PCRE regular expression. Backslashes inside the pattern must be JSON-escaped.
* If the IBAN does not match the expression, the transaction has no customer, or the customer has no IBAN, the rule is skipped and routing falls through to the default connector.
* Available for routing meta-connectors only — not in multi-method routing documents.