Travel Rule in South Africa: FIC Directive 9

The Travel Rule asks a simple thing: when value moves between institutions, information about who sent it and who receives it should move with it. In South Africa, the Financial Intelligence Centre (FIC) applied this to crypto asset transfers through Directive 9, which has been in force since 30 April 2025.

What the Travel Rule is

The Travel Rule comes from the international standards on anti-money laundering set by the Financial Action Task Force. Banks have long sent originator and beneficiary details with wire transfers. The same principle now applies to crypto asset transfers between service providers: the sending institution collects and passes on information about the originator and the beneficiary, and the receiving institution checks that it is there.

What Directive 9 means in practice

For an institution in South Africa that sends or receives crypto assets on behalf of clients, Directive 9 turns the Travel Rule into an operational requirement. In practice that means three things:

• collecting the required originator and beneficiary information before a transfer is sent;
• checking that incoming transfers carry the information they should;
• keeping records that show what was collected, what was checked and what was decided.

The detailed obligations are set out in the Directive itself and in the FIC's guidance, which institutions should read in full with their compliance advisers.

Why the order of checks matters

The difficult part is not collecting data; it is making sure no transfer leaves before the checks are complete. When screening, identity checks and Travel Rule data are handled in separate systems, gaps appear: a transfer can be released while one check is still pending.

DAPL already runs transaction screening (KYT) with Chainalysis or LedgerBrain and identity checks (KYC) with Sumsub in sequence on every transfer, before funds move, under the rules the institution sets. A transfer that fails a check is held and does not leave the institution's custody, and every step is written to a single record. Travel Rule support, through Sumsub's GTR network and aligned with FIC Directive 9, is on Arrel's 2026 roadmap, so the data exchange will run in the same sequence.

A short checklist

• Map every flow where crypto assets leave or arrive on behalf of a client.
• Decide who in your institution approves exceptions, and write it down.
• Make sure no transfer can be released before screening and Travel Rule checks complete.
• Keep one record per transfer that an auditor can follow.

To see how these checks run on DAPL, read about DAPL's compliance module or talk to Arrel.

Questions