CreditcardBinSegment

Matches transactions whose card segment is (or is not) in a configured list. Shown as "Credit card: BIN segment" in the condition catalogue.

Parameters

Field	Type	Required	Allowed values
comparator	string	yes	"in" or "notin"
segments	array of strings	yes	"Consumer", "Business", "Commercial", "Government", "Unknown"

Example

{
  "constraint": "CreditcardBinSegment",
  "params": {
    "comparator": "in",
    "segments": ["Consumer"]
  }
}

Notes

• Availability: might not be included in your platform package — if this condition is missing from the catalogue returned by List routing constraints, contact your Customer Success Manager to have it activated.
• Available for routing meta-connectors only — not in multi-method routing documents.
• Segment values are case-sensitive — use the exact capitalization listed above (for example "Consumer", not "CONSUMER").
• If no BIN data is found for the card, "in" conditions do not match while "notin" conditions match. For transactions without card data (or when the BIN lookup fails), rule evaluation stops and the default connector is used.