← Back
Stripe
Stripe adds crypto fingerprint support to Radar value lists for wallet-based fraud rules
Stripe API · apifeaturerelease · docs.stripe.com ↗

New Capability

Stripe has added support for crypto_fingerprint as a new item type when creating Radar ValueList objects. This brings cryptocurrency wallet fingerprinting to feature parity with existing fingerprint types like sepa_debit_fingerprint and us_bank_account_fingerprint.

Use Cases

With this addition, developers can now:

  • Trust known wallets: Create allowlists of crypto wallet fingerprints for trusted customers
  • Block fraudulent wallets: Maintain blocklists of known malicious cryptocurrency addresses
  • Enforce Radar rules: Write fraud detection rules that make decisions based on crypto wallet identity

This capability enables more granular fraud prevention for platforms accepting cryptocurrency payments or transfers.

Implementation

The change is available in API version 2026-03-25.dahlia. To use this feature:

  1. Upgrade your SDK to the latest version (or manually set the Stripe-Version header for REST API calls)
  2. Use the new crypto_fingerprint value for the item_type parameter when creating ValueList items
  3. Reference these fingerprints in your Radar rules via the standard rules engine

All major SDKs (Ruby, Python, PHP, Java, Node.js, Go, .NET) support this update. The complete upgrade process requires testing against the new API version in your development environment before rolling out to production.