Custodial and non-custodial wallets: implications

In the world of crypto-assets, the difference between custodial and non-custodial wallets looks like a technical detail. In reality it is the line that separates two business models with opposite regulatory implications. Anyone designing a service that touches clients’ wallets needs to understand from the outset which side of the line they are on, because that is what determines the obligations, the structure and even the feasibility of the project.

The question that decides everything: who controls the keys

The distinction revolves around a single thing: who holds the private keys, that is, who has effective control of the assets.

• Custodial wallet. The provider holds the keys on behalf of the client. It is the provider that, in fact, has the power to dispose of the assets. The client “owns” the balance but depends on the provider to move it.
• Non-custodial wallet. The keys are and remain in the user’s hands. The provider makes a tool available (software, interface) but never has access to the assets nor the power to dispose of them.

Everything else — obligations, risks, regulatory scope — flows from this difference.

Why custodial changes the regulatory profile

Holding crypto-assets on behalf of third parties means holding others’ values. In economic substance, this brings the activity close to custody and financial intermediation, with significant consequences:

• Anti-money laundering (AMLA). Holding and moving values on behalf of clients generally constitutes financial intermediation: client identification, clarification of the beneficial owner, transaction monitoring and reporting obligations are triggered, with affiliation to a self-regulatory organisation (SRO) or placement within a supervised entity.
• Treatment in the event of insolvency. How are the custodied crypto-assets held? Are they segregated and kept separate from the provider’s assets, so that they can be returned to clients in the event of bankruptcy? This is a central point in Swiss law and must be resolved in the structure, not left to improvisation.
• Organisational requirements. Key security, custody, internal procedures, operational and IT risk management become an integral part of the model.

Why non-custodial is (usually) lighter

If the provider never controls the keys, it does not hold others’ values: it makes a technological tool available. In many cases this places the activity outside the scope of financial intermediation, bringing it close to the supply of software. Note, however, that the classification depends on substance, not on the label. If the model adds functions that, in fact, give the provider control or a power of disposal — server-side “recoverable” keys, integrated exchange services, fund management — the line can shift and bring the activity back within the regulated scope.

Hybrid models: where the problems lurk

The most delicate cases are not the two pure extremes, but the intermediate architectures: “non-custodial” wallets with provider-managed key backup, multi-signature setups in which the provider holds a signature, services that combine wallets with exchange or staking functions. In all these configurations the question stays the same — does the provider, at any point, have the power to dispose of the client’s assets? — but the answer must be sought in the actual technical architecture, not in the product’s commercial name.

The practical implications for builders

Before writing a line of code, it is worth fixing three points:

1. Precisely define the custody model and document it: who controls the keys, at which moments, with which exceptions.
2. Map the anti-money-laundering obligations that follow and design the safeguards upstream, not downstream.
3. Resolve the matter of segregation and asset return, because it affects client trust and the relationship with banking partners.

How SIH ONE approaches the topic

SIH ONE deals with structuring and advisory: analysis of the custody model, classification of the activity (custodial vs non-custodial and hybrid), identification of the anti-money-laundering and regulatory scope, design of the corporate structure and safeguards. Where the activity requires an authorisation or an SRO affiliation, the regulated activities pass through authorised partners. The goal is that, before launching, you know which side of the line you are on and what it entails.

This content is informational and does not constitute legal or regulatory advice. The framework evolves: every model must be verified in the specific case.

Are you building a service with wallets and want to understand which scope you fall within? Let’s talk: we analyse your custody model and identify the correct structure, with the right partners where an authorisation is needed.