Skip to main content

Spotting Repeat Fraudsters (Device Fingerprinting)

TL;DR
  • Device fingerprinting links orders that seem to come from the same phone or computer, so a fraudster who comes back with a new name, email and card can still look familiar. It's a match with a level of confidence, not a certainty
  • A device match isn't a person ID. It can't tell you who was holding it
  • Platforms can flag signs of VPNs, emulators, phone farms, remote desktop tools and anti-detect browsers. Each flag is a lead to check, because real customers can trip them too
  • Signals like battery state, gyroscope data, TLS fingerprints and typing cadence can add what transaction data alone can't, where the browser, device and permissions allow them
  • Vendors range from shared reputation networks (ThreatMetrix, Iovation) to behavioral analytics (Sardine) to managed decisions (Forter)
  • No single signal is definitive. The power comes from comparing the device, its connection, the browser and the behavior for details that don't agree

Your processor may already do some of this, so the question is whether you need more. Device fingerprinting is a way of recognizing the phone or computer placing an order. A small script reads details the browser gives away anyway, such as browser version, screen size, graphics chip and time zone, and builds an ID out of them. A native app SDK can read more, within what the platform permits. The point is to link a returning device, with some confidence, even when the fraudster comes back with a new name, a new email and a different card. A changed setting can break that link, and a shared family computer can make a false one (Fingerprint's accuracy explainer).

Stripe and Adyen both document some of this, depending on your integration and plan.

Device fingerprinting started as an ID for a browser. Device intelligence goes further, across hardware, software, network and behavior. All of it tries to answer four questions. Is this a real device? Is a real person using it? Have we seen it before? Is someone else driving it? It gives you a read on each, not a certain answer.

This page is the signals, what each one can show, and what vendors say they offer. Putting them into rules? See Building Fraud Rules.


How It Works​

Fingerprint Types​

A rough guide, not a measurement:

TypeHow It WorksPersistenceEvasion Difficulty
Cookie-basedStores a token in the browserLow (cleared easily)Trivial
Browser fingerprintHashes browser attributes (user agent, plugins, fonts)Medium (changes with updates)Moderate
Device fingerprintCombines hardware signals (GPU, CPU, screen, sensors)Higher (can survive a browser change)Harder
Probabilistic/fuzzyUses ML to match devices even when some attributes changeHigher (can survive cookie clearing and incognito), with some false matchesHarder
BehavioralLearns how someone uses a device (typing, movement)Builds over sessionsHard to replicate at scale

Vendors can combine several types and compare the layers, so spoofing one signal can leave inconsistencies in the others. Ask for the confidence level and known limits of any match. Fingerprint's Smart Signals show what one vendor lists.


Signal Categories​

Platforms can collect signals across seven categories. No one category decides anything on its own. The useful reads are the inconsistencies between them. What you can get depends on web or native app, the browser or OS, and permissions. So read each row below as a lead to check against your normal customers and your confirmed outcomes.

1. Browser and App Signals​

The traditional fingerprinting layer. Still useful, but easily spoofed in isolation.

SignalWhat It RevealsWhat to Check
Canvas fingerprintHash of rendered 2D graphics (varies by GPU, driver, OS)A match with a known emulator or headless signature
WebGL fingerprintGPU vendor and renderer string, 3D rendering outputGoogle SwiftShader points to a software GPU, which a headless browser, an emulator or an ordinary machine can use. VirtualBox Graphics Adapter points to a VM
Audio fingerprintAudio processing output, which varies with the hardware and OSIdentical output across many sessions. Don't assume it's absent in headless, because current headless Chrome shares normal Chrome's functions
Font enumerationInstalled font listA Windows device with Linux fonts may be a spoofed user agent
Navigator propertiesPlugins, languages, hardware concurrency, device memorynavigator.webdriver true means automation is driving the browser (Selenium, Puppeteer). It doesn't say why
User agentBrowser and OS identificationEasily spoofed, but inconsistencies with other signals are revealing
Anti-Detect Browsers

Multilogin, GoLogin and Dolphin Anty let users isolate browser profiles and control these signals. They have legitimate uses, and fraudsters can use them too. Platforms can sometimes spot them when the browser attributes don't line up with harder-to-fake signals like TLS fingerprints, sensor data and behavior. Don't assume every one gets caught.

Looking for Basic IP Enrichment?

Want server-side IP lookups with no SDK? Geolocation, VPN detection and datacenter detection are available by API. See Data Enrichment. This section goes further, and each technique runs in a different place. WebRTC tests run in the browser. TLS fingerprints come from the server or network edge, and Cloudflare exposes them in its rules and analytics. Spotting a residential proxy by device correlation needs a device signal.

2. True IP and Network Intelligence​

The IP is easy to hide. Some platforms try to look past the visible one.

TechniqueHow It WorksWhat It Can Point To
WebRTC leak detectionCreates a hidden peer connection via STUN servers. Under some network and browser settings, UDP traffic can bypass a VPN tunnel and expose the real IPVPN users whose real IP leaks through WebRTC
TLS fingerprinting (JA3/JA4)Hashes the TLS ClientHello message (cipher suites, extensions), at the server or edge. Many similar clients share a fingerprint, and it can be missingUser agent says "Chrome" but the TLS fingerprint matches Python's requests library: possibly a bot. It isn't a person's ID or a hidden IP (Cloudflare)
ASN/datacenter detectionMaps IP to owning organization. Classifies as residential, mobile, datacenter, or hostingA datacenter IP at a consumer checkout is a tell worth checking. Some real shoppers browse through VPNs or proxies, so weigh it with the device and behavior signals
Residential proxy detectionCorrelates IP rotation patterns with stable device fingerprintsIP changes every request while the device fingerprint stays constant: possibly a rotating proxy. Weigh it with account history
Timezone vs. IP mismatchCompares browser timezone (Intl.DateTimeFormat) with IP geolocationIP in London, timezone set to America/Los_Angeles: possibly a VPN, possibly a traveler. Weigh it with account and device evidence (SEON)

Several vendors sell "True IP" technology, ThreatMetrix and Sardine among them. It tries to surface the actual IP behind a VPN or proxy. Accuracy swings by technique, and by how the VPN is configured. Don't treat it as ground truth.

IP classification matters as much as the IP itself. It tells you who owns the address, not whether the customer is real (SEON on IP types). Measure the risk on your own orders.

IP TypeExample OwnerHow to Read It
ResidentialComcast, AT&T, BTExpected for consumers. A residential proxy can look the same
Mobile/CellularT-Mobile, VodafoneExpected for mobile. Many customers can share one IP
Datacenter/HostingAWS, DigitalOcean, OVHWorth checking at a consumer checkout. Real customers can come through VPNs, shared networks or remote environments
Known VPN providerNordVPN, ExpressVPN rangesReal customers use these. Weigh it with device and account history
Known proxy serviceBright Data, OxylabsWorth checking, with device and account history
Tor exit nodePublished exit node listsWorth a closer look, and easy to check against the published lists

3. Device Integrity​

These signals check the device itself. Has it been tampered with, or is it an emulator? Is someone driving it remotely? Many of them need a native app SDK. A web script sees only what the browser exposes, and it can't read native process lists or hardware IDs like the IMEI.

SignalWhat You'd Usually SeeWhat to Check
Emulator detectionReal hardware identifiers (e.g., samsung/...)Generic build strings (goldfish, ranchu, sdk_gphone), SwiftShader GPU, missing sensors
Root/jailbreakStock OS, normal permissionsPresence of su binary, Cydia/Magisk, SELinux permissive, writable system partition. Some real users root their own phones
Remote desktopNo remote access software activeTeamViewer, AnyDesk, Windows RDP, Zoom screen sharing detected
VM detectionReal GPU, normal CPUVirtualBox/VMware graphics adapters, low CPU core count, VM-specific BIOS strings
Developer toolsnavigator.webdriver is falsenavigator.webdriver === true, empty plugins array, CDP connection active. Developers and test tools set these too
Frida/instrumentationNo runtime hooksFrida toolkit detected (commonly used to bypass security checks and manipulate API responses)
Remote Desktop Detection Matters

Remote access scams get past ordinary device checks. A fraudster calls the victim and talks them into installing TeamViewer. Then they drive the victim's device and make the transaction themselves. It comes off the victim's real device, on their real IP. Traditional signals look clean. Spotting active remote desktop software is one of the few ways to catch it.

4. Behavioral Biometrics​

How someone uses a device is harder to fake at scale, though automation can imitate some of it. Behavioral Analytics covers how to test these.

Typing and keystroke dynamics:

SignalWhat It MeasuresWhat to Check
Typing speedCharacters per second, words per minutePerfectly uniform timing may be automation
Dwell timeHow long each key is heldZero variance may be injected keystrokes
Flight timeGap between releasing one key and pressing the nextIdentical intervals may be scripted input
Segmented typingTyping in bursts with pauses (switching to reference material)Name or address typed in fragments. It may be someone reading a stolen data sheet, or someone checking their own details
Copy-paste in identity fieldsWhether name, SSN, or address was pasted vs. typedPasted identity details. Autofill and password managers are legitimate, so compare with your real customers

Mouse and pointer behavior:

SignalWhat It MeasuresWhat to Check
Movement trajectoriesCursor path between targetsPerfectly straight lines or geometric patterns may be scripted
Micro-movementsTiny jitter when cursor is "still"Zero jitter may be a bot. Trackpads and assistive tools can differ
Click patternsTiming, location, frequencyUniform click intervals may be automation
Scroll behaviorSpeed, direction, pausesUniform scroll with no pauses may be a bot
Guided movementCursor controlled by someone else (latency artifacts)Possibly a remote access tool in use

Mobile sensor data:

These depend on the platform. Sensor APIs can be unavailable or blocked, motion access can need a tap or a permission, and pointer pressure has a default value on hardware that doesn't report it. Missing data isn't proof of an emulator.

SignalWhat It MeasuresWhat to Check
GyroscopeDevice orientation and rotationZero readings may be an emulator or a device on a rack. Or a phone on a table
AccelerometerMovement and vibrationPerfectly static may mean nobody's holding it. A phone on a stand looks the same
Touch pressureForce of finger on screenUniform pressure may be automation
Device orientationHow the phone is heldStatic at ~90 degrees may be a rack, or a phone on a stand

5. Battery and Power Signals​

A small category. On the web it depends on the Battery Status API, which some browsers support, including some on Android, and others don't. Native apps read it through their platform's own APIs. A missing reading doesn't mean an emulator.

SignalWhat You'd Usually SeeWhat It May Point To
Always at 100%, always chargingBattery fluctuates throughout the dayA phone farm on USB hubs. Or a laptop that stays plugged in
Battery level never changes across sessionsVaries naturallyAn emulator reporting a static level like 0.50 or 1.00, or a browser hiding the real one
Inconsistent battery between "same user" sessionsConsistent within short timeframesAccount sharing or credential selling. Or a customer with two devices

Battery data alone is weak, and it's only useful as corroboration. Take a device that's always charging and never moving the gyroscope. It's turned up on 50 accounts. Investigate a possible phone farm, and rule out shared equipment and other honest explanations. Even together, those signals don't tell you who used the device.

6. Phone Farm and Fraud Factory Detection​

A phone farm is a rack of devices pretending to be independent users. Physical or virtual, doesn't matter. No single signal catches them, so don't go hunting for one. You catch farms on the composite profile. A native app SDK sees more of this than a web script.

SignalWhat a Farm Device Can Look Like
BatteryAlways at 100%, always charging (plugged into USB hubs)
Gyroscope/accelerometerZero movement (mounted on rack, not held by a human)
Device attributesSame hardware fingerprint appearing across many "different" accounts
Factory resetsFrequent resets (every few hours/days) to create "fresh" identities
Device ID cyclingIMEI, Android ID, or advertising ID changes on the same hardware, where a native SDK is permitted to see them
Network patternsMany devices sharing the same IP range or cycling through a small pool
Behavioral uniformityAll devices show identical interaction patterns, timing, and session flow
No natural idle periodsLegitimate users sleep. Farm devices may operate 24/7
Physical proximityDozens of "independent" devices co-located in the same physical space

7. Consortium and Reputation Data​

The simplest signal here is the one to ask first. Has this device been linked to fraud before?

Consortium networks pool device reputation across their members. What you get is the provider's own signal, at the access and update speed it documents, not every other merchant's report (TransUnion's Device Risk is one). Ask how old a flag is and what caused it.

What Consortium Data Can Tell YouExample
Device has a bad historyFlagged at 3 other merchants in the past 90 days. If the flag came from a chargeback, that's a dispute, not confirmed fraud
Device is brand new to the networkNever seen before, no history. Test whether that means more risk on your new accounts
Device has a long historyFirst seen 2 years ago, nothing flagged across 12 merchants. A good sign, not a guarantee
Device is linked to a suspected ringSame device cluster seen in coordinated attacks across the network

How Signals Work Together​

No single signal is definitive, so you layer them and cross-reference. It's the inconsistencies between layers that give you the strongest read.

Example: Spotting a possible anti-detect browser

An anti-detect browser can spoof canvas fingerprint, WebGL renderer, user agent, timezone and language. But say you also see this:

  • The TLS fingerprint (JA3/JA4) matches a Chromium build, not the user agent it claims
  • The battery API reports a static level
  • Typing patterns don't match the account's historical behavior
  • The IP is residential, but the ASN belongs to a known residential proxy provider

Any one of these alone might be explainable. All four together are a strong reason to investigate. They still don't prove it.

Example: Spotting a possible remote access scam

The transaction comes from the victim's real device, real IP, real location. Traditional signals look clean. But say you also see this:

  • Remote desktop software (TeamViewer) is active
  • Mouse movements show latency artifacts consistent with remote control
  • The user is on an active phone call during the session, where a native SDK is permitted to see that
  • Typing patterns show hesitation and segmented entry (possibly a victim being coached)

Vendors​

Vendors vary a lot. What they collect, how big the network is, how they hand you a decision.

What Vendors Say They Offer​

These are each vendor's own claims, read 3 November 2026, not independent results. Ask what you'd get on your product, platform and plan, including anything not listed here. Network sizes count different things, so don't rank them.

VendorWhat Its Own Material CoversAsk About
SardineDevice and behavior signals. It reports spotting remote screen-sharing tools with 92% precision and a 96% detection rate, which is its own figureThe population and period behind those numbers
ThreatMetrix and BehavioSec (LexisNexis)Combined device and behaviorCurrent network size and what it counts
Iovation (TransUnion)Device reputation, with its own network claimsWhat a flag means and how old it is
Kount (Equifax)Policies, case and risk functions, with its own network scope. Its legacy PC_REMOTE field says a device is enabled for PC Remote software, not that a remote session is activeThe current Orders API mapping before relying on a legacy field
SiftPayment, account and abuse riskScore types and packaging on your plan
ForterCovered and uncovered pricing, so a guarantee is a contract choiceWhether you can write your own rules, and what your contract covers

Choosing a Vendor​

The right vendor matches the biggest problem you've measured. Not the longest feature list. Then compare a real quote and test it on your own traffic.

If Your Primary Problem Is...Look At
Sophisticated fraud bypassing basic rules (anti-detect browsers, residential proxies, emulators)Sardine, ThreatMetrix. Ask how each handles these on your traffic
Needing device reputation at scale (has this device been seen in fraud before?)ThreatMetrix, Iovation. Ask how much of the network is in your own industry and country
Remote access / social engineering scamsSardine, or BioCatch, which is aimed at banks. The 92% precision figure is Sardine's
Identity verification + device signals (synthetic identity, application fraud)Kount (Equifax), or NeuroID (Experian) for form interaction. Ask what data each uses on your plan
Multi-abuse-type detection (payment fraud + promo abuse + content abuse + ATO)Sift. It scores by abuse type, so ask which types your plan covers
Not wanting to manage rules at all (outsourced decisions, possibly with a financial guarantee)Forter. A covered contract reimburses chargebacks on orders it approved, under its terms. That isn't a network liability shift
Budget-conscious / just getting startedFingerprint, which publishes a price, or your processor's built-in tools (Stripe Radar, Adyen Protect)

Pricing and Accessibility​

VendorPricePrimary Use Case
FingerprintFree up to 1,000 API calls/month. Pro Plus from $99/month for 20,000 calls on web and iOS, then $4 per 1,000 more. Android has its own allowance of 500,000Device identification, returning visitor recognition
SEONStarter $699/month (2,500 fraud checks, 10 users, 50 rules). Premium is customEmail and phone enrichment plus device signals
ThreatMetrix (LexisNexis)Ask for a quoteDevice intelligence, shared reputation
BioCatchAsk for a quoteBehavioral biometrics for banks, social engineering detection
NeuroID (Experian)Ask for a quoteForm interaction analytics, application fraud detection
Iovation (TransUnion)Ask for a quoteDevice reputation
SardineAsk for a quoteBehavioral signals and remote desktop detection

The Fingerprint and SEON rows come off their own pricing pages, read 4 November 2026. Check them again before you budget.

Budget-conscious? Fingerprint and SEON both publish a price. Fingerprint has a free plan. SEON publishes none: its Starter is $699/month for 2,500 fraud checks, ten users, fifty custom rules. That's roughly 28 cents a fraud check. Fingerprint's Pro Plus works out to about half a cent a call at its included 20,000. Those aren't the same unit, because SEON's a wider fraud platform, so compare what each call or check includes. Use both as a yardstick when a quote-only vendor sends a proposal.

Enterprise? Expect to talk to sales at ThreatMetrix, BioCatch, NeuroID, Iovation and Sardine. Contract length and any minimum volume are questions for them. The only way to find out if you're too small is to ask: "At [monthly orders], is there a minimum commitment, and what would I pay in year one?" A vendor that won't quote you has answered the question. If that happens, start with Fingerprint or your processor's built-in tools (Stripe Radar, Adyen Protect).

Processor Tools vs. Standalone Vendors

On Stripe Radar or Adyen Protect? You've got some of this already. Stripe documents device and activity signals through Stripe.js, and Adyen has its own basic and premium scope. A standalone vendor may add more, such as behavioral biometrics, sensor data, True IP or shared reputation. Name the gap you've measured, then compare a real quote and the time your checkout can spare. See Processor Rules Configuration for what each processor includes.


Use Cases​

Fraud Detection​

Use CaseHow Device Intelligence Helps
Card testingSame device cycling through hundreds of card numbers points to a single source
Multi-accounting / promo abuseSame device fingerprint across multiple "different" accounts. Could also be a shared household device
Account takeoverNew device + new location + new behavioral pattern on existing account
Fraud ring linkageCluster of devices with shared attributes, same IP ranges, same behavioral patterns
Application fraudSigns to investigate: emulator flagged, pasted identity fields, missing sensor data
Remote access scamsSigns to investigate: active remote desktop software, mouse latency artifacts, an active phone call where a native SDK can see one

Account Security and Trust​

Use CaseHow Device Intelligence Helps
Step-up authenticationTrigger MFA on unknown device (see 3DS)
Trusted device recognitionReturning device with clean history = lower friction
Session managementLimit active devices per account
Compelling evidenceA device match is one element of the purchase history Visa CE 3.0 needs. On its own it isn't enough

Implementation Approaches​

Build vs. Buy​

ApproachWhat You GetWhat to Weigh
In-house (FingerprintJS open source)Basic device fingerprinting, full control, no data sharingNo shared reputation, and you maintain it yourself
Device ID vendor (Fingerprint)Device IDs and the Smart Signals on its planTest the accuracy it advertises on your own traffic. Ask about behavior signals and shared reputation
Full platform (Sardine, ThreatMetrix, Sift, etc.)Wider signals and a rules engine, by productCost, data sharing terms, vendor dependency
Processor-included (Stripe Radar, Adyen)Some device signals and ML scoring, by plan and integrationHow much of the signal you can see and write rules against

See vendor selection guide for evaluation criteria.

What to Ask a Vendor​

Ask these on the vendor call, in these words:

  1. What signals do you collect beyond basic fingerprinting? (Behavioral biometrics, sensor data, TLS fingerprints)
  2. How do you handle anti-detect browsers and residential proxies? (Cross-layer correlation, not just database lookups)
  3. How big is your consortium, and is it relevant to my vertical? (A billion devices doesn't help if none are in your industry)
  4. Can I write custom rules against your signals, or are decisions fully managed?
  5. What's the latency? (Compare it with the time your own checkout can spare)
  6. How do you handle privacy compliance? (Data tokenization, consent management, GDPR readiness)

Privacy Considerations​

Check the Privacy Rules First

A fingerprint reads information from the customer's device, so these rules can apply before there's an order:

  • EU and UK: Reading device data can need prior consent, unless it's strictly necessary for a service the customer asked for (EDPB guidelines). A GDPR legitimate interest doesn't replace that consent where it's required. Ask counsel where a fraud check falls
  • California: The CCPA covers purpose limits, consumer rights and sharing as well as disclosure, and its security and fraud exception has conditions (CPPA FAQ)
  • Elsewhere: Check local rules

Talk to counsel before you implement it. Sharing with a vendor's consortium needs its own look.

Best Practices​

  1. Transparency: Disclose device fingerprinting in your privacy policy
  2. Purpose limitation: Use only for fraud prevention and security
  3. Data minimization: Collect only what's needed for fraud detection
  4. Retention limits: Expire device profiles (consortium retention may differ)
  5. Consent where required: Cookie banners, opt-in where legally necessary
  6. Vendor data sharing: Know what your vendor shares across its consortium, and on what terms. TransUnion's iovation notice is one to read

Rolling It Out​

Just getting started?

  1. Start with what your processor's tools already do (Stripe Radar, Adyen Protect)
  2. Build velocity rules (how they work) using device ID as a dimension
  3. Review privacy requirements before adding standalone tools

Adding standalone device intelligence?

  1. Choose a vendor based on your primary fraud problem
  2. Integrate it and run shadow mode until your planned sample and outcome window are ready. Thirty days is a planning start, not proof
  3. Compare the new signals to your current catches and false positives

Do next​

Deeper​

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.