Virtual asset regulation in the Dominican Republic

A business planning a digital asset product in the Dominican Republic must first establish whether it acts as a payment provider, securities issuer or another operator. That classification changes the outcome: SIPARD prohibits specified activities for particular provider categories, while securities legislation requires assessment of the offering and legal representation of rights.

The project cannot rely solely on digital assets being mentioned in a tax reform or on the availability of supervised testing. It should establish who receives funds, what right the customer acquires and which permission supports the activity before choosing a wallet or token issuance architecture.

What payment, securities and digital asset provisions cover

Dominican regulation requires separating payments, securities and other digital asset activities. The Payment Systems Regulation, adopted on August 28, 2025, and published on October 21, contains express prohibitions for specified providers. Describing the framework solely as Central Bank warnings or a complete absence of legislation would be inaccurate.

Law 30-26 brings digital assets into capital-asset tax treatment, while the 74-25 Criminal Code mentions cryptocurrencies and tokens in pyramid fraud. Neither reference grants an exchange or custody license. Two bills were introduced in the Chamber of Deputies in 2026, 05400-2024-2028-CD on cryptocurrencies and 05569-2024-2028-CD on digital assets and crypto-assets, which the session of April 15, 2026 referred to the Standing Finance Committee. As of October 16, 2026, the legislative information system records both with an expired committee deadline and no promulgation; pending bills do not amount to a sectoral statute.

How BCRD, SIMV and UAF responsibilities differ

The Monetary Board establishes the framework for the Dominican Republic Payment System, SIPARD, and the Central Bank, BCRD, exercises the functions assigned by that regulation. The Superintendency of the Securities Market, SIMV, oversees public offerings and market participants under Law 249-17, whose Article 358 repeals and replaces Law 19-00.

The Financial Analysis Unit, UAF, receives and analyzes preventive information; obligations and supervision depend on the covered sector and person. Articles 31–33 of Law 155-17 distinguish financial and non-financial obliged entities, and none of their categories refers to virtual asset service providers. The national anti-money-laundering committee may add other risk activities by regulation, but none of the resolutions published by the UAF does so for these providers. Using a distributed ledger does not automatically make every developer an obliged entity or establish a general UAF VASP registration.

Restrictions on market access and payment testing

The SIPARD regulation prohibits virtual-asset-based products or services for payment or settlement system administrators, electronic payment entities, acquirers, subacquirers, ATM network administrators, digital wallet providers and payment initiation providers. The clauses appear in Articles 11.v, 17.w, 31.t, 33.l, 35.p, 37.j and 39.l. These are categories defined by the regulation; the restrictions are not extrapolated to all private holdings or every software application. In addition, the BCRD statement of September 30, 2021, which reiterates the June 2017 statement, warns that regulated financial-system institutions are not authorized to use virtual assets or carry out transactions with them within the Payment System and could be sanctioned under the Monetary and Financial Law.

Article 83 provides for testing environments for authorized payment providers. Where other providers or external users participate, prior BCRD non-objection, a product description, implementation plan, participant list and risk analysis are required. This procedure establishes neither a virtual asset exception nor general commercial permission. Nor, given its existence, can it be claimed that no supervised testing mechanism exists.

Requirements for a tokenized securities offering

Articles 47–53 of Law 249-17 govern representation and approval of publicly offered securities. Subject to statutory exceptions, they require dematerialization and book entries at a central securities depository. Offering approval does not guarantee solvency, price or investment quality. Before issuing a token, its securities classification and permissions for the issuer and each intermediary require assessment.

Articles 79–84 address entries, issuance documentation and the effects of registration and transfer. No evidence establishes that an entry on any blockchain replaces this system. A project must identify the right, obligor and legally effective register; transferring a token does not automatically convey real estate or dispense with underlying-asset formalities.

Distinguishing compliance, tax and criminal liability

Law 155-17 requires compliance programs, due diligence and reporting from its obliged entities, including specified securities intermediaries, trust businesses and real-estate participants. Assessment starts with actual activity, customers and powers over funds. Preventive compliance does not cure a sectoral prohibition or replace permission to raise funds or intermediate.

Article 19 of Law 30-26 amends Article 289(e) of the Tax Code, expressly including digital goods and crypto-assets in the capital-asset concept while retaining exclusions such as ordinary-course inventory, depreciable property and specified receivables. Guzmán Ariza's analysis provides professional context. No exemption, universal rate or identical treatment for every business transaction is inferred.

Criminal Code Article 240 criminalizes pyramid fraud that collects money or digital assets, such as cryptocurrencies, tokens or NFTs, through false promises of returns; it does not criminalize ordinary use. Article 243 penalizes anyone who habitually raises funds from the public to transfer them to third parties without prior authorization from the Monetary and Financial Administration or the SIMV, whatever the instrument used. Under its Article 393, the Code enters into force twelve months after its promulgation and publication. Law 44-26, published in Official Gazette 11254 of August 5, 2026, leaves those provisions unchanged and defers by three months, counted from that date, the entry into force of Articles 8 to 11 on the criminal liability of legal persons. That specific period does not postpone the rest of the Code.

What to resolve before designing commercial operations

Before development, document each entity’s activity and assess its SIPARD category. Where the project involves a securities offering, review authorization, legally effective records and transfer; a blockchain selected by the promoter does not itself establish compliance with those formalities.

The retrieved documentation establishes payment restrictions and a general securities route, but does not establish an operational general VASP license. Confirm sector instructions and legislative developments before launch. The overall assessment remains pending because comparable evidence on general access and custody is insufficient.

To understand how this framework applies to your project, discuss your case with our team.