DESK
What a referral code is and why the desk declines to publish one
iplfantasyteam.com does not publish referral codes for any fantasy platform and does not accept compensation for sharing them. A referral code is a string of characters that ties a new account to an existing user; the existing user usually receives a benefit when the new user signs up and meets the platform's eligibility conditions. The desk declines to publish codes for the same reasons it declines to publish bonus codes: the desk cannot verify eligibility, cannot keep the offer current, and cannot adjudicate a dispute if the new account is credited differently from what the headline promised.
Where a reader wants to use a referral link, the platform's own refer-code terms page is the right source. The page describes the benefit, the eligibility, the expiry and the dispute path. The desk's role is to explain how referral codes are typically structured and what to verify before using one. The desk does not take the place of the platform's own page.
How a referral code works in plain language
A referral code is tied to a specific user. When the new reader signs up using the code, the platform records the connection between the new account and the existing user. The benefit — usually a small credit, a free contest entry or a points boost — is paid out when the new user meets the platform's eligibility conditions. The eligibility conditions usually include a minimum deposit, a first contest entry, a verified KYC check or a minimum wallet activity.
The benefit for the new user is usually smaller than the benefit for the existing user. The existing user is the marketing channel; the existing user's benefit is the platform's cost of acquiring the new user. A reader who understands the structure is in a better position to weigh the offer than a reader who sees only the headline. The structure is described in plain language on the platform's refer-code page; the reader who reads that page has done the most useful reading.
Why the desk declines to publish codes
Publishing a code from a desk creates three risks. First, the desk cannot verify the offer is current; an offer that changes weekly cannot be republished weekly with confidence. Second, the desk cannot verify the reader's eligibility; a code that requires a fresh account or a first deposit does not apply to every reader who clicks the link. Third, the desk cannot adjudicate a dispute if the reader's account is credited differently from what the headline promised. A desk that publishes codes is effectively taking on a service role for an operator it does not represent.
The editorial position is straightforward. Codes belong to the platform that issues them and to the user who refers them; the platform's own pages are the place to confirm the offer. The desk's contribution is to explain how codes are typically structured, what the small print usually restricts, and how to spot a code that is being used to add pressure rather than to communicate a benefit. The reader who knows the structure is harder to mislead than the reader who is just searching for a string of characters.
What the small print usually says
On most fantasy platforms, the small print behind a referral code covers the same terms as the small print behind a bonus code. It says what the benefit is, what the eligibility conditions are, when the benefit expires and what happens if the new user withdraws before the benefit is fully used. A reader who clicks through a referral link without opening the small print has accepted an offer whose value they cannot verify. The desk recommends opening the small print before applying the code, not after.
Some platforms also publish a refer-code FAQ beside the small print. The FAQ is often faster to read and is sometimes clearer than the formal terms, but it is also less precise. Where the two disagree, the formal terms govern. The reader who notices the disagreement can ask the platform's customer-care channel for clarification before applying the code. A code applied under the wrong rule can be hard to reverse.
Eligibility, expiry and the catch
Three conditions decide most of the value of a referral code. First, eligibility: many referral offers are open only to new accounts or to accounts that have not yet made a first deposit. A reader who already has an account or has already made a first deposit may not be eligible at all. Second, expiry: the benefit usually expires after a defined window. A code applied too close to a contest window can produce a benefit that the new user cannot use in time. Third, the catch: the benefit can sometimes be forfeited if the new user withdraws before the benefit is fully used.
A reader who knows these three conditions can read a refer-code page in a few seconds and decide whether the offer is worth applying. The desk does not endorse any particular offer, but it does suggest that a reader pause on the offer page long enough to read the three conditions. The pause is the cheapest part of the process and the part that most often changes whether the code is worth applying.
| Condition | What it controls | Why a reader should check it |
|---|---|---|
| Eligibility | Whether the new account qualifies for the offer. | An existing account or a previously made deposit can disqualify the reader. |
| Expiry | How long the benefit lasts once credited. | A short expiry can wipe out the value of a large benefit. |
| Withdrawal behaviour | What happens if the benefit is partly used. | Some platforms forfeit the remainder on withdrawal. |
| KYC requirement | Whether identity verification is required before the benefit is credited. | A KYC delay can push the credit past the expiry. |
| Dispute path | Where to take a query if the benefit is not credited. | The platform's customer-care channel is the first destination. |
Codes received through chat groups and forwards
A code that arrives in a chat message, a Telegram group, a Discord server or a forwarded SMS is not necessarily an offer from the platform. It may be an affiliate link, a referral from a current user, a code that is no longer valid, a code that ties the reader to a particular account, or a code that exists only to track which channel the reader came from. The desk treats all of these as signals to slow down rather than as signals to apply.
If the reader recognises the channel and trusts it, the next step is to open the platform's official onboarding screen in a separate browser tab and type the code in directly. Applying a code from a third-party page is not the same as applying it from the platform; some affiliate links change which account the code credits. A reader who wants to test a code can do so without surrendering the ability to verify the offer first.
Affiliate codes versus user-shared codes
Affiliate codes are tied to a professional affiliate partner. The partner usually has a website or a channel through which the partner promotes the platform; the platform pays the partner a commission when the new user signs up and meets the eligibility conditions. The benefit for the new user is sometimes larger under an affiliate code than under a regular referral code, because the platform is paying for the affiliate's marketing. The desk's position is that the affiliate relationship is the affiliate's, not the desk's.
User-shared codes are tied to an existing user. The benefit is usually smaller because the platform is paying for the user's word-of-mouth. Both kinds of code are legitimate; both kinds of code should be checked on the platform's own page before being applied. The check is the same: open the platform's refer-code terms page, look for the code or the partner name and confirm the benefit. The reader who can do the check quickly is the reader who has done the most useful reading.
What to do when a code is not credited
Where a code is applied and the benefit is not credited, the next step is the platform's customer-care channel. The reader should include the code applied, the date and time of application, a screenshot of the offer T&Cs at the time, the registered email address and the device or browser used to apply. The reader who keeps a record of the application has a record the platform's customer-care team can use to investigate. A code applied and forgotten is a code the reader will struggle to recover.
Where the platform's customer-care team does not resolve the issue, the next step is the platform's grievance officer. The reader who escalates to the grievance officer should attach the previous support conversation and the date of each interaction. The escalation is a documented step on the same chain; the reader who keeps the record is the reader whose escalation is most likely to be answered.
How the desk describes referral codes without publishing them
The desk can describe the structure of a referral code, the typical eligibility conditions and the small print that usually applies. The desk can also explain the difference between an affiliate code and a user-shared code and the kinds of disputes that often arise. The desk does not publish codes because the desk cannot verify eligibility, cannot keep the offer current and cannot adjudicate a dispute.
The desk's role is therefore structural, not transactional. A reader who understands the structure is in a better position to evaluate any particular code than a reader who has been given a code without context. The structural approach is also the approach that survives the longest; the structure of a code does not change between seasons, even if the codes themselves do.
Reader questions
Does this desk publish referral codes?
What is the benefit of using a referral code?
Are affiliate codes different from user-shared codes?
What if the benefit is not credited?
Can the desk verify a code for me?
Is a bigger referral benefit always better?
Continue with care
Open the platform's refer-code terms page directly. Verify eligibility, expiry and withdrawal behaviour before applying any code; the desk stays out of that flow on purpose.