Skip to main content

BinRangeRegexp

Matches transactions whose card BIN matches (or does not match) a configured regular expression. Shown as "BIN Range matches RegExp" in the condition catalogue.

Parameters

FieldTypeRequiredAllowed values
regexpstringyesPCRE-style regular expression (without delimiters), applied to the card's BIN digits
comparatorstringyes"eq" (matches) or "neq" (does not match)

Example

Match Visa BINs starting with 4 followed by any 5 digits:

{
"constraint": "BinRangeRegexp",
"params": {
"regexp": "^4[0-9]{5}",
"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, contact your Customer Success Manager to have it activated.
  • The expression is applied to the card's BIN digits — these may be 6 or 8 digits, so avoid $-anchored 6-digit patterns. Backslashes inside the pattern must be JSON-escaped.
  • If the transaction has no card or the BIN is empty, rule evaluation stops and the default connector is used.