How long does a referral reward take to credit?

It is not a fixed waiting period — it depends entirely on your invitee. The reward pays when they reach the redeem unlock, which counts days they were actually active rather than days since they joined. Someone using the app daily reaches it quickly; someone who installed and drifted may never reach it at all.

My friend entered the code but nothing happened. Can support add it manually?

If the attribution window had already closed, no. The rule is enforced at signup in the data itself, which is what stops established accounts being farmed for referral credit, so there is no manual override. If the code was entered in time and the invite shows as pending, nothing needs adding — it is already attributed and waiting.

Does reinstalling the app let me use a referral code again?

No. Signing back in with the same Google account returns the same user record, including its original referral history, and an account can be referred only once ever. Reinstalling changes nothing.

I referred my family member on our shared phone and it was rejected. What now?

This is the one case in this list worth raising with support, because shared-device signals are how self-referral is detected and a genuine shared household looks identical to fraud from the data alone. Contact support with both accounts identifiable and explain the situation.

Referral Reward Not Credited? 6 Reasons, and Which Ones You Can Fix

Your friend installed the app, entered your code, and nothing arrived. Here is what is really happening — and being honest, most of it is not fixable after the fact.

You invited someone, they joined, and the reward never appeared. Before assuming the app is refusing to pay, it is worth knowing that referral systems fail in a small number of very specific mechanical ways — and that most of them are decided in the first day, long before you noticed anything was wrong.

Here they are in rough order of how often each is the answer.

1. The reward is pending, not missing

This is the most common answer by a wide margin. A well-designed referral does not pay when someone signs up — it pays when they reach the redeem unlock, which requires being genuinely active on a set number of separate days.

Until then the referral sits in a pending state. It is recorded, it is attributed to you, and it will pay the moment the condition is met. Your referral screen shows pending invites separately from paid ones for exactly this reason. If your invite is listed as pending, nothing has gone wrong and there is nothing to do except wait for them to keep using the app.

2. Your friend counted calendar days, not active days

A closely related trap. The unlock counts days on which the account was actually used, not days since signup. Someone who installs the app, opens it once, and comes back a week later has one active day, not seven.

This is the single biggest reason a referral stays pending far longer than either side expects. If your invite is stuck, the useful message to send is not "have you got my reward" but "open the app today" — each separate day they show up moves the counter by one.

3. The code was entered too late

Referral codes attach only to genuinely fresh accounts, typically within about a day of signup. After that window closes, the code is refused.

The reason is defensive rather than mean: without a window, anyone could paste a code into a long-established account and mint referral credit from users who were never referred by anybody. Because the rule is enforced in the data at signup, this one cannot be fixed afterwards — not by support, not by re-entering the code, not by your friend reinstalling.

The practical takeaway for next time: send the code with the invite, and tell the person to enter it during signup rather than "later".

4. The account had already been referred

An account can be referred exactly once in its lifetime. If your friend previously joined through somebody else's code — even months ago, even if they forgot — your code will not attach.

The same rule catches reinstalls. Deleting the app and installing it again does not create a new account; signing back in with the same Google account returns the same user, still carrying its original referral record. There is no reinstall loop.

5. It was flagged as self-referral or same-device

Referring your own second account is refused directly. Beyond that, referral systems watch for patterns that look like one person operating both sides — the same device, the same network, accounts created minutes apart, or an invitee whose activity mirrors the referrer's.

If you genuinely share a household or a phone with the person you invited, this can catch you unfairly. That is the one case in this list where contacting support is worth it, because a human can look at the accounts and see two real people. Have both accounts ready to identify.

6. They installed from a link but never entered the code

Worth checking before anything else, because it is embarrassingly common. Sharing a link is not the same as the code being applied — if the person went to the store, searched for the app manually, and signed up without pasting anything, there is no attribution at all. Nothing was recorded, so nothing is pending.

Ask them directly whether they typed or pasted a code during signup. If they cannot remember seeing the field, they probably skipped it, and the window described above has likely closed.

What to do now

Open your referral screen and find which state the invite is in. If it says pending, the answer is cause 1 or 2 and the fix is your friend opening the app on more separate days. If the invite is not listed at all, the code never attached — causes 3, 4 or 6 — and it cannot be recovered, though your next invite can be done correctly. Only if the invite is listed and rejected is support worth contacting.

For how these programmes are structured and what separates a fair one from a pyramid, see refer and earn apps in India. If it is not referrals but ordinary earnings that have gone missing, points not credited covers that path instead.