How a myteam11 refer code flows from sender to receiver
Refer codes are generated inside the app for the sender and pasted by the receiver at sign-up. The flow below documents eligibility, KYC gating, and when the credit lands.
Sender flow: generate, share, wait
Open the app and pick Profile
The profile tab is the bottom-right icon.
Tap "Refer a friend"
The screen shows your personal refer code and a share button.
Share the code or the share link
Both are valid. The share link auto-fills the code on the receiver's sign-up screen.
Wait for the invitee to complete KYC
The credit lands only after the invitee's KYC clears; see /wallet-kyc/ for the verification timing.
Receiver flow: paste at sign-up
Install the app from /download/
Use the verified APK from the myteam11play.com editorial.
Enter the mobile number and tap "Have a refer code?"
The field appears under the OTP entry.
Paste the code or open the share link
The share link auto-fills the field on the receiver's device.
Complete KYC at first withdrawal
The sender credit does not fire until the receiver has cleared KYC at least once.
Eligibility rules
- Sender account must be in a state that is not in the {STATE_LIST} restriction list.
- Receiver must be a new mobile number, not previously registered on the platform.
- Receiver must clear KYC (PAN, Aadhaar, or both, depending on the withdrawal path).
- Receiver must make at least one contest entry before the sender credit fires.
- The sender-receiver pair must not share a device fingerprint.
Credit timing
The credit lands in the sender's wallet within 24 to 72 hours of the receiver clearing KYC and entering the first contest. A credit that does not appear after 72 hours can be traced by emailing /customer-care/ with the registered mobile numbers of both accounts.
Stacking with the welcome code
A refer code and a welcome code cannot both be applied on the same receiver account. If the receiver has both available, the in-app form prompts the reader to pick one. The editorial recommendation is to use the welcome code if the receiver has no network of friends already on the app, and the refer code if the sender expects to refer more than two receivers in the same month.
State rule Paid entry is restricted in Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, Sikkim, Nagaland. The app enforces the list at sign-up and again at first deposit. Verify your state in the in-app eligibility screen before staking real money.
Welcome code mechanics, including the welcome code string itself, are documented on /bonus-code/. The two flows share the same deposit step but use different eligibility paths.
The flow, the gating rule, and the credit timeline
The refer-a-friend flow has four steps: the referrer opens the in-app profile, picks Share, and the app generates a share link. The invitee taps the link, installs the app, and signs up through the link. The invitee plays through the KYC pass. The referrer is credited on the operator's schedule.
The gating rule: the invitee must complete KYC before the referrer is credited. If the invitee signs up through the link but does not complete KYC, the referrer is not credited and the invite link is treated as incomplete. The gating rule is enforced inside the app; the writers mirrors the rule on this guide.
The credit timeline: the operator credits the referrer on a schedule set by the operator, typically within 24 to 72 hours of the invitee's KYC pass. The credit is visible in the referrer's wallet history inside the app. Writers does not publish a specific timeline because the operator can shift it between campaigns.
Who is eligible to refer: any verified account that has cleared KYC and has at least one successful contest entry. A brand-new account that has not yet played cannot refer; the operator enforces the eligibility rule inside the app. The eligibility check happens at the moment the referrer generates the share link.
What the invitee sees: the invitee sees the welcome screen with the referrer's identifier attached to the account. The welcome offer on first deposit applies normally; the referrer credit is on the referrer's side, not the invitee's. The invitee does not see the referrer's credit; the invitee sees only the welcome credit.
What remains stable across refer campaigns: the gating rule, the credit on the referrer's side, and the eligibility check at share-link generation. The timeline, the credit amount, and the campaign availability can shift between cycles; the framework does not. The in-app Promotions tab is the canonical source for the current campaign.
Editorial methodology for the referral walk-through
The refer-code page is the referral-mechanics walk-through. The desk publishes the in-app refer-a-friend flow, the eligibility rules, the invitee experience, and the reward credit timeline. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a reward.
For the in-app flow, the source is the in-app Profile, Refer a Friend screen. The desk does not publish a refer-a-friend flow that the in-app screen does not surface. The flow is the canonical reference; the desk does not paraphrase the screen labels.
For the eligibility rules, the source is the in-app Help tab's Refer a Friend rules. The desk does not publish an eligibility rule that the in-app Help tab does not surface. The eligibility rule is the canonical reference; the desk does not invent a rule.
For the invitee experience, the source is the in-app install flow that surfaces the refer code field. The desk does not publish an invitee experience that the in-app install flow does not surface. The invitee experience is the canonical reference; the desk does not invent an experience.
For the reward credit timeline, the source is the in-app Help tab's Refer a Friend rules. The desk does not publish a reward credit timeline that the in-app Help tab does not surface. The timeline is the canonical reference; the desk does not invent a timeline.
For what the desk does not do, the answer is publish a reward credit amount that the in-app Help tab does not surface. The reward is the canonical reference; the desk does not invent a reward. The verification is the test account's recorded interaction.
Update cadence: reviewed when the in-app Profile, Refer a Friend screen changes, when the in-app Help tab's Refer a Friend rules changes, when the reward credit timeline changes, or when the product brand publishes a new referral policy. The review date is in the footer of every page in this guide.
What this desk does not publish
The refer-code page does not publish a refer-a-friend flow that the in-app Profile does not surface. The desk does not publish an eligibility rule that the in-app Help tab does not surface. The desk does not publish a reward credit timeline that the in-app Help tab does not surface.
The desk does not publish a reward credit amount that the in-app Help tab does not surface. The desk does not publish an invitee experience that the in-app install flow does not surface. The desk does not publish a refer-code projection that the test account has not recorded.
The desk's role is the editorial coverage. The reader's role is the refer-code execution. The desk does not substitute its editorial coverage for the reader's own execution; the reader can follow the in-app Refer a Friend flow and verify the eligibility rule and the reward credit timeline inside the in-app Help tab. The verified entry route is at /app/.