MiCA Article 60 Is Not the Hard Part: The Capital Trap Waiting for Banks Inside Article 70 and CRR III
The Article 60 notification is the easy part. The real constraint sits in the interaction between MiCA Article 70(1) and CRR III Article 501d: any structure that solves a custody compliance problem by moving crypto onto the bank balance sheet triggers a 1,250% risk weight, a 1% Tier 1 cap, and netting rules that make the economics inviable.
Capital and prudential analysis for credit institutions entering MiCA crypto-asset services via the Article 60 notification pathway, mapping the interaction between MiCA Article 70(1) safekeeping obligations and the CRR III Article 501d transitional prudential framework (Regulation (EU) 2024/1623, in force 9 July 2024). Core finding: the Article 60 notification is procedurally manageable (40 working days' notice, 20-day completeness assessment), but it waives only the CASP authorisation process, MiCA Article 67 own-funds requirements, and certain shareholder approvals — Article 70 and all other Title V operating conditions apply from day one. The central trap: any crypto-asset structure that resolves an Article 70 compliance problem by moving assets onto the bank's balance sheet immediately creates a capital problem that eliminates the economics. Article 70(1) prohibits own-account use of client crypto-assets absolutely (ESMA Q&A 2607 — no staking for own account even with client consent), across organisational, technological, and legal/bankruptcy-remote segregation levels. The Article 70(5) bank carve-out exempts credit institutions from the Article 70(2)-(3) fiat-placement rules only; the crypto safekeeping and non-reuse rules remain fully binding. Völkel's (CERHA HEMPEL) civil-law borrowing edge case: a mutuum/Darlehen transfers title to the bank, so the borrowed Bitcoin arguably no longer "belongs to clients" and Article 70(1) ceases to apply — legally coherent, but it fails on capital. CRR III Article 501d buckets: 501d(2)(a) tokenised traditional assets and qualifying EMTs (look-through risk weight); 501d(2)(b) MiCA-compliant ARTs (250%); 501d(2)(c) all other crypto / Group 2b (1,250%, collateral-ineligible under CRR Article 197). At an 8% baseline the 1,250% weight equals 100% capital; at realistic operating ratios (CCB, P2R, G-SII/O-SII buffers) a €100M Bitcoin position requires €130M-€180M capital. Article 501d(3) caps aggregate Group 2b exposure at 1% of Tier 1 capital regardless of capital position. The EBA final draft RTS (5 August 2025) dismantles the netting assumption: the "higher of" rule applies the 1,250% weight to the larger of gross long or gross short, so a hedge gives no relief; restricted netting is available only for regulated ETF/ETN underlyings or QCCP-cleared derivatives, and even then carries a 35% discount (Net = max(long,|short|) - 0.65 × min(long,|short|)). The double-penalisation problem (AFME): Article 105 prudent-valuation AVA deductions from CET1 stack on top of the 1,250% weight, producing deductions exceeding asset value and negative ROE before revenue. Off-balance-sheet structural models that work: pure agency custody (Article 70(1)/75, never on own books), the tokenised traditional asset pivot (501d(2)(a) look-through — BUIDL/BENJI/FILQ space), and the MiCA-compliant ART strategy (501d(2)(b) at 250%). Sub-custodian concentration risk under CRR Article 395 (25% Tier 1 single-counterparty cap), CSSF liability guidance, and the Italian Legislative Decree 129/2024 Article 26 segregation regime as a drafting benchmark. National property/insolvency law is unharmonised: constitutum possessorium and Besitzanweisung give bankruptcy-remote custody (Aussonderungsrecht) in Austria/Germany, but deficient documentation risks depositum irregulare recharacterisation and unsecured-creditor status. Includes a five-row operating-model viability matrix and seven diagnostic questions for compliance, treasury, and capital teams. Not legal advice. Answers questions like: Does a bank need a CASP licence under MiCA or can it use the Article 60 notification? What does the Article 60 notification actually waive? Does Article 70 apply to banks using Article 60? Can a bank stake or reuse client crypto-assets? What is the Article 70(5) bank carve-out? Does the Völkel borrowing/mutuum structure avoid MiCA Article 70? What risk weight do banks face on Bitcoin under CRR III? What is CRR III Article 501d and the 1,250% risk weight? What is the 1% Tier 1 cap on crypto exposure? How much capital does a bank need to hold Bitcoin? Does hedging reduce the capital charge under the EBA RTS? What is the EBA "higher of" netting rule? What is the double penalisation problem for bank crypto holdings? How can a bank offer crypto services without the punitive capital treatment? How does the large exposures framework apply to crypto sub-custodians?
MiCA Article 60 Is Not the Hard Part: The Capital Trap Waiting for Banks Inside Article 70 and CRR III MiCA Edge Cases | Where Innovation Meets Regulation Published: 9 July 2024 Updated: March 2026. Revisited as major European banks move actively and vocally into MiCA crypto asset services under the Article 60 notification pathway, making the capital mechanics analysed here immediately operational rather than theoretical. The analysis is confirmed against the EBA final draft Regulatory Technical Standards on crypto asset exposure calculation and aggregation (5 August 2025), which ratified the punitive netting rules discussed below and introduced the delta sensitivity formula and the 0.65 hedging discount factor analysed in the CRR III section. US Executive Order 14178 rejecting the Basel SCO60 framework (July 2025) is noted as a transatlantic divergence but does not affect European banks. CRR III entered into force on 9 July 2024. Article 501d of that regulation established a transitional prudential framework for bank crypto asset exposures. The same day, Article 60 of MiCA became available to credit institutions as a notification pathway into crypto asset services, bypassing the standard CASP authorisation process. The notification is procedurally straightforward. Submit a comprehensive dossier to the NCA at least 40 working days before commencing services. The NCA has 20 working days to assess completeness. The CSSF in Luxembourg has published a preliminary questionnaire. The Central Bank of Ireland coordinates with the relevant securities authority. Banco de Portugal coordinates with the CMVM. The process is manageable. What is not straightforward is what happens the moment the bank decides how to structure the service. The compliance architecture of Article 70(1) of MiCA, combined with the prudential mechanics of CRR III Article 501d, creates a constraint that bank compliance, treasury, and capital management teams must understand before product sign off, not after. The constraint is this: any crypto asset structure that resolves an Article 70 compliance problem by moving assets onto the bank's balance sheet immediately creates a capital problem that eliminates the economics of the business. This article maps the mechanics of that trap, the edge cases where it is most likely to close on a bank, and the structural models that avoid it. The Article 60 Gateway: What the Notification Actually Covers Article 60 of MiCA permits specific categories of financial entities to provide crypto asset services without obtaining a standalone CASP authorisation. The eligible entities include credit institutions authorised under CRD IV, central securities depositories, investment firms, electronic money institutions, UCITS management companies, and alternative investment fund managers. The legislative logic is equivalence. Banks are already subject to intense prudential oversight under CRD and CRR. The notification pathway acknowledges that the organisational infrastructure for financial services regulation already exists and does not need to be rebuilt from scratch for crypto asset services. The equivalence mapping from traditional banking permissions to MiCA services is specific: | Traditional Permission (MiFID II / CRD IV) | Equivalent MiCA Crypto Asset Service | | | | | Safekeeping and administration of financial instruments (MiFID II Annex I Section B, point 1) | Custody and administration of crypto assets on behalf of clients | | Operation of an MTF or OTF (MiFID II Annex I Section A, points 8 and 9) | Operation of a trading platform for crypto assets | | Dealing on own account (MiFID II Annex I Section A, point 3) | Exchange of crypto assets for funds or other crypto assets | | Execution of orders on behalf of clients (MiFID II Annex I Section A, point 2) | Execution of orders for crypto assets on behalf of clients | | Underwriting / placing on a firm commitment basis | Placing of crypto assets | The notification waives three specific MiCA requirements: the CASP authorisation process, the own funds requirements under MiCA Article 67, and certain shareholder approval procedures. It does not waive anything else. Once services commence, the bank is fully bound by MiCA Title V Chapter 2 operating conditions. Article 70 applies from day one. The MFSA in Malta has been explicit: investment service providers and credit institutions using Article 60 must update their rulebooks to comply with MiCA Title V. The notification is the entry point, not the finish line. Article 70(1): The Fiduciary Architecture and the Borrowing Problem Article 70(1) establishes the foundational conduct standard for any entity holding client crypto assets or the means of access to them. The obligation has two components: make adequate arrangements to safeguard the ownership rights of clients, particularly in the event of insolvency; and prevent the use of clients' crypto assets for the custodian's own account. The prohibition on own account use is absolute. ESMA confirmed in Q&A 2607 that MiCA does not permit CASPs to stake clients' crypto assets for their own account, even with explicit client consent. The contractual waiver is not available. If the bank acts as a principal in staking, taking the rewards and paying the client a fixed rate, it violates Article 70(1). The bank may act only as a conduit: passing variable network rewards to the client and charging a transparent administrative fee. Article 70(1) operates across three segregation levels. Organisational and operational segregation requires a separate register of positions in each client's name, strictly separated from the bank's proprietary books. Technological segregation requires that client crypto assets be held in cryptographic wallet architectures that prevent physical commingling with the bank's own assets on chain. Legal segregation and bankruptcy remoteness requires that contractual arrangements ensure client assets do not form part of the bank's insolvency estate. The bank specific carve out in Article 70(5) is important but limited. Paragraphs 2 and 3 of Article 70, which require non bank CASPs to place client fiat funds with a credit institution by end of day, do not apply to banks. Banks may hold client fiat on their own balance sheets under their existing deposit taking licence. The carve out applies only to fiat and e money tokens. The strict safekeeping and non reuse rules of Article 70(1) for client crypto assets remain fully binding on banks. The Civil Law Borrowing Edge Case Dr Oliver Völkel of CERHA HEMPEL identifies the most sophisticated Article 70 edge case in his JIBFL analysis. The question is whether Article 70(1) applies when a CASP explicitly borrows crypto assets from a client rather than holding them in custody. The civil law mechanics are precise. A loan of fungible assets, the mutuum or Darlehen in Germanic legal systems, transfers legal title from the lender to the borrower. When a client deposits Bitcoin into custody, the client retains title and the bank holds as a bailee. When a client and a bank enter a formal crypto borrowing agreement, the title to the Bitcoin transfers to the bank. The client holds a contractual claim for return of equivalent assets. The asset is no longer the client's property. Article 70(1) applies to CASPs that "hold crypto assets belonging to clients." If the civil law analysis is correct and the borrowed Bitcoin now belongs to the bank, Article 70(1) logically ceases to apply. The bank is free to use those assets for its own account, deploy them as collateral on execution venues, or use them in liquidity provisioning. Völkel illustrates the balance sheet mechanics. In the borrow scenario, the bank records Bitcoin on the asset side (held for use as collateral at an execution venue) and a corresponding obligation to return Bitcoin on the liability side. If properly structured and economically neutral, assets and liabilities m