How it works

How a referral code benefits both sides

A referral code triggers a bonus for both the referrer and the referee. The exact benefits depend on the operator’s terms.

The referrer receives a bonus when the referee meets the eligibility criteria (typically: signs up, completes KYC, makes a first deposit, plays through the bonus amount). The referee receives a welcome offer that may include a deposit match, contest credits, or a free entry.

The picks desk does not run a referral programme. We are an editorial desk. Our coverage of referral codes is informational — we link to the operator’s official site for the verified terms.

Eligibility

Who can use a referral code

Referral codes are usually limited to new accounts, accounts in eligible states, and accounts that meet the operator’s KYC requirements.

01

New accounts

Referral codes are usually limited to new accounts. You cannot refer yourself.

02

Eligible states

The referee must be in an eligible state. The operator’s eligibility page lists the states.

03

KYC completion

KYC is usually required before the bonus is paid. The referee must complete KYC.

04

First deposit

Most operators require a first deposit (if applicable) before the bonus is paid.

05

Bonus terms

The bonus may be withdrawable or contest credits with a wagering requirement. Read the terms.

A user sharing their referral code
Share responsibly

How to share your referral code responsibly

A referral works best when both sides benefit honestly. Share with people who actually play, not with strangers. Never share in exchange for cash or in violation of the operator’s terms.

The best place to share your code is with friends who already play fantasy cricket and have asked for your recommendation. Most operators forbid sharing codes publicly in exchange for compensation — read the referral terms before posting your code on social media.

The editorial desk does not run a referral programme. We do not benefit from your referrals and we do not solicit them. Our editorial picks coverage is independent of the operator’s referral programme.

Referral walkthrough →
Tips

Five tips for sharing your code

The five tips below are the standard patterns for sharing a referral code responsibly.

Share with people who play

Friends, family, and colleagues who already play fantasy cricket are the right audience. Avoid sharing with strangers.

Read the operator’s terms

Most operators forbid sharing in exchange for compensation. Read the terms before posting your code publicly.

Avoid spam

Posting your code in unrelated forums or comment sections is usually considered spam. The operator may disable your code.

Track your referrals

Most operators show your referral activity in the app. Track it to make sure your code is being used correctly.

Escalate issues

If a referral bonus is not paid correctly, contact customer care on the verified channel with the referee’s account ID.

Referral conditions and eligibility rules under review
Rule source

Begin with the current written rules

For fantasy referral programmes, the operator’s own current instructions must outrank screenshots, social posts, and memory. Read the exact language for eligibility, code attribution, reward timing, expiry, and responsible sharing, then record the date. Product rules, limits, and scoring bands can change without matching an older explainer.

If a condition affects identity, deposits, rewards, entry, or withdrawals, verify on the operator’s official site. We have not independently verified operator-specific values unless a dated source is stated. Do not treat a typical industry practice as a promise.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Referral code shared responsibly from a mobile phone
Before acting

Complete a five-minute pre-action check

Confirm the verified domain, the account name, current eligibility, and the exact action you intend to take. For fantasy referral programmes, decide in advance what a successful outcome should look like and where the confirmation will appear.

Save non-sensitive evidence such as a transaction ID, rules timestamp, or ticket number. Never save an OTP, password, full card number, or unmasked identity document in casual notes. Good records help without creating a second security risk.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Support response used to verify referral status
Worked scenario

Use a small scenario before committing

Imagine a picker facing fantasy referral programmes for the first time. The sensible route is to use the operator’s current referral screen, written terms, account status, and verified support, test the smallest practical action where relevant, and stop if any detail conflicts with the published rules. A small test exposes process problems before they become expensive.

The decision is not whether the interface looks polished. It is whether whether a referral is valid for both people before either acts. When evidence is incomplete, pause and ask verified support for a written answer instead of filling the gap with an assumption.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Analyst comparing fantasy cricket roles and recent match evidence
Timing and status

Separate normal processing from a real problem

Many account actions move through several states: submitted, under review, accepted, processed, and completed. A status still inside the operator’s published window is different from a rejected or reversed action. Track the stage before sending repeated requests.

If the published window passes, send one clear ticket containing the account identifier, timestamp, transaction or contest reference, and a concise description. Repeated attempts can create duplicate cases and make the timeline harder to reconstruct.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Cost and risk

Count the full downside, not only the visible amount

The visible fee or credit cost is only one part of fantasy referral programmes. Also consider time, locked funds, missed deadlines, variance, identity exposure, and the possibility that an offer or contest condition changes the usable value.

Set a fixed limit before the event. A limit chosen after a loss is usually not a limit; it is a reaction. Never borrow to participate, never chase a result, and take a break if the activity creates stress or secrecy.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Evidence file

Keep a clean record without oversharing

Useful records include dates, rule versions, non-sensitive screenshots, ticket numbers, and the exact wording of a support reply. They help distinguish a product issue from user error and support a focused escalation.

EvidenceCheck recency and source.
OpportunityTranslate the update into volume.
RiskWrite what could invalidate it.

Redact PAN, Aadhaar, bank details, addresses, QR codes, and balances before sharing any image. Verified support should not ask for a password or OTP. A request for either is a reason to stop the conversation.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Support path

Escalate through verified channels

Use contact details shown inside the signed-in product or on the operator’s official site. Explain fantasy referral programmes in chronological order and state the resolution requested. A short factual ticket is easier to investigate than several emotional messages.

If the first answer does not address the evidence, reply within the same case and ask for the relevant rule or status. Avoid numbers copied from search listings. We have not independently verified third-party support contacts.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Referral FAQ

Six questions about referral codes

Plain answers to recurring referral questions.

No. Most operators explicitly forbid self-referrals. Attempting to refer yourself usually results in both accounts being flagged.

Most operators do not publish a cap, but the referral terms describe any limits. Read the terms before running a large referral campaign.

Typically when the referee completes KYC and makes their first deposit (if applicable). The bonus may take 24-72 hours to appear.

It depends on the operator’s terms. Some bonuses are withdrawable, others are contest credits with a wagering requirement.

Only if the operator accepts players from that state. The referee’s account must meet the operator’s eligibility rules.

Contact customer care through the verified channel. The code may have been disabled if you violated the referral terms.

Read the responsible-play stance

Referral codes are a tool, not a guarantee. Read the responsible-play page before you opt in.

Responsible play
Sign in Get Started