01 · Persistent Fingerprinting
sess_demo_checkout_42Hardware-backed identifiers that survive app reinstalls, factory resets, and device cloning attempts.
How it works
DevizeScore turns noisy device and behavior telemetry into a stable fingerprint, risk score, and recommendation your fraud stack can act on immediately.
SDK and server events collect device, network, sensor, and session context.
Persistent identity links the session to known devices and device clusters.
Attestation, behavior, and graph context resolve into one risk score.
final_risk_scoreThe trust spectrum
Every device is scored on a continuous trust spectrum. New devices start uncertain. You decide where to draw the line.
Sample data
Compliance
Capabilities
sess_demo_checkout_42Hardware-backed identifiers that survive app reinstalls, factory resets, and device cloning attempts.
sess_demo_checkout_42Emulator, root, VPN, mock GPS, screen mirroring, MITM.
emulatorsess_demo_checkout_42Accelerometer, gyroscope, touch, keystroke patterns analyzed for session anomalies.
sess_demo_checkout_42Play Integrity, App Attest, DeviceCheck verified server-side.
sess_demo_checkout_42One API, every surface — native, hybrid, web, and server-side.
sess_demo_checkout_42Per-merchant block + step-up, velocity checks, geo anomaly detection.
sess_demo_checkout_42Comparison
Fraud teams usually choose between brittle rules, point-solution IDV, or a custom signal stack. DevizeScore combines device, behavior, attestation, and identity context behind one risk decision.
fingerprint_idis_new_devicestabilityLimited: Usually session or event scopedPartial: Often tied to a verification eventPartial: Possible, but expensive to hardenpointer_eventsaccel_intervalsgyro_intervalskey_press_eventsLimited: Thresholds after behavior is knownPartial: Usually document or selfie focusedPartial: Requires sensor collection and modelsplay_integrity_tokenapp_attest_assertiondevice_check_tokenLimited: Rarely native to rule enginesPartial: May cover app integrity indirectlyPartial: Requires per-platform maintenanceis_emulatorcluster_idPartial: Catches known velocity patternsLimited: Not the primary detection surfacePartial: Needs graphing and feedback loopshard_block_thresholdstep_up_thresholdBuilt in: Strong rule policy controlsPartial: Step-up is usually verification basedPartial: Flexible, but ops-heavyplatformsdk_versionuser_agentPartial: Works where events are instrumentedPartial: Best around onboarding flowsPartial: Requires SDK and backend ownershipENTITY_REUSE_DETECTEDcluster_idevidence_countPartial: Finds obvious shared attributesLimited: Usually person-check focusedPartial: Needs graph storage and review toolingfinal_risk_levelrisk_causesrecommendationPartial: Rule hits explain the policy outcomePartial: Verification artifacts explain identity checksPartial: Only if logging is built deliberatelyGet started with the DevizeScore API. Explore the documentation or talk to our team about your use case.