Bitunix Self-Referral Rules: Independent Users vs Controlled Accounts

A referral code does not decide by itself whether a Bitunix relationship is legitimate. The central question is whether the invited account belongs to and is controlled by an independent user who supplies their own funds and makes their own trading decisions. If the inviter creates or effectively controls another account to generate rewards, the arrangement is not the ordinary “invite a friend” model.

Bitunix’s public invitation FAQ says that inviting yourself, using multiple accounts, or inviting from the same device is not allowed and may cause rewards not to be issued. Its Market Conduct, Account Integrity, and Enforcement Rulebook goes further: accounts may be assessed collectively when ownership, control, beneficial interest, trading behavior, funding arrangements, devices, networks, or another relevant relationship connects them.

This guide is based on the official referral-rebate instructions, invitation FAQ, account-integrity rulebook, and campaign terms checked on October 14, 2026. Regional campaigns and account offers can differ. The Bitunix exchange page provides the general service overview, while the guides index separates other user questions.

Use independence, not names, as the first test

The intended referral pattern is straightforward. User A shares an official Bitunix link or code with an independent friend, User B. B registers through that link, owns the account, funds it, and decides how and whether to trade. The official app route is Profile icon → Referrals → Invite Now. The user can share a link, code, poster, or QR from that area.

A self-referral pattern is different. A creates, owns, finances, or operates B’s account so that A can collect a referral reward generated by activity A controls. A different email address or registered name does not establish independence if the same person has the beneficial interest or operational control.

The public rules support the following decision matrix:

Family, employee, or corporate relationships need particular care. The public documents do not say that every relative is automatically prohibited. They also do not say that separate names automatically make related users eligible. Ownership, funds, control, decision-making, devices, and networks may all matter. The prudent route is a truthful pre-trade support inquiry, not an assumption.

Referral binding happens during registration

The public invite page states that the code must be entered when the friend registers and that a referral relationship cannot be added afterward. The detailed referral guide similarly says that an invitee’s channel cannot be changed after registration unless the person registers a new account, and the invitee’s rebate ratio cannot be modified after registration.

One FAQ says a user may delete an account and register again through the desired channel. That answer must be read together with the multiple-account and self-invitation restrictions. It is not permission to keep parallel accounts, invite yourself, conceal control, or bypass compliance restrictions.

If a legitimate channel correction is necessary, first ask support about account-deletion completion, balances, open orders, identity-verification records, and eligibility to register again. Do not create the replacement while the old account is still active unless Bitunix has explicitly directed that process.

The Referrals page also allows an inviter to use Add Link and select a rebate split within the permitted range. The official guide says up to 20 referral-rebate links can be created. Multiple links are campaign-management tools for genuine invitees; they do not authorize one operator to populate those links with accounts under the operator’s control.

Approved referral or affiliate cashback is not the same as self-referral

Under the ordinary Referral Rebates program, an independent friend registers through the exclusive link or code and completes fee-bearing eligible trades. The inviter then receives a percentage of the friend’s trading fees. The official guide says the referral-rebate benefit is valid for one year and can arise from both spot and futures trades that incur a fee. Deposits and withdrawals do not generate this trading-fee commission.

A separate Affiliate Program is an approved business relationship. Possessing a consumer referral code does not automatically grant affiliate-contract rights, rates, regions, or marketing permissions. An affiliate or cashback operator must follow the approved agreement, permitted channels, local scope, payout basis, and customer-share terms.

That distinction is important for a cashback service. Returning part of a verified commission to a genuinely independent customer under an approved link or contract is structurally different from placing accounts controlled by the operator under the operator’s own referral tree. The first can fit an authorized referral arrangement; the second creates self-referral and account-integrity concerns.

The arithmetic is simple, but eligibility comes first:

Referral rebate = invitee’s eligible trading fee × rebate percentage applied to the link or account

Bitunix’s own help article uses an example in which a trading fee of 100 and a 3% rebate rate produce a rebate of 3 on the following day. If the link includes an allowed friend split, the division must follow the terms displayed for that link. An operator should not advertise an invented fixed rebate that differs from the live link or affiliate agreement.

The ordinary referral guide and a separate affiliate article can also use different validity or commission language. Do not transfer an affiliate-contract claim to a consumer referral link, or vice versa. The dashboard and signed agreement applicable to the specific account control.

Connected accounts can be reviewed as one arrangement

The account-integrity rulebook says each account is intended to represent an independent user conducting genuine trading activity. It prohibits creating, acquiring, controlling, or operating multiple accounts to circumvent eligibility rules, platform restrictions, compliance measures, or risk controls. It also prohibits paired, mirrored, offsetting, or complementary structures designed to remove genuine exposure, transfer value, or manipulate platform operation.

