Why wind-down is a licensing and exam topic, not just bankruptcy counsel
Regulators learned from abrupt crypto platform failures that customer harm spikes when withdrawals are throttled without communication, keys are lost, or support vanishes while marketing still promises safety. California’s Digital Financial Assets Law (DFAL) and DFPI oversight treat exit planning as part of responsible operation — especially if you hold custody or transmit value for residents.
A wind-down plan is not pessimism; it is fiduciary hygiene. Boards should approve a living document reviewed annually and after material business model changes — new custody model, partner exit, or capital stress.
This article is educational, not legal advice. Surrender, assignment, and insolvency paths differ materially; coordinate with counsel and DFPI Digital Financial Assets resources at https://dfpi.ca.gov/regulated-industries/digital-financial-assets/ before you file anything or tell customers you are closing.
Triggers that should activate the wind-down playbook
Define objective and subjective triggers: failure to meet capital or surety requirements, loss of critical banking or custody partners, unremediated exam findings, voluntary strategic exit, merger where the survivor lacks California authority for your activities, and cyber incidents that destroy operational capacity.
Each trigger links to a decision tree: stabilize, sell book, assign license, or surrender. Ambiguity during crisis produces Twitter announcements ahead of regulator notifications — avoid that ordering at all costs.
Name a wind-down executive with authority to freeze marketing, halt new customer onboarding, and convene daily war rooms across legal, compliance, engineering, and finance.
Customer communications: timeline, channels, and tone
Pre-draft communications for phases: warning of potential service changes, confirmed wind-down start, withdrawal instructions, final deadlines, and post-close support channels. Legal and compliance must approve templates before crisis weekend edits.
Use all verified contact methods — email, in-app, SMS where opted-in, and postal mail for material balances. Assume scammers will impersonate your wind-down emails; publish verification guidance on your official site and DFPI-recognizable channels where appropriate.
Multilingual communications are not optional for many California customer bases. Pull from approved translation memory, not rushed contractor work without compliance review.
Custody, keys, and asset return mechanics
Document how customer assets move from your controlled wallets to customer self-custody or successor platforms: fee schedules during wind-down, minimum withdrawal sizes, network congestion handling, and unsupported token policies.
Key ceremonies and HSM access during wind-down need heightened controls — insider risk spikes when layoffs loom. Segregate duties, log every signing event, and require dual control for bulk movements.
Reconciliation must run daily until balances hit zero or assigned; publish internal exception thresholds that halt outbound bulk transfers if ledgers diverge.
License surrender vs assignment: different paths, different evidence
Surrender typically means ceasing regulated activity in California with formal filings and demonstrating customer harm mitigation. Assignment or sale of licensed operations may transfer obligations — due diligence on the acquirer’s capacity is your reputational and legal risk.
Maintain a filing checklist with NMLS and DFPI touchpoints, fees, and sworn statements. Missing a step can leave ghost licenses on registries while you thought you were done.
Preserve copies of all submissions and regulator acknowledgments in the evidence vault permanently — tail liability does not expire when the app shuts down.
Complaints, disputes, and regulatory correspondence during exit
Complaint intake must stay staffed until statutory tail periods end or DFPI agrees otherwise. Tag complaints as wind-down themed; escalate threats, self-harm statements, and elder exploitation immediately per existing playbooks.
Regulatory correspondence gets priority routing — daily coverage, logged requests, and coordinated responses through counsel. Parallel federal inquiries may continue after state surrender; one request log should span both.
Do not delete social channels until you have a plan for redirecting consumers to official support — abandoned accounts become scam magnets.
Vendor and partner termination
Contracts should include wind-down assistance clauses: data export, transition services, and key escrow releases. Terminate vendors in sequence — losing KYC archives before SAR retention obligations are met is a classic mistake.
Partners must receive written wind-down instructions if they touch California customers on your behalf. Uniform customer messaging prevents partners from promising continuity you cannot deliver.
Settle invoices promptly enough to keep critical vendors engaged through final reconciliation; nickel-and-diming during exit buys outages.
Employees, access revocation, and knowledge transfer
Offboarding checklists revoke system access same day while preserving audit logs. Identify single points of knowledge — the engineer who alone understands wallet labeling — and document before notices go out.
Retention agreements for small skeleton crews should be pre-negotiated template-wise, not improvised under insolvency pressure.
Insider trading and material non-public information policies still apply if you are public or fundraising — wind-down does not suspend securities law.
Records retention after shutdown
Wind-down does not mean shred everything. BSA records, complaint files, licensing submissions, and litigation holds follow federal and state retention schedules — often five years or more, sometimes longer if litigation is reasonably anticipated.
Designate a records custodian entity or role post-dissolution with budget for secure storage and legal hold capability.
Cloud account closure without export is an exam and litigation nightmare — export to immutable storage with index metadata first.
Tabletop exercises boards should demand
Annual tabletop: sudden loss of banking partner, seventy-two-hour withdrawal surge, ransomware during wind-down week, and acquirer walks from deal day before close. Score decision time, customer message accuracy, and reconciliation integrity.
Board minutes should record exercise findings and resource approvals — DFPI-facing governance narratives improve when directors engage realistically.
Fix the highest-severity gap within ninety days; do not rerun the same failed scenario twice.
Capital, surety, and third-party continuity providers
Wind-down may trigger minimum net worth or surety bond conversations with DFPI before you can surrender cleanly. Model cash burn for extended support staffing, vendor transition, and legal fees separately from customer asset return — they are different wallets mentally and literally.
Identify successor custodians or platforms early in strategic reviews; last-minute letters of intent signed under duress rarely favor customers or regulators.
Document every regulator touchpoint during wind-down in the request log — phone calls included with summary emails confirming understandings.
Where CompliFi fits wind-down readiness
Orderly exit requires the same evidence discipline as growth — checklists, communications versions, reconciliation logs, and filing proofs in one vault. CompliFi helps California-focused teams maintain DFAL-shaped continuity artifacts and calendars so wind-down is executable, not a theoretical PDF in legal’s drive.
What to do this week
If you do not have an approved wind-down plan, draft triggers and customer communication phases this week and place them on the next board agenda. Run a one-hour reconciliation drill assuming you must return all custody balances in fourteen days.
Join the CompliFi waitlist at https://complifi.co/waitlist for vault and workflow support that keeps exit planning exam-ready alongside your licensing program — growth and graceful departure deserve the same operating rigor.