Refer code: where to enter it, when it binds, why it fails
The refer code on myteam11app.com is entered during registration on the verified first-party path, before the first qualifying deposit. Captured 17 August 2026, the entry mechanic is stable; the failure modes below are preventable by reading the standing reading once.
/Login/playnow) which records the click and continues to the operator. Editorial links inside the body remain independent. Read the responsible play notice before participating.
Where the code goes in the registration flow
The refer code on myteam11app.com is the operator-issued string a referrer generates from the refer and earn surface and the referee enters during registration. The code carries the referrer's verified account identifier; the code itself is short, case-insensitive and unique to the referrer's account.
The code is entered on the registration screen inside the operator's flow, not on the myteam11app.com surface. The Verified Path carries the referee to the registration screen on the verified first-party path /Login/playnow. Editing the code after registration is not supported; the welcome bonus eligibility is locked at registration.
Codes do not carry a fee. Codes do not carry an expiry inside the promotional cycle. Codes do not carry any data outside the operator's referrer-to-referee link. Anyone offering a paid code is not offering an operator-issued code.
Three valid moments, three invalid moments
Valid code-entry moments are: during registration on the verified first-party path, before the first qualifying deposit. Invalid code-entry moments are: after registration, after the first deposit, against a second account on the same mobile number, against a deposit that fails KYC.
Codes entered after registration do not bind. Codes entered against a second account on the same mobile number do not bind. Codes entered against a deposit that fails KYC do not bind. None of these three failure modes is recoverable through customer care; the referee must reach the contract without a referrer-side payment or restart the registration flow with a new mobile number.
Reading the contract once before signing up saves the referee from every invalid-moment failure. The standing reading is on /refer-and-earn/; the KYC requirement is on /wallet-kyc/.
What the referrer clicks to get the code
The referrer generates the code inside the operator's refer and earn surface. The mechanism is a button labelled something like Generate code on the in-app rewards tab. The generated code is a short alphanumeric string that the referrer copies and shares through the channel of their choice. Sharing the code does not share the referrer's identity beyond the operator's record.
Codes are bound to the referrer's verified account. The referrer cannot generate two codes at once, cannot override an unforced code and cannot generate a code for a different referee. The standing reading of these constraints is on /refer-and-earn/.
The referral surface does not let a referrer see who has used their code in real time. The referrer's refer and earn screen settles the reward after the referee's KYC and verified first-deposit threshold are both cleared.
Why a code does not bind
Five conditions cause a refer code not to bind. They look mechanical on the surface; each one voids the contract without warning.
- Wrong field. The code is entered on a non-registration screen, such as the in-app help field or the wallet screen.
- Whitespace or characters. The code is copied with leading or trailing whitespace, or with a character set outside the alphanumeric range.
- Second account on the same number. The referee's mobile number matches an existing verified mobile number; the second account forfeits the welcome bonus.
- State restriction. The referee's state is in the restricted list and the operator's flow blocks the registration.
- Code expired. The code was generated in an earlier promotional cycle and the operator has rotated the referrer-side reward.
Each condition is preventable. Read the contract on /refer-and-earn/, the state rules on /is-legal/, and the KYC chain on /wallet-kyc/ before signing up.
Five routes to read before generating or using a code
The reading order is short: confirm state eligibility on /is-legal/; confirm age on /responsible-play/; confirm KYC requirements on /wallet-kyc/; confirm the contract on /refer-and-earn/; then reach the verified registration flow through /Login/playnow.
Visitors who read these five routes in order before signing up reach the welcome bonus on the first attempt. Visitors who skip the reading order lose either the bonus or the referrer's reward or both, and must either restart the flow with a new mobile number or accept the loss.
Seven routes worth opening
Five questions visitors ask first
Where is the code entered?
Can the code be edited after registration?
Why does the code not bind?
Is the code paid?
Where is the standing reading?
Enter the code on the verified path
Read the contract, confirm state and KYC, and reach the registration screen on the verified first-party path.