Guru11 refer code conditions: five things that determine payout
A refer bonus sounds simple: you share a code, your friend signs up, both of you get a reward. The simplicity hides a set of conditions that determine whether the bonus actually pays out. This post walks through the five conditions most often missed and what to confirm before you share the code or use a code someone shared with you.
Confirm the qualifying action
The qualifying action is the step your friend has to complete for both bonuses to fire. Most operators use a minimum first deposit - usually ₹100, ₹500, or ₹1000. Some add a second requirement (a paid contest entry, KYC completion). The qualifying action is published in the refer program's terms; it's the single most important number to confirm before either of you commits to anything.
If the qualifying action is KYC completion, your friend has to upload PAN and bank details before the bonus fires. That's a sensitive step, and the responsible-play hub explains the kind of caution that should apply. If the qualifying action is a first deposit, your friend should still make the deposit only after the 24-hour pause covered in the coupon post.
Confirm the time window
The time window is how long your friend has to complete the qualifying action after signing up with your code. Common windows are 7, 14, and 30 days. If your friend signs up but doesn't complete the qualifying action within the window, both bonuses are voided even if the deposit eventually happens.
Read the time window before you share the code. If your friend is on the fence, a 7-day window may not give them enough time to think it through. A 30-day window does. The coupon post covers the same idea - the 24-hour pause rule applies as much to whether to sign up at all as it does to whether to deposit.
The single-account rule is non-negotiable
Every operator enforces a single-account rule. One person, one account, one phone, one PAN, one bank account. The detection is strict - device fingerprint, IP address, network fingerprint, identity data. If the system flags a connection between your account and your friend's account, both bonuses are voided and the accounts may be suspended.
The most common violation is the family share - a son shares his refer code with his father, the father signs up using the son's Wi-Fi, the system flags both accounts because they share an IP and possibly a device. The son loses his bonus, the father loses his welcome offer, and both accounts are now flagged. The fix is simple: don't share the code with people who use your device or your network.
Bonus turnover and how to handle it
The refer bonus, like the coupon bonus, usually carries a turnover requirement. The bonus moves from bonus balance to cash balance only after you've entered contests worth the required multiple of the bonus amount. A ₹100 bonus with a 5x turnover requires ₹500 in contest entry fees before the ₹100 becomes withdrawable cash.
The refer-hub covers the turnover mechanic in detail. The short version: only share the code with friends who will actually play through the turnover. If your friend is signing up just to try the app, the bonus may sit in their bonus balance until it expires, and neither of you benefits from the referral.
The one-offer-per-account stack rule
Most operators don't allow stacking the refer bonus with a coupon bonus on the same account. Your friend signs up using your code, claims the refer welcome offer, and then tries to claim a separate coupon - the second claim is rejected, or worse, it cancels the first. The rule is server-side and silent; the reader finds out only when the bonus disappears.
The fix: read the offers page before your friend signs up, decide which single offer is best for them, and have them claim only that one. If the refer offer is the better deal, they use your code and skip the coupon. If a specific coupon is the better deal, they use the coupon and skip your code. Pick one, not both.
What "new user" actually means
The new-user restriction for refer bonuses is enforced against phone, PAN, bank account, and device fingerprint. A reader who already has a Guru11 account - even if it's been inactive for a year - is not a new user. A reader who previously had a Guru11 account that they closed - same thing. The system remembers.
If you're not sure whether a friend qualifies as a new user, ask them directly. If they have any prior relationship with the operator, your refer code won't fire. Better to know that before you share than to discover it from a silent bonus cancellation weeks later.
How to track your referrals
The Refer or Invite section of the app shows the status of each friend you referred. The statuses are typically: signed up (entered your code at registration), deposited (completed the qualifying deposit), qualified (met all conditions including turnover), bonus credited (paid to your account). If a status looks stuck or wrong, raise a support ticket with the operator's app, not by email or WhatsApp.
If a referral doesn't progress to qualified within the published window, the bonus is voided - not delayed. The system doesn't extend the window because you raised a support ticket at day 28. Plan around the published window, not around the support ticket you'd raise if the window passes.
Closing thought
The refer bonus is a small benefit on top of a sign-up that's already happening. Treat it that way. Don't share the code with people who haven't decided whether they want to play fantasy cricket. Don't try to game the single-account rule. Don't deposit money just to clear the qualifying action. The conditions exist because the operator is paying for an introduction, not for a lifetime customer - and the rules are designed to be enforced.
The refer hub covers the operational side. The coupon post covers the parallel rules on the coupon side. The fantasy cricket hub covers what to do once your friend is signed up and ready to play. Together, the three posts cover the full life-cycle of a referral, from "should I share this code" through "did the bonus pay out" to "what does my friend do next."