Expert Contribution by Equilex
A company does not automatically need a crypto-service license simply because it launches a white-label non-custodial wallet. When users control their own keys and the company only provides software, the wallet itself may fall outside crypto-service licensing requirements.
The situation changes when the operator provides additional services, such as custody, exchange, order handling or transfers on behalf of clients.
Licensing requirements vary by jurisdiction, custody model and the services a business provides. This article focuses specifically on the European Union (under MiCA) and Canada (under FINTRAC), explaining which wallet features may trigger regulatory obligations in these two markets.
Adding regulated features after launch can mean rebuilding onboarding, transaction flows and compliance processes. Identifying potential licensing requirements before development helps avoid expensive architectural changes.
Launching a white-label non-custodial wallet does not, by itself, create a CASP (crypto-asset service provider) licensing requirement under the EU’s Markets in Crypto-Assets Regulation (MiCA).
If users retain control of their private keys and the company does not provide custody, exchange, order-related or transfer services on behalf of clients, the wallet may remain a software-only product.
Regulated features can also be provided by licensed partners. For example, a third-party crypto-asset service provider (CASP) may handle crypto purchases, swaps or fiat on-ramps under its own authorization, terms and compliance procedures.
In that arrangement, the wallet operator may not need its own CASP authorization for those services. The outcome depends on the actual user journey, contractual relationships and which company performs each regulated activity.
The important distinction is between providing wallet technology and providing financial or crypto-asset services through that technology.
MiCA distinguishes software providers from companies that provide regulated crypto-asset services.
Recital 83 of MiCA states that providers of non-custodial wallet hardware and software should fall outside the regulation’s scope.
The FATF’s 2021 guidance makes a similar distinction: businesses that only develop or sell unhosted wallet software are generally not treated as virtual asset service providers unless they also conduct or actively facilitate covered services as a business.
If users control their keys and the company cannot independently access or move their funds, the operator may simply be providing software. Branding the wallet or offering an administrative interface does not automatically turn the provider into a custodian.
However, custody arrangements must be assessed based on actual control over assets and signing mechanisms, including recovery systems and shared-key architectures.
For a closer explanation of the underlying technology, see what a non-custodial wallet is.
“The first thing I ask a wallet founder is whether anyone at the company can move or freeze a user’s funds,” says Oksana Krasilnikova, Head of Licensing at Equilex. “If the answer is yes, the regulator sees a custodian, whatever your marketing says.”
Regulators assess what a business actually does for its customers, rather than relying on the product’s name or technical description.
The table below summarizes key considerations in the EU and Canada.
| Feature | What determines the regulatory treatment | EU (MiCA) | Canada (FINTRAC and other rules) |
|---|---|---|---|
| White-label non-custodial wallet | Users control their keys; operator only supplies software | Software-only model generally outside MiCA | Software provision alone generally does not trigger MSB registration |
| Custody or shared-key (MPC) setup | Whether the company controls client assets or the means of access | Custody and administration for clients may require CASP authorization | Custody, related services and applicable securities rules require separate assessment |
| In-app swaps | Whether the operator executes, transmits orders or provides exchange services | Relevant exchange or order-related services may require CASP authorization | Virtual currency exchange services generally trigger MSB registration |
| Fiat on-ramp and off-ramp | Which entity conducts the exchange and handles fiat payments | Crypto-for-funds exchange may require CASP authorization; payment services may fall under separate rules | MSB registration may apply; qualifying fiat payment activities may also require Bank of Canada registration |
| Transfers and payouts | Whether the company provides transfers on behalf of clients | Transfer services for clients may require CASP authorization | Virtual currency transfer services generally trigger MSB registration |
A feature’s presence in the wallet interface does not, on its own, determine the licensing outcome. For example, a swap integration must be assessed according to who receives the order, provides the exchange service and assumes responsibility toward the customer.
The same principle applies to MPC systems. A shared-key architecture requires analysis of the operator’s actual authority over transactions, rather than assuming that every MPC configuration is custodial.
Companies providing regulated crypto-asset services in the EU generally require authorization as crypto-asset service providers under MiCA, unless a specific exemption or other permitted arrangement applies.
The EU-wide transitional period ended on 1 July 2026. According to ESMA’s statement, providers that have not obtained the necessary authorization cannot continue offering regulated crypto-asset services to EU clients based solely on previous national transitional arrangements.
MiCA authorization covers the services specified in the authorization and can generally be passported across the EU and EEA under the applicable framework.
The required authorization depends on the business model. Providing custody, exchanging crypto-assets, receiving and transmitting orders, and transferring crypto-assets on behalf of clients are distinct regulated services under MiCA.
In Canada, businesses providing virtual currency exchange or transfer services may need to register with FINTRAC as money services businesses (MSBs).
Companies operating outside Canada may also be required to register as foreign MSBs when they direct covered services at Canadian clients and provide those services to them.
Under FINTRAC’s requirements, dealing in virtual currency includes exchanging funds for virtual currency, exchanging one virtual currency for another, and transferring virtual currency at a client’s request.
Registration comes with ongoing compliance responsibilities, including:
Certain crypto-asset trading platforms may also fall under provincial securities regulation. Businesses performing qualifying fiat payment functions may need registration under the Retail Payment Activities Act, depending on the activities and applicable exclusions.
A Canadian MSB registration does not replace securities registration, payment-service registration or authorization required in another jurisdiction.
A wallet business does not always need to obtain every authorization itself.
A licensed partner, such as an exchange or fiat on-ramp provider, can provide regulated services directly to wallet users under its own authorization, contractual terms and customer verification procedures.
However, the arrangement must reflect the services actually performed. If the wallet operator independently provides an order-related, exchange or transfer service, the partner’s authorization may not cover the operator’s own activities.
| Aspect | Licensed partner | Your own authorization |
|---|---|---|
| License holder | The licensed service provider | Your company |
| Regulated customer relationship | Usually with the partner for its service | Directly with your company |
| Compliance responsibility | Partner handles its regulated activities; the wallet operator remains responsible for its own obligations | Your company manages the applicable compliance framework |
| Revenue model | Commercial agreement or revenue share | Fees generated from your authorized services |
| Launch considerations | Integration and partner onboarding requirements | Regulatory application, approval and ongoing compliance |
| Typical fit | MVPs, market testing and products using third-party regulated services | Products built around directly providing regulated financial or crypto services |
Working with a licensed partner can simplify the launch of certain features, but it does not eliminate the need to review the complete product architecture.
The partner also determines which customers it can accept under its compliance policies.
Several recurring mistakes create legal and operational problems for wallet businesses.
1. Calling a wallet non-custodial when the backend controls user funds
Regulators look at actual access and control. A recovery mechanism, shared signing arrangement or administrative function that gives the operator effective control over client assets may change the regulatory classification.
2. Assuming a licensed integration automatically covers the entire product
Connecting to a regulated exchange or payment provider does not mean every activity performed by the wallet operator falls under that provider’s license.
The contractual structure, customer relationship and technical flow must match the proposed regulatory model.
3. Using a Canadian MSB registration as authorization to operate in Europe
FINTRAC registration does not grant access to the EU market for regulated crypto-asset services. A business targeting both markets must assess the requirements separately.
4. Serving EU clients from outside the EU without the necessary authorization
Establishing a company outside the EU does not automatically exempt its services from MiCA when it targets EU clients.
MiCA provides a narrow reverse-solicitation exception for certain services initiated exclusively by the client. ESMA interprets this exception restrictively, so it should not be treated as a general alternative to authorization.
5. Adding swaps or payment services after launch without reviewing licensing
A wallet that originally operated as a software-only product may introduce regulated activities as it expands.
Licensing implications should therefore be reviewed before new features go live, not after customer transactions have already started.
Licensing and technical architecture should be considered together from the beginning of a wallet project.
Four decisions deserve particular attention.
1. Define the custody model
Decide who controls private keys, signing permissions and recovery mechanisms.
If your company participates in an MPC or shared-key arrangement, establish what transactions it can authorize, prevent or initiate. Those capabilities may be relevant to the custody assessment.
2. Define the swap and payment flows
Identify which entity receives customer instructions, executes transactions, handles fiat funds and provides regulated services.
The architecture must reflect whether those functions belong to the wallet operator or a licensed partner.
3. Select target markets early
A feature that triggers MiCA authorization in the EU may create different registration and compliance obligations in Canada.
Defining the launch markets before development helps teams avoid rebuilding onboarding, transaction and reporting systems.
4. Plan for address ownership verification
Under the EU Transfer of Funds Regulation, CASPs must assess ownership or control of a self-hosted address in certain transfers exceeding EUR 1,000.
Wallet products interacting with regulated service providers may benefit from technical capabilities such as message signing or other supported verification methods.
These requirements primarily concern regulated service providers, but they can influence the wallet functionality and integration requirements.
A well-defined wallet infrastructure architecture can help separate user-controlled wallet functions from services provided by regulated partners, while supporting the transaction flows and integrations required by the product.
A non-custodial wallet is not automatically a regulated crypto-asset service. The licensing question depends on what the operating company does with and for its users.
In the European Union, software-only non-custodial wallet provision may fall outside MiCA, while custody, exchange, order-related and transfer services can trigger CASP authorization requirements.
In Canada, providing wallet software alone generally does not require MSB registration, but virtual currency exchange and transfer services may bring a business within FINTRAC’s rules. Other regulatory requirements can apply depending on the product.
These conclusions concern the EU and Canada. Businesses operating in other jurisdictions must assess the rules applicable to their target markets separately.
The most effective approach is to determine the custody model, regulated functions and target markets before finalizing the wallet architecture.
Equilex, a crypto licensing consultancy working across multiple jurisdictions, helps businesses assess licensing requirements and prepare regulatory applications when authorization is necessary.
Once the regulatory model is defined, ND Labs can support the technical implementation through a white-label non-custodial wallet or custom crypto wallet development, depending on the product requirements.
The result is a wallet architecture built around both the user experience and the regulatory responsibilities of the businesses involved.
This expert contribution is provided for general informational purposes only and does not constitute legal or regulatory advice. The article focuses on the European Union and Canada.