Tunisia has no crypto-specific licensing statute. The Central Bank of Tunisia (BCT) supervises all foreign-exchange and cross-border monetary flows under the 1976 exchange-control code, and unauthorised crypto-asset transactions (purchase, sale, exchange conversion) fall outside any BCT-authorised channel, making them treated as unauthorised/prohibited in practice. A draft crypto-regulation bill has circulated in the Assembly of the Representatives of the People but is not enacted law.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Tunisia has no statute classifying crypto-assets into security-token, e-money-token, asset-referenced-token, stablecoin, utility-token, or NFT categories. The BCT's published legal-framework inventory (banking law, exchange regulation, circulars) contains no reference to token taxonomy.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
No BCT or other Tunisian supervisory instrument addresses staking, DeFi lending, DEX operation, mining, node operation, validator activity, or tokenization. These activities are neither licensed, exempted, nor explicitly prohibited by name; they sit outside the perimeter of the exchange-control code except to the extent any associated cross-border currency flow would itself trigger the general prohibition.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
No Tunisian law authorises, licenses, or sets reserve/redemption/disclosure standards for stablecoins, e-money tokens, or asset-referenced tokens. Issuance of a stablecoin referencing the dinar or foreign currency would implicate the exchange-control code's restrictions on foreign-currency-denominated instruments and BCT's exclusive currency-issuance mandate.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
No crypto-specific consumer-protection obligations (marketing restriction, custody segregation, complaint handling, suitability) exist in Tunisian law. General consumer-protection and banking-supervision statutes do not extend explicitly to crypto-asset service providers, as BCT's banking supervision mandate under Loi n°2016-48 covers banks and financial institutions, not unlicensed crypto platforms.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
No dedicated Tunisian tax code provisions addressing capital gains, income tax, VAT/GST, withholding, or reporting obligations specific to crypto-asset transactions were identified in available sources. This is a genuine research gap requiring escalation to primary tax-code sources (Code de l'IRPP et de l'IS, Code de la TVA) rather than a confirmed exemption.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Cross-border transfers of value connected to crypto-asset transactions are captured by Tunisia's general capital and current-account exchange controls, which require BCT authorisation for most capital-account operations and impose declaration duties on foreign-currency asset holdings. Because crypto transactions are treated as unauthorised, any associated outward transfer of funds to acquire or liquidate crypto-assets would itself constitute a breach of exchange-control provisions absent BCT authorisation.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
This module is subscribed from the Financial Integrity Module (FIM) aml_ctf baseline per fleet doctrine; no aml_cft_regime claims are produced in this crypto DR baseline. Disambiguation context only: the FATF's 2025 Targeted Update on VA/VASP implementation notes continuing global gaps in licensing/registration and Travel Rule adoption, relevant context for Tunisia's unassessed VASP AML posture.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Sources and findings (1)
T?source not recordedM1non-binding
No categories match.
Filters combine as OR inside a group and AND across
groups.
Editorial metadata
Provenance only. Nothing below gates publication or affects the render.
Editorial metadata for Tunisia
Field
Value
trust.lawyer_review.status
never_reviewed
trust.lawyer_review.reviewer
not recorded
trust.content_source
ai_generated
Provenance and declared absence
Disclosure model: module cards load OPEN; standing positions render in full; sub-briefs and jurisdiction briefs load as a clamped teaser with an explicit “read full” control carrying the true word count; earlier updates stay collapsed behind a counted summary. No text is hidden without disclosing how much of it there is.
Sentinel-fed modules receive no special rendering treatment. sentinel_feed is an attribution chip only: it does not suppress content, does not generate an absence reason code, and does not exclude the module from any count, filter, search index or export on this page.
Family taxonomy is renderer-level presentation config, not a JID field. Colour is always duplicated in text and is never the sole carrier of meaning.