South Dakota has no bespoke crypto-asset licensing statute. Virtual-currency exchange and money-transmission-type activity is regulated under the state's general Money Transmission Act (S.D. Codified Laws Title 51A, Chapter 51A-17), administered by the South Dakota Division of Banking and processed through NMLS. Separately, crypto custody-focused firms (e.g., Anchorage, BitGo) have used South Dakota's limited-purpose trust company chartering regime (Title 51A, Chapter 51A-6A) as an alternative, non-MTL pathway to obtain fiduciary/custody authority. No dedicated 'crypto license' distinct from these two general regimes has been confirmed.
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.
South Dakota has no state-level statute classifying crypto-assets as securities, e-money tokens, or utility tokens; token characterization for securities/commodities purposes is governed by federal SEC/CFTC jurisdiction, not state law. Separately, South Dakota's 2023 HB 1193 amended the state's Uniform Commercial Code definition of 'money' to exclude decentralized virtual currencies (e.g., bitcoin) while including government-issued central bank digital currencies; confirmation of final enactment (gubernatorial signature) was not independently verified in this pass.
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.
South Dakota has not enacted activity-specific statutes addressing staking, DeFi lending, decentralized exchange operation, mining, node operation, validator activity, or tokenization. These activities are not separately licensed at the state level; only conduct that independently meets the definition of money transmission under Title 51A, Chapter 51A-17 would trigger licensing.
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.
South Dakota has no state-specific stablecoin issuance, reserve, or redemption regime. Stablecoin issuers operating in or from South Dakota would fall under the general money-transmission/trust-charter framework at the state level and under the federal GENIUS Act payment-stablecoin framework at the federal level.
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.
South Dakota has no crypto-specific consumer protection statute. General money-transmission law imposes some consumer safeguards applicable by extension to virtual-currency transmitters, including a requirement that funds received for transmission be held in trust for the benefit of the licensee/principal (S.D. Codified Laws §51A-17-33) and theft/loss reporting duties (§51A-17-34). Crypto-specific marketing restrictions, risk-disclosure mandates, or suitability rules have not 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.
South Dakota levies no state personal income tax, so crypto-related gains and income are not subject to state-level income or capital-gains taxation; federal IRS treatment of virtual currency as property (subject to federal capital gains/income tax rules) governs regardless of state residence.
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.
South Dakota imposes no state-specific restrictions on cross-border crypto transfers. Cross-border transfer obligations for South Dakota-licensed money transmitters and trust companies derive from federal law, including FinCEN's Bank Secrecy Act framework governing money transmitters (including virtual currency exchangers/administrators) and OFAC sanctions requirements.
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.
AML/CFT obligations for South Dakota-regulated money transmitters and trust companies are addressed under the fleet's Financial Integrity Monitor (FIM) aml_ctf module rather than researched independently in this crypto baseline, per the module subscription rule. Federal BSA/FinCEN registration, KYC/CDD, and SAR obligations apply to South Dakota-licensed money transmitters and trust companies as a baseline, but detailed claims are out of scope here.
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 recordedM3non-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 United States – South Dakota
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.