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

# CreditcardCardNetwork

Matches follow-up transactions whose card network is in a configured list. Shown as "Credit card: Card Network" in the condition catalogue. Card networks are coarser-grained than card brands — useful for routing rules that apply to an entire network's traffic.

This condition applies to follow-up transactions that reference an initial transaction: the card network is determined from the initial transaction. Transactions without a reference transaction never match.

## Parameters

| Field          | Type             | Required | Allowed values                                                  |
| -------------- | ---------------- | -------- | --------------------------------------------------------------- |
| `cardNetworks` | array of strings | yes      | One or more network identifiers from the list below (lowercase) |
| `comparator`   | string           | yes      | `"in"`                                                          |

### Network identifiers

`visa`, `mastercard`, `nyce`, `star`, `accel`, `amex`, `cartes_bancaires`, `jcb`, `diners`, `discover`, `mada`, `maestro`, `omannet`, `pulse`, `upi`

## Example

```json
{
  "constraint": "CreditcardCardNetwork",
  "params": {
    "cardNetworks": ["visa"],
    "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.
* Network identifiers are case-sensitive and must be lowercase.
* Only the `in` comparator is supported. To express "not in network X", nest two rules and swap the `then` / `else` branches.