← Regulations / Maldives / Operating Models / Custodial SaaS

Custodial wallet / SaaS in Maldives

Hosted wallet provider that holds keys on behalf of end users, often white-labeled to businesses (custody as a service).

Conditional AI-Generated · Unreviewed

Custodial SaaS is conditionally permitted in Maldives without local incorporation, subject to AML obligations and medium licensing burden.

Verdict Details

Permitted
conditional
Local entity required
No
Licensing burden
Medium
Last updated
2026-07-13

AML Obligations

  • Implement robust KYC procedures for all customers (per AML/CFT Act No. 10/2014 and FATF Recommendations)
  • Conduct ongoing customer due diligence (CDD)
  • Monitor transactions for suspicious activity
  • Maintain records for a specified period
  • Report suspicious transactions (STRs) to the Financial Intelligence Unit (FIU) of the Maldives Monetary Authority
  • Implement sanctions screening
  • Appoint an AML Compliance Officer
  • Adhere to the FATF Travel Rule for virtual asset transfers
  • Custodial wallet provider must register as a VASP with the MMA/FIU due to 'safekeeping and/or administration of virtual assets or instruments enabling control over virtual assets' being a VASP activity
  • If the SaaS involves fiat payment processing (e.g., settling in MVR), a payment service provider license from the MMA and its associated AML obligations also apply

Key Restrictions

  • No specific 'qualified custodian' or VA custody license exists in the Maldives — custody is treated as a VASP activity under general AML/CFT law
  • No explicit segregation, insurance/bonding, proof-of-reserves, or cold-storage mandates exist in the regulatory framework — these are industry best practices only
  • Cryptocurrencies are not recognized as legal tender in the Maldives; the MMA has issued public advisories warning consumers about the risks of unregulated crypto activities
  • If the custodial wallet/SaaS touches fiat (MVR or other fiat) for payment processing, a payment service provider license from MMA is required, bringing capital requirements and local incorporation
  • The MMA does not currently license or provide regulatory oversight for pure crypto custody activities — operators would be operating in a regulatory gap with only AML/CFT compliance expected
  • The white-label client (the business using the SaaS) would also bear independent AML obligations as a VASP if they control customer relationships

Key Risks

  • Regulatory ambiguity — no dedicated VA custody framework means operators must self-interpret how the AML/CFT Act applies to custody-as-a-service models
  • The MMA has publicly warned against unregulated crypto activities and consistently stated it does not license or oversee crypto businesses, creating enforcement exposure if the regulator later deems custodial services as requiring a license
  • No segregation or insurance mandates mean customer assets lack statutory protection in case of hack, insolvency, or operational failure
  • The operator operates in a gray zone — the MMA could issue new guidance or enforcement action at any time as the Maldives responds to FATF pressure
  • If the SaaS enables white-label clients to offer services to Maldivian residents, those clients may themselves be unlicensed VASPs, creating downstream regulatory risk for the SaaS provider

Evidence

This verdict synthesizes the following facts. Each fact links to its primary source(s).

licensing 60% confidence

Custody Providers: Similar to exchanges, if a provider merely holds virtual assets (cold or hot storage) without engaging in other regulated financial activities (like fund management of traditional assets), there isn't a specific VA custody license. However, if the custody service is part of a broader financial service or if it involves managing client funds/assets that are then invested in traditional markets, existing licenses (e.g., for investment funds, trustees) might apply.

licensing 60% confidence

AML/KYC (Anti-Money Laundering / Know Your Customer): This is the most crucial requirement for any entity dealing with virtual assets in the Maldives, regardless of licensing. VASPs are expected to:

licensing 60% confidence

Maldives Monetary Authority (MMA): The central bank and financial regulator.

licensing 60% confidence

Prevention of Money Laundering and Financing of Terrorism Act (No. 10/2014): This is the core AML/CFT legislation in the Maldives. VASPs, even without specific licensing, are expected to comply with its provisions.

licensing 60% confidence

Financial Action Task Force (FATF) Recommendations: The MMA and the Maldivian FIU base their AML/CFT expectations for VASPs heavily on FATF standards, particularly Recommendation 15 and its Interpretive Note.

licensing 60% confidence

