Independent educational website - not an official exchange service

Reviewed guide | 2026-09-30

Reading a Referral Code Disclosure Before You Share It

A practical guide for South African readers on how to read a referral code disclosure properly before sharing a link, so the person who signs up understands what the code actually changes for them.

southafricacryptoguide.com

Multiple exchanges | South Africa | ZAR | fees, access and account safety

Sharing a referral link is easy. Explaining what that link does to the person who clicks it is harder, and most people never read the disclosure that sits behind the code. In South Africa, where referral links move quickly through WhatsApp groups, community chats and social feeds, the gap between what the sharer assumes and what the new user gets is where confusion starts. This guide walks you through reading a referral disclosure line by line before you forward it, so you can describe the arrangement honestly instead of guessing. It covers where the relevant terms usually live, which parts you should verify on the exchange help centre rather than repeat from memory, what to write down for the person you are inviting, and when to stop and ask support instead of promising something you cannot confirm. Nothing here is investment advice, and no code guarantees a better outcome; the goal is simply that both sides understand the arrangement before anyone signs up.

What a referral disclosure actually covers

A referral disclosure is the text that explains the relationship between three parties: the platform, the person sharing the code, and the person who signs up with it. It normally describes what the code changes about the new user's account setup, what it changes for the sharer, and what conditions apply. It is not a summary of the exchange's whole product range, and it is not a promise about trading results. Read it as a contract about attribution, not as a review of the platform.

The most common mistake is treating the disclosure as marketing copy and skipping to the signup button. In practice, the parts that matter are the conditions attached to the code: whether it applies only to new accounts, whether it must be entered during registration or can be added later, and whether the arrangement can be changed or withdrawn. Those details determine whether the person you invite actually receives anything, so they are worth reading before you forward anything.

In South Africa, referral links often circulate without any accompanying explanation, which pushes the burden of interpretation onto the recipient. If you are the one sharing, you are effectively the first line of explanation. If you cannot describe what the code does in plain language after reading the disclosure, you are not ready to share it.

Where the terms live and what to check on the platform

Referral terms are rarely on the signup page itself. They usually sit inside the exchange help centre, sometimes as a dedicated referral or invitation article, and sometimes as part of a broader account or rewards section. Start there rather than relying on a screenshot someone else posted. Open the official help centre for the exchange you use and search for the referral or invitation topic directly.

As you read, separate what the disclosure states from what you assume. Note whether eligibility depends on account verification, whether the code expires, whether it applies to specific products, and what the platform says about changing or removing the arrangement later. If the article refers you elsewhere for fee details, follow that path and read the fee page as well, because a referral arrangement and a fee schedule are two different documents that people routinely confuse.

Where the help centre is unclear or silent, that silence is itself information. Do not fill the gap with a confident claim. Write down the exact question you could not answer and treat it as a stop condition until support responds. You can reach support through the official help centre channels listed on the platform, and you should keep the reply for your own records.

Writing a plain-language summary for the person you invite

Once you have read the disclosure, write a short summary you can send alongside the link. Keep it to what the document actually says: what the code is for, what the recipient needs to do for it to apply, and where they can read the same terms themselves. Avoid adjectives that imply a benefit you cannot point to in the text. If the disclosure does not state a benefit, your summary should not either.

A useful summary answers four questions in order. First, what does the recipient need to do for the code to take effect. Second, what does the platform say the code changes, if anything. Third, what conditions could prevent it from applying. Fourth, where can the recipient verify all of this independently. If you cannot answer the fourth question with a specific official page, you have not finished reading.

Keep the summary short and factual, and avoid repeating the same phrasing you used in the link message. The recipient should come away knowing which official page to open, not just trusting your description. If they later find that your summary and the platform's terms disagree, the platform's terms win, and you should say so up front rather than after the fact.

Common mistakes and when to stop and ask

The most frequent error is sharing a code before reading the conditions attached to it, then discovering later that it did not apply to the recipient at all. The second is paraphrasing the terms from memory, which drifts over time as platforms update their articles. The third is mixing up a referral arrangement with a fee discount, a promotional campaign, or a loyalty programme, which are separate things with separate terms.

Another common mistake is assuming the arrangement is permanent. Referral terms can be revised, and a description that was accurate last year may not match the current help centre article. Before you share a code again, re-read the relevant page rather than reusing an old message. This takes a few minutes and prevents the awkward conversation that follows a mismatch.

Stop and ask support when the disclosure contradicts what you were told, when eligibility conditions are ambiguous, when the recipient's situation does not clearly match the stated criteria, or when you cannot find the terms on the official help centre at all. Do not resolve those gaps by guessing, and do not pass the uncertainty on to the person signing up. A short wait for a written answer is cheaper than a broken expectation.

Risk boundary: South Africa Crypto Guide

Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.

Scenario checkpoint

  • Read the referral or invitation article in the exchange help centre before forwarding any code, and note the date you read it.
  • Write down what the code changes for the new user, what conditions apply, and which official page states it.
  • Check the fee page separately if the disclosure points there, so you do not confuse a referral arrangement with a fee schedule.
  • Send the recipient a short factual summary plus the official page where they can verify the terms themselves.
  • Re-read the terms before sharing the code again, since articles and conditions can be updated.
  • If any condition is unclear or missing, contact support through the official help centre and keep the written reply.
Risk boundary

Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat.