Loyalty points fraud

Protect points and miles from being drained.

10 minutes

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

What you will build: a check on the action you protect that allows normal users, asks doubtful ones to verify, and blocks the clear cases. See the loyalty points fraud overview for the attack in pictures.

Before you start

Finish one Web quickstart (for example JavaScript or React) and one Server quickstart (for example Node.js). The decision code below is TypeScript; every server SDK returns the same event.

How the attack works

  • Account takeover. Stolen logins to reach the points.
  • Fast transfers. Points moved out within minutes.
  • Shared accounts. One member account used everywhere.

What to look at

FieldWhy it matters here
accountSharingOne member on many devices.
velocityRedemptions bunched in minutes.
vpnLocation that does not fit the device.
  1. 1

    Identify on the action

    Call the browser SDK when the user performs the action, not on page load, and send the eventId with the request. Pass your own user id as linkedId whenever you have one: the account signals count by it.

    TypeScript
    const { eventId } = await trace.get({ linkedId: user?.id, tags: { action: 'loyalty-fraud' } });
  2. 2

    Verify on your server

    import { verifyEvent } from '@trace-id/sdk-node';
    
    const event = await verifyEvent(eventId, { secretKey: process.env.TRACE_SECRET_KEY!, endpoint, timeoutMs: 1500 }).catch(() => null);

    Events can be verified for 60 minutes. If verification fails, decide whether to fail open or closed; for most of this flow, fail open.

  3. 3

    Decide

    TypeScript
    const event = await trace.verify(eventId);
    const known = await db.devices.exists({ memberId, deviceId: event.deviceId });
    
    if (!known && points > 10_000) return confirmByEmail();
    if (event.signals.velocity.detected) return holdRedemption();

    trace.verify() is the embedded call; with a server SDK, use the event from step 2 instead. The thresholds are yours. Trace scores and explains; event.reasons lists which signals added how much, so log it with every decision.

Example decisions

Redemptions on one member account, illustrative:

DevicePointsDecisionWhy
Known phone2,000AllowUsual device
New laptop, VPN40,000VerifyNew device + vpn: confirm by email
New laptop, VPN40,000Blockvelocity

Roll it out

  1. Ship steps 1 to 3 with logging only: record the decision, block nothing.
  2. After a week, look at who would have been blocked or asked to verify. Shared computers, offices and privacy tools are the usual false positives.
  3. Turn on Verify first, then Block for the clearest cases.
Suggest an edit

Spotted something wrong or unclear? Tell us on GitHub and we will fix it.