Passive device fingerprinting
Automatic organisation-level collection of the session's DeviceContext data block with FingerprintJS Pro instead of the IDnow internal collector
Every session collects a DeviceContext data block when it starts, before any Step runs. By default, this passive collection uses the IDnow internal collector and records the browser's basic device and network information.
When your organisation has FingerprintJS Pro credentials, Protect access, and a saved Protect rule configuration, the IDnow web Player collects the data block with FingerprintJS Pro instead — adding FingerprintJS device identification, IP geolocation, and VPN and Tor detection to every session, without adding a Device signals (v2) Step to your flow.
What it does
With passive fingerprinting active, sessions started in the IDnow web Player — or in the Android SDK with the optional FingerprintJS module — report a DeviceContext data block with:
providerset to"fingerprint"- a FingerprintJS device identifier in
deviceId - IP geolocation and VPN and Tor detection in
ipAddresses - FingerprintJS detections in
detections
With the default internal collector, the same data block reports provider set to "idnow", with basic browser, device, and IP information.
Collection happens silently when the session starts: the end user sees no additional UI, and your integration needs no changes. The data block is available on the session like any other data block — see Get data blocks.
Collection also runs when a session is taken over in another tab, window, or device: the Player re-acquires the session and collects a fresh DeviceContext, so the stored block reflects the device and network context at takeover.
The same behaviour applies to sessions started from the Android mobile SDK when your integration adds the optional FingerprintJS module — see Mobile SDKs.
Passive collection only changes how the DeviceContext data block is collected — it does not assess device risk and cannot drive routing. To evaluate a device's trustworthiness and route on the result, add a Device signals (v2) Step to your flow.
Mobile SDKs
Android
Sessions started by the Android SDK collect the DeviceContext with FingerprintJS Pro whenever the organisation qualifies, under exactly the same conditions as the web Player.
Collection is opt-in for your integration: you must add the optional FingerprintJS module to your app. Once it is added, no further host-app or flow configuration is needed for a qualifying organisation.
// build.gradle.kts
repositories {
maven {
url = uri("https://maven.fpregistry.io/releases")
content { includeGroupByRegex("com\\.fingerprint.*") }
}
}
dependencies {
implementation(platform("io.idnow.trustplatform:bom:<version>"))
implementation("io.idnow.trustplatform:core")
implementation("io.idnow.trustplatform:fingerprint")
}
Without the module, the SDK keeps the native collector at no added cost and no added app size: sessions report provider set to "idnow" exactly as before.
With the module, the SDK collects one FingerprintJS event when the session starts and sends its event identifier to the IDnow platform, which builds the DeviceContext from FingerprintJS — including Android-specific detections such as emulator, cloned app, and root detection (reported in detections.jailbroken). The SDK itself maps no FingerprintJS fields.
If FingerprintJS cannot initialise or collect — no network, a blocked request, a timeout — the session still starts on the native collector. The fallback is recorded server-side. An event identifier the platform cannot verify is rejected with error code FINGERPRINT_EVENT_NOT_FOUND, exactly as in the web Player.
iOS does not collect the DeviceContext with FingerprintJS Pro yet. Sessions started from the iOS SDK continue to report the device context collected by the SDK.
When it is active
Passive collection uses FingerprintJS Pro for a session when all three conditions hold for your organisation:
- FingerprintJS Pro credentials are configured for your organisation in the session's environment (
stagingorlive). Draft sessions use thestagingcredential. - Protect is enabled for your organisation — your organisation has Protect access.
- A Protect rule configuration exists — your organisation has saved a Protect configuration, regardless of how many rules it turns on.
There is no per-flow or per-version setting. Every flow of a qualifying organisation — including flows with no Device signals Step — produces the enriched DeviceContext.
The conditions are evaluated when the session is created and bound to that session for its lifetime. Changing your credentials or Protect configuration during a running session does not switch its provider; the change applies to sessions created afterwards.
Organisations that do not meet the conditions continue to use the internal collector. Nothing is misconfigured and no warning is shown: the organisation simply has not enabled the FingerprintJS Pro integration.
When collection cannot complete
Collection happens while the session is being started, before the first Step runs. If it cannot complete — FingerprintJS is unreachable, or the credentials were removed after the session was created — the session still starts. The DeviceContext falls back to the standard internal collector for that collection, with provider set to "idnow", and without FingerprintJS detections or IP geolocation.
Protect rules that rely on those signals do not match for that session, since a rule whose required signals are not present simply does not match.
An unrecognised FingerprintJS event id is different: the session is rejected with error code FINGERPRINT_EVENT_NOT_FOUND. This indicates a forged or stale event rather than an outage, so it is not retried and does not fall back.
Relationship to Device signals steps
Device signals Steps always use FingerprintJS Pro and always require the organisation's FingerprintJS Pro credentials, regardless of whether passive collection is active. The two are independent:
- Passive device fingerprinting collects the
DeviceContextdata block for every session, silently at session start, with no routing. - A Device signals (v2) Step collects
DeviceContextand produces aDeviceRiskAssessmentdata block that drives routing — with verdicts, confidence scores, and vault references to the raw provider responses.
A flow does not need passive collection to be active for its Device signals Steps to use FingerprintJS Pro.