A Wecap referral code looks like a five-second promise: copy, paste, share, wait. The desk habit is the opposite. The first share is the slowest share, because every link you send out carries your account's signature for the next ninety days. A referral chain that does not form is not a refund. It is a quiet null result, hidden behind a Refer & Earn screen you may never reopen.
The strongest time to verify the chain is before the first share, not after the third or fourth failure to credit. The desk's habit is to run a six-step checklist the moment the code is generated, and again whenever the operator quietly publishes a fresh terms revision. The checklist below borrows from that habit. Nothing in it requires anything more than the in-app Refer & Earn screen, the league eligibility rules, and a one-screen audit of the referee's sign-up path.
What the code actually is, and what it is not
The Wecap referral code is a signed string that the operator issues at the moment your account clears identity verification. It is bound to your verified PAN and to the device that signed up first. It is not a static printed coupon. It is not your user name, your registered email, or the wallet address your deposits flow from. It is also not a public asset: the operator keeps the rules for reward caps, validity windows, and per-state eligibility on the in-app Refer & Earn page, not on the App Store listing.
The single source of truth on what the code pays out is the in-app Refer & Earn screen. The single source of truth on whether the chain has formed is the same screen, after the referee signs up. The screen shows the code, the cap, the validity window, and the count of referees who have already cleared KYC for the current month. Anything printed outside that screen is editorial context, not policy.
A reader who treats the code as a printable coupon is setting up a chain that will not pay out. A reader who treats the screen as the source is reading the chain the way the operator writes it. The difference is the same six checks.
Six checks before the first share
Run these six checks in order. Most readers finish the loop in three minutes. The first three are about your account. The next three are about the referee you are about to message.
Check 1, your KYC is fully approved. Open the wallet screen and confirm that the PAN and Aadhaar verification have both flipped to a green or approved state. A code issued against a partial KYC will sit in your profile, but the moment a referee enters KYC the chain is voided. Most failed chains the desk has traced came from this one check.
Check 2, your state of residence is on the permitted list. Fantasy cricket is restricted in Telangana, Andhra Pradesh, Assam, Odisha, Sikkim, and Nagaland. If your address moved during a KYC re-verification and you are now in one of those states, the code still issues, but rewards cannot credit you. The cleanest move is to confirm the state on file before you share, not after the first payout fails to land.
Check 3, the code itself matches the one in the operator's record. Open the Refer & Earn screen, copy the code, and paste it into a notes file. Reopen the screen after thirty seconds and confirm the same value is still there. The desk has seen rare cases where an outdated cache or a stale session showed an old code, which silently produces a chain that cannot attribute to the current account. The reload habit is the cheapest fix.
Check 4, the referee is reachable on the channel you plan to use. An email referral to a friend whose primary inbox is full produces an unread invite. A WhatsApp share to a friend whose number has already been used in another account is treated as a duplicate. A Telegram share to a friend whose handle is on a banned list is ignored. The cleanest check is a one-line confirmation: are you on the same channel I am about to send this from?
Check 5, the referee is in a state where Wecap pays out. The chain still forms if the referee is in a restricted state, but no reward credits to either side. Confirming state before the share saves the awkward conversation about why a friend's account never paid out.
Check 6, the referee understands that KYC and a paid contest come first. Practice contests and unverified accounts do not unlock the reward. Telling the referee, before they download, that the chain unlocks the moment they finish PAN and enter one paid contest inside the validity window, removes ninety percent of the friction that produces "I signed up, where is my reward?" follow-ups.
What to watch after the share
The post-share window is where the desk habit diverges from the casual reader's habit. The casual reader waits. The desk reader runs a one-screen audit every twenty-four hours, until the referee has cleared both gates.
The audit looks like this. Open Refer & Earn. There is a referee count in the current month, a referee status icon, and a reward status chip. The chip sits in one of four states: pending verification, KYC submitted, KYC approved, contest entered, and rewarded. Each state is a normal milestone. Skipping from pending verification straight to rewarded happens on the rare three-pathway chain where the operator carries forward an old KYC. Skipping from pending to nothing happens on the much more common chain where the referee abandoned the install.
The cleanest rule is to count milestones, not weeks. If three days pass without movement from pending verification, send a one-line nudge: did the install complete? If seven days pass without movement from KYC submitted, send another nudge: did PAN finish? The rules allow generous slack. The desk's habit is to assume silence means a stalled sign-up, not a refusal, and to send the smallest possible message rather than wait indefinitely.
Where chains actually break
Three failure modes drive the bulk of unresolved chains. Each one is detectable before the share, and each one is much harder to detect after.
The first failure mode is what the desk calls an attribution break. The referee installs the app on a different device from the one you used to generate the code, or pastes the code into a different browser before the phone number is entered. The operator binds the chain to the device and to the phone number used at sign-up. Switching either one before the KYC step finishes produces a chain that sits in neither account. The check is to send the referee a screenshot of the code with a one-line instruction to install on the same phone they will use long term.
The second failure mode is a reward cap collision. Most operators cap referral rewards at a single-digit monthly ceiling. A reader who shares the code to a fifty-person WhatsApp group on the day they cross the cap produces fifty chains that never pay out for the month. The cleanest check is to re-read the Refer & Earn screen right before a broadcast share, and time the share for the first of the following month when the cap resets.
The third failure mode is a state mismatch. The referee's KYC binds to the address at the time of identity verification, not the address on their Aadhaar at any other moment. A referee who travels at the moment of sign-up, or who lists an out-of-state address on PAN while keeping an in-state address on their phone bill, can land in either bucket. The cheapest fix is to confirm with the referee, before they sign up, where they will be doing the verification.
What if you skip the check: a counterfactual
Run the same six checks on a different reader's habit. The reader copies the code from a friend's message, pastes it into the in-app Refer & Earn field, signs up under a phone number they had used three years earlier on a closed account, completes PAN with a missing Aadhaar digit, and joins a practice contest the same evening. Five minutes of friction, no reward.
Now run the same six checks with the desk habit in place. The reader confirms PAN and Aadhaar match before sharing, asks the referee to install on a long-term device, asks the referee to list their current state of residence on PAN, tells the referee that a paid contest unlocks the reward, and times the broadcast for a clean monthly cycle. The chain forms, KYC clears on day one, the paid contest unlocks on day two, and the reward credits on the third. Same code, same operator, different reader habit.
Strong evidence that the six checks are the binding factor would be a controlled test on the same chain. The desk's habit is to treat the absence of the six checks as a sufficient explanation whenever a chain stalls. A reader who disagrees should look for evidence first inside the six checks, and only escalate to support if every check passes and the chain still does not form.
Where to read when the screen is silent
The in-app Refer & Earn screen is the source of truth. The Refer Code page on the desk site is the editorial context for that screen: how the program is structured, what the eligibility milestones look like, where the desk has seen chains break, and what to confirm before sharing at scale. The two surfaces are written to be read together. The screen is the contract. The editorial is the explanation behind the contract.
When the screen is silent on a specific condition, the next place to read is the wallet KYC page, which carries the verification chain that backs the code. When the wallet page is silent, the next place is the state eligibility page, which lists the permitted and restricted states as of the last refresh. When all three are silent, the chain has either been rewarded or it has expired, and a one-line enquiry to customer care resolves the open question in most cases.
What changes when the next cycle opens
Two things move on a fresh operator cycle: the cap and the validity window. The cap can move up, down, or stay flat. The validity window can shrink, lengthen, or stay flat. A reader who has run the six checks at sign-up day should re-run the third and the fifth checks at the start of every new monthly cycle, because the cap and the validity window are the two fields most likely to have changed.
The single watch the desk keeps is the reward status chip on the Refer & Earn screen. A reward that has sat in pending for more than seventy-two hours is almost always stalled on the referee's KYC step, not on a chain failure. A reward that has sat in pending for more than seven days is worth a customer care ticket, with the referrer's user ID and the referee's phone number at the top of the message.
The implication is straightforward. The verification loop is six checks before the first share, one daily audit until the referee clears both gates, and a customer care ticket if the chain stays pending beyond a week. The reader who treats the loop as a habit rather than a checklist will not have to relearn it on the next monthly cycle, because the loop survives the cycle changes. The reader who treats it as a one-time event will relearn it every time.