Same device, same visitor_id — even after a full browser wipe, even across incognito, even after a clean reinstall. Match new accounts back to known-bad devices in your existing rules engine.
FOR FRAUD & RISK TEAMS
The fraudster cleared cookies. You should still know it's them.
fingerprint.dev gives your risk stack a stable device ID that survives cookie wipes, incognito mode, browser switches, and fresh installs. Catch repeat offenders the first time they come back — not after the third chargeback.
THE PROBLEM
Your fraud rules are blind on rerun.
Modern fraud isn't sophisticated — it's repetitive. The same handful of bad actors return with new emails, new cards, and a freshly wiped browser. Cookie-based device identity collapses on contact:
- Incognito mode writes nothing to disk
- Cookie clearing is a one-tap action on every modern browser
- Browser switching (Safari → Chrome → Firefox) breaks every client-side identifier
- Multi-accounting through profile switching defeats most session-based rules
- Privacy regulation is forcing you to store less, not more
Your fraud team knows this. They see the same handwriting on different accounts every week. They just can't prove it in time.
WHAT YOU GET
A stable ID that ties yesterday's chargeback to today's signup.
Every identify call returns a confidence score. Route high-confidence matches to auto-block. Send mid-confidence to manual review. Skip the noise.
REST API for backend rules engines. Hashed evidence, no PII storage by default. Built so your compliance team can sign off.
ROI
The math your CFO will ask about.
A mid-size marketplace processing $50M/year typically loses 0.9–1.4% to repeat fraud and promo abuse — call it $500K on the low end. If fingerprint.dev catches even 30% of that repeat activity at the point of the second attempt, that's $150K recovered annually. At Pro pricing of $199/mo plus overages, break-even is in the first week of any given month.
Most fraud teams see closer to 50–70% reduction in repeat-actor losses within 90 days of deployment.
estimated annual savings
$—
— catch rate assumption
HOW IT SLOTS IN
Drop it into the stack you already have.
fingerprint.dev isn't a fraud platform. It's the device signal your fraud platform was missing. Pipe visitor_id into:
- Rules engines — Sift, Sardine, Unit21, in-house
- Identity verification — Persona, Alloy, Veriff (as a pre-check)
- Auth providers — Auth0, Clerk, WorkOS (as a step-up signal)
- Data warehouses — for retrospective analysis and model training
// In your existing risk check
const fp = await identify({ apiKey: "fp_live_..." });
if (fp.confidence > 0.85 && knownBadDevices.has(fp.visitor_id)) {
return riskEngine.block("repeat_actor", { visitor_id: fp.visitor_id });
}
PROOF
What teams find in the first 30 days.
accounts collapsed to devices in a typical promo-abuse ring uncovered in the first week
median reduction in repeat chargebacks within 90 days across pilot customers
lift in fraud-rule precision when device confidence is added as a signal
"We'd been chasing the same ring for nine months. fingerprint.dev tied it together in an afternoon. The conversation with our chargeback partner has changed completely."
Head of Trust & Safety, marketplace
READY?
Stop paying twice for the same fraudster.
Free tier covers 1,000 identify calls — enough to run against a day of suspicious traffic and see what comes back. No credit card.