South Africa's CASP regime: the technical evidence the FSCA and FIC expect
What South African CASPs must show the FSCA and FIC: Directive 9 travel rule, PCC 61, Joint Standard 2 of 2024, records, and who owns each piece of evidence.
Kostiantyn Boiko, Blockchain Engineer
English original
South Africa regulates crypto asset service providers (CASPs) under two laws at once. The Financial Sector Conduct Authority (FSCA) licenses them as financial services providers under the FAIS Act, after declaring crypto assets a financial product on 19 October 2022. The FIC Act has made them accountable institutions since 19 December 2022, and the FSCA inspects them against that Act too. Its latest published update (15 April 2026) reported 310 licences approved out of 533 applications received by 31 March 2026.
An inspector asks for evidence, not architecture slides: the travel rule record behind a withdrawal, the screening log behind a deposit, proof that a frozen address stayed frozen. At system level, most South Africa crypto compliance work comes from FIC Directive 9 and its guidance, PCC 61; Joint Standard 2 of 2024 adds cybersecurity rules for some licence categories. Below we map each obligation to a control, the evidence and an owner. This is a technical reading, not legal advice.
What are the key dates?
| Date | What happened |
|---|---|
| 19 October 2022 | FSCA declaration of crypto assets as a financial product is gazetted |
| 19 December 2022 | CASPs become accountable institutions (item 22, Schedule 1, FIC Act) |
| 1 June 2023 | FSCA starts licensing CASPs |
| 30 April 2025 | FIC Directive 9 (travel rule) comes into operation |
| 1 June 2025 | Reported commencement of Joint Standard 2 of 2024; confirm against Joint Notice 1 of 2024 |
| 1 March 2026 | SARS starts the Crypto-Asset Reporting Framework (CARF) |
| 30 March 2026 | FIC publishes PCC 61 on implementing the travel rule |
| 17 April 2026 | Draft Capital Flow Management Regulations bring crypto into exchange control |
| 28 May 2026 | SARB and FSCA: crypto is not a payment under the National Payment System Act |
| 7 September 2026 | Final FIC Directive 12 takes effect, as Moonstone reports: CASPs file their compliance programme by 31 October each year |
| 21 October 2026 | Finance Minister says the capital flow rules will be redrafted |
What does the FSCA look for in a licence application?
Anyone who, as a regular feature of their business, gives advice or intermediary services in relation to crypto assets must be an authorised FSP or a representative of one. That covers exchanges, brokers and custody; mining and node operation are exempt, but that exemption does not cover a business’s separate financial services.
The FSCA’s April 2026 update gives the reasons for its 17 declines: failure to meet the fit and proper requirements on operational ability (no “clear and comprehensive business plans and business model descriptions” with the operational frameworks behind them) and on competency. Another 124 withdrew after talks with the FSCA about whether their business models were appropriate. Without a licence, neither group may provide those services.
Our recommendation: describe the system you actually run. A wallet map, who can move funds and how, and the reconciliation method answer most operational questions before they are asked.
Payment firms should read the joint communication the SARB and FSCA signed in May 2026. Crypto assets, stablecoins included, are not payments under the National Payment System Act and are not legal tender, but an intermediary that facilitates a payment-type crypto transaction still needs a FAIS licence. The SARB is unlikely to treat foreign-currency stablecoins as domestic payment instruments. Licensed CASPs must tell customers clearly how limited their licence is.
Our review did not identify a CASP-specific FSCA conduct standard, but the regulatory library could not be searched comprehensively. Existing FAIS conduct requirements still need to be assessed. The FSCA’s July 2026 Regulation Plan referred to the COFI Bill as pending introduction and identified work on joint standards for governance, outsourcing and operational resilience; that wording does not establish the Bill’s status at publication.
What does Directive 9 require of your transfer flow?
Directive 9 applies to accountable institutions falling within Schedule 1 items 12 or 22 when they act as ordering, intermediary or recipient CASPs; failure to register does not remove an institution’s obligations. PCC 61 adds that it covers transfers within, from and into South Africa, to and from unhosted wallets, and stablecoins.
| Party | Data the ordering CASP must transmit (Directive 9, 4.2 and 4.4) |
|---|---|
| Originator, natural person | Full name; SA identity number, or passport or foreign ID number and date of birth; residential address if readily available, otherwise country of birth |
| Originator, legal person | Registered name, registration number, registered address |
| Originator, both | Wallet address used; account number at the CASP, or a unique transaction reference |
| Beneficiary | Full name; wallet address; account number at the recipient CASP if readily available |
- R5,000 is not a threshold for the rule. For qualifying single transactions below R5,000, Directive 9 permits reduced information and verification requirements; suspicion and specified high-risk circumstances can still trigger verification, including recipient-side checks under clause 6.3. PCC 61 sets a zero threshold for transfers in a business relationship.
- Before, never after. Data goes before or with the transfer; batches are allowed, post-facto sending is not (7.2, 7.3). PCC 61 allows no buffer time and recommends pre-settlement authorisation.
- Block non-compliant outgoing transfers; hold unmatched incoming value. An ordering CASP that cannot comply must not execute the transfer (4.8). For incoming transfers, apply PCC 61’s information, suspension, rejection and return procedures before making value available to the client.
- A hot wallet address is not a customer identifier when it is shared or rotated (PCC 61, 2.6.8).
PCC 61 is guidance, but the FIC says an institution that departs from it must show it met the obligation in an equivalent way.
Requirement, control, evidence, owner: the FIC side
The first column is the requirement, paraphrased, with its citation. The other columns are our implementation recommendation, drawn from building and running exchange, wallet and custody software at the reference exchange since 2024 and from technical files we prepare for licence applications. They are not legal requirements.
| Requirement (citation) | Control in the platform | Evidence | Owner |
|---|---|---|---|
| No anonymous clients, even below R5,000 (FIC Act s 20A; PCC 61 3.4, 3.8) | KYC tier gates every deposit address and withdrawal | KYC decision log; tier rules | Compliance officer |
| Travel rule data on every transfer in a business relationship (Dir. 9, 4.2–4.5; PCC 61 3.1) | Capture the applicable originator and beneficiary fields; classify the destination as a CASP or unhosted wallet; key the record to an internal transfer ID and link the transaction hash once available | Sample records linking internal transfer IDs, travel rule messages and, where applicable, on-chain transaction hashes | CTO |
| Data sent before or with the transfer (Dir. 9, 7.2–7.3; PCC 61 3.14–3.15) | Broadcast blocked until required data has been transmitted through the agreed channel; delivery failures trigger a hold and escalation | Message and broadcast timestamps; rejection log | CTO |
| No value to the client until data arrives; return only if no designated person is involved (PCC 61 4.17) | Unmatched deposits held in suspense, not the available balance | Suspense register with ageing | Treasury, compliance officer |
| Due diligence on counterpart CASPs, refreshed as risk changes (Dir. 9, 4.7; PCC 61 3.19–3.20) | Counterpart register: licence, jurisdiction, travel rule support, review date | Register export | Compliance officer |
| Unhosted wallets: risk-based policy, holder identity, volume monitoring (Dir. 9, 8.2–8.3; PCC 61 4.27–4.31) | Address book records who controls each external address; unhosted flag on transfers | Unhosted volume per client | Compliance officer |
| Screen originator, beneficiary, counterpart CASP and wallet identifiers against applicable targeted financial sanctions information before making value available; apply legally required freezing measures without delay (PCC 61 4.14, 4.22–4.24) | Per-transfer screening; block relevant account activity and movement of assets under the CASP’s control, with compliance escalation | Screening log; freeze log; report reference | Compliance officer |
| Comply with a section 34 intervention directive for its specified period, up to the statutory limit of 10 working days (PCC 61 4.15) | Block the specified transaction or funds under the CASP’s control; record the directive’s scope and expiry | Drill record | CTO |
| Automated monitoring for reportable and suspicious activity (PCC 61 4.20; FIC Act s 29) | Rules for transaction velocity, structuring and unusual counterparty patterns | Alert and case log | Compliance officer |
| Retain records for at least five years from the applicable statutory trigger, including relationship termination, transaction conclusion or submission of a section 29 report; third-party recordkeeping does not remove the CASP’s liability or section 24 notification duties (FIC Act ss 23, 24) | Append-only store; hosting and KYC vendors in a register | Restore test; sample export; notification | CTO |
| Controls written into the risk management and compliance programme (Dir. 9, 4.9; PCC 61 4.16), filed on goAML by 31 October each year under Directive 12 as Moonstone reports it; confirm against the final text | Programme that cites the live configuration | Board-approved programme; goAML receipt | Compliance officer, board |
PCC 61 also says a third-party travel rule tool leaves the CASP responsible (4.38) and advises independent testing of travel rule controls (4.39).
Does Joint Standard 2 of 2024 apply to a CASP?
Only if the CASP fits the standard’s own definition of “financial institution”. Joint Standard 2 of 2024, published by the FSCA and Prudential Authority on 17 May 2024, lists banks, insurers, market infrastructures, scheme managers and pension funds, among others. Moonstone reports commencement on 1 June 2025 under Joint Notice 1 of 2024; that notice was not retrieved for this review. On the FAIS side it covers discretionary FSPs, as defined by the standard, administrative FSPs and Category I FSPs that administer investment funds. A CASP licensed as a Category I FSP for advice and intermediary services only, with no fund administration, is outside it. Secondary summaries describe a similar institutional scope for Joint Standard 1 of 2023 on IT governance and report commencement on 15 November 2024. Confirm its definition and commencement against the official text; licence category alone is not a substitute for that assessment.
If it applies, these clauses generate the most evidence:
| Requirement (Joint Standard 2 of 2024) | Control | Evidence | Owner |
|---|---|---|---|
| Asset inventory including third-party assets, reviewed at least every two years (7.1.1(d), 7.1.2) | Register of systems, nodes, KYC and hosting providers | Register with review dates | CISO |
| Multi-factor authentication for critical functions; MFA or privileged access management for admin accounts; privileged activity logged and reviewed (8.2.1, 8.3.1) | 2FA on every console role; session logging | Role matrix; access reviews | CISO |
| Logs protected from editing and deletion (7.3.2(a)) | Tamper-evident log shipped off the host | Integrity check | CISO |
| Key management policy; keys kept in hardened, tamper-resistant systems; key backups (7.2.6) | Key storage assessed against the hardening and tamper-resistance requirements; controlled key ceremonies and tested backups | Ceremony records | CISO, treasury |
| Penetration test of internet-facing systems after major changes, at least yearly (7.7.3(a)(iii)) | Test calendar tied to releases | Reports; remediation tracker | CISO |
| Encrypted offline or offsite backups; recovery objectives; response plan tested against them (7.4.1, 7.5.1(d)) | Restore drills on clean hardware | Timed drill report | CTO |
| Material cyber incidents reported in the form the Authorities set (9.1) | Incident classes with a materiality trigger | Incident register | CISO, CEO |
If it does not apply, use the list as an engineering baseline, not as an FSCA-approved checklist.
How do exchange control and tax reporting affect your systems?
Whether sending crypto offshore needs exchange control approval is unsettled. Clyde & Co’s June 2026 summary describes conflicting High Court decisions: Standard Bank v SARB treated crypto as neither money nor capital under the 1961 Exchange Control Regulations, while Mangundhla v SARB reached the opposite conclusion for Bitcoin. The summary reported an appeal in Standard Bank; the judgments and appeal status at 31 October 2026 were not independently checked.
Treasury and the SARB published draft Capital Flow Management Regulations on 17 April 2026 and a draft Crypto Assets Manual on 3 August 2026. Under the manual, transfers between an authorised domestic CASP and an offshore CASP or a non-custodial wallet would be reportable to the SARB’s Financial Surveillance Department, and inbound transfers from non-custodial wallets would not be allowed. ITWeb and Business Day reported on 22 October 2026 that the Finance Minister had announced a revised approach the previous day. Verify the latest official position before relying on the proposals; their draft status does not displace existing exchange-control obligations.
SARS’s CARF has applied since 1 March 2026. Reporting CASPs collect self-certifications from new and existing users, and the first return, for the period to 28 February 2027, is due by 31 May 2027.
Our recommendation: tag every transfer with the counterparty type (domestic CASP, foreign CASP, unhosted wallet) and the client’s residency. Directive 9 already needs the first, and the draft exchange control manual uses both.
Where do South African stacks fall short?
Check your implementation for these failure modes:
- The travel rule message goes out from a batch job after the withdrawal is broadcast.
- Deposits are credited before the sending CASP’s data arrives.
- Sanctions screening covers names at onboarding, not wallet addresses per transfer.
- The address book stores addresses but not who controls them.
- A third party keeps statutory records on the CASP’s behalf without the required section 24 notification.
What should a CASP do now?
- Confirm your FAIS categories and whether either Joint Standard applies.
- Check the Directive 12 filing went through goAML and keep the receipt; confirm the reported 10-day amendment rule against the final text.
- Hold withdrawals before broadcast until travel rule data is sent.
- Put unmatched deposits in suspense and age them.
- Screen wallet addresses on every transfer and rehearse a freeze.
- Identify third-party statutory recordkeepers and provide the prescribed particulars to the FIC and applicable supervisory body as required by section 24.
- Tag counterparty type and residency on every transfer, and start CARF self-certification.
South Africa CASP FAQ
Do I need an FSCA licence to run a crypto exchange in South Africa?
Yes, if you give advice or intermediary services in relation to crypto assets as a regular feature of your business. You must be authorised as an FSP under the FAIS Act or appointed as a representative of one.
How many crypto asset service provider licences has the FSCA approved?
310 of 533 applications as at 31 March 2026, with 17 declined and 124 withdrawn. The FSCA publishes the list of licensed CASPs on its website.
What is the FIC Directive 9 travel rule threshold?
Zero for transfers in a business relationship, according to PCC 61. The R5,000 figure concerns reduced information and verification requirements for qualifying single transactions, not an exemption from the travel rule. Suspicion and specified high-risk circumstances can still require verification.
Does Joint Standard 2 of 2024 apply to CASPs?
Only to those within its definition of financial institution, such as discretionary or administrative FSPs. A Category I CASP giving only advice and intermediary services is outside it; confirm your categories with counsel.
Can a South African CASP accept deposits from unhosted wallets?
Directive 9 and PCC 61 contemplate transfers involving unhosted wallets, subject to applicable information, due-diligence and risk controls. That is not blanket permission under every relevant law. The August 2026 draft manual proposes restricting inbound transfers from non-custodial wallets; press reports say the proposals will be revised.
Is USDT a payment instrument in South Africa?
Not under the National Payment System Act. The May 2026 joint communication says crypto assets, stablecoins included, are not payments under that Act, and the SARB is unlikely to treat foreign-currency stablecoins as domestic payment instruments. Facilitating payment-type crypto activity still needs a FAIS licence.
Does licence-ready software make a CASP compliant?
No. Software provides controls and evidence; compliance depends on your company, people and conduct, and the FSCA decides.
How BitPolaris helps
BitPolaris builds the exchange, wallet and custody software that has run in production at the reference exchange since 2024. The exchange has KYC tiers with Sumsub or Didit, travel rule data capture and export for your chosen provider—not a complete travel rule messaging service, sanctions screening hooks, deny-by-default roles and an exportable audit log. Self-hosted custody adds hot, warm and cold tiers, M-of-N approvals, a 24-hour delay on new withdrawal addresses, round-the-clock ledger-against-chain reconciliation and signed proof-of-reserves exports. Our cloud option uses EU servers. If the arrangement involves keeping FIC Act records on your behalf, assess section 24 notification duties; separately assess POPIA requirements for cross-border personal-information transfers.
The Licence Technical Pack covers the documentation:
| Item | Price excl. VAT (31 October 2026) | What you get |
|---|---|---|
| Lite | €1,250 one-time | For platform customers: standard sections, your regime noted |
| Pro | €6,300 one-time | Section by section to one regime, your diagrams, third-party register, recorded restore drill |
| Regulator Q&A | €1,450 a month | Engineer answers to technical questions during review |
Pro maps MiCA, the Central Bank of Armenia, SPK and VARA as standard; South Africa is not yet on that list, so agree the scope with us first. A first draft takes two weeks from the scoping call. See also what regulators ask for and the Kenya VASP Act checklist.
We are not a law firm and do not file applications; your counsel does. Installing our software does not make anyone compliant or licensed.
Sources
- FSCA, Declaration of crypto assets as a financial product, 20 October 2022
- FSCA, Update on licensing and supervision of CASPs, 15 April 2026
- FSCA, 2026 Three-Year Regulation Plan, 3 July 2026
- National Treasury, GN 2800 amending Schedules 1 to 3 of the FIC Act, 29 November 2022
- Financial Intelligence Centre, Directive 9, GN 5543, 15 November 2024
- Financial Intelligence Centre, PCC 61 on the travel rule, 30 March 2026
- Financial Intelligence Centre Amendment Act 1 of 2017, substituting FIC Act ss 23 and 24
- Financial Intelligence Centre, Consultation note on draft Directive 12, 31 July 2026
- Moonstone, FIC revises annual RMCP deadlines in final Directive 12, 7 September 2026
- FSCA and Prudential Authority, Joint Standard 2 of 2024, 17 May 2024
- Moonstone, Cybersecurity Joint Standard: commencement date confirmed, 2024
- ENSafrica, FSCA and PA publish Joint Standard 1 of 2023, 22 November 2023
- SARB and FSCA, Joint Communication: crypto assets for domestic payment purposes, May 2026
- National Treasury and SARB, Statement on the draft Capital Flow Management Regulations, 15 May 2026
- National Treasury and SARB, Draft Crypto Asset Manual for cross-border activities, 3 August 2026
- Clyde & Co, Crypto assets in South Africa: regulation and case law, 5 June 2026
- ITWeb, Crypto players back rethink of cross-border rules, 22 October 2026
- Business Day, Treasury and Reserve Bank to redraft crypto asset regulations, 22 October 2026
- SARS, Crypto-Asset Reporting Framework, checked 31 October 2026