Points belong to the member.

Loyalty balances are cash that is rarely watched. Spot logins from new devices and the burst of redemptions that follows a takeover.

SignalsaccountSharingvelocityvpn
scenario
Step 3 of 3velocityBlock
Figure 1Redemptions on one member account. 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. Account takeoverStolen logins to reach the points.
  2. Fast transfersPoints moved out within minutes.
  3. Shared accountsOne member account used everywhere.
02 · What Trace sees

Fields on the verified event

  • accountSharingOne member on many devices.
    "accountSharing": {  "detected": true,  "details": { "devicesForAccount": 7, "threshold": 5 }}
  • velocityRedemptions bunched in minutes.
    "velocity": {  "detected": true,  "details": { "exceeded": ["eventsPerVisitor5m"] }}
  • vpnLocation that does not fit the device.
    "vpn": { "detected": true }
03 · What you do

Decide, with your own thresholds

  • AllowUsual device
  • ChallengeNew device + vpn: confirm by email
  • Blockvelocity
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.

10suspectScore / 100
AllowLet the action through.
10/ 100
reasons
  • accountSharing+10

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.