← Regulations / Holy See / Operating Models / Self-custodial wallet

Self-custodial wallet / non-custodial software in Holy See

Publisher of software where users hold their own private keys. The publisher never holds, controls, or has access to user funds.

Conditional AI-Generated · Unreviewed

Self-custodial wallet is conditionally permitted in Holy See without local incorporation, subject to AML obligations and none licensing burden.

Verdict Details

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

AML Obligations

  • No AML obligations — the publisher does not meet the VASP definition under Decree No. CCCLVI (356) of 19 May 2021 because it does not conduct exchange, safekeeping/administration, or transfer activities on behalf of another person
  • AML obligations only attach to VASPs as defined under va.aml.decree-no-ccclvi-356-of, which requires acting 'as a business' and 'for or on behalf of another natural or legal person' — self-custodial software publishing does not satisfy this

Key Restrictions

  • Publisher must not hold, control, or have access to user private keys or funds — custody triggers VASP classification under va.licensing.custody-providers-entities-providing-safekeeping
  • Publisher must not facilitate exchange between VAs and fiat or between different VAs on behalf of users, as that would trigger VASP classification under va.licensing.exchanges-entities-facilitating-the-exchange and va.licensing.payment-processors-dealing-with-vas
  • Any integration with on-chain transfer initiation services on behalf of users could be interpreted as 'participation in and provision of financial services' under va.aml.participation-in-and-provision-of

Key Risks

  • Regulatory ambiguity: the VA regulatory framework is primarily AML-focused and designed for traditional financial institutions — the status of non-custodial software publishers is not explicitly addressed and may be subject to interpretive risk
  • Extremely low market activity in VA (va.enforcement.low-cryptocurrency-activity-the-vatican) means there is no enforcement precedent to clarify the boundary between software publishing and VASP activity
  • ASIF could in the future broaden its interpretation of 'safekeeping and/or administration of VAs or instruments enabling control over VAs' (va.aml.safekeeping-andor-administration-of-vas) to encompass certain non-custodial products

Evidence

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

licensing 60% confidence

Exchanges: Entities facilitating the exchange between virtual assets and fiat currencies, or between different forms of virtual assets, would be classified as VASPs.

licensing 60% confidence

Custody Providers: Entities providing safekeeping or administration of virtual assets or instruments enabling control over virtual assets would be classified as VASPs.

licensing 60% confidence

Payment Processors (dealing with VAs): Entities involved in the transfer of virtual assets or providing services related to the issuance/sale of virtual assets would also fall under the VASP definition.

aml 40% confidence

Decree No. CCCLVI (356) of 19 May 2021, issued by the Secretariat of State (amending Law No. CCXCVII and introducing specific provisions for Virtual Assets and Virtual Asset Service Providers): This crucial decree specifically brought virtual assets and VASPs under the Holy See's AML/CFT regulatory scope, implementing FATF Recommendation 15 and its Interpretive Note. It defines virtual assets and VASPs and subjects them to the same AML/CFT obligations as traditional financial institutions.

aml 40% confidence

Defines "Virtual Asset Service Provider" (VASP) as any natural or legal person who, as a business, conducts one or more of the following activities or operations for or on behalf of another natural or legal person:

aml 40% confidence

Exchange between VAs and fiat currencies.

aml 40% confidence

Exchange between one or more forms of VAs.

aml 40% confidence

Safekeeping and/or administration of VAs or instruments enabling control over VAs.

aml 40% confidence

Participation in and provision of financial services related to an issuer's offer and/or sale of a VA.

enforcement 60% confidence

Low Cryptocurrency Activity: The Vatican City State is a unique, extremely small sovereign entity with a highly specialized financial system primarily focused on managing the assets of the Catholic Church and its charitable works, as well as supporting its diplomatic missions. It is not a center for commercial cryptocurrency activity or innovation.

enforcement 60% confidence

Robust AML/CTF Framework: The Holy See has significantly strengthened its anti-money laundering (AML) and counter-terrorist financing (CTF) framework in recent years, under the supervision of its financial intelligence and supervisory authority, the Autorità di Supervisione e Informazione Finanziaria (ASIF). This includes complying with international standards set by the Financial Action Task Force (FATF) and undergoing evaluations by MONEYVAL (the Council of Europe's AML body).

licensing 60% confidence

Local Presence: While there isn't a specific "local presence" requirement for external crypto businesses to set up shop (as this is not the Holy See's regulatory focus), any entity operating under its jurisdiction (e.g., Vatican banks or financial institutions) is, by definition, locally present. For foreign entities, the question of "local presence" is generally moot, as the Holy See is not seeking to attract such entities.

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 — a publisher of self-custodial (non-custodial) wallet software that never holds user private keys or funds is unlikely to be classified as a VASP under Vatican law, but the legal framework is untested and focused on AML/CFT for regulated financial institutions; no license or AML obligations attach so long as the publisher does not cross into exchange, custody, or transfer facilitation on behalf of users.

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?