Morocco has no crypto-specific licensing statute in force. The binding position remains the November 2017 joint communiqué by the Ministry of Economy and Finance, Bank Al-Maghrib (BAM) and the Autorité Marocaine du Marché des Capitaux (AMMC), which treats virtual-currency activity as unregulated and warns the public against its use; enforcement precedent (e.g. prosecutions for crypto-based purchases) has functioned as a de facto prohibition even though MENAFATF found no legal text formally confirming a ban. Draft Law 42.25 (SGG avant-projet, Aug 2025) would create a VASP licensing regime under AMMC oversight, with BAM approval required for certain activities, but it is not enacted and no effective date exists.
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 statutory taxonomy of crypto-assets currently exists in Morocco; under the 2017 communiqué, virtual currencies are simply treated as an unregulated instrument. Draft Law 42.25 (pending) proposes a MiCA-inspired taxonomy distinguishing crypto-assets, asset-referenced/stablecoin tokens (BAM-regulated), and other digital tokens (AMMC-regulated), while explicitly excluding NFTs, CBDCs and crypto-mining from its scope.
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 in-force rules address staking, mining, DeFi, DEX, node operation, validation or tokenization in Morocco. Draft Law 42.25 (pending) expressly excludes crypto mining and leaves DeFi/other digital financial instruments to existing capital-market law rather than covering them directly; staking, validator and node-operation activity are not addressed by either the 2017 communiqué or the pending draft.
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 local stablecoin issuance-authorisation, reserve, redemption or disclosure regime is currently in force. Draft Law 42.25 (pending) proposes that BAM will regulate issuers of asset-backed tokens/local stablecoins, but implementing detail (reserve backing, redemption rights, disclosure) is not yet verified against the enacted text since the bill remains in adoption.
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.
The 2017 BAM/AMMC/MEF communiqué functions as the primary consumer-facing risk-disclosure instrument, warning of the absence of protection against exchange-platform failure, absence of a specific legal protection framework for users, and price volatility. No custody-segregation, complaint-handling, or suitability regime specific to crypto exists; Draft Law 42.25 (pending) would bring custodial exchange operators into AML/CFT-linked licensing scope, but this is not yet in force.
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.
A 2022 DGI (Direction Générale des Impôts) circular reportedly classifies cryptocurrencies as intangible assets for tax purposes, applying a 20% capital-gains rate on disposals and treating mining income as business income subject to income tax, with a general reporting obligation. This is corroborated only via a secondary summary source, not the primary DGI circular text, so confidence is capped at Probable per the seed's caution flag pending primary-source verification.
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.
Morocco's binding-adjacent position frames virtual-currency risk partly through the country's general exchange-control regime, as reflected in the 2017 BAM/AMMC/MEF communiqué's unregulated-activity framing. No crypto-specific cross-border reporting threshold exists in force. Draft Law 42.25 (pending) proposes travel-rule-style information-sharing obligations for licensed VASPs, but these are not yet operative.
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.
Crypto subscribes to the FIM aml_ctf baseline; independent aml_cft_regime claims are intentionally not produced here to avoid duplication (absent_field_provenance: not_applicable_in_regime — tracked under FIM subscription, not this baseline). For cross-reference context only: MENAFATF's May 2024 5th Enhanced Follow-Up Report on Morocco shows <cite index="22-2">Recommendation 15 has been re-rated from non-compliant to partially compliant</cite>, reflecting incremental progress on virtual-asset AML/CFT technical compliance, though a comprehensive VASP risk assessment remains outstanding per the seed disambiguation.
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 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 Morocco
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.