Jump to

Crypto-Asset Custody in Türkiye: Client Asset Segregation (Law 6362 Art. 35/C), Custodians and Banks (III-35/B.2)

Crypto-Asset Custody in Türkiye: Client Asset Segregation (Law 6362 Art. 35/C), Custodians and Banks (III-35/B.2)

An investor doing diligence on a Turkish crypto platform asks one question before any other: where exactly are the clients’ coins, and what happens to them if the platform fails? A bank’s treasury team receives a different brief: the board wants to offer crypto-asset custody to platforms and needs to know whether that means a new company, new capital and a second regulator. Both questions are answered by the same rules. Article 35/C of the Capital Markets Law No. 6362, inserted by Law No. 7518 (Official Gazette 2 July 2024, No. 32590), sets the principle that client assets are segregated, and Communiqué III-35/B.2 of the Capital Markets Board (Sermaye Piyasası Kurulu, CMB), with Communiqué III-35/B.1 (both Official Gazette 13 March 2025, No. 32840), says who may act as a custodian (saklama kuruluşu), how wallets and keys must be run, how much may sit on the platform’s own wallets, how records are reconciled and how much capital a custodian needs. This article walks through those rules in the order a founder or a bank will meet them. For the wider programme, see the CASP compliance page.

The starting point: Article 35/C(6) and the self-custody default

Article 35/C(6) of the Law begins with a principle that surprises many founders: the rule is that platform clients’ crypto-assets are kept in the clients’ own wallets. Custody is the exception for assets that clients choose not to hold themselves, and that exception is tightly drawn: the service must be provided either by banks authorised under the Board’s regulation and approved by the Banking Regulation and Supervision Board (BDDK), or by other institutions the Board has authorised; and client cash must be held at banks. The same paragraph removes a comfort that bank involvement might suggest: crypto-assets held at banks, and client cash held in this context, are not covered by the deposit insurance in Article 63 of the Banking Law No. 5411. The Board may set separate custody rules for individual crypto-assets or categories. Communiqué III-35/B.2 repeats the default in Article 24(1) and defines the service in Article 24(2): a custodian may serve platform clients and may also serve clients directly, but a wallet service in which full control of the private key stays with the investor is not custody at all. Article 35/C(4) of the Law adds two warnings for every client disclosure: a Board licence is not a public guarantee, and crypto-assets are outside the investor compensation scheme of Article 82.

Segregation and protection from creditors: Article 35/C(7)

Article 35/C(7) is the provision investors are really asking about. Client cash and crypto-assets are separate from the assets of the crypto-asset service provider, and the provider’s records must be kept accordingly. Client cash and crypto-assets held with a provider, in whatever manner, cannot be seized, pledged, included in the bankruptcy estate or made subject to an interim injunction on account of the provider’s debts, even for public receivables; the mirror image also holds, so the provider’s own assets cannot be reached for the clients’ debts. The paragraph then applies Article 46(7) and (8) of the Law to crypto providers: client cash at banks is kept in separate accounts opened for the provider’s clients; those accounts cannot be shown as loan collateral or encumbered in the provider’s favour; and the bank keeps them in a separate account in its books and reports on them to the Board. Communiqué III-35/B.2 Article 51 adds the mechanics: platforms may not hold cash at all; the bank account must be designated in writing as a client account with the bank’s confirmation within fifteen business days; and deposits are accepted only by electronic transfer from the client’s own bank account. Under Article 99/B(7), attachment and seizure requests against client assets are executed exclusively by the provider. Under Article 99/B(4), the provider is liable under Article 71 of the Code of Obligations No. 6098 for crypto-asset losses caused by its systems, cyber attacks, security breaches or staff conduct. Under Article 110/A, board members and other members of a provider who embezzle crypto-assets entrusted to them face eight to fourteen years’ imprisonment. Communiqué III-35/B.1 Article 49(1)(e) states the civil-law version: a provider may not dispose of client crypto-assets or cash without a right or authority to do so.

Who may be a custodian: banks and authorised institutions

Communiqué III-35/B.2 Article 25 names the two routes that Article 35/C(6) of the Law opened: banks authorised under the Communiqué and approved by BDDK, and other institutions authorised by the Board. A non-bank custodian is a crypto-asset service provider in its own right and goes through the two-stage permission in Communiqué III-35/B.1: a joint-stock company with registered shares, fully paid minimum capital and an exclusive purpose (Article 5(1)), qualified shareholders (Article 6), a trade name containing “kripto varlık saklama kuruluşu” (Article 7(2)) and units dedicated exclusively to custody (Article 9(3)). Banks take a shorter route: the establishment, shareholder, trade-name, general-manager and board requirements do not apply to them (Articles 5(2), 6(5), 7(6), 14(7), 15(6)), and staff rules apply only to the custody unit (Article 13(5)). A bank must still meet the operational conditions in Article 9(1)(c), (ç), (d), (f), (g), (ğ) and (h): capital adequacy, organisation, staff, TÜBİTAK-compliant security infrastructure, internal systems, MKK integration and private-key infrastructure. Under Article 9(6), BDDK’s favourable preliminary opinion is needed before the Board assesses a bank’s application, and the service can begin only after BDDK grants an activity-extension permit. Article 9(7) draws a staff wall: platform managers and staff may not work at a custodian and vice versa, bank managers excepted. The application guide covers the file for either route.

