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’s Web SDK and event API attach a device fingerprint to each evaluated event. You can score the device, list it, and include it in ALLOW, REVIEW, or BLOCK rules. Public product pages describe 150+ device signals—confirm the current SDK surface in the docs rather than inferring extra sensors.
What it is not
A fingerprint is not legal identity and is not a KYC document check. Treat it as a risk signal. Combine it with velocity, IP reputation, and customer history instead of blocking solely because a hash looks new.
Frequently asked questions
Short answers written so search and answer engines can cite them.
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.
Can device fingerprinting replace MFA?
No. It is a complementary signal. A new or previously blocked device can trigger step-up authentication; it should not be the only control.
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.