Outbound Wiki

Referral fraud prevention

Preventing self-referrals, duplicate submissions, fake accounts, and other attempts to claim rewards improperly.

Treat referral fraud as a payout-control problem. Hold a reward until the referral passes checks for duplication, account creation, and purchase quality. Put the friction at the reward boundary, where a referral earns money, so the control appears before abuse becomes expensive. Once a program offers cash incentives or commission-based referral rewards, fraud becomes a significant concern.1

Set the exposure level

Decide what makes a reward payable and how much of that decision the system will make automatically. This sets where checks run and where a person reviews an exception.

If the program offers cash or commission-based rewards, add fraud controls to the launch plan before increasing participation. Record the event that qualifies a referral, the checks that can place it on hold, and the condition that releases payment. Keep those rules near the referral terms so participants can understand them before submitting.

Define eligible referrals

Set eligibility rules around the ways someone might claim a reward without producing a valid new referral. Participants should be able to tell what counts, what fails, and which sign-up path the invited person must use.

Common patterns include self-referrals under a different email, duplicate submissions of the same person, and fake account cycling to trigger a reward.2 The invited person must not sign up through a referral link or code shared by someone else.3

Design the program with clear terms and conditions, reward caps, unique tracking codes, and fraud-detection systems.4 State the rules before submission. When a referral fails a stated condition, the review decision has a clear rule to point to.

Screen each submission

Run checks when the referral enters the program, before its reward status becomes payable. Use a fixed order so the same pattern receives the same treatment across submissions.

Review the referral record first. Check whether the invited person already appears in the program, whether the sign-up followed the allowed link or code, and whether the account looks like a new participant. Then compare the referrer and invited person for shared details that may indicate self-referral or account cycling.

Put any referral that needs review on hold.

Gate the reward on quality

Pay only after an action shows that the referral has produced a legitimate customer outcome. A submitted form alone does not prove quality.

Flag referrals where the referrer and prospect share the same IP address. Require a minimum purchase before the reward pays out, and cap referrals per person per month until you have validated the quality.5

Keep the hold visible in the referral record and give it a reason that matches the rule. Once the purchase condition and fraud checks clear, release the reward through the same process used for other approved referrals. If quality stays weak, keep the cap in place and review the pattern before expanding it.

Handle exceptions

A referral that triggers a rule needs a decision path. Collect the missing context, record the decision, and keep the reward on hold while the condition remains unresolved.

In employee referral programs, fraudulent referrals can include fabricating a professional relationship, presenting an agency-sourced candidate as a personal referral, colluding to misrepresent qualifications, or failing to disclose a material personal or financial relationship.6

Use separate review questions for sourcing and disclosure concerns. Ask how the referrer knows the candidate, how the candidate entered the process, whether anyone helped present the referral as personal, and whether a personal or financial relationship should be disclosed. These questions help you inspect the referral's origin without treating every exception as a duplicate or fake account.

What not to do

These mistakes leave the reward path open after the program has made abuse easy.

  • Do not run an automated referral program with financial incentives without basic fraud checks.7
  • Do not allow a self-referral under another email, a duplicate submission, or fake account cycling to pass as a valid referral.2
  • Do not treat a tiered incentive program as safe from fake referrals because the reward is split across levels.8
  • Do not treat a leaderboard program as safe from fake referrals because participants compete for position.9

Sources

  1. 1
    “If you ever scale to the point where you're offering cash incentives or commission-based referral rewards, fraud becomes a real concern.”
  2. 2
    “The common patterns are self-referrals (someone referring themselves under a different email), duplicate referrals (submitting the same person multiple times), and account cycling (creating fake accounts to trigger the reward).”
  3. 3
    “Didn’t sign up through a referral link or code that someone else shared with them”
  4. 4
    “Implement clear terms and conditions, set reward caps like Spanx’s 50-referral annual limit, use unique tracking codes, and employ fraud detection systems.”
  5. 5
    “Flag referrals where the referrer and prospect share the same IP address, require a minimum purchase before the reward pays out, and set a cap on referrals per person per month until you've validated the quality.”
  6. 6
    “Fraudulent referrals include fabricating a professional relationship with the candidate, submitting agency-sourced candidates as personal referrals, colluding with the candidate to misrepresent qualifications, and failing to disclose material personal or financial relationships.”
  7. 7
    “But if you're building an automated referral program with financial incentives, build in basic checks.”
  8. 8
    “Will need fraud protection measures in place to ensure referrals aren’t fake”
  9. 9
    “You’ll need fraud protection measures in place to prevent fake referrals”