A South African crypto provider may ask who is sending or receiving a transfer because the Travel Rule requires information to accompany relevant transfers. Answer through the provider's authenticated channel and describe the destination accurately. A request for beneficiary details is not, by itself, evidence that you have done something wrong.
FIC Directive 9 became operational on 30 April 2025. The FIC's April 2025 joint advisory confirms the effective date, while its November 2024 announcement explains the accompanying-information and recordkeeping purpose.
Understand the two layers
The blockchain records a movement between addresses. A provider also needs information about the people or entities associated with a transaction. An address alone may not answer who owns the destination account, which service is involved or whether a transfer meets the provider's compliance requirements.
Travel Rule information is not the same thing as public blockchain data. Do not publish identity documents or beneficiary records alongside a transaction ID. The provider should explain how to submit information securely and how it will be used.
Nor does completion of a questionnaire establish tax compliance, exchange-control permission or product eligibility. Those are separate questions. The exchange hub and SARS guide provide the surrounding context.
Annotated beneficiary questionnaire
This is an illustrative worksheet, not an official FIC form or a claim that every provider asks identical questions.
| Example question | What your answer should establish | Common mistake |
|---|---|---|
| Who is the recipient? | The actual person or entity receiving the assets | Entering an exchange brand when asked for the account holder |
| Is this your own account? | Whether ownership at both ends is yours | Assuming every saved address belongs to you |
| Where is it held? | A custodial provider or a wallet you control | Calling an exchange deposit address self-hosted |
| Which provider? | Correct service and, where requested, legal entity | Guessing from a logo |
| What is the address and network? | Exact intended destination | Reusing an address from transaction history without verification |
| Why are you transferring? | A truthful, concise purpose | Selecting a misleading category to avoid checks |
Keep your completed answers with the transaction record. If you do not understand a field, ask official support before authorising. Do not copy someone else's beneficiary answers from a forum.
A self-hosted wallet is a distinct case
Paragraphs 8.2 and 8.3 of Directive 9 require providers to maintain risk-based procedures for unhosted-wallet transfers and obtain further information when higher risk is identified. Describe the destination according to who controls it: your own wallet or a custodial account supplied by another service. Ask your provider which evidence its current process requires for that destination. This guide makes no finding that a particular self-hosted transfer is permitted or prohibited.
A wallet you control and an account held at another exchange can therefore lead to different questions. Technical ability to sign a message or send funds does not automatically settle the provider's required ownership evidence. Follow its documented process without exposing your seed phrase or private key.
Do not split transfers or alter answers to evade checks. A compliance review should be resolved through truthful information, not by searching for an amount or route that avoids the question.
If a transfer is delayed
First establish whether it was submitted, broadcast or credited. Record the transaction ID if one exists, the provider reference, the timestamp and the requested information. A blockchain confirmation does not prove that a custodial provider has completed its account-crediting checks.
Ask which item is missing and where to upload it. If the sender and recipient providers use different terminology, ask each to identify the relevant account or entity rather than inventing a match. Keep one coherent support thread so the evidence does not fragment across conflicting tickets.
Never send extra crypto to an unsolicited “compliance agent” to release a transfer. Independently open the provider's support page. If asked for an unusually sensitive document, verify the request in the authenticated account and ask about secure transmission and retention.
Final pre-transfer check
Confirm the asset and network at both ends, account ownership, beneficiary information, active deposit status and fees. Save the confirmation privately. The USDT buying guide can help with acquisition, but buying an asset does not pre-approve its next destination.
The worksheet helps organise accurate answers; it cannot guarantee that a provider will release a particular transfer or establish permission for a cross-border transaction.
Sources and verification
Primary sources checked on 20 September 2026. Prices, availability and processing arrangements can change.