Bitunix may consider accounts collectively when it reasonably believes they are connected through ownership, control, beneficial interest, trading behavior, funding, devices, networks, or another relevant relationship. That is a substance-based review. It is not a checklist showing which single technical signal must be changed.

Trying to hide the connection with different networks, borrowed identities, or altered funding paths can add misrepresentation or circumvention problems. The rulebook expressly prohibits false, misleading, or incomplete information and concealing account ownership or relationships.

Promotion rules have the same substance. Campaigns, bonuses, rebates, and referral programs are meant to reward genuine participation. Artificial trading, coordinated participation, repetitive structures, reward farming, and artificial qualification can be disregarded, and related benefits can be refused, canceled, adjusted, or recovered.

The rulebook states that monitoring can include orders, cancellations, account activity, trading behavior, funding activity, campaign participation, device information, and blockchain transactions. Internal surveillance methods are not promised to users. The correct compliance response is to preserve evidence of legitimate independence, not to seek a method that avoids detection.

Diagnose a missing rebate without creating another account

Step 1: verify the registration link. Open Referral Records and confirm that the invitee is bound to the expected link. Because binding cannot be added after registration, later trading does not repair a missing registration relationship.

Step 2: verify a fee-bearing trade. The referral guide says deposits and withdrawals do not create commission. Match an actual spot or futures fill that charged a trading fee.

Step 3: use the correct settlement window. The guide says commission is credited the next morning to the Spot account and can be found as Trading Rebate in Funds Details or Rebate History. Set the date filter to include the relevant trading and settlement dates.

Step 4: separate the ordinary referral rebate from a campaign bonus. A regional campaign can have its own deposit, volume, claim, redemption, and expiry conditions. If the activity page is not available to the account, do not assume eligibility from a screenshot or another region’s page.

Step 5: document independence. Record the legal account owner, source of funds, device owner, person making trading decisions, API or operating authority, and beneficial owner of profits. If one person controls both sides, the evidence does not support an ordinary friend referral.

Step 6: if rewards are held or an account is restricted, use the designated support and review route. Provide Referral Records, Rebate History, order IDs, funding evidence, and a truthful explanation of the relationship. Do not open another account to bypass the review.

A useful support packet contains:

• inviter UID and invitee UID;
• the referral link or code and registration time;
• the fee-bearing order ID and its trading fee;
• the expected settlement date and Rebate History range;
• the campaign page, if a separate campaign is claimed;
• a clear ownership, funding, control, and trading-decision statement.

This packet identifies whether the problem is binding, fee eligibility, settlement timing, campaign scope, or account-integrity review.

What enforcement can affect rewards and accounts

The rulebook lists a range of measures: warnings, enhanced monitoring, campaign disqualification, reward cancellation or recovery, transaction adjustment, removal of improperly obtained benefits, service restrictions, account suspension or closure, and refusal of future platform access. Measures can be combined depending on the circumstances.

The invitation campaign terms separately state that fraud, duplicate registration, multiple accounts, self-trading, or other abnormal behavior used to manipulate rewards can lead to termination or cancellation of rewards, revocation of rewards already issued, freezing of involved accounts, and other action.

A rebate that has appeared in an account is therefore not insulated from review if the underlying behavior is found abusive. The rulebook says a user has no vested right to retain rewards, rebates, bonuses, or benefits obtained through conduct inconsistent with the rules.

The lowest-risk operating policy is simple:

1. Invite only genuinely independent users.
2. Explain the link and displayed split before registration.
3. Do not place yourself or accounts you control under your referral tree.
4. Treat family, employee, and entity relationships as cases requiring disclosure.
5. Keep affiliate approval, permitted-channel, and settlement records.
6. Use support and review procedures instead of creating workaround accounts.

Frequently Asked Questions

Is inviting a family member automatically self-referral?

The public documents do not make family status alone an automatic answer. However, connected ownership, control, beneficial interest, funding, devices, networks, or trading behavior can cause accounts to be reviewed together. Disclose the relationship and request guidance before funding or trading.

Can an invitation code be added after an account is already registered?

No. The public invitation FAQ says referral binding must occur during registration and cannot be added afterward. If a channel correction requires deletion and re-registration, confirm the permitted process with support and do not use it to maintain multiple accounts or invite yourself.

Is cashback through an approved affiliate link self-referral?

Not when a genuinely independent new customer joins through an approved referral or affiliate arrangement and the benefit is distributed under the applicable terms. The operator still needs proof of approval, scope, region, link terms, and settlement basis.

Can two accounts use the same device?

The public invitation FAQ specifically groups same-device invitations with self-invitation and multiple-account behavior as not allowed. Do not attempt to disguise the relationship. If a legitimate shared-device situation exists, obtain written guidance from Bitunix before use.