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 28 August 2025 and published on 21 October, 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 licence. April 2026 parliamentary records document virtual asset bills; legislative processing does not establish an enacted 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 analyses 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 persons. Using a distributed ledger does not automatically make every developer an obliged person 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.

Article 83 provides testing environments for authorised 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. Equally, it prevents claiming that no supervised experimentation 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 dematerialisation 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 programmes, diligence and reporting from its obliged persons, 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 Tax Code Article 289.e, including digital assets among capital assets 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 addresses fraudulent pyramid schemes that may collect digital assets; it does not criminalise ordinary use. Law 44-26 leaves that provision unchanged and defers Articles 8–11 on corporate criminal liability for three months from 5 August 2026. That specific period neither postpones the entire Code nor permits presenting those corporate provisions as fully applicable in October.

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 authorisation, 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 licence. 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.