Self-custodial wallet / non-custodial software in Dominican Republic
Publisher of software where users hold their own private keys. The publisher never holds, controls, or has access to user funds.
Self-custodial wallet is conditionally permitted in Dominican Republic without local incorporation, subject to AML obligations and low licensing burden.
Verdict Details
- Permitted
- conditional
- Local entity required
- No
- Licensing burden
- Low
- Last updated
- 2026-07-13
AML Obligations
- No AML obligations attach to pure software publishers that never hold, control, or have access to user funds, as they are not 'obligated parties' under Ley No. 155-17 (the law targets entities dealing with virtual assets in a professional capacity such as exchanges or custodians).
- If the publisher were deemed an obligated party, obligations would include CDD (identity verification, beneficial ownership identification, purpose of business relationship), risk-based due diligence (SDD/EDD), ongoing transaction monitoring, suspicious activity reporting to the UAF, appointment of a compliance officer, and record-keeping for 5 years.
- Sanctions screening obligations (UNSC, OFAC with USD nexus, EU lists) would apply if the software publisher has any U.S. financial system nexus or deals with U.S. persons/touch sanctioned jurisdictions.
Key Restrictions
- The publisher must not hold, control, or have access to user private keys or funds — this distinguishes it from custodial VASPs that trigger obligated-party status.
- The software must not facilitate transactions that touch Dominican-regulated financial institutions, as Resolución R-BC-004-2022 forbids banks from engaging with virtual assets.
- The Dominican Republic has no specific VASP licensing framework, so there is no pathway to be a 'licensed crypto business' — the entity operates in a regulatory grey zone for custody-free software.
Key Risks
- Regulatory ambiguity: The definition of 'obligated parties' under Ley No. 155-17 is broad and could theoretically be interpreted to include any professional dealing with virtual assets, including software publishers, creating legal uncertainty.
- Central Bank hostility: The BCRD has repeatedly warned that cryptocurrencies are not legal tender, are not regulated, and carries risks — this public stance may create consumer-protection or reputational exposure even if no formal prohibition applies.
- No specific licensing framework means that any regulatory action would be ad hoc and unpredictable; there is no established precedent for how a non-custodial wallet publisher would be treated.
- If the software generates revenue through embedded swaps, staking, or other on-chain services that touch custody or value transmission, the operator risks reclassification as an obligated party subject to full AML/CFT obligations.
- Enforcement risk from OFAC if the software allows users to transact with sanctioned entities or jurisdictions (e.g., Tornado Cash precedent) — the publisher could face U.S. sanctions risk even if compliant locally.
Evidence
This verdict synthesizes the following facts. Each fact links to its primary source(s).
Ley No. 155-17 contra el Lavado de Activos y el Financiamiento del Terrorismo (Law No. 155-17 Against Money Laundering and Terrorism Financing), enacted in June 2017.
This law defines "obligated parties" (sujetos obligados) which include a broad range of financial and non-financial businesses and professions. While it doesn't explicitly name "virtual asset service providers," entities dealing with virtual assets in a professional capacity (e.g., exchanges, custodians, transfer services) are likely to be interpreted as falling under its scope due to the nature of the financial services they provide or facilitate.
Resolución R-BC-004-2022 de la Junta Monetaria (Monetary Board Resolution R-BC-004-2022): This resolution, while not a VASP specific regulation, is crucial context. It forbids financial entities regulated by the Superintendencia de Bancos (SIB) from engaging with virtual assets, cryptocurrencies, or crypto assets. This means traditional banks cannot offer VASP services.
Absence of a Specific Licensing Framework: Unlike some other jurisdictions, the Dominican Republic does not currently have a specific regulatory framework for the licensing and supervision of cryptocurrency exchanges or related businesses. This means there isn't a specific set of crypto regulations for regulators to enforce against these entities.
Warnings and Advisories: The Central Bank of the Dominican Republic (Banco Central de la República Dominicana - BCRD) has repeatedly issued public statements and communications warning about the risks associated with cryptocurrencies, stating that they are not legal tender, are not backed by any government or central bank, and are subject to high volatility and lack of regulation.
Prohibition for Regulated Entities: Financial institutions regulated by the BCRD and the Superintendency of Banks (Superintendencia de Bancos - SB) are generally prohibited from dealing in or offering services related to cryptocurrencies.
UN Security Council Resolutions (UNSC Resolutions):
U.S. Department of the Treasury's Office of Foreign Assets Control (OFAC) Sanctions:
Crypto-Specific OFAC Sanctions: OFAC has explicitly sanctioned cryptocurrency mixers (e.g., Tornado Cash, Blender.io), exchanges (e.g., Garantex, Suex, Chatex), and wallets/entities associated with ransomware groups (e.g., Lazarus Group, Conti, Hive).
Verdict Attribution
- Source:
- AI-Generated · Unreviewed
- AI synthesized:
- 2026-07-13 (deepseek-chat)
- Last updated:
- 2026-07-13
- Confidence:
- medium
This verdict was produced by an AI model from the underlying facts. Confirm with counsel before relying on it for material decisions.
Conditionally permitted — pure non-custodial wallet software publishers that never hold user private keys or funds likely do not trigger VASP/obligated-party classification under Dominican law, but operate in a regulatory grey zone given the absence of a specific crypto licensing framework and the Central Bank's hostile stance; no formal AML obligations attach solely for software publishing, though any revenue-generating features (swaps, staking) could risk reclassification.
Questions this verdict aims to answer
- Does software publishing trigger VASP / MSB classification?
- Do AML obligations attach when no custody exists?
- What disclosure or consumer-protection rules apply?