MiCA and Crypto Treasury Custody: Self-Custody vs the CASP Line

A company treasury and a regulated crypto custodian look superficially similar — both hold crypto and private keys — but MiCA treats them very differently, and the first question a treasury should ask is the scope question, not the compliance one: do MiCA's custody rules even apply to us? Custodying crypto for clients is a regulated CASP activity; self-custodying your own treasury generally is not. This spoke is the treasury-custody angle specifically — that line, what the CASP custody obligations are if you cross it, and how the distinction interacts with your own accounting. For where MiCA's custody rules sit inside the broader regime, see the MiCA timeline.

The custody line in brief

• MiCA custody-and-administration obligations bind a CASP custodying on behalf of clients — safekeeping assets, the means of access (keys), or control for clients.
• A company self-custodying its own treasury is generally on the other side of that line, not a client-custody service. This is fact-specific and counsel-confirmed.
• CASP custody duties: segregate client assets (physically and legally, with separate DLT storage), keep an individual position register, hold a custody policy and agreement, and provide at least quarterly statements.
• Custody is an authorised CASP class with own-funds/insurance set by its authorisation tier — not one universal figure.
• Transitional: CASP authorisation from early 2025; member-state grandfathering of up to ~18 months (broadly to mid-2026), jurisdiction-specific.
• MiCA governs the custody service; it does not replace the treasury's own accounting and reconciliation.

The question that comes first

MiCA is Regulation (EU) 2023/1114. Its definition of custody and administration of crypto-assets on behalf of clients covers safekeeping crypto-assets, holding the means of access (private keys), or exercising control over them — for clients. The decisive treasury question is therefore one of scope:

• self-custodying your own treasury means holding your own assets, generally not a client-custody service;
• holding or controlling crypto for third parties is potentially a CASP custody service.

Treating an internal treasury as if it triggered the full CASP client-asset rules over-applies the regime; missing that your structure does hold for others under-applies it. Get the characterisation right first, with counsel, before any operational design.

What a CASP custodian must do

If the activity is a CASP custody service, MiCA requires (among other things):

The own-funds requirement is class-dependent: do not assume a single universal figure, because it follows the CASP's authorisation tier.

The transitional timing

MiCA's CASP regime applies with member-state transitional arrangements: CASP authorisation processes from early 2025, and a grandfathering period of up to around 18 months for existing providers depending on the member state (broadly up to around mid-2026). Exact dates are member-state-specific — France's transitional period, covered in the PSAN to CASP spoke, ends 1 July 2026, and the stablecoin titles followed their own clock (see MiCA stablecoins). If your activity is or becomes a CASP custody service, the authorisation and its transitional window are jurisdiction-specific and need to be confirmed with counsel.

Custody arrangement vs accounting

Whether self-custodied or held with a regulated custodian, the treasury still has to account for the assets — what changes is the audit evidence:

• under self-custody, existence evidence rests on key control;
• under third-party custody, it rests on the custody relationship and confirmations (see auditing crypto existence).

MiCA governs the custody service; it does not replace the treasury's own obligations to classify, value, reconcile, and keep an audit trail (see multisig treasury reconciliation).

Practical guidance

1. Characterise first — self-custody of your own treasury versus custody for clients — with counsel.
2. Do not over-apply the CASP client-asset rules to an internal treasury.
3. If it is a CASP custody service, design for segregation, the position register, the policy and agreement, and statements.
4. Treat own-funds as class-dependent and confirm the figure for your authorisation tier.
5. Track the member-state transitional window if authorisation applies.
6. Account and reconcile regardless — MiCA custody is not a substitute for treasury accounting.

How vendor tools relate to MiCA custody

Cryptio and Bitwave sit on the accounting and reconciliation layer, which is relevant whether the treasury is self-custodied or held with a CASP. The thing to confirm in any such tool is that it keeps a per-account/position register and audit trail supporting either custody model — that is accounting evidence, not the MiCA authorisation itself.

Where Wag3s fits

Whether your structure crosses the CASP custody line is a legal question for counsel, and Wag3s does not answer it. What it does, on either side of that line, is the accounting: Wag3s Ledger maintains the per-position register, reconciliation, and audit trail a treasury needs whether it self-custodies or uses a regulated custodian — supporting the financial side while the custody characterisation stays a counsel-confirmed legal question. See the Ledger product page and the Wag3s for accountants page.

Further reading

• Safe Treasury Setup Best Practices
• Multisig Treasury Reconciliation (Safe)
• Auditing Crypto Existence and Ownership
• MiCA Stablecoins (ART/EMT)
• Crypto Audit Trail and Piste d'Audit Fiable
• DAO Treasury

Edge cases that blur the self-custody/CASP line

Most treasury teams correctly identify themselves as not providing a custody service — they hold their own assets. But several common treasury structures introduce ambiguity that is worth naming.

Multi-entity group treasury. A parent company holds crypto in a wallet and on-lends it to three subsidiaries under intra-group arrangements. From one angle, the parent is still holding its own assets on behalf of the consolidated group. From another, the subsidiaries may have a legal claim on specific assets held by the parent, which could look like client-asset administration. Whether MiCA's custody regime applies depends on the legal structure of the intra-group arrangements and the degree of control each subsidiary has over the assets. Counsel-confirmed.

DAO treasury managed by a foundation. A Swiss foundation is appointed as the legal administrator of a DAO's treasury. The foundation holds private keys and signs transactions in accordance with DAO governance decisions. Is the foundation providing a custody service to the DAO (i.e., to the DAO's token holders as collective clients)? The answer depends on how the foundation's mandate is structured. Where the foundation has discretionary authority over assets that legally belong to others, a custody-service characterisation becomes plausible.

Protocol-managed yield positions. A DeFi protocol that holds user funds in smart contracts, earning yield on behalf of users, is performing a function that at least resembles custody and administration. MiCA explicitly addresses smart-contract-managed assets and has separate guidance on DeFi; the application of the CASP custody obligations to a protocol is a significant open question that ESMA-level guidance has begun to address but not definitively resolved.

Sub-custodian arrangements. A CASP that hires a third-party sub-custodian to hold client assets on its behalf is still the responsible CASP from the client's perspective. The CASP cannot outsource its MiCA custody obligations to the sub-custodian; it remains liable for the segregation, register, and statement obligations. The sub-custodian arrangement must be structured to flow those obligations through.

These cases are illustrations, not legal conclusions. Each is fact-specific and must be confirmed with counsel in the relevant member state.

Sources

• Regulation (EU) 2023/1114 (MiCA) — EUR-Lex official text: the definition of custody and administration of crypto-assets on behalf of clients (safekeeping assets, the means of access/private keys, or control for clients), the CASP segregation, position-register, policy/agreement and statement obligations, and the transitional provisions.
• ESMA — Markets in Crypto-Assets Regulation (MiCA): technical standards on CASP authorisation, own-funds and custody, and member-state transitional timing.
• Note on the key distinction: self-custody of a firm's own treasury versus a client-custody service is a fact-specific, counsel-confirmed characterisation; own-funds/insurance requirements are class-dependent rather than a single universal figure.