EST · MMXXVI
Home/Services/Licensing & Registration/Institutional Digital-Asset Custody: Legal and Regulatory Design
Licensing & Registration

Institutional Digital-Asset Custody: Legal and Regulatory Design

Institutional Digital-Asset Custody: Legal and Regulatory Design. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee

An institutional fund announces a strategic allocation to digital assets and discovers that holding Bitcoin, Ether and stablecoins on behalf of third parties triggers custody regulation in three jurisdictions at once. The technical infrastructure – cold storage, multi-signature protocols, hardware security modules – is ready, but the legal perimeter is not. Whether the entity needs a standalone custody licence or can nest the activity within an existing payment-institution authorisation depends on which regime applies, how the assets are classified and whether the arrangement crosses a balance-sheet or off-balance-sheet line. Institutional digital-asset custody sits at the junction of regulated financial services, cryptographic key management and cross-border AML, and the design of the legal wrapper must precede the first client deposit.

This page maps the regulated perimeter, the segregation and governance obligations that follow, and the licensing pathways across the leading hubs. As regimes converge on the MiCA custody model and the Payment Services Act framework in Singapore, the path to compliant institutional custody becomes clearer – but not uniform. You will see where custody sits as a standalone activity, where it nests inside a broader CASP or VASP authorisation, and what the regulatory authority expects by way of key-management governance, insurance and sub-custody oversight. The analysis includes practical decision points for funds, exchanges and tokenised-asset platforms choosing where to obtain the relevant authorisation and how to structure the custodial chain when a single entity cannot serve every user jurisdiction.

What brings digital-asset custody into the regulated perimeter

Custody becomes a regulated activity when the entity holds, safeguards or administers digital assets on behalf of third parties and exercises control over the private keys or signing authority required to move those assets. The precise trigger varies by framework. Under MiCA, the custody and administration of crypto-assets on behalf of clients is one of the enumerated CASP services; an entity providing it must hold a CASP authorisation and meet dedicated safeguarding requirements. Under Singapore's Payment Services Act, the custody of digital payment tokens falls within the regulated DPT service set and requires either a standard payment institution or a major payment institution licence, depending on transaction thresholds. VARA in Dubai regulates custody as a separate Virtual Asset Activity, and the VARA Custody Rulebook prescribes the governance, segregation and sub-custody model the licensee must adopt.

The common thread is control. If the client retains sole control of the private keys – for example, through a non-custodial wallet or a hardware device the provider never touches – the arrangement typically falls outside the custody perimeter. But if the provider generates the keys, holds them in a multi-signature quorum or manages a hardware security module on the client's behalf, the activity is custodial and the relevant regime applies. In our cross-border practice, operators seeking to serve institutional clients across multiple jurisdictions discover that the same technical architecture can map onto three different licensing requirements depending on where the custodian is domiciled, where the client sits and where the keys are generated or held.

The classification of the digital asset itself influences the regulatory route. MiCA draws a line between asset-referenced tokens, e-money tokens and other crypto-assets; custody of each falls under the CASP regime, but the capital and reserve obligations differ. In jurisdictions that classify certain tokens as securities – Hong Kong's VATP regime covers virtual assets that are securities or deemed securities – custody may require a Type 1 securities licence or equivalent, not solely a VASP registration. The entity must pressure-test the asset classification in each relevant jurisdiction before committing to a custody model.

For an institutional fund or exchange planning to offer custody, the first legal question is whether the business model crosses the custody threshold in any of the jurisdictions where clients or assets sit. If it does, the second question is whether the required authorisation can be obtained in the chosen domicile or whether the entity must restructure to place custody in a separate licensed vehicle. Map your custody perimeter against the relevant regimes before you deploy the infrastructure.

Segregation and safeguarding obligations under MiCA, VARA and the PSA

Once custody falls inside the regulated perimeter, the regime imposes safeguarding and segregation obligations designed to protect client assets from the custodian's insolvency and to prevent commingling with the entity's own holdings. Under MiCA, CASPs providing custody must segregate client crypto-assets from their own and from other clients' assets where requested; they must maintain records that allow each client's position to be reconstructed at any time, and they must implement policies to prevent the use of client assets for the entity's own account. The framework requires that custody arrangements be disclosed in the client agreement and that the CASP obtain explicit consent before using client assets in any transaction.

