Crypto Travel Rule South Africa: why a CASP asks about a transfer

The crypto Travel Rule South Africa applies through the Financial Intelligence Centre’s Directive 9 of 2024. It requires accountable institutions that provide or engage in crypto asset transfers to collect, keep and transmit specified details about the person sending and the person receiving a qualifying transfer. For an exchange customer, that can mean a platform asks who owns a wallet, which exchange is receiving a withdrawal or what transaction reference belongs to an incoming deposit. The required information is transfer metadata; a seed phrase or private key is never needed to complete a normal compliance check.

Who the directive applies to

Directive 9 applies to accountable institutions listed under items 12 and 22 of Schedule 1 to the Financial Intelligence Centre Act when they act as an ordering, intermediary or recipient crypto asset service provider. The FIC says the directive came into operation on 30 April 2025. It covers domestic and cross-border crypto transfers facilitated for or on behalf of a client. That scope is about accountable service providers and their transfer roles; it does not mean every person who holds crypto operates a CASP.

The South African Government hosts the full Directive 9 Gazette notice. The FIC’s announcement explains that originator and beneficiary information must be transmitted securely before or at the same time as the crypto transfer. Use the directive itself for the exact fields and role-specific requirements.

What information may accompany a transfer

For a natural-person originator, the directive lists a full name and identity details, with different identification fields for South African citizens or residents and for foreign nationals. It also includes a residential address when readily available, or country of birth when that address is not readily available. For a legal-person originator, it lists the registered name, registration number and registered address. The transfer’s distributed-ledger address and the sender’s account number or unique transaction reference are also part of the required information when applicable.

The beneficiary information includes a full name, the beneficiary’s distributed-ledger address when relevant and a recipient account number when one is used and readily available. The ordering CASP sends this information to the recipient CASP, directly or through an intermediary. The provider may ask its customer for missing details because it cannot transmit information it does not have. The requested fields can depend on whether the transfer is between service providers or involves an unhosted wallet.

What the R5,000 line does and does not mean

Directive 9 has a special minimum-information rule for a single crypto transfer below R5,000. The sending CASP must still transmit core originator and beneficiary information, including names and the relevant ledger or account reference where applicable. For that limited category, the directive says the provider need not verify the accuracy of the paragraph 4.5 information unless there is a suspicion of money laundering or terrorist financing. This is not a blanket exemption from the Travel Rule, and it is not a promise that an exchange will never request supporting details.

Transfers at or above that boundary and other circumstances are governed by the wider information and due-diligence provisions. Providers also have duties concerning counterpart CASPs, recipient checks and risk controls. Avoid applying one threshold sentence to every transfer type. If a provider asks you to clarify a transaction, check the request in its official app or support channel and ask which field is missing.

Transfers involving an unhosted wallet

An unhosted wallet is defined in Directive 9 as a wallet where the user has exclusive control of the private keys. The directive requires accountable ordering and recipient CASPs to maintain risk-based policies for transfers involving such wallets. If the provider determines that a higher risk is present, its procedures must explain how it obtains further information about the wallet. This does not say every unhosted-wallet transfer is automatically blocked; it means the provider must have documented controls for handling those cases.

If an exchange requests proof that you control a wallet, follow the service’s secure instructions and check its current support page. Never sign an unclear message or send assets to a “verification wallet” merely because someone contacted you. A transaction hash, public wallet address and account ownership record may help explain a transfer, but they do not give a third party control of your funds. Keep account passwords and recovery phrases private.

Why a transfer may be held

The directive says an ordering CASP may not execute a crypto transfer if it cannot comply with the relevant information requirements. Recipient and intermediary providers also need risk-based procedures for transfers that arrive without required information. That can result in a request for clarification, a delay, suspension, return or other provider action under its documented process. The cause may be a compliance-data gap rather than a blockchain confirmation problem.

When a deposit is delayed, preserve the transaction hash, the sending platform’s confirmation, the asset and network, the amount in rand or token units, and the receiving service’s support reference. Do not send a second transfer until you know whether the first one was received or is still being reviewed. Use the receiving provider’s official support channel to ask what information it needs and whether it can locate the transfer.

Keep a clear South African transfer record

For each exchange or wallet transfer, save the date and time, asset, blockchain network, amount, fee, public sending and receiving addresses, transaction hash and account reference. Note whether both wallets belong to you or whether another person or service is the beneficiary. If a CASP asks for information, record what you submitted and when. These records help you reconcile exchange exports later and explain a transfer if the platform or a competent authority asks for documentation.

  • Confirm the asset, network, destination address and memo or tag before sending.
  • Check that a data request appears inside the verified exchange app or website.
  • Provide accurate originator and beneficiary details; do not guess at account ownership.
  • Keep the transaction hash and transfer confirmation with your exchange records.
  • Never share a seed phrase, private key, password or one-time code.
  • Ask the CASP which rule or data field applies if a transfer is delayed.

Keep Travel Rule records separate from CARF

The Travel Rule moves originator and beneficiary information with an individual transfer through CASPs. South Africa’s crypto-asset reporting and CARF discussions concern a separate tax-information framework. A transfer-information request does not calculate a user’s tax, and a tax reporting statement is not the same document as transfer metadata sent between service providers. CryptoSigy has a separate South Africa CARF and CASP reporting guide for that topic.

For more exchange and custody guidance, visit CryptoSigy’s exchange guides and the South Africa crypto collection. The FIC Directive is the primary source for the rules; platform workflows can vary. This overview explains the transfer-data process and does not replace a provider’s official instructions or legal advice for a specific case.