Navigate to the Stripe Dashboard under Radar > Rules, or use the API at POST /v1/radar/rules to create a rule programmatically.
Create a value list of type card_bin via POST /v1/radar/value_lists with item_type: card_bin and a meaningful alias (e.g., blocked-bins).
Add BIN values (first 6 digits of the card number) to the list via POST /v1/radar/value_list_items with value_list and value fields.
Write a Radar rule predicate referencing the list: block if ::card_bin:: in @blocked-bins. The ::card_bin:: attribute is evaluated at authorization time.
Test the rule in Radar's test mode using a test card whose first 6 digits match a BIN in your list; confirm the rule fires before enabling in production.
Known gotchas
Radar rule predicates use double-colon delimiters for attributes (e.g., ::card_bin::) — omitting the colons or using single colons will cause a rule parse error.
BINs are typically 6 digits, but with BIN expansion some issuers now use 8-digit BINs; verify whether your target issuer uses 6 or 8 digits before adding list items.
Radar rules run in declaration order; if an earlier allow rule matches, a subsequent block rule will not fire — review rule ordering in the Dashboard.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?