Is there a universal refer code?
No — each user has a unique code inside the app. We don't publish a "desk-wide" refer code.
The FanCode refer pipeline: invite a friend via your unique code, both get practice-contest credits at KYC. We never invent a refer number.
The FanCode refer / referral program lets an existing user invite a friend: both get practice-contest credits at KYC. The pipeline uses a unique code issued to each existing user inside the app — not a single desk-wide code.
The refer code sits inside the app, under "Profile → Refer & Earn". Each existing user has a unique code; the code is yours alone and is tracked at the operator side. The desk does not host a desk-wide refer code.
| Term | Detail |
|---|---|
| Eligibility | 18+ · India resident · non-restricted state. |
| KYC requirement | PAN + bank/UPI must clear for the invitee before either party gets the credit. |
| One-time vs recurring | The refer credit is typically one-time per invitee account. |
| Withdrawal | Refer credit is non-withdrawable; usable on practice contests during the campaign window. |
| Tracking window | The operator tracks each referral for the duration of the campaign window. |
Self-referrals (referring your own account), multi-account abuse, or inviting friends in restricted states are operator-level violations. The desk does not provide advice on how to circumvent these limits — if you have questions about whether an action is allowed, use the in-app support tab.
If a credit didn't land, check three things — (1) the invitee entered your code at sign-up (not after), (2) the invitee's KYC cleared, (3) the campaign window is still open. If the issue persists, write to compliance [at] fancodein.com with both account handles and timestamps.
No — each user has a unique code inside the app. We don't publish a "desk-wide" refer code.
Yes — the standard pipeline allows multiple invitee accounts per inviter. Each invitee clears KYC separately.
Refer credit typically sits in your wallet for the campaign window. After the campaign, the credit is non-withdrawable.
The invitee cannot be onboarded by the operator — the refer will not complete. The state-level regime prohibits paid fantasy entry.
The refer pipeline is the operator's primary acquisition channel — it outperforms paid social on a "verified user" basis because the invitee already has a positive trust signal from the inviter. The operator passes some of that value back to both inviter and invitee as practice-contest credit, which the operator can issue without diluting any commercial paid-entry pool.
It does not unlock restricted states (those are state-level restrictions). It does not change the captain multiplier. It does not bypass KYC. It does not change the payout tier of any contest. It is a credit-only channel — usable on practice contests during the campaign window.
The refer pipeline rewards have changed quarter to quarter. Some quarters the operator offers a flat practice-contest credit; others a tiered credit based on the invitee's KYC speed. The desk tracks the current quarter's structure on the refer code lane.
The invite pipeline is also subject to campaign windows. Where the campaign is closed, the standard invite + KYC pipeline may not yield a credit. Read the operator's in-app banner for the active window.
The refer pipeline rewards have changed quarter to quarter. Some quarters the operator offers a flat practice-contest credit; others a tiered credit based on the invitee's KYC speed; others a contest-entry discount on a specific sport's contest register. The desk tracks the current quarter's structure on the refer code lane.
The invite pipeline is also subject to campaign windows. Where the campaign is closed, the standard invite + KYC pipeline may not yield a credit. Read the operator's in-app banner for the active window before sending invites.
Self-referrals (referring your own account), multi-account abuse, or inviting friends in restricted states are operator-level violations. The desk does not provide advice on how to circumvent these limits — if you have questions about whether an action is allowed, use the in-app support tab or write to compliance [at] fancodein.com for editorial clarity.
The desk publishes the current refer pipeline structure on the lane. Where the structure changes mid-quarter, the desk publishes the change within 24 hours of the operator's announcement. Corrections log entries are recorded on this page.