Local Presence: For any financial service that requires an MMA license (e.g., payment services), a physical local presence, typically in the form of a locally incorporated entity and local management, is usually mandatory. For purely crypto-related activities without a specific license, a local presence might not be legally mandated but is generally advisable for effective AML/CFT compliance and to engage with regulators.

licensing 60% confidence

Capital Requirements: There are no specific capital requirements for VASPs as VASPs yet. However, if a business falls under an existing financial license (e.g., payment service provider, money service business), then the capital requirements for that specific license would apply.

licensing 60% confidence

Processing payments in MVR (or other fiat) for goods/services, with crypto merely as an underlying settlement layer: This would likely require a payment service provider license from the MMA under the existing payment systems framework.

licensing 60% confidence

For purely crypto activities: For now, the focus would be on ensuring full compliance with the Maldivian AML/CFT Act and engaging proactively with the MMA and FIU regarding your operations and compliance framework.

aml 60% confidence

No specific "custody license": The Maldives does not currently have a dedicated license type explicitly for "cryptocurrency custodian."

aml 60% confidence

VASP Registration/Licensing: However, entities providing custodial services for virtual assets would likely fall under the definition of a Virtual Asset Service Provider (VASP) as defined by the AML/CFT Act and subsequent regulations. VASPs are subject to AML/CFT obligations and may require registration or licensing with the MMA/FIU.

aml 60% confidence

The definition of a VASP, consistent with FATF standards, includes entities that conduct one or more of the following activities or operations for or on behalf of another natural or legal person:

aml 60% confidence

Safekeeping and/or administration of virtual assets or instruments enabling control over virtual assets. (This is where custody falls)

aml 60% confidence

No explicit mandates: There are no specific regulatory mandates in the publicly available Maldivian virtual asset framework that explicitly require the segregation of client digital assets from the custodian's proprietary assets.

aml 60% confidence

No explicit requirements: There are currently no specific regulatory requirements for cryptocurrency custodians in the Maldives to hold insurance or bonding for potential losses (e.g., due to hacks, operational errors, or insolvency).

aml 60% confidence

No specific mandates: The Maldivian regulatory framework does not include specific technical requirements or mandates for the use of cold storage (offline storage) for client digital assets. Custodians are expected to implement appropriate security measures, but the specifics of how they secure assets (e.g., hot vs. cold storage percentages) are not dictated by regulation.

aml 60% confidence

No specific definition: The concept of a "qualified custodian" as seen in some jurisdictions (e.g., under the U.S. Investment Advisers Act) does not have a specific definition or regulatory framework within the Maldives' virtual asset laws.

enforcement 60% confidence

MMA's Consistent Position: The Maldives Monetary Authority has repeatedly stated that cryptocurrencies are not recognized as legal tender in the Maldives. They also do not provide licenses or regulatory oversight for any cryptocurrency-related activities or businesses operating within the country.

enforcement 60% confidence

Focus on AML/CFT: While there isn't a specific crypto regulatory framework, the Maldives, as a member of the Asia/Pacific Group on Money Laundering (APG), is working to strengthen its Anti-Money Laundering and Counter-Terrorist Financing (AML/CFT) regime. This includes addressing virtual assets in line with FATF recommendations, but this is more about developing future regulations rather than current enforcement actions against existing crypto businesses.

enforcement 60% confidence

Lack of Licensed Entities: Since no crypto businesses are licensed by the MMA, there are no regulated entities for the MMA to "enforce" against in the traditional sense (e.g., for non-compliance with licensing conditions or specific crypto-related regulations). Any potential criminal activity involving crypto would fall under general criminal law enforcement by the police, rather than specific financial regulatory enforcement.

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.

Conditional — custodial wallet/SaaS is permitted in the Maldives only as an unlicensed VASP subject to comprehensive AML/CFT obligations under Act No. 10/2014 and FATF standards, but operates in a regulatory gap with no dedicated custody license, no segregation or insurance mandates, and significant enforcement risk given the MMA's publicly stated position against unregulated crypto activities.

Questions this verdict aims to answer

  • What custody license / qualified-custodian status applies?
  • What segregation, insurance, and proof-of-reserves rules apply?
  • What AML obligations attach to the SaaS vs the white-label client?