VARA's Custody Rulebook goes further, mandating on-balance-sheet or off-balance-sheet segregation at the blockchain level where technically feasible and requiring that the custodian maintain a real-time reconciliation between the internal ledger and the on-chain state. The rulebook prescribes key-management governance standards – separation of duties, multi-signature quorums for large transfers, hardware security module controls – and requires that the custodian's systems log every access to private-key material. In a recent Dubai licensing engagement, a payments company restructured its custody offering to place client assets in segregated wallets with dedicated signing keys, precisely to meet the VARA segregation expectation before application.

Singapore's Payment Services Act requires that a DPT service provider holding customer digital payment tokens safeguard them by holding them on trust or through other arrangements that give the customer priority in the event of insolvency. The MAS Notice on Prevention of Money Laundering and Countering the Financing of Terrorism sets out further expectations around cold-storage ratios, insurance and the use of sub-custodians. Operators we advise routinely structure custody as a statutory trust under Singapore law, documented in the customer agreement, to satisfy the safeguarding obligation and to ensure that client tokens do not form part of the custodian's estate if the custodian fails.

The practical implication is that institutional custody requires legal segregation at the contractual and insolvency level, technical segregation at the wallet or address level where the blockchain permits it, and accounting segregation in the internal ledger. The entity must document how each layer operates, how reconciliation occurs and what happens to client assets if the custodian becomes insolvent or suffers a security breach. For a tokenised-asset platform or a digital-securities issuer building a custodial layer into the primary offering, this means designing the key-management model and the client agreement together, not in sequence.

Key-management governance: policies, quorums and audit trails

The cryptographic keys that control blockchain assets are the legal equivalent of the vault combination in traditional custody. Regulators in the leading hubs expect the custodian to implement key-management governance that reduces the risk of unauthorised access, insider theft and single-point-of-failure scenarios. The VARA Custody Rulebook requires that private keys be generated and stored in a secure environment – typically a hardware security module certified to a recognised standard – and that access to key material be logged, monitored and subject to role-based controls. The rulebook mandates multi-signature arrangements for high-value transactions, meaning that no single individual can authorise a transfer above a defined threshold without a second or third signatory approving the operation.

Under MiCA, CASPs must implement internal control mechanisms and ICT security policies that address the protection of cryptographic keys, the segregation of functions and the continuity of service in the event of system failure. ESMA's technical standards, expected to take effect in stages from mid-2024 through 2026, will set detailed requirements around key generation, backup and recovery procedures, and the use of third-party key-management services. In our regulatory practice, we advise CASP applicants to document the key-management policy in a standalone annex to the application, mapping each control to the corresponding MiCA obligation and identifying the individuals or systems responsible for each step.

Singapore's MAS has signalled that custodians should adopt cold-storage arrangements for the majority of client digital payment tokens – the precise ratio varies by the custodian's risk profile and insurance coverage – and that hot wallets used for day-to-day transfers must be subject to transaction limits and real-time monitoring. The key-management policy must address how keys are rotated, how they are backed up and what happens if a key is lost or compromised. For a fund or an exchange holding tokens worth tens of millions of dollars, a key-compromise event can trigger both a client loss and a regulatory breach, so the governance model is not a technical detail – it is a core compliance control.

In practice, institutional custody operators structure key management as a policy-and-procedure matrix: cold-storage keys held in geographically distributed HSMs, accessed only during scheduled transfer windows; hot-wallet keys subject to velocity limits and multi-approval workflows; and a disaster-recovery protocol that allows key reconstruction from encrypted backups held by independent custodians or notaries. The entity must test the recovery protocol regularly and document the results for the regulator. Operators we advise routinely conduct a tabletop exercise simulating a key-loss or HSM-failure scenario before the licence application is filed, precisely to demonstrate that the governance model works under stress.

Insurance and sub-custody arrangements: risk allocation when assets move

Institutional clients expect that custodied digital assets are insured against theft, loss and operational failure. Regulatory frameworks increasingly require or encourage custody insurance as a condition of authorisation or as a factor in the capital calculation. MiCA does not mandate insurance but allows member-state regulators to set their own expectations; several NCAs require that CASPs hold cyber-insurance or crime insurance covering the value of assets under custody, with coverage limits adjusted to the scale of the operation. VARA requires that custody licensees maintain professional indemnity insurance and, where client assets exceed a defined threshold, obtain specific coverage for digital-asset loss or theft.

