Why You Should Treat Referral Rewards as Two Separate Stages

Nearly every mainstream AI platform (OpenAI, Anthropic, Mistral, Perplexity, the AI services inside major cloud providers, and aggregators like OpenRouter) pays referrals in two stages, not one:

  • Stage 1 (first-touch reward): when the invitee registers, verifies email, or makes a first payment, the inviter receives a credit/voucher/token grant almost immediately.
  • Stage 2 (retention reward): when the invitee is still paying roughly 30 days later, or hits a usage/spend threshold, the inviter receives a second grant.

Most people only chase Stage 1, end up with a pile of one-off credits, and lose almost all Stage 2 rewards. Running the two stages separately is what turns referral programs into a steady Token supply.

> Note: the ratio, threshold, and settlement window differ a lot between platforms. Always check the "Referral / Invite / Affiliate" page in your own dashboard. This article deliberately avoids hard-coding any numbers.

Steps

Step 1: Write down the two-stage rules first

Open the platform's referral page (often labeled Referral, Invite friends, Affiliate, or Partners) and record:

  1. Stage 1 trigger: registration or first payment? Is there a minimum top-up?
  2. Stage 2 trigger: renewal or usage threshold? What is the observation window (commonly 30/60/90 days)?
  3. Reward form: API credits, platform points, or a voucher locked to subscriptions? Can it be converted into Token usage?
  4. Expiry: do the rewards expire (commonly 30–90 days)?
  5. Caps: how many valid referrals can one account earn per month/year?

Put this into a single table. Every later action references it.

Step 2: Tier your invite codes

Don't blast one code in every group. Tier by "will this invitee survive to Stage 2":

  • Tier A (high retention): colleagues, classmates, people already using similar tools. They will likely renew after the first payment, so Stage 2 is the most reliable. Give them a dedicated code so you can track them.
  • Tier B (medium): people in tech communities, Discord/Slack, who actively ask "is there free credit?". When you hand over a code, state the first-payment threshold and the renewal timing — this noticeably raises the Stage 2 hit rate.
  • Tier C (low retention): one-off public drops. Only count Stage 1 for these; don't put Stage 2 in your forecast.

Platforms usually give each inviter a unique code or a link that can generate several. If tagging/notes are supported, label everything A/B/C.

Step 3: Turn "first-payment reminders" into a fixed routine

Stage 2 most often fails because the invitee simply doesn't know they need to renew or keep using the product. So:

  • Remind them on day 3 and day 25 after registration (day 25 is to land before the observation window closes).
  • The reminder should focus on what *they* get (their own credits, unlocked features), and mention in passing that you also earn a referral reward.
  • If the platform allows it, record their renewal deadline next to your Stage 2 settlement date.

Step 4: Build a reconciliation sheet

Check the dashboard on a fixed weekly cadence:

| Invitee | Signup date | Stage 1 paid? | Window ends | Stage 2 paid? |

| --- | --- | --- | --- | --- |

| A-1 | … | Y/N | … | Y/N |

For anyone where Stage 1 landed but Stage 2 didn't, check whether they stopped using the product or never hit the renewal threshold. That list becomes your priority follow-up group.

Step 5: Spend earned credits by expiry date

Referral credits usually expire. Spend order: soonest expiry first. Tag every grant with its expiry date in your dashboard or ledger so hard-won credits don't silently lapse.

Caveats

  • No self-referral: mass-registering with the same payment method, device, or IP to farm referrals is almost always caught by risk controls. Best case the reward is denied; worst case the account is banned. Don't do it.
  • Rules change: referral ratios and thresholds shift frequently. Read today's official terms before acting; don't rely on a screenshot from months ago.
  • Stage 2 is never guaranteed: whether an invitee renews is ultimately their decision. You can only raise the probability.
  • Tax and compliance: on some platforms referral rewards are withdrawable income and may trigger reporting above a threshold. Follow your local rules.
  • Don't spam codes: most communities ban it, and platforms may flag your account.

When This Applies

  • Solo developers who want referral rewards to cover part of their API costs.
  • Small teams running A/B/C tiered drops together to pool referral rewards into a shared Token budget.
  • Community organizers who make "help newcomers get their first month of credit" a routine service, while earning referral rewards along the way.

Common Mistakes

  1. Chasing signups, ignoring retention: you bank Stage 1 and lose all of Stage 2 — real returns can be half of what you expected.
  2. Treating all credits as the same: subscription vouchers often can't be used for API calls. Check before planning.
  3. Remembering credits only when they're about to expire: referral credit validity is often shorter than you think.