When offices closed across Turkey in March 2020, banks, insurance agencies, and fintech companies all faced the same operational question at once: how do you verify a customer’s identity without ever meeting them in person? Processes built around branch visits, wet signatures, and face-to-face document checks were suspended overnight. Remote customer onboarding — the digital equivalent of KYC (Know Your Customer) — stopped being a competitive differentiator and became a survival requirement. Blockchain-based digital identity frameworks, long discussed in theory but slow to reach production, re-entered the conversation with new urgency. The question worth asking carefully is whether the technology is genuinely ready, or whether the pressure of the moment is pushing institutions toward a solution that has not yet earned its place in live operations.
The core logic of blockchain-based digital identity rests on a straightforward idea: instead of storing a person’s verified credentials in a centralised database controlled by one institution, those credentials live in an encrypted, distributed structure. The individual controls access and shares only what is necessary, only with whom it is necessary. This is what the field calls decentralised identity, or DID. The W3C has been developing interoperability standards in this space; Microsoft’s ION project, the Sovrin Foundation network, and IBM’s Hyperledger Indy infrastructure are among the more substantive initiatives. Turkey’s situation looks different. The Banking Regulation and Supervision Agency (BDDK) is still working through its regulatory framework for remote identity verification. The e-Devlet (e-Government) portal handles identity authentication for many public and private services, but blockchain integration remains at the pilot stage. That gap reflects not a failure of the technology itself, but the slower pace of regulatory clarity and institutional readiness.
It is worth being precise about what remote verification actually looks like in practice today, with or without blockchain. Video KYC, document scanning, facial matching, and e-Devlet-based authentication are the tools most Turkish financial institutions and fintechs are using right now. Some digital banks and payment platforms had already moved in this direction before the pandemic; the crisis accelerated adoption and broadened the user base. Blockchain’s specific contribution to this picture is different in kind: it enables a verified credential to be used across multiple institutions without each one starting the verification process from scratch. This is what practitioners call a reusable credential, and in principle it reduces both friction for the end user and verification cost for the institution. In practice, however, realising this benefit requires all participating parties to accept the same underlying infrastructure — which presupposes an ecosystem coordination that does not yet exist in Turkey at any meaningful scale.
The practical obstacles deserve direct attention rather than a footnote. The first is legal standing: does a credential stored and verified on a blockchain satisfy Turkey’s legal requirements for identity authentication? The answer is not yet settled. The second is the SME reality. A mid-sized accounting firm in Anatolia or a regional insurance agency operates with tight IT budgets and limited technical capacity. In an environment already under pressure from currency volatility and inflation, the return on a blockchain identity investment is difficult to calculate with confidence. The third obstacle is on the user side. Decentralised identity requires customers to manage a digital wallet, understand what they are sharing and with whom, and avoid errors that could lock them out of their own credentials. Digital literacy levels vary enormously across Turkey’s user base. A flow that runs smoothly in a controlled demo can behave very differently when it meets a real customer under real conditions. Treating demo success as operational proof is one of the more persistent mistakes in enterprise technology adoption.
Who can realistically benefit from this technology today? In the near term, the clearest opportunities sit with large financial institutions and sectors in direct dialogue with regulators. A small number of major Turkish banks and payment organisations are running quiet pilots on blockchain-based identity verification; none of these have produced publicly documented results at scale. In the medium term, the more significant shift depends on building cross-sector trust infrastructure: a credential verified at a bank being accepted by an insurer, a public utility, or an e-commerce platform. That scenario requires regulators, technology providers, and industry participants to coordinate around shared standards. Whether and when that coordination takes shape in Turkey remains an open question. Pandemic pressure may accelerate the conversation, but pressure alone does not resolve the technical and regulatory prerequisites.
For a technology or operations leader making decisions today, the practical guidance is straightforward. Do not commit capital to a blockchain identity infrastructure before the regulatory framework is clear and the ecosystem has reached a critical mass of participants. The immediate need for remote verification can be met with more mature tools: e-Devlet integration, video KYC, and document verification services that already operate within a defined legal framework. Keep blockchain-based digital identity on the monitoring list, not the procurement list. Revisit the decision as BDDK guidance firms up, as interoperability standards mature, and as the cost structure becomes accessible at SME scale. The trust infrastructure of a contactless world is genuinely being rebuilt — but the institutions that navigate this well will be those that move on solid ground, not those that move fastest.
This article was originally written in Turkish by Gökhan MERCANOĞLU on April 27, 2020 and has been automatically translated into English and other languages using machine translation.