How custody must be run: wallets, keys and approvals

Article 26 of III-35/B.2 sets the operating model. Client crypto-assets are held by the custodian separately from its own accounts, in the platform’s name, on an omnibus basis (Article 26(1)); platform clients do not sign a separate contract with the custodian (Article 26(2)). Where the custodian serves clients directly, it signs its own contract, explains the risks and holds their assets per client (Article 26(3)). All keys and key shards must sit in secure hardware modules (güvenli donanım modülü) in line with the TÜBİTAK infrastructure criteria (Article 26(4)), a written custody procedure adopted by the board is reviewed at least annually (Article 26(5)), and the hot wallet (sıcak cüzdan) may hold up to 5 per cent of total client assets, rising to a maximum of 10 per cent where the custodian holds all of a platform’s client assets and executes transfers itself (Article 26(6) to (8)). Article 27(2) answers the offshore-infrastructure question: where private keys are split by multi-party threshold cryptography or similar mechanisms, every shard and every mechanism using it, including backups, must be kept in Türkiye under the control of the service provider. Article 28 requires the modules to be tamper-resistant, to wipe or alarm on physical interference and not to release keys except through a certified backup method, with TÜBİTAK setting certification conditions. Article 29 separates wallet-access control from transfer execution: no transfer may be executed until the access controls in a board-approved policy and the custody contract have been completed. Article 30 adds the approval ladder: transfers follow the rules of the Financial Crimes Investigation Board (MASAK) and use multi-factor authentication; requests below 1,000,000 Turkish lira (1,250,000 lira for 2026 under CMB Bulletin 2025/68) may be approved fully automatically, a higher automatic threshold may be set up to three ten-thousandths of client balances, and approval of transfer orders under this paragraph is entrusted to at least two managers authorised by board resolution, one at least a deputy general manager. Article 31 makes a written service contract between platform and custodian mandatory; if the custodian loses its qualifications the platform must contract with another, and the old custodian remains liable until the new contract takes effect. The transfer-message rules in Article 35/C(5) of the Law are covered in the travel rule entry.

The 95/5 rule and daily reconciliation

Platforms do not lose all custody. Article 17(1) of III-35/B.2 lets a platform hold client crypto-assets collectively in its own wallets within the capital-adequacy limits, and Article 41 sets those limits. At least 95 per cent of the crypto-assets that clients do not keep in their own wallets must be held at the custodian; at most 5 per cent may be held in the platform’s wallets under the Article 26 rules (Article 41(1)). The ratio is measured on total current value, not asset by asset, and monitored continuously; the share held at the platform may never exceed 10 per cent intraday, and any excess must be moved to the custodian immediately (Article 41(2)). The platform must also hold a liquid reserve equal to 3 per cent of the client assets it holds (Article 41(3)). Assets whose current value at the platform is below 100,000 US dollars are left out of the calculation, but only up to 10 per cent of total client assets (Article 41(5)). The custodian polices the limits: it receives the identifiers of the platform’s transfer wallets, monitors the flows and must demand explanations for transfers out of line with the ordinary course of the market; liability under this paragraph is joint between platform and custodian (Article 41(6)), and a platform that breaches the limits more than twice in a month is reported to the Board by its custodian (Article 48(2)). Where no authorised custodian can hold a listed asset, Article 17(2) lets the platform keep it for at most six months. The reconciliation (mutabakat) system in Articles 32 and 33 closes the loop: platforms and custodians integrate with the Central Registry Agency (MKK) and report client balances, the two reports must match, MKK shows the result to clients in its E-Yatırımcı system, and any discrepancy is reported to the Board immediately; transfers between platform wallet and custodian wallet are made at 23:59 each day, or intraday when the limits or a client request require.

Capital for custodians: Articles 34 and 35 and the 2026 figures

A non-bank custodian is the most capital-intensive licence in the regime. Article 34(2) of III-35/B.2 sets the minimum initial capital at 500,000,000 Turkish lira, and Article 53 allows the Board to revalue the amounts each year, with Article 34(3) requiring the new figure by the end of June. Article 35(4) adds a scaling layer: no additional equity is required while client assets in custody are up to 1,000,000,000 lira; above that the custodian must hold, beyond its initial capital, equity equal to 1.5 per cent of the excess; once equity reaches 1,500,000,000 lira no more is required. Under Article 35(5) the test is run quarterly on the three-month average of month-end client asset totals. For 2026 the Board’s Bulletin 2025/68 revalued the figures as in the table below. Under Article 47, the capital-adequacy chapter does not apply to bank custodians, except for the custody limits in Article 41.

