Cryptoassets Regulatory Intelligence cryptoassets.gi
US-MO · run crypto-2026-08-06 v13.3.0
content: ai_generated 10 sources retrieved model claude-sonnet-5 ·

United States – Missouri

US-MO schema crypto-v2.0.0 trajectory: not recordedregulatedoverlaps: FIM, WPM

Last updated · 8 categories · 11 sourced findings · 10 sources in the cumulative register

8Categoriesbaseline.
11Findings.claims[]
0Tier-1 sourcesrun_metadata.t1_source_count
Confidence mix (sums to 8 rendered categories; click to filter)
No categories moved this cycle.

Jurisdiction brief

No content recorded at this JID path.

8 of 8 categories
Signal
Density

Selections OR within a group, AND across groups. Press / to search.

#

Missouri has no bespoke crypto-asset licensing statute. Virtual-currency exchange, custody and transmission businesses are captured under Missouri's general money-transmitter licensing regime, administered through the multistate NMLS infrastructure, rather than a dedicated 'BitLicense'-style instrument. The precise state statutory citation and any crypto-specific carve-outs could not be independently confirmed via retrievable primary source in this run and should be escalated for direct statutory verification. Separately, state-level scrutiny of virtual-currency kiosk operators has been exercised primarily through consumer-protection litigation rather than licensing enforcement.

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 (2)
  1. T?source not recordedM4bindingin force
  2. T?source not recordedM3non-binding

#

Missouri defers token-as-security/commodity characterization to the federal SEC/CFTC framework rather than maintaining an independent state taxonomy. Within that federal overlay, the Missouri Secretary of State's Securities Division actively enforces the state's blue-sky (Missouri Securities Act) regime against crypto-investment offerings that meet the security definition and are marketed to Missouri residents.

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 (2)
  1. T?source not recordedM4bindingin force
  2. T?source not recordedM3bindingin force

#

Missouri has no bespoke statute addressing crypto mining, staking, DeFi lending, DEX operation, node operation, validator activity or tokenization. A 2023 legislative effort to grant statutory protections to crypto-mining operations (comparable to laws enacted in Arkansas and Montana) died without passage, leaving miners subject only to general business, zoning and utility law. No evidence of subsequent enactment was found.

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 (2)
  1. T?source not recordedM3non-binding
  2. T?source not recordedM2non-binding

#

Missouri has not enacted a state-specific stablecoin issuance-authorisation, reserve, redemption, disclosure or systemic-designation regime. Payment stablecoin issuance nationally, including for issuers serving Missouri residents, is governed by the federal GENIUS Act framework, which preempts the need for a Missouri-specific regime for compliant federally-permitted issuers. Implementation of GENIUS Act rules was still being finalized as of the most recent available reporting.

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)
  1. T?source not recordedM3bindingenacted not yet effective

#

Missouri's principal live consumer-protection vector for crypto is Attorney General enforcement against virtual-currency kiosk (crypto-ATM) operators under general state consumer-protection law, driven by a documented and rising volume of fraud complaints. No crypto-specific marketing-restriction, custody-segregation or suitability statute distinct from this general enforcement posture has been identified.

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 (2)
  1. T?source not recordedM5bindingin force
  2. T?source not recordedM4non-binding

#

No Missouri-specific statute altering the treatment of cryptocurrency for state tax purposes was identified in this pass. Missouri state income tax is generally understood to follow federal adjusted-gross-income conformity, implying that federal property/capital-gains characterization of crypto would flow through by default absent contrary state guidance, but this inference could not be independently confirmed against a live Missouri Department of Revenue source in this run and should be escalated.

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)
  1. T?source not recordedM3bindingin force

#

Missouri imposes no identified state-specific restriction on cross-border transfer of virtual currency. Applicable controls derive from the federal Bank Secrecy Act / FinCEN framework, including the Travel Rule and 2025 FinCEN guidance specifically flagging convertible-virtual-currency kiosks as a vector for illicit cross-border fund movement — a typology directly relevant given Missouri's documented crypto-ATM fraud caseload.

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)
  1. T?source not recordedM3bindingin force

#

Crypto AML/CFT obligations applicable to Missouri-based virtual-asset businesses are sourced via the fleet's shared Financial Integrity Module (FIM) aml_ctf subscription and are not duplicated in this crypto baseline, per the module subscription reminder. As disambiguation context only: FinCEN is the primary federal AML/CFT regulator for money-services businesses, including Missouri-licensed money transmitters engaged in virtual-currency activity, and has issued kiosk-specific typology guidance relevant to Missouri's active crypto-ATM caseload.

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 United States – Missouri
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewernot recorded
trust.content_sourceai_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.

Suppressed by doctrine: derived risk score; per-module RAG traffic light; derived_scores = {}.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-08-17. A year-precision row is never promoted into a tighter band.

Orphan deltas: 0 cycle_delta row(s) target non-module objects and are listed in the rail rather than attached to a card.

Envelope: baseline resolved at jurisdiction_json.baseline; 8 module(s), 11 finding(s), 10 source(s) in the cumulative register.