The insurance market for digital-asset custody remains thin, and premiums are high for entities without a track record or those holding volatile assets. Insurers typically require that the custodian demonstrate robust key-management controls, cold-storage arrangements and third-party security audits before they will quote coverage. In a recent structuring matter, a tokenised private credit fund seeking to custody its own on-chain loan certificates discovered that the insurer would cover the assets only if they were held by a licensed third-party custodian with an established insurance programme; the fund ultimately placed custody with a Singapore-licensed entity and treated the custodian's insurance as part of the overall risk-mitigation stack.

Sub-custody introduces a second layer of risk and regulatory expectation. A primary custodian may delegate custody of certain assets to a sub-custodian – for example, because the sub-custodian operates in a jurisdiction where the primary custodian is not licensed, or because the sub-custodian specialises in a particular blockchain or token type. MiCA requires that CASPs using sub-custodians conduct due diligence on the sub-custodian's financial stability, its safeguarding arrangements and its insurance coverage, and that the CASP remain liable to the client for any loss arising from the sub-custody arrangement. VARA's rulebook sets out similar expectations and requires that sub-custody agreements be approved by the VARA supervisor before they take effect.

The practical challenge is that many sub-custodians sit in jurisdictions where digital-asset custody is unregulated or where the regulatory standard is lower than the primary regime. The primary custodian must document how it satisfies itself that the sub-custodian meets the same segregation, key-management and insurance standards the primary regime requires. In cross-border custody structures, this often means negotiating bespoke contractual protections – indemnities, minimum insurance thresholds, audit rights – and obtaining legal opinions confirming that client assets held by the sub-custodian are protected in the event of the sub-custodian's insolvency.

Licensing pathways by jurisdiction: CASP, DPT, VARA and standalone custody

The route to a custody authorisation depends on the jurisdiction, the entity's broader business model and whether custody sits as a standalone activity or as one of several services. Under MiCA, custody is one of nine enumerated CASP services, so an entity that provides custody alongside trading, exchange or portfolio management can apply for a single CASP authorisation covering all activities. The authorisation process runs through the national competent authority in the member state where the entity is established; once authorised, the CASP can passport custody services across the EU and the EEA. The application timeline varies by member state – Lithuania and Malta historically offered faster processing, though the MiCA transition has extended some timelines – and the capital requirement is set according to the service mix and the scale of client assets.

In Singapore, custody of digital payment tokens is a regulated DPT service under the Payment Services Act. An entity providing custody must hold either a standard payment institution licence (if annual transaction volumes are below the major-institution threshold) or a major payment institution licence (if volumes exceed it). The MAS applies a rigorous fit-and-proper assessment to key personnel, requires that the entity demonstrate adequate capital and insurance coverage, and expects that the custody model aligns with the safeguarding and AML obligations set out in the relevant MAS notices. The application process typically takes several months, and the MAS frequently requests additional documentation on key-management governance and sub-custody arrangements before granting approval.

VARA in Dubai issues activity-based licences, and custody is one of the enumerated Virtual Asset Activities. An entity can apply for a standalone custody licence or for a multi-activity licence that includes custody alongside trading, advisory or other services. The VARA application process is staged: an initial assessment of the business plan and the individuals behind it, followed by a detailed review of policies, systems and controls once the applicant is admitted to VARA's sandbox-like preparatory phase. The custody licence application must include the key-management policy, the segregation model, the insurance arrangements and evidence of compliance with the VARA Custody Rulebook. Operators we advise routinely spend several months in dialogue with VARA before the final licence is issued, addressing specific questions about sub-custody, insurance and the technical architecture.

In Hong Kong, custody of virtual assets that are or are deemed to be securities requires a Type 1 securities licence from the SFC; custody of non-security tokens falls under the VASP licensing regime. The SFC expects custodians to meet institutional-grade standards – segregation, insurance, annual audits – and to demonstrate that the key-management model aligns with the SFC's guidelines on the custody of digital assets. The VASP application process includes a detailed review of the applicant's systems and controls, its AML programme and its financial resources, and the SFC has broad discretion to impose licence conditions tailored to the custody model.

