Brand SERP · ReferralThe Zupee refer-and-earn flow lets an existing player share a personal invite. New players enter that invite during first sign-up, and both sides see a bonus unlock once the new player clears the operator-defined activity threshold. This page reads the flow end to end and flags the four caveats the desk has surfaced over the last six review cycles.
The refer flow is a personal invite between two players. The inviter shares a code or a link. The new player enters the code during sign-up. Both sides earn a bonus that is bound to gameplay activity, not free cash.
1. It is not free cash. Bonus funds unlock as you play and are non-withdrawable until cleared.
2. It is not symmetric. The inviter and invitee may see different bonus sizes.
3. It is not permanent. The operator refreshes the bonus terms periodically.
The personal refer code lives inside the operator app, on the Refer & Earn tab in the profile menu. Open the app, tap the profile icon, tap Refer & Earn, and copy the code.
The invite field appears during sign-up. If you skip it, the operator app does not let you add the code later. Ask your inviter to send the code before you begin sign-up.
Across recent desk reviews, the refer bonus typically sits in three tiers.
1. The bonus is non-withdrawable until the operator conditions are met.
2. Refer bonuses can expire. The window is typically 30–90 days from invite.
3. Self-referral is prohibited. The operator verifies KYC.
4. State rules apply. Refer bonuses do not unlock in restricted states. See the state guide.
Some Indian states restrict paid contests. The refer bonus only unlocks when both inviter and invitee are in permitted states. The state eligibility guide covers the per-state frame.
Refer code app के अंदर Refer & Earn tab में मिलता है। नया player sign-up के समय invite field में code paste करे। Bonus activity threshold पूरा होने पर unlock होता है। Bonus non-withdrawable होता है और state rules लागू रहते हैं।
Three habits the desk has internalised. First, treat the credit as a play-credit bonus, not cash; wagering rules and ceilings apply. Second, treat the qualifying steps as the variable; they change between refresh cycles. Third, treat the operator published terms as the source of truth on the day you invite.
Two things the desk treats as anchor facts. First, self-referral is explicitly disallowed; same-device, same-KYC and same-bank accounts are detected. Second, state restrictions on credit usage are real; the invite mechanic may be available in restricted states, but the credit cannot be used in some formats.
Three recurring ones. First, "what happens if my invitee does not complete KYC?" The mechanic is paused until your invitee completes KYC and the first-cycle play. Second, "do I get a credit on every referred friend?" Usually yes, up to a per-operator cap; verify the cap on the operator help section. Third, "can I refer from a restricted state?" The mechanic itself is usually available, but the credit cannot be used in some formats.
Two checks. First, the operator published refer terms on the help section. Second, your own number. Self-referral is explicitly disallowed.
For the welcome offer, see the bonus code page. For the KYC ladder, see the wallet & KYC guide. For the first-cycle habits, see the how to play guide. For the verification habit, see the verification desk.
Three questions the desk uses when readers ask. First, are you already registered with the operator? If yes, the refer path is the only one available to you. Second, do you intend to deposit more than the welcome bonus tier minimum? If yes, the bonus path pays back faster; the refer tier often takes more cycles to settle. Third, are you referring someone else at the same time? If yes, pick the refer path on the invite side and let your invitee pick bonus or refer on theirs.
Two recurring ones. First, "what happens if my friend does not complete KYC?" The mechanic is paused until your friend completes KYC and the first-cycle play. Second, "do I get a credit on every referred friend?" Usually yes, up to a per-operator cap. Verify the cap on the operator help section.
Two checks. First, the operator published refer terms on the help section. Bonus credits often carry a wagering rule that turns "free cash" into "play credit with a ceiling". Second, your own number. Self-referral is explicitly disallowed.
Two recurring ones. First, ceiling on bonus-derived winnings. Many readers learn about this only at withdrawal time. Second, state restrictions on credit usage. Even if the invite mechanic is available in restricted states, the credit cannot be used in some formats. Verify with the operator.
For the welcome offer, see the bonus code page. For the first-cycle habits, see the how to play guide. For the verification habit, see the verification desk.
Three habits the desk has internalised for the invite mechanic. First, share the code only after you have verified it on the operator main site. Second, confirm the invitee's KYC completion before treating the credit as settled. Third, expect the credit to settle as bonus or wallet credit, not cash.
Two things the desk treats as anchor facts. First, self-referral is explicitly disallowed. Second, state restrictions on credit usage are real.
For the welcome offer, see the bonus code page. For the KYC ladder, see the wallet & KYC guide.
In the app, Profile → Refer & Earn. The code is unique to your account.
No. The operator verifies KYC against self-referral patterns.
When the invitee completes deposit plus the activity threshold.
No until the operator conditions are met. After unlock it acts as bonus cash subject to standard rules.
Codes typically do not expire, but individual bonus offers do.
There is no public cap, but abusive patterns trigger review.
No. Both sides must be in a permitted state.
The two welcome surfaces look similar but reward different reader behaviour. The refer path rewards you when someone you invite plays. The bonus path rewards you when you deposit. Choose refer if your network has active players who would open the app anyway. Choose bonus if you are the first mover in your circle and the network is still cold. The two are not mutually exclusive: the refer and the bonus are tracked separately, and you can run both cycles in parallel. The bonus guide covers the welcome tier in detail.
One small detail that is easy to miss: the refer reward is credited to the inviter's account only after the invitee has played at least one paid contest. The invitee-side reward is credited after the first deposit. The settlement cycle is published in the operator's terms, and the wallet page tracks the actual balance.
The refer settlement has three discrete windows. The first is the invitee registration, which is instantaneous. The second is the invitee first deposit, which the operator ties to the matched-deposit bonus. The third is the invitee first paid contest, which the operator ties to the inviter's reward. The third window is the one most readers miss. The inviter's reward is queued at the invitee's first deposit and released at the invitee's first paid contest. If the invitee deposits but never plays, the inviter's reward is never released. The cycle is published in the refer program's terms, and the desk's habit is to record the settlement on a private sheet so the reader can reconcile the actual credit against the expected credit.
The wallet page shows the refer balance separately from the bonus balance, and the settlement date is published on the wallet ledger. If the credit is missing, the reader's first move is to check the invitee's first-paid-contest history before raising a support ticket.
Five pitfalls come up often enough to document. The first is dual-accounting, where the invitee creates a second account because the first sign-in failed. The dual-account is treated as a single invitee, and the inviter's reward is paid once. The second is shared-device, where the inviter and the invitee play from the same device. The operator's device-token registry flags shared-device invites and the reward is held until the inviter writes to the support desk. The third is geo-mismatch, where the invitee signs up from a restricted state. The inviter's reward is paid only after the invitee plays a contest in a permitted state. The fourth is KYC incomplete, where the invitee has not yet completed Aadhaar. The reward is held until the invitee clears the KYC ladder. The fifth is invitee churn, where the invitee plays one contest and never returns. The reward is paid; the recurring bonus is not.
The fastest path is the order of operations: check the invitee's first-paid-contest history, then check the KYC status, then write to the support desk with the invitee's registered mobile number and the contest ID. The desk can re-verify the invitee path and release the held reward. The reader should not expect the release to be instant; the support queue's published SLA is 48 hours.
The is-legal page covers the state-by-state eligibility that governs the invitee path. The terms page documents the operator's published cycle.