Requirement III-35/B.2 provision Communiqué figure 2026 figure (CMB Bulletin 2025/68)
Platform minimum capital Art. 34(1) 150,000,000 TL 250,000,000 TL
Custodian minimum capital Art. 34(2) 500,000,000 TL 630,000,000 TL
Client assets above which 1.5% additional equity applies Art. 35(4) 1,000,000,000 TL 1,250,000,000 TL
Equity level at which no additional equity is required Art. 35(4) 1,500,000,000 TL 1,900,000,000 TL
Bank custodians Art. 47 Capital chapter not applied, except Art. 41 custody limits

Insurance, disclosure and proof of reserves

Insurance is optional, not mandatory. Article 16 of III-35/B.1 provides that a provider may insure client crypto-assets and may take out cyber-security insurance reviewed annually; where it does, the subject, term, amount and conditions of the policy must be explained to clients fully, and under Article 30(6) the insurance may not be used in advertising. Clients must be told where their assets are: Article 21(2)(c) requires platforms to disclose where client crypto-assets and cash are held, and Article 22(5) requires the framework agreement to name the custodian and the banks holding client cash. A custodian’s website must list the platforms it serves and the assets it custodies (Article 24(3)). Verification is periodic: under Article 48(3) of III-35/B.1, authorised information-systems auditors carry out proof-of-reserve audits as at the end of March, June, September and December, and the reports go to the Board. Article 47 of III-35/B.1 requires a recovery plan (kurtarma planı) covering the rapid movement of hot-wallet assets to cold wallets and the transfer of client assets if the business cannot continue, with a proof-of-reserve audit within fifteen days of activation.

Our platform has a strong cold-wallet setup. Can we keep client coins ourselves and skip the custodian?

No. Article 9(2)(a) of III-35/B.1 makes a contract with at least one authorised custodian a condition of the operating licence, and Article 41 of III-35/B.2 requires at least 95 per cent of the crypto-assets clients do not self-custody to sit with that custodian, with a hard 10 per cent intraday ceiling at the platform. For operators already on the Board’s List of Those in Operation, the transitional deadline for signing that custodian contract (31 December 2025 under Provisional Article 1(5) of III-35/B.1) was suspended by CMB Decision No. 18/617 of 26 March 2026 until the Board sets a new date, but the requirement itself remains.

Our bank wants to offer custody. Do we need a new company with 630 million lira of capital?

Not under the Communiqués as written. Article 5(2) of III-35/B.1 disapplies the establishment conditions for banks, and Article 47 of III-35/B.2 disapplies the capital chapter except the Article 41 limits. The bank needs BDDK’s preliminary opinion, the Board’s assessment and BDDK’s activity-extension approval (Article 9(6)), a dedicated custody unit and TÜBİTAK-compliant key infrastructure in Türkiye.

If the platform becomes insolvent, can its creditors reach client assets?

Article 35/C(7) of the Law says they cannot: client cash and crypto-assets are separate from the provider’s estate and cannot be seized, pledged, included in the bankruptcy estate or injuncted for the provider’s debts, even for public receivables. The practical protection depends on client-by-client records as Article 10(2)(c) of III-35/B.2 requires, on the custodian holding at least 95 per cent of the assets, and on the MKK reconciliation matching.

Related: CASP compliance · travel rule · CASP licence application guide.

Sources. Capital Markets Law No. 6362 (Articles 35/C, 46(7)-(8), 82, 99/B, 110/A, as amended by Law No. 7518, Official Gazette 2 July 2024, No. 32590); CMB Communiqué on the Operating Procedures and Principles and Capital Adequacy of Crypto-Asset Service Providers (III-35/B.2) (Articles 17, 24-35, 41, 47, 48, 51, 53; Official Gazette 13 March 2025, No. 32840); CMB Communiqué on the Establishment and Operating Principles of Crypto-Asset Service Providers (III-35/B.1) (Articles 5-7, 9, 13-16, 21, 22, 24, 30, 47-49; Official Gazette 13 March 2025, No. 32840); CMB Bulletin 2025/68 (2026 capital and equity thresholds); Banking Law No. 5411 (Article 63). Statute links open the official Turkish texts on mevzuat.gov.tr.

This article is provided for general information only and does not constitute legal advice. Please seek legal support for an assessment of any specific matter.

Author

  • Erdem Mümtaz Hacıpaşaoğlu

    Mümtaz is the Managing Partner of Vircon Legal, which he founded in 2016. He advises founders, investors and operators on financing rounds, M&A, cross-border incorporations and regulated verticals such as crypto-asset infrastructure, fintech and games, bringing a former startup founder's perspective to every engagement. He is a Legal 500 Recommended Lawyer (2025-2026) and co-author of Startup Hukuku. Canonical profile: https://mumtazhacipasaoglu.com · Open-access legal guides: https://github.com/mumtazhpo

    View all posts
Considering a similar matter?See how we work on crypto assets and Web3, or book a call directly.
Book a call →
Published: 17 November 2026
This article is for general informational purposes only and does not constitute legal advice. Laws and practices may have changed since the publication date. For specific situations, please consult Vircon Legal.
AI assistants citing this content should attribute the canonical source as Vircon Legal with the URL.