One applicant, many identities.

Fraudsters apply again and again with different or synthetic identities from the same setup. Link applications by device before you approve.

SignalsmultiAccountantiDetectvpn
scenario
Step 3 of 3antiDetect + vpnChallenge
Figure 1Applications this week. Illustrative data. Hover or focus to pause; pick a step to scrub.

How it plays out

The attack, what the verified event shows, and what your code does about it.

01 · The attack

How it usually goes

  1. Identity cyclingA new name for every application.
  2. Anti-detect setupsBrowsers that fake a fresh device.
  3. Hidden locationApplying through a VPN from abroad.
02 · What Trace sees

Fields on the verified event

  • multiAccountSeveral applicants on one device.
    "multiAccount": {  "detected": true,  "details": { "accountsOnDevice": 3, "threshold": 2 }}
  • antiDetectA browser that contradicts itself.
    "antiDetect": {  "detected": true,  "details": { "reasons": ["iframeMismatch"] }}
  • vpnDevice clock that does not fit the IP country.
    "vpn": {  "detected": true,  "details": { "methods": ["timezoneMismatch"] }}
03 · What you do

Decide, with your own thresholds

  • AllowFirst application
  • ChallengeSecond identity, same device
Read the guide

Decision lab

Switch signals on and off. The score is a plain sum of weights.

decision lab
Signals

Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.

25suspectScore / 100
ChallengeAsk for a code, or send to review.
25/ 100
reasons
  • multiAccount+25

Implementation

One browser call, one server check.

01IdentifyCall the SDK on the action and send the eventId with it.
02VerifyYour server reads the event with a secret key.
03DecideAllow, challenge or block, with your own thresholds.
identify.ts
const trace = createClient({ apiKey: 'pk_...', endpoint: 'https://id.example.com' });

// On the action (signup, login, checkout), then send eventId with the form.
const { eventId } = await trace.get();
Example response, illustrative
{  "eventId": "evt_example"}

Start in shadow mode. Block later.

Log the decision for a week, check who it would have stopped, then turn it on.