What is device fingerprinting?
Device fingerprinting collects attributes from a browser or mobile app—such as OS, screen, fonts, sensors, and Web SDK signals—and hashes them into an identifier that can persist across sessions even when cookies are cleared.
Why fraud teams use it
IP address and email change often. A device identifier lets you see whether a login, payment, or signup is coming from a known good device, a brand-new device, or a device already tied to multiple customer accounts. That is the core signal behind account-takeover and multi-accounting rules.
How Naiza applies device fingerprinting
Naiza attaches Web SDK device fingerprints to fraud events. Combine device context with velocity, IP reputation, and lists in ALLOW, REVIEW, or BLOCK rules, and follow device activity across sessions.
Combine device signals
Use device fingerprints alongside velocity, IP reputation, and customer history. Shared devices and browser changes are part of the review context; compare the signals before applying a rule.
Frequently asked questions
Answers about screening, risk signals, and Naiza integration.
What is a device fingerprinting API?
A device fingerprinting API or SDK collects client signals, returns an identifier, and lets your server attach that identifier to fraud events for rules and investigation.
How does device fingerprinting work with MFA?
Device context helps target step-up authentication. A new device or a previously blocked fingerprint can trigger additional verification while familiar, low-risk sessions continue.
Does Naiza persist fingerprints across sessions?
Yes. Device intelligence is designed to track devices across sessions so you can score repeat devices and detect multi-accounting. See the features and docs pages for the current fields.