> 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.

# IbanRoutingRule

Matches transactions whose customer IBAN contains a configured substring at a configured position — useful for routing rules that depend on a specific bank identifier or country block within the IBAN. Shown as "Check IBAN exact position value" in the condition catalogue.

## Parameters

| Field        | Type    | Required | Allowed values                                                                                    |
| ------------ | ------- | -------- | ------------------------------------------------------------------------------------------------- |
| `position`   | integer | yes      | 1-indexed start position within the IBAN string (e.g. `1` for the first two country-code letters) |
| `value`      | string  | yes      | The expected substring to compare against                                                         |
| `comparator` | string  | yes      | `"eq"` (matches)                                                                                  |

## Example

Match IBANs whose first two characters are `DE` (Germany):

```json
{
  "constraint": "IbanRoutingRule",
  "params": {
    "position": 1,
    "value": "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 match extracts a substring of the same length as `value`, starting at `position` (1-indexed). Lengths and positions must be consistent with the IBAN structure you're checking.
* If 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.