Toobit Referrals: UID Attribution and Customer Registration

What should a useful Toobit attribution confirmation actually establish?

Separate the registration route, exchange attribution and customer settlement registration. Ask for the covered account, products and effective date if the response leaves those points unresolved.

Choose the correct enquiry for your situation

If you saved the signup code, state the date and code and ask which introducer relationship is currently recorded for the UID. If you have no signup record, disclose that limitation and ask for the existing status. If support confirms another relationship, do not conceal the answer and start again through a different link.

Here is a hypothetical example, not a verified customer case. An intended code was visible during registration, but the customer never completed TradePayback settlement registration. The exchange later confirms the account's attribution. That resolves one question, while the customer still needs confirmation of settlement registration, effective date and eligible activity. Creating another exchange account would not answer those outstanding questions.

A useful message is: “Please confirm the current referral or affiliate attribution for UID [identifier]. I registered on [date] using [known route]. If the intended relationship is not recorded, please explain whether any official correction process applies to this existing account.” It requests a finding and a permitted process without demanding a predetermined outcome.

Ask a question that identifies the account

Start with the UID displayed after you log in to your own account. Keep that identifier separate from an email address, a Telegram username or the text of a referral code. These values may all appear in a support conversation, but they identify different things. A valid code does not establish that a particular UID is attributed to it.

Write down the registration date, the route used and any code visible before registration was completed. If you did not save those details, say so. A truthful enquiry with missing evidence is more useful than a confident reconstruction that cannot be supported. Request the present account status and any permitted official next step rather than asserting a relationship that the exchange has not confirmed.

Separate the three relevant records

The first record describes the signup journey. The second is the exchange's actual attribution for the account. The third describes customer payment eligibility and settlement registration. A screenshot of a landing page may support the first record without resolving either of the others.

TradePayback may receive partner compensation. That compensation is not automatically identical to the customer's payment. Preserve the distinction when reading an exchange partner page or discussing displayed conditions with customer support.

Use the centrally maintained signup destination

The Toobit user guide provides the exchange's registration background. If you intend to use TradePayback's route, consult the current Toobit detail page for its maintained signup button and displayed code. Do not rely on a fixed destination copied into an old article when the central information may have changed.

For an existing account, begin with that account's UID. Do not present it as a new registration or assume that following a new link changes an established relationship. Whether an addition, correction or transfer is available requires the exchange's applicable process and account-specific confirmation. This guide does not promise code changes or retroactive benefits.

Understand the compliance boundary

Toobit's compliance and risk-control announcement addresses referral abuse, including self-referral, coordinated account control and artificial generation of activity or fees. An attribution problem should not be answered by multiplying accounts under your control or coordinating trades to create promotional value.

The existence of these restrictions does not establish that every ordinary customer enquiry is misconduct. Actual relationships, conduct and applicable terms matter. The affiliate programme agreement concerns partner conditions; it should not be substituted for the separate terms governing a customer payment.

Ask support to identify the permitted process for the existing account. Do not ask an introducer for a workaround that conceals a previous code or treats related accounts as independent merely because different email addresses were used. The goal is an accurate record of a legitimate relationship, not a more convenient description of the account.

Prepare an evidence pack without handing over access

A focused pack contains the UID, registration date, signup route when known and a concise description of the uncertainty. Include the support case number and the account-specific wording of any earlier answer. A screenshot should show the relevant identifier or code while concealing unnecessary personal information.

Keep passwords, authentication codes and API secrets out of the conversation. Even an identifier such as a UID should be shared through the intended support route rather than a public comment or announcement group. Support may require further verification through its official process, but a request to describe the attribution issue is not a reason to give an introducer control of the account.

Read the reply precisely

A response saying that a code is active may refer to the code itself, not its application to your account. A response saying that an account is linked should identify which UID and which programme are covered. Compare the subject of the answer with the subject of your question before marking the enquiry resolved.

For TradePayback customer registration, use the contact page or the site's support controls and provide the exchange name and UID. Keep request received, exchange attribution confirmed and customer settlement confirmed as separate statuses. An acknowledgement proves receipt; it does not establish all three outcomes.

Verify the payment terms independently

Ask for the effective date, eligible products, calculation base, exclusions and settlement process. Deposit value, trading volume and paid trading fees have different units. Applying the same percentage to each produces different amounts, so an unexplained headline percentage is insufficient for estimating a customer payment.

Do not assume that an exchange referral promotion and a separate customer rebate can always be combined. Each arrangement has its own conditions. Nor should a promotional task become a reason to create unnecessary trading activity. Resolve eligibility first and keep any unconfirmed payment outside realised income records.

Maintain a dated history for the UID: signup evidence, exchange case numbers, attribution findings and customer settlement confirmation. If an answer changes, preserve the earlier version and note the correction date. A later reviewer should be able to reproduce why a status was recorded without relying on someone else's memory.

FAQ

Does clicking a referral link prove that my account is linked?

No. It supports the signup-route record, while the completed account's attribution requires UID-specific confirmation.

Should I create another account to repair an uncertain code?

Do not use that as a workaround. Ask official support about the existing account and any process it actually permits.

Is an affiliate commission the same as my cashback?

No. The recipient and agreement differ. Confirm customer registration, eligible activity and the calculation base separately before expecting a payment.