Referral fraud

Pay referral rewards for real new users.

10 minutes

Referral programs pay for each new user. Check that the referrer and the new account are not the same device.

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 referral 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

  • Self-referral. Inviting your own second account.
  • Browser hopping. The invite opened in another browser.
  • Referral rings. One device signing up many invitees.

What to look at

FieldWhy it matters here
deviceIdCompare referrer and invitee devices. Shared by every browser on one device. Store it with the account or the action.
crossBrowserCatches the invite opened in another browser.
  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.

    TypeScript
    const { eventId } = await trace.get({ tags: { action: 'referral-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 invitee = await trace.verify(eventId);
    const referrer = await db.users.get(referrerId);
    const linked = invitee.linkedVisitors.map((v) => v.visitorId);
    
    if (invitee.deviceId === referrer.deviceId || linked.includes(referrer.visitorId)) return noReward();

    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

Referrals from @nour, illustrative:

New accountDeviceDecisionWhy
@saraOther deviceAllowReward paid
@nour_2Nour's laptop, FirefoxBlockLinked to the referrer's device
@friend_xNour's laptop, privateBlockSame visitorId as the referrer

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.