Turkey's SPK crypto licence: the technical requirements for platforms moving from the temporary list to an operating licence
What Turkey's SPK (CMB) expects from a crypto platform's systems before an operating licence: TÜBİTAK criteria, custody limits, records, audits, evidence.
Kostiantyn Boiko, Blockchain Engineer
English original
To operate as a crypto asset service provider in Turkey (Türkiye), a company needs two approvals from SPK, the Capital Markets Board (CMB): an establishment permit, then an operating licence evidenced by an authorisation certificate (Capital Markets Law No. 6362, Articles 35/B and 35/C). The temporary list includes existing providers that made declarations under provisional Article 11 and applicants covered by SPK’s subsequent transitional decisions; it is not a register of licensed providers. The temporary list dated 28 October 2026 contains 49 entries: 40 platform entries and nine labelled as custody applications. Those labels are not a reliable guide to current licensing status: the three banks licensed for custody in June remain labelled as applications. The separate liquidation list contains 59 entries. SPK states at the top of the page that being listed does not mean being authorised.
As of 31 October 2026, SPK has deferred the transitional 30 June 2026 deadline for authorisation certificates without announcing a replacement date. On 26 March 2026 SPK said it will set a new one once the custodians it authorises serve platforms widely, and in June 2026 three banks were licensed as crypto custodians. What must be ready when the clock restarts is already defined: a working security infrastructure that meets Communiqué VII-128.10 and the TÜBİTAK criteria, integration with MKK (the Central Registry Agency), reconciliation with your custodian, an annual information systems audit and a quarterly proof-of-reserves audit.
Below, each obligation is mapped to a control, the evidence an auditor or SPK can inspect, and an owner. This is not legal advice, and BitPolaris is not a law firm. BitPolaris software has run in production at the reference exchange since 2024. That deployment is not evidence of compliance with Turkish licensing requirements, and BitPolaris does not hold an SPK licence.
Where does the timeline stand?
| Date | What happened |
|---|---|
| 2 July 2024 | Law No. 7518 takes effect, adding the crypto provisions (35/B, 35/C, 99/A, 99/B, 109/A) to the Capital Markets Law |
| 13 March 2025 | Communiqués III-35/B.1, III-35/B.2 and VII-128.10 published; III-62.2 amended to cover crypto providers. VII-128.10 enters into force on 30 June 2025, with transitional deadlines for specified provisions. |
| 8 May 2025 | TÜBİTAK BİLGEM publishes its infrastructure criteria; SPK issues its proof-of-reserves audit principles the same day |
| 30 June 2025 | Last day for listed entities to apply for an operating licence |
| 31 December 2025 | Information systems audit report for the application due (extended from 30 September); deadline for primary and secondary systems to be in Turkey |
| 1 January 2026 | Revalued minimum founding capital: TRY 250 million for a platform, TRY 630 million for a custodian |
| 26 March 2026 | Custody contract deadline (already moved to 31 March 2026) and certificate deadline to be reset once custody is widely available |
| 4 June 2026 | Three banks licensed as crypto custodians |
| 31 January 2027 | Outer reporting deadline under our reading of VII-128.10 Art. 8/7; the report is also due within one month of test completion. Confirm applicability to your filing with the auditor. |
The March 2026 decision deferred the certificate and custody-contract deadlines; it did not extend the technical compliance deadlines. The technical provisions are in force, and the annual audits under Article 48 of III-35/B.1 are due for the first time for 2026. Nor is the list a safe harbour: the 28 October list notes that on 23 September 2026 one platform was barred from taking new customers and listing new assets.
What has to be ready technically for an operating licence?
Article 9 of III-35/B.1 ties the operating licence to these technical conditions:
- A security infrastructure meeting VII-128.10 and the TÜBİTAK criteria has been built and is operating (Art. 9/1-f). A design document is not enough.
- Technical and system integration tests with MKK are complete (Art. 9/1-ğ).
- Private key storage is in place and blockchain integration is finished (Art. 9/1-h).
- For platforms: a contract and reconciliation integration with at least one authorised custodian, a bank account for customer cash, a complaints mechanism and a price surveillance system, each with a written procedure (Art. 9/2).
If SPK considers it necessary, an information systems audit takes place during licensing together with TÜBİTAK and other public bodies, covering wallets and blockchain operations (Art. 9/4). After licensing, a firm on SPK’s list audits information systems at least once a year, including compliance with the TÜBİTAK criteria (Law 6362, Art. 99/B-2; III-35/B.1, Art. 48).
The detail is in four texts: III-35/B.1 (establishment and operations), III-35/B.2 (custody, transfers, reconciliation, capital), VII-128.10 (information systems management for every SPK-supervised entity, crypto providers included) and the TÜBİTAK criteria BİLGEM published on 8 May 2025, which cover areas such as wallet security, IS governance, information security and business continuity. The communiqués refer to the criteria for key management, HSMs and wallet technology. The control mapping below is based on the communiqués, not a verified review of the full TÜBİTAK criteria PDF. BİLGEM’s announcement confirms the broad subject areas, but the applicable criteria version and its detailed requirements must be checked before using this mapping for an application. Article 24/A of the AML Measures Regulation (the Travel Rule) and Communiqué III-42.1 on remote identification, extended to crypto providers in February 2026, also reach your software.
A control, evidence and an owner for each obligation
The first column summarises the cited provisions; it is not a complete compliance checklist. The control and evidence columns are our recommendation: the communiqués mostly describe outcomes and leave the technology to you. Owners use the job titles in Article 18 of III-35/B.1.
Custody, keys and transfers
| Requirement (article) | Control we recommend | Evidence | Owner |
|---|---|---|---|
| At least 95% of crypto that customers do not self-custody sits with a custodian, at most 5% on the platform; above 10% during the day, the excess moves at once (B.2 Art. 41/1-2) | Monitor the custody ratio continuously; trigger transfers before the platform allocation exceeds 5%, enforce the 10% intraday ceiling and immediately transfer any excess; verify the end-of-day allocation. | Ratio time series, on-chain transfer records | Risk management staff |
| Keys and key shares never leave the HSM except for backup by a certified method; MPC shares, backups included, stay in Turkey under the provider’s control (B.2 Art. 27/2, 28/1) | Signing only inside the HSM; inventory of every key and share with its location | Key inventory, HSM serials and locations, backup records | Information security officer |
| HSM initialisation and recovery key handover happen under supervision of TÜBİTAK or an information systems audit firm; if done before 13 March 2025, repeated within three years (B.2 Art. 28/4, provisional Art. 1/3) | Scripted ceremony, several participants, recorded session | Signed ceremony and handover minutes | IT operations staff |
| Wallet access control is separate from the transfer, and signing cannot start until it completes; smart cards or similar with multi-factor authentication (B.2 Art. 29/2-3) | Policy engine separate from the signer; unapproved transactions cannot reach it; approvers sign with hardware keys | Board-approved policy, approval chain per transfer | Internal control staff |
| In 2026, transfers under TRY 1,250,000 may be approved automatically (higher allowed up to 0.03% of customer assets); the board authorises at least two managers to approve, one at deputy general manager level or above (B.2 Art. 30/3; SPK bulletin 2025/68) | Approval matrix by amount; as an additional control, require two approvals above the automatic-approval threshold. Art. 30/3 requires the board to authorise at least two managers, but does not explicitly require two approvals for each transfer. | Approval matrix, board authorisation, threshold change log | Deputy general manager |
| Crypto transfer messages of TRY 15,000 or more require verified sender details; below that threshold, sender name and wallet address are still required, without mandatory verification under this provision. Missing incoming information must be requested, with return if it is not completed (AML Measures Regulation Art. 24/A). | Mandatory message fields, hold-and-return flow, customer declarations for unhosted wallets | Message, return and declaration records | Internal control staff |
Records and reconciliation
| Requirement (article) | Control we recommend | Evidence | Owner |
|---|---|---|---|
| Every order, cancelled and amended ones included, with minimum fields; IP addresses and logs showing the source of electronic orders (B.1 Art. 39/2, 40/2) | Order event log, one row per state change, with client IP and channel | Export available immediately on request | IT operations staff |
| Account movements, prices shown to customers (including from liquidity providers) and logs cannot be deleted or altered; file integrity values timestamped daily; records kept ten years (B.1 Art. 40/3-4) | Daily hash manifest with a timestamp; write-once (WORM) storage | Manifests, timestamp tokens, independent verification script | Internal auditor |
| Transactions netted per customer for each asset; platform-custodian transfers as of 23:59; balances the platform and custodian report to MKK must match (B.2 Art. 32/3, 33) | End-of-day netting job; comparison with the custodian’s balances before reporting | Netting reports, MKK submissions and responses, break records | Operations staff |
| Proof-of-reserves audit for every quarter; the auditor picks two random dates and discloses them only the day before (B.1 Art. 48/3; SPK principle decision i-SPK.35/B.2) | Reconstructible ledger-to-chain balances for quarter-end and auditor-selected dates; documented wallet-control proofs using methods accepted by the auditor. | Snapshot archive, address list, ownership proofs | Risk management staff |
| Money accepted only by electronic transfer from the customer’s own bank account (B.2 Art. 51/3) | Match the sending IBAN’s holder to the customer; return unmatched deposits | Match results, return records | Operations staff |
Information systems and continuity
| Requirement (article) | Control we recommend | Evidence | Owner |
|---|---|---|---|
| Primary and secondary systems in Turkey, not exposed to the same natural risks; operating again within 24 hours if the primary fails completely; a recorded restore test every year (VII-128.10 Art. 27) | Data centres in two Turkish regions, continuous replication, written failover steps | Recovery time and data loss targets, signed drill records | IT operations staff |
| Audit trails retained for at least five years under VII-128.10, with the ten-year period applied to logs covered by B.1 Art. 40; central monitoring and correlation rules; separate log and system administrators; a common atomic-clock-derived time reference; infrastructure changes recorded with their author (VII-128.10 Art. 22-23; B.1 Art. 40/4-5). | Central log management (SIEM), separate permission domain, release pipeline that blocks unapproved deployments | Correlation rules, permission matrix, change history | Information security officer |
| Independent penetration test yearly; report to SPK within a month, by 31 January of the next year at the latest (VII-128.10 Art. 8/6-7) | Scope includes wallet services, admin console and APIs | Report, remediation tracker | Information security officer |
| Recovery plan: urgent hot-to-cold sweep, isolation of affected systems, transfer of customer assets if needed; proof-of-reserves audit within 15 days of activation (B.1 Art. 47) | Pre-approved sweep and isolation runbooks with transaction validation, required approvals and a trusted recovery destination; test them without bypassing signing controls. | Approved plan, drill record, the two appointed officers | Risk management staff |
How are software vendors and outsourcing treated?
Outsourcing does not remove the provider’s responsibility (B.1 Art. 32/6). For outsourced information systems, decision-making power and responsibility for management, access, control and updates stay with the provider (Art. 32/9). A foreign vendor must not stand in the way of SPK obtaining information or auditing, and an action plan must be ready if the service stops (Art. 32/10). The outsourcing contract must provide SPK’s required access rights and include service-continuity and handover obligations (Art. 34/1); those clauses do not replace a tested exit plan. VII-128.10 counts cloud as outsourcing and says the in-country rule must be observed there too (Art. 19/6), and requires multi-factor authentication and the information security officer’s approval for remote access (Art. 13/7).
Our recommendation: treat your vendor’s remote support as outsourcing until your counsel says otherwise. No standing production access; each session requested, approved, time-limited and logged; no path to the signing infrastructure at all. Document who can operate the system if the vendor becomes unavailable, including source-code rights or escrow where needed, build instructions, deployment credentials and operational handover.
Build the evidence file from day one
Give each control an ID and file its evidence under it: the policy, the configuration itself rather than a screenshot, a sample record, the latest test report. The information systems auditor, the reserves auditor and SPK will ask for the same data from different angles; one export path keeps answers consistent. Rehearse the reserves audit on random dates you pick yourself. Set and test a retrieval target with your auditor; missing historical balances or unreconciled differences should be resolved before the audit.
Additional implementation recommendations, subject to the applicable criteria and your auditor’s requirements: agree early with your auditor which timestamping service is acceptable, keep reproducible builds and a software bill of materials (SBOM), put limit and whitelist changes under four-eyes approval, and exercise the wallet path continuously with small test withdrawals.
Turkey SPK licence FAQ
Is being on SPK’s list of operating entities a licence?
No. The list shows entities that declared they would keep operating under provisional Article 11 of the law, and SPK writes on the page that being listed does not mean authorisation. Authorisation is proven by the certificate SPK issues.
What is the deadline for the authorisation certificate?
As of 31 October 2026, SPK has not announced a replacement for the deferred transitional certificate deadline of 30 June 2026. Its 26 March decision links the new deadline to wider availability of authorised custody services. This deferral is not an exemption from technical requirements or other application deadlines.
Can a platform keep customer crypto in its own wallets?
For customer crypto not held in customers’ own wallets, the standard allocation is at least 95% with a custodian and at most 5% on the platform. The intraday ceiling is 10%, and any excess must be transferred immediately. If no custodian can hold a listed asset, the platform may keep it for up to six months (B.2 Art. 17/2). Platform wallets follow the same HSM and access rules, and the platform holds a liquid reserve of 3% of the customer assets it keeps (Art. 41/3).
Can we host our systems abroad or in the cloud?
Primary and secondary systems must be in Turkey (VII-128.10 Art. 27/1); crypto providers had until 31 December 2025. Cloud is allowed as outsourcing, but the in-country rule must still be observed. MPC key shares and their backups must also stay in Turkey (B.2 Art. 27/2).
Who carries out SPK’s information systems audit, and how often?
A firm on SPK’s list of authorised information systems auditors, at least yearly, covering a general audit under III-62.2 and internal controls, processes and TÜBİTAK compliance; one report can cover both (B.1 Art. 48). Reserves audits are quarterly and penetration tests yearly. The internal information systems audit is yearly too and cannot be outsourced (VII-128.10 Art. 29).
What does it take to start a crypto exchange in Turkey from scratch?
A joint-stock company with registered shares and capital paid in cash (B.1 Art. 5); 2026 minimum founding capital is TRY 250 million for a platform and TRY 630 million for a custodian. The general manager must be resident in Turkey, full-time, with at least seven years of experience (Art. 14). The establishment permission lapses if no operating-licence application is made within six months, unless SPK grants an extension under Art. 17/1. The infrastructure has to be working when you apply.
What BitPolaris does
BitPolaris supplies exchange and self-hosted custody software; it does not act as a custodian, payment processor or licence holder. HSM integration is available on request, but is not a claim of TÜBİTAK compliance. Its hosted offering uses a dedicated EU instance and therefore does not meet the Turkish location requirement for primary or secondary systems. A self-hosted deployment still needs its architecture, integrations and controls assessed against the applicable requirements. The Licence Technical Pack Pro costs €6,300 one-time and covers technical documentation mapped to SPK and TÜBİTAK requirements, with Turkish delivery available on request; the Lite technical file is €1,250 for platform customers. Neither package is an audit or a guarantee of authorisation. Software does not make anyone compliant: your counsel runs the application, an auditor on SPK’s list audits, and SPK decides.
Sources
- Resmî Gazete, Law No. 7518 (2 July 2024, issue 32590)
- Resmî Gazete, 13 March 2025 (issue 32840): III-35/B.1, III-35/B.2, III-62.2.b, VII-128.10
- SPK, list of operating entities and liquidation list (28 October 2026)
- SPK bulletins: 2025/29 (proof-of-reserves principles), 2025/47, 2025/61, 2025/68 (2026 amounts), 2026/18, 2026/34
- TÜBİTAK BİLGEM, criteria announcement (8 May 2025)
- Resmî Gazete, AML Measures Regulation amendment (25 December 2024, issue 32763) and III-42.1.a (28 February 2026, issue 33182)
- Erdem & Erdem, briefing on the secondary regulations (19 March 2025, in Turkish)