For entities operating across multiple hubs, the typical structure is a hub-and-spoke model: a primary licensed entity in the entity's home jurisdiction, with sub-custody or agency arrangements in jurisdictions where clients or assets sit. The primary entity holds the client relationship and the regulatory authorisation; local agents or sub-custodians hold keys or assets in their respective jurisdictions under service agreements that allocate liability, insurance and regulatory reporting obligations. The model works only if the primary entity can demonstrate to its home regulator that it exercises effective oversight of the sub-custodians and that client assets remain segregated and protected across the entire chain.

Cross-border interaction: tax, banking and the Travel Rule in custody arrangements

Institutional custody does not sit in isolation; it interacts with tax treatment, banking relationships and AML obligations in each jurisdiction where the custodian or the client operates. The tax classification of custodied digital assets – whether they are treated as property, financial instruments or something else – determines whether the custodian has withholding, reporting or capital-gains obligations. In jurisdictions that apply the situs rule, the location of the private keys or the custodian's domicile may determine where the asset is deemed to sit for tax purposes, which in turn affects estate-planning and tax-residency questions for high-net-worth clients.

Banking presents a practical constraint. Many custodians discover that obtaining a banking relationship capable of handling fiat on- and off-ramps for institutional clients is more difficult than obtaining the custody licence itself. Banks in the leading hubs apply stringent due diligence to digital-asset custodians, and some will bank only entities that hold a custody licence in a recognised jurisdiction and that maintain insurance coverage above a defined threshold. In a recent matter, a CASP applicant in Malta secured the custody authorisation but could not open a bank account with a Maltese bank willing to handle euro settlements; the entity ultimately placed banking in Lithuania and routed custody-related fiat flows through a Lithuanian payment institution under a service agreement. The lesson is that the banking and custody structures must be designed together, not sequentially.

The Travel Rule – the obligation under FATF Recommendation 15 to pass originator and beneficiary information with a virtual-asset transfer – applies to custodians that facilitate transfers on behalf of clients. The precise data set and the threshold at which the rule applies vary by jurisdiction, but the expectation is converging: custodians must collect, verify and transmit counterparty data when a transfer involves another regulated VASP or when the transfer exceeds a de-minimis threshold. In practice, this means that the custodian's systems must integrate with Travel Rule messaging protocols – TRUST, Sygna or similar – and that the custodian's AML programme must address how it handles incomplete or missing counterparty data.

For an institutional fund using a custodian in one jurisdiction to hold assets on behalf of investors in three others, the cross-border reality is that the custody arrangement triggers AML obligations in multiple places: the custodian's home jurisdiction, the investor's jurisdiction and potentially the jurisdiction where the underlying blockchain activity occurs. The fund's legal team must map the obligations across the stack and confirm that the custodian's AML programme covers every node where data must be collected or reported. If it does not, the fund may need to impose additional contractual obligations on the custodian or to place certain investors in a separate custodial sub-structure to isolate the AML risk.

Common mistakes and a self-assessment checklist

The most common mistake in institutional custody design is assuming that the technical infrastructure – cold storage, multi-signature, HSMs – satisfies the regulatory obligation without a corresponding legal and governance wrapper. A technically sound custody model fails the licensing test if the entity cannot demonstrate segregation at the insolvency level, if the key-management policy is undocumented or if the insurance coverage is insufficient for the scale of assets under management. Regulators in the leading hubs expect to see a policy manual, an audit trail and evidence that the entity has tested its disaster-recovery procedures, not merely a description of the cryptographic architecture.

A second mistake is treating custody as a purely domestic activity when the client base or the asset footprint is cross-border. An entity domiciled in Singapore that custodies tokens for clients in the UAE, the EU and Hong Kong is subject to regulatory expectations in all four jurisdictions, and the failure to register or to comply with local AML obligations in any one of them exposes the entire operation to enforcement risk. The custody structure must map the regulatory perimeter in every relevant jurisdiction before the first client asset is accepted, and the entity must confirm that it holds the necessary authorisations or that it operates under a valid exemption.

A third mistake is underestimating the insurance and banking constraints. Custody insurance is expensive and coverage is limited; entities that wait until after the licence is granted to approach insurers often discover that the available coverage is lower than the regulator's expectation or that the premium makes the business model unviable. Similarly, banking relationships for custodians are scarce, and the due diligence process can take months. The entity should open dialogue with insurers and banks in parallel with the licensing application, not after it.

