Purpose of the Template
Expanding a crypto business across U.S. states presents a complex compliance challenge. Some states require traditional money transmitter licenses, while others have developed crypto-specific frameworks like California's Digital Financial Assets Law. Certain jurisdictions impose strict consumer protection standards, and some have unique requirements for business models like crypto kiosks.
This template provides a jurisdiction-specific compliance matrix to map requirements before entering a new state, document your compliance posture for regulators, and build modular controls that adapt to each jurisdiction's rules without overhauling your entire program.
You're not creating 50 separate compliance programs. You're building one flexible framework with jurisdiction-specific configurations.
Prerequisites
Before using this template, ensure you have:
Baseline Federal Compliance
Your FinCEN registration as a money services business, your Bank Secrecy Act (BSA) compliance program, and your Customer Due Diligence procedures must be operational. State licensing builds on federal obligations.
Business Model Clarity
Clearly define the services you're offering in each state. Are you custody-only? Do you facilitate fiat-to-crypto exchanges? Are you issuing stablecoins? States classify these activities differently, affecting your licensing requirements.
Legal Counsel with State Licensing Experience
This template organizes and tracks requirements but doesn't replace legal advice. You'll need counsel familiar with state money transmission law to validate your interpretations and handle applications.
Internal Ownership Structure
Know your beneficial owners, where your corporate entities are registered, and where your key personnel are located. State regulators require this information during licensing, and inconsistencies can delay approvals.
The Template
Copy this into a spreadsheet or compliance management system. Each row represents one state where you're evaluating or operating.
STATE CRYPTO LICENSING MATRIX
State: [State Name]
Date Evaluated: [YYYY-MM-DD]
Evaluator: [Name/Role]
--- LICENSING REQUIREMENTS ---
License Type Required:
☐ Money Transmitter License (traditional)
☐ Crypto-Specific License (specify framework)
☐ No License Required
☐ Exemption Available (describe)
Application Requirements:
- Minimum net worth: $[amount]
- Surety bond required: $[amount]
- Background checks required for: [roles]
- Physical presence required: [Yes/No]
- Application fee: $[amount]
- Annual renewal fee: $[amount]
Estimated Processing Time: [X months]
Regulator Contact: [Agency name, website, phone]
--- OPERATIONAL REQUIREMENTS ---
Consumer Protection Mandates:
☐ Mandatory transaction receipts
☐ Complaint remediation process
☐ Specific disclosure language required
☐ Fee transparency requirements
☐ Other: [describe]
Reporting Obligations (state-specific):
☐ Quarterly activity reports
☐ Annual audited financials
☐ Suspicious activity reporting (state-level)
☐ Consumer complaint logs
☐ Other: [describe]
Reserve/Capital Requirements:
- Permissible investments for reserves: [describe]
- Segregation requirements: [Yes/No/Details]
- Third-party custody allowed: [Yes/No]
--- ENFORCEMENT LANDSCAPE ---
Recent Enforcement Actions in This State:
[Describe any relevant actions, coordination with other states, or enforcement priorities]
Known Coordination with Other Regulators:
☐ Multi-state examinations observed
☐ Information sharing with federal agencies
☐ Independent enforcement posture
☐ Unknown
--- COMPLIANCE CONFIGURATION ---
Jurisdiction-Specific Controls Required:
☐ Modified onboarding flow
☐ Additional customer disclosures
☐ Adjusted transaction monitoring thresholds
☐ Enhanced record retention
☐ Other: [describe]
System Configuration Notes:
[Document any changes to your CDD process, [transaction monitoring rules](/glossary/transaction-monitoring-rules), or customer communications needed for this state]
Risk Rating for This Jurisdiction:
☐ Low (clear rules, established licensing process)
☐ Medium (some ambiguity, but guidance available)
☐ High (unclear requirements, recent enforcement activity, or conflicting guidance)
--- DECISION LOG ---
Expansion Decision:
☐ Proceed with licensing
☐ Delay pending regulatory clarity
☐ Avoid this jurisdiction
☐ Seek exemption or limited operations
Rationale:
[Document why you made this decision, including business factors and compliance risk]
Next Review Date: [YYYY-MM-DD]
Customizing the Template
Adjust for Your Business Model
If you're a stablecoin issuer, add rows for reserve requirements and redemption expectations, which vary by state. If you operate crypto kiosks, include fields for physical location requirements and transaction limits. If you're custody-only, you might face different licensing thresholds than exchange operators.
Track Regulatory Changes Actively
Set reminders to review each state's entry every six months. State legislatures frequently introduce crypto bills, and what's accurate today may be outdated by next quarter. Assign someone on your compliance team to monitor state legislative trackers and regulator announcements.
Map Controls to Your Existing Systems
In the "System Configuration Notes" section, specify changes. If California requires additional disclosures, document the exact language and where it appears in your onboarding flow. If New York requires enhanced transaction monitoring for certain activities, note the rule adjustments and thresholds.
Document Your Risk Logic
The "Risk Rating" section isn't just a checkbox. Explain why you rated a jurisdiction high-risk. Did you see recent enforcement actions? Is there conflicting guidance between state agencies? Are application processing times unpredictable? This documentation protects you if regulators question why you delayed expansion into a particular state.
Link to Supporting Documentation
Don't recreate regulatory guidance in this template. Instead, link to the official statute, the regulator's FAQ page, or your legal counsel's memo. Keep the template lean and navigable.
Validation Steps
Cross-Check with Legal Counsel
Before finalizing any licensing decision based on this matrix, have your attorney review your interpretation. State money transmission law is dense, and exemptions often have hidden conditions.
Test Your System Configurations
If you've documented jurisdiction-specific controls, validate them in a test environment before going live. Run sample transactions through your modified monitoring rules. Confirm that your onboarding flow displays the correct disclosures based on customer location.
Conduct a Mock Regulatory Inquiry
Ask yourself: if a state regulator requested documentation of your compliance posture tomorrow, could you pull this matrix and demonstrate that you've systematically evaluated their requirements? If the answer is no, you haven't captured enough detail.
Compare Against Peer Enforcement Actions
When state regulators publish enforcement actions against crypto companies, compare the cited violations to your matrix. Did you account for the requirement they flagged? If not, update your template and reassess affected jurisdictions.
Schedule Quarterly Compliance Reviews
Your first version of this matrix won't be perfect. Set a recurring meeting where your compliance team reviews new state developments, updates the matrix, and escalates any jurisdictions where risk has increased or requirements have changed.
Fragmentation isn't going away. Treat it as a permanent condition and build systems to manage it. This approach will help you expand faster and with less regulatory exposure than waiting for federal clarity that may never come.
