Refer code, what the share sheet shows
A refer code is a short identifier that links a new reader's sign-up to the referrer's account. This page explains what the share sheet shows and what the receiving reader should expect.
What a refer code is
A refer code is a short identifier (usually 6 to 12 characters) that the platform uses to attribute a new reader's sign-up to an existing referrer's account. The receiving reader types the code during sign-up; the platform credits the referrer and may apply a small welcome bonus to the new reader.
The code itself is a string, not a link. Some platforms generate a share link that includes the code; the share link is the same code wrapped in a URL. A reader who receives a code should be able to type it into a "refer code" field on the sign-up screen without following a link.
What the code does
The code does three things. (1) It attributes the new reader to the referrer for accounting. (2) It may apply a welcome bonus to the new reader, a small practice-table credit, a deposit bonus or a free entry. (3) It may apply a credit to the referrer when the new reader reaches a milestone.
The terms of any welcome bonus should be visible before the new reader signs up. A platform that hides the terms behind a confirmation screen is making the welcome bonus harder to evaluate.
What the share sheet shows
Most platforms expose a share sheet that includes the refer code and a short message. A serious share sheet lets the reader edit the message and choose the channel; a marketing share sheet sends the message unedited and pushes a single channel.
A reader who receives a code
A reader who receives a refer code from a friend should treat it as a small, optional gesture. The code does not change the rule references on Boomerang or the verification questions on the safety page. The reader who decides to use the code should still run the verification checklist before depositing.
Read the safety checklist
A welcome bonus does not change the verification checklist. Run the four-step checklist before any first deposit.
How a refer code is usually formatted
Refer codes are typically a short alphanumeric string (six to twelve characters) that is unique to the inviting reader and tied to the platform's referral engine. The code is usually embedded in the share link as a query parameter (for example, ?ref=ABC123) so the platform can attribute the new account to the inviting reader at the moment of sign-up. Boomerang's editorial standard is to treat the code as an attribution tag, not as a credential; the code does not give the inviting reader access to the new reader's account, and it does not give the new reader any special access to the platform beyond the published bonus.
Some platforms issue a refer code that is unique to the inviting reader and reusable across multiple invites. Other platforms issue a single-use code that can only be redeemed once. The share sheet on the platform typically tells the reader which type of code they hold; a reader who is unsure can check the platform's own help page or contact customer support before sharing the code.
What a reader who receives a code should do
A reader who receives a refer code from a friend, a family member, or a Telegram group should treat it as a small, optional gesture. The code does not change the rule references on Boomerang, the verification questions on the safety page, or the responsible-play guidance on the limits page. The reader who decides to use the code should still run the four-step verification checklist before depositing, and should still set deposit limits and session-time caps on day one.
The code does, in most cases, entitle the new reader to a small welcome bonus (a deposit match, free tournament tickets, or a small balance credit). Boomerang's editorial standard is to treat the welcome bonus as a small, time-limited marketing gesture, not as a reason to deposit more than the reader intended. A reader who would not have deposited without the code should think carefully about whether the welcome bonus changes their decision; the verification checklist applies regardless.
What a reader who sends a code should do
A reader who shares their refer code is publicly associating themselves with the platform's marketing. Boomerang's editorial standard is to share a code only through channels where the receiver has explicitly asked to receive it, and to include a short, accurate message about why the reader is sharing the code. Sharing the code unsolicited, or in a channel where the receiver has not asked to receive it, is poor form and may violate the platform's own referral terms.
The inviting reader is also responsible for the message they attach to the share. Some platforms let the inviting reader edit the share message; a reader who edits the message should keep it honest and should not promise any outcome that the platform's documentation does not back up. A reader who has been promised an outcome by a sender should verify that promise against the platform's own help page before signing up.
How a refer code differs from a bonus code
A refer code and a bonus code are typically two different things. A refer code is tied to an inviting reader and usually entitles both parties to a small bonus when the new reader signs up. A bonus code is a marketing code that the platform issues directly (often during a seasonal promotion) and that any reader can apply at sign-up or at deposit. The two codes are sometimes combined into a single share sheet, but they remain logically distinct: a refer code attributes the new account to the inviting reader, while a bonus code attributes the new account to a marketing campaign.
Boomerang's editorial standard is to keep the two codes on separate routes. The /refer-code/ page covers refer codes specifically, and the /bonus-code/ page covers bonus codes specifically. A reader who has both should read both pages; the verification checklist on the safety page applies to either type of code.
When a welcome bonus is not worth using
There are situations where the right answer is to skip the welcome bonus. A welcome bonus that requires a deposit the reader would not otherwise make is not a bonus; it is a marketing nudge. A welcome bonus tied to a turnover multiplier the reader cannot realistically meet is not a bonus either; it is a lock-in. A welcome bonus that the platform will only honour if the reader keeps playing for thirty days is a commitment the reader should think twice about.
Boomerang's editorial standard is to read the welcome-bonus terms carefully before using any code. The platform's own help page lists the bonus terms, and a reader who finds the terms hard to meet is entitled to skip the bonus and sign up without a code. The verification checklist on the safety page applies regardless of whether the reader uses a code or not.
How the code credits the sender
When a new reader signs up using a refer code, the platform's referral engine credits the inviting reader with a small bonus (a deposit match, free tournament tickets, or a small balance credit). The credit is automatic; the inviting reader does not need to claim it. Boomerang's editorial standard is to think of the credit as a marketing gesture from the platform to both readers, not as a payment from the new reader to the inviting reader.
A reader who is unsure whether a credit has been applied can check the inviting reader's account history. Most platforms list the credit on the inviting reader's transaction history with a date stamp and the new reader's account name (or a pseudonym, depending on the platform's privacy policy). A reader who finds that the credit has not been applied can contact the platform's customer-care channel and ask for a manual review.
A reader who is uncomfortable with the referral mechanism can choose not to use a refer code at sign-up. Most platforms allow the reader to skip the refer-code field, and the new reader will not lose any feature or functionality by skipping it. Boomerang's editorial standard is to support readers who choose to use a refer code and readers who choose not to, and the verification checklist on the safety page applies regardless of the reader's choice.
When a sender pushes codes aggressively
Some refer-code senders are aggressive in their outreach, posting the code in Telegram groups, on social media, or in comments sections of unrelated sites. Boomerang's editorial standard is to think of this kind of outreach as poor form at best and as spam at worst, regardless of whether the platform's referral terms allow it. A reader who receives a code through an unsolicited channel is entitled to ignore the code without responding to the sender.
A sender who pushes codes aggressively is often more interested in the credit than in the receiver's experience. The receiver's verification checklist still applies; a code that arrives through an unsolicited channel does not bypass the platform's verification flow, and the receiver should run the checklist before depositing. Boomerang's editorial standard is to apply the same checklist to every code, regardless of how the code was delivered.
A reader who is being spammed with codes by a particular sender can block the sender on the channel where the spam is occurring. Most messaging apps and social-media platforms have block controls that prevent the sender from reaching the reader again. Boomerang's editorial standard is to remind the reader that the block control is the reader's, and a reader who uses it is not being rude; the reader is enforcing a reasonable boundary.
Code anatomy
Reading a refer code, line by line, before sharing it
A refer code is a short string of characters with a small contract attached to it. The notes below walk through the contract line by line, in the order the terms tend to surface.
The code itself
The refer code is the alphanumeric string the reader shares with a friend. Codes are typically between 6 and 12 characters, case-insensitive, and may include dashes for readability. The code identifies the referrer, not the referee; the platform matches the referee to the referrer's account at the moment the referee signs up or makes the qualifying deposit. Codes that are valid for one platform are not valid for any other platform; treating a code as portable is the single most common refer-code mistake.
Who qualifies as the referee
The referee is the new account the code is applied to. Most platforms specify the qualifier: a new account with no prior deposit, a new account using a specific instrument, a new account opening during a specific calendar window. The qualifier is what turns a refer code into a refer offer; without it, the code is a stray string. A reader who shares a code without naming the qualifier sets their friend up to fail the contract silently.
What the referrer receives
The referrer's reward is what the referrer receives when the referee clears the qualifier. The reward is typically a flat bonus, a percentage of the referee's first deposit, a free entry into a contest, or a one-off platform credit. The reward usually carries its own wagering requirement and its own expiry window, both of which are listed in the offer document rather than in the code's share sheet. Read the offer document before sharing the code, not after the referee has signed up.
What the referee receives
The referee's reward is what the friend receives at sign-up or first deposit. The referee's reward is typically the same as the referrer's, or a different smaller bonus. The referee and the referrer are both bound by the offer document, even though only the referee reads it on the platform's offer page. The referee who accepts the offer without reading the document has the same forfeiture risk as the referrer who shares the code without reading it.
The wagering multiplier on the rewards
Both rewards carry a wagering multiplier. The multiplier on the referee's reward is usually the same as a first-deposit match; the multiplier on the referrer's reward is sometimes lower (because the referrer is already a customer). The multiplier is what turns a refer code into a refer offer; without it, the rewards are credits that cannot be withdrawn. Read the multiplier on both sides before either side commits.
The expiry window
The expiry window on a refer reward is typically shorter than on a first-deposit match. Most platforms apply between 7 and 30 days from the moment the reward is credited. The referee's expiry starts at first deposit; the referrer's expiry starts when the referee clears the qualifier. If either side misses the window, the unconverted portion is forfeited silently. Treat the expiry window as a deadline, not a horizon.
The maximum referrer reward
Most platforms cap the referrer's total reward at a specific number of successful referees (commonly 5 to 20 over a calendar year) or at a specific total bonus amount. The cap is rarely published on the share sheet itself; it is in the terms linked from the share sheet. A reader who shares the code widely without reading the cap will end up claiming offers that are technically valid but that the platform will not credit past the cap.
The state exclusion list
On Indian platforms, the state exclusion list applies to refer codes as much as it applies to first-deposit matches. A referee in an excluded state who signs up using the refer code will, on most platforms, void both rewards at the moment of withdrawal. The right reader posture is to confirm the referee's state before sharing the code, not at the moment of dispute.
Sharing a code as a contract
The fastest way to think about a refer code is as a contract the reader is offering to a friend. The reader is offering the friend a path into a platform with a small attached bonus; both sides are bound by the terms. A code shared carelessly is not a free gift; it is a contract the reader is committing the friend to without the friend having read it. The editorial standard is to share the offer document alongside the code, so the friend can accept or decline informed.
Anti-spam posture
Receiving codes, evaluating them, and responding without pressure
Most readers receive refer codes in two forms: codes a friend has chosen to share, and codes that arrive unsolicited through messaging apps, social-media DMs, or sponsored posts. The four notes below describe the right response shape to each.
A code from a friend
A code from a friend is normally welcomed and accepted, but only after the friend has shared the offer document alongside the code. The reader's response should be to read the offer document, confirm the state exclusion list, and confirm the qualifying deposit for the referee's reward. If the friend has shared the code without the offer document, the right move is to ask for it rather than to accept the code blindly.
A code from an unsolicited sender
A code from an unsolicited sender (a stranger messaging on a social platform, a sponsored DM, an email from an unknown sender) should be declined by default. The exception is when the sender is a verified platform representative offering the reader a code by name; in that case, the reader should still ask for the offer document before entering the code. Most unsolicited codes are bait for an illegitimate offer that does not exist on the platform the code names.
Repeated codes from the same sender
Repeated codes from the same sender, in the reader's messaging app or social platform, are a sign that the sender is automated. The right response is to block the sender on the platform where the codes are arriving, not to respond to the codes. The reader is not being rude by blocking; the reader is enforcing a reasonable boundary. Boomerang's editorial standard is to remind readers that the block control is theirs.
A code with the same string on multiple platforms
Some short codes (typically 4 to 6 characters) collide between platforms. The right response when a reader sees a code that they recognise from a different platform is to ask the sender which platform the code is for, and to confirm the code on the platform's offer page before entering it. Entering a code on the wrong platform does not produce an error message; it produces a no-op, and the reader then enters the correct code without realising the first one was registered.
Frequently asked questions
Refer-code questions readers actually send
Phrasing paraphrased from real correspondence; the underlying answers are the ones the editorial team has heard back from operators in the same exchange.
I shared my code but the bonus never appeared on my friend's account. What now?
Three usual reasons. First, the friend may not have entered the code at the right moment (typically a specific field on the cashier screen, not the sign-up form). Second, the friend may have been in an excluded state at the moment of sign-up. Third, the friend's deposit may have been below the qualifying threshold for the refer offer. Ask the friend to re-check those three points; if the bonus still does not appear, escalate via the contact form with both account references.
Can I share my code on a public forum?
Yes, on most platforms, although the maximum-referrer cap applies regardless of how the code is shared. Sharing on a public forum does not invalidate the code; it does mean the reader's cap may be reached faster than expected. The right reader posture is to share publicly only if the reader is happy to receive the maximum reward early in the year and forfeit the rest of the year's referral bonuses to cap-out.
Does a code expire?
The code itself does not expire on most platforms; the rewards it generates do. A code shared years ago may still match a new referee, but the offer document at the time of the match determines the reward and the wagering requirement, not the offer document at the time the code was originally issued. A reader who has a code stored in a message thread from years ago should confirm the current terms before sharing it again.
Can I have more than one active code on my account?
Most platforms allow only one active refer offer at a time. A reader who enters a second code (or accepts a second offer) usually forfeits the unconverted portion of the first, mirroring the stacking rule that applies to first-deposit matches. The right reader response is to clear the first offer first, withdraw the cash portion, and only then accept the second code.