Self-assessment checklist (review before filing a custody licence application):

  • Does the business model involve holding, safeguarding or administering digital assets on behalf of third parties?
  • Are client assets segregated from the entity's own holdings at the wallet, ledger and insolvency level?
  • Is the key-management policy documented, with multi-signature quorums for high-value transactions and HSM controls for key generation and storage?
  • Does the entity hold insurance covering theft, loss and operational failure, with coverage limits aligned to the scale of assets under custody?
  • If sub-custodians are used, has the entity conducted due diligence on each sub-custodian's licensing status, safeguarding arrangements and insurance?
  • Does the entity have a banking relationship capable of handling fiat on- and off-ramps for custody clients, and has the bank confirmed its willingness to serve a digital-asset custodian?
  • Does the AML programme address the Travel Rule, including data collection, verification and transmission to counterparty VASPs?
  • Has the entity tested its disaster-recovery and key-reconstruction procedures, and are the results documented for the regulator?

A "no" or "partial" answer to any of these questions signals a gap that must be closed before the custody licence application is filed. If the custody structure crosses multiple jurisdictions, run the checklist separately for each jurisdiction to confirm that no regulatory obligation is left uncovered.

Related at OBOLUS

FAQ

How long does a crypto licence take to obtain?

The timeline varies by jurisdiction and by the complexity of the application. Under MiCA, a CASP authorisation in a faster member state such as Lithuania or Malta historically took four to six months, though the MiCA transition has extended some timelines. In Singapore, a major payment institution licence for DPT custody typically takes several months, with the MAS requesting additional documentation during the review. VARA in Dubai operates a staged process that can span three to six months from initial submission to final licence issuance, depending on the quality of the application and the responsiveness of the applicant. For a multi-activity licence covering custody, trading and advisory, the timeline is generally longer than for a single-service application, because the regulator must assess systems and controls across the entire service set. Engaging counsel before the application is filed can reduce the back-and-forth and compress the overall timeline.

Which jurisdiction suits my crypto business?

The answer depends on where your clients sit, where you can bank and where the regulatory cost aligns with your revenue model. Entities serving EU clients or seeking to passport across the EEA gravitate toward a MiCA CASP authorisation in a member state with a developed crypto sector, such as Lithuania, Malta or Ireland. Entities targeting the Middle East or seeking a common-law legal framework often choose Dubai under VARA or Abu Dhabi under the ADGM/FSRA regime. Singapore remains the preferred hub for entities focused on Asia-Pacific institutional clients, given the MAS's reputation for rigorous but predictable supervision and the depth of the banking and custody-infrastructure ecosystem. For entities with a global client base, a hub-and-spoke model with a primary licence in one jurisdiction and sub-custody or agency arrangements in others is often the most practical approach. The jurisdiction question cannot be answered in the abstract; it requires mapping your client geography, your banking options and your operational capacity against the regulatory expectations in each candidate hub.

Do I need a separate custody licence?

It depends on the jurisdiction and whether custody sits alongside other regulated activities. Under MiCA, custody is one of several CASP services, so an entity that provides custody alongside trading or portfolio management applies for a single CASP authorisation covering all activities; a separate custody licence is not required. In Singapore, custody of digital payment tokens is a DPT service under the Payment Services Act, so the entity needs a payment institution licence, but it can combine custody with other payment services under a single licence. VARA in Dubai issues activity-based licences, and custody is a separate Virtual Asset Activity; an entity can apply for a standalone custody licence or for a multi-activity licence that includes custody. In Hong Kong, custody of security tokens requires a Type 1 securities licence, while custody of non-security tokens requires a VASP licence; an entity may need both if it custodies a mixed portfolio. The critical question is whether the custody activity can be nested within an existing authorisation or whether a separate application is required. Operators we advise routinely conduct a jurisdiction-by-jurisdiction regulatory mapping before committing to a custody model, precisely to avoid the situation where a single business line triggers multiple licensing obligations that were not anticipated.

About OBOLUS

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. In our cross-border work, we routinely separate the regulated custody perimeter from the technical one, map the licensing requirements across the client and asset footprint, and design the key-management governance and sub-custody structures that satisfy the regulator before deployment. For a scoped assessment of your custody model and the licensing pathway in your target jurisdictions, contact info@oboluslaw.com.

By Aisha Tan, Licensing & Jurisdictions Analyst – Aisha specialises in digital-asset licensing pathways across the EU, the Middle East and Asia-Pacific, with a focus on custody, exchange and VASP registration frameworks.

This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours