Stripe Radar ValueList accepts crypto_fingerprint items

Introduced 2026-03-25 · score 0.96

HOW TO USE IT

When using Stripe API version `2026-03-25.dahlia`, create a Radar ValueList with `item_type=crypto_fingerprint`. Add wallet fingerprints as list items; the release note says Radar rules can then use those fingerprints to allow trusted wallets or block fraudulent ones.

curl https://api.stripe.com/v1/radar/value_lists \
  -u "<SECRET_KEY>" \
  -H "Stripe-Version: 2026-03-25.dahlia" \
  -d "name=<LIST_NAME>" \
  -d "alias=<LIST_ALIAS>" \
  -d "item_type=crypto_fingerprint"

curl https://api.stripe.com/v1/radar/value_list_items \
  -u "<SECRET_KEY>" \
  -H "Stripe-Version: 2026-03-25.dahlia" \
  -d "value_list=<VALUE_LIST_ID>" \
  -d "value=<WALLET_FINGERPRINT>"

WHY THIS HELPS

When writing Radar rules to allow trusted crypto wallets or block known fraudulent wallets, add wallet fingerprints to a Radar ValueList.

REQUIREMENTS AND LIMITATIONS

alias (required): Name of the list for use in rules; maximum 100 characters.
name (required): Human-readable list name; maximum 100 characters.
item_type: Type of list items. Set to `crypto_fingerprint`; the documented enum values are alternatives, not mutually exclusive object sub-keys.
value_list (required): ID of the parent ValueList to receive the item.
value (required): Item value, which must match the parent list's item type; maximum 800 characters.
Stripe-Version (required): For API requests using this change, set the version to `2026-03-25.dahlia`.
Prerequisite: Use API version `2026-03-25.dahlia` for requests that rely on this change.
Prerequisite: Authenticate the API request with a Stripe secret key.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

Stripe Radar ValueList accepts crypto_fingerprint items