Evidence for every dispute.
"I never ordered that." Trace keeps the device history behind each account, so you can show the same browser placed earlier orders the customer did not dispute.
SignalsdeviceIdvisitorId
Step 3 of 3Disputed: same visitorId as past ordersChallenge
#10214Device ADelivered, not disputed
#10560Device ADelivered, not disputed
#11032Device ADisputed: same visitorId as past orders
same visitorId on every order
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
- Friendly fraudA real order, disputed after delivery.
- Family purchasesSomeone else in the house used the card.
- Weak evidenceAn IP address alone rarely wins a dispute.
02 · What Trace sees
Fields on the verified event
- visitorIdThe same browser across orders.
"visitorId": "Xk3pQ9vLmT2aR7sBn4Wc","matchKind": "token","confidence": 0.99 - historyGET /v1/visitors/:id lists past events.
"eventCount": 12,"firstSeenAt": "2026-08-02T09:00:00.000Z"
03 · What you do
Decide, with your own thresholds
- AllowDelivered, not disputed
- ChallengeDisputed: same visitorId as past orders
Decision lab
Switch signals on and off. The score is a plain sum of weights.
Signals
Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.
20suspectScore / 100
AllowLet the action through.
20/ 100
reasons
vpn+20
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.