How invites and rewards work, and the inputs the desk recommends reading.
A referral code is a personal or promotional code that links a new account to an existing one. The mechanics vary by platform, but the inputs the desk recommends reading are consistent: the eligibility, the reward, the attribution window, and the privacy implications.
On this page
How a referral code works
A referral code is a personal or promotional code that links a new account to an existing one. When the new account meets a condition (usually a first deposit or a first entry fee), both the referrer and the new account receive a reward, and the new account is attributed to the referrer. The mechanics are simple, but the clauses that govern the mechanics are not. The desk recommends reading all four clauses below before you enter or share a referral code.
Clause 1: eligibility
Eligibility is the set of conditions you must meet to claim the reward. Common conditions are: you must be a new customer, you must be in an eligible jurisdiction, you must not have claimed a previous bonus, and you must meet a minimum deposit. The desk's recommendation is to read the eligibility clause before you enter the code, and to confirm you meet every condition.
Clause 2: reward
The reward is what the platform gives you for using the referral code. Common rewards are: a bonus credit, a free entry, a cashback, or a contest entry. The desk's position is that the reward is the second input to read, after the eligibility clause. A large reward with a low eligibility threshold is a strong signal; a large reward with a high eligibility threshold is a signal to read the rest of the offer more carefully.
Clause 3: attribution window
The attribution window is the time between the new account creation and the reward being credited. A short attribution window (less than 24 hours) is a signal that the platform wants the new account to act quickly. A long attribution window (more than 30 days) is a signal that the platform is more patient about the conversion. The desk's recommendation is to read the attribution window before you enter the code, and to plan the entry fees to fit inside the window.
Clause 4: privacy implications
The privacy implications are the data the platform collects when you use a referral code, and the data the platform shares with the referrer. Common data points are: the new account's email address, the new account's first deposit amount, and the new account's first entry fee. The desk's recommendation is to read the privacy implications before you enter the code, and to confirm the data sharing is consistent with your expectation.
Four clauses, two accounts, one link. Read the link before you click it.
Pair the referral code with the bonus code page
The four clauses apply to both. Read both pages before you enter or share a code.
Affiliate disclosure: the button above routes through a first-party redirect. The desk may earn a small commission if you sign up.
How to read a referral code you have never seen before
A new referral code is a code the desk has not covered. The desk's reading of a new referral code is conservative: read the eligibility, read the reward, read the attribution window, and read the privacy implications. The four reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a new referral code, and the desk does not recommend a specific referral without the four reads. The reason is the same: a hot take is a guess, and a guess is not the product.
How the desk handles a referral code with vague eligibility
A referral code with vague eligibility is a signal to slow down, not a signal to dismiss. The desk's reading of a vague-eligibility referral code is conservative: read the eligibility, read the terms page, and read the publisher name. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a vague-eligibility referral code is verified, and the correction is the input the desk recommends reading.
How to read a referral code with a short attribution window
A referral code with a short attribution window is a signal to slow down, not a signal to dismiss. The desk's reading of a short-attribution referral code is conservative: read the attribution window, read the reward, and read the eligibility. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a short-attribution referral code is verified, and the correction is the input the desk recommends reading.
How the desk handles a referral code with restrictive privacy implications
A referral code with restrictive privacy implications is a signal to slow down, not a signal to dismiss. The desk's reading of a restrictive-privacy referral code is conservative: read the privacy implications, read the data sharing, and read the terms page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a restrictive-privacy referral code is verified, and the correction is the input the desk recommends reading.
How to read a referral code with a large reward
A referral code with a large reward is a signal to slow down, not a signal to dismiss. The desk's reading of a large-reward referral code is conservative: read the reward, read the eligibility, and read the attribution window. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a large-reward referral code is verified, and the correction is the input the desk recommends reading.
How the desk handles a referral code on a day with no matches
The desk does not publish a referral code update on a day with no matches. The desk's reading of a no-match day is conservative: read the corrections log, read the editorial policy, and read the responsible-play page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a no-match day, and the desk does not recommend a specific referral code. The reason is the same: a hot take is a guess, and a guess is not the product.
How to read a referral code that has been retired
A referral code that has been retired is a signal to slow down, not a signal to dismiss. The desk's reading of a retired referral code is conservative: read the retirement notice, compare the retirement notice to the original terms, and read the date. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a retired referral code is verified, and the correction is the input the desk recommends reading.
How the desk handles a referral code that has been replaced
A referral code that has been replaced is a public document, and the public document is the source of truth. The desk's reading of a replaced referral code is conservative: read the replacement notice, compare the replacement notice to the original terms, and read the date. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a replaced referral code is verified, and the correction is the input the desk recommends reading.
How to read a referral code that requires a phone number
A referral code that requires a phone number is a signal to slow down, not a signal to dismiss. The desk's reading of a phone-required referral code is conservative: read the phone requirement, compare the requirement to the privacy implications, and read the terms page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a phone-required referral code is verified, and the correction is the input the desk recommends reading.
How the desk handles a referral code that is restricted to a single jurisdiction
A referral code that is restricted to a single jurisdiction is a public document, and the public document is the source of truth. The desk's reading of a jurisdiction-restricted referral code is conservative: read the jurisdiction, compare the jurisdiction to the legal status page, and read the terms page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a jurisdiction-restricted referral code, and the desk does not recommend a specific platform without the three reads. The reason is the same: a hot take is a guess, and a guess is not the product.
How to read a referral code that is restricted to a single payment method
A referral code that is restricted to a single payment method is a signal to slow down, not a signal to dismiss. The desk's reading of a payment-restricted referral code is conservative: read the payment method, compare the method to the wallet and KYC page, and read the terms page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk publishes a correction when a payment-restricted referral code is verified, and the correction is the input the desk recommends reading.
How the desk handles a referral code on a day with no matches
The desk does not publish a referral code update on a day with no matches. The desk's reading of a no-match day is conservative: read the corrections log, read the editorial policy, and read the responsible-play page. The three reads are the inputs the desk recommends, and the inputs are the difference between a guess and a bet. The desk does not publish a hot take on a no-match day, and the desk does not recommend a specific referral code. The reason is the same: a hot take is a guess, and a guess is not the product.