Blockchain KYC in Nepali Banks: Ending the "Fill the Same Form" Problem

Open an account at a second bank in Nepal, and you will fill out almost the exact same Know Your Customer form you already completed at your first bank — the same citizenship copy, the same address proof, the same in-person verification, repeated from scratch. Multiply that across every bank, cooperative, brokerage, and mobile wallet a person uses, and Nepal's financial sector is running an enormous amount of duplicate paperwork that solves nothing but bureaucratic box-ticking.

Blockchain-based, reusable KYC has been proposed as the fix, and Nepal has already taken real first steps toward centralising this process — though not yet with blockchain at its core. This article explains how KYC actually works in Nepal today, what's changing, and where blockchain could take it next.

Why KYC Exists — and Why It's So Repetitive

Know Your Customer requirements exist to prevent fraud, money laundering, and terror financing, and they became mandatory worldwide largely after the international regulatory response to 9/11. Nepal Rastra Bank enforces its own KYC standard through Nepal's Money Laundering Prevention framework, requiring every bank and financial institution to independently verify a customer's identity, address, and in many cases source of funds before opening an account or processing certain transactions.

The problem is that "independently" means exactly that — each institution runs its own verification from scratch, with its own paperwork, its own in-person checks, and its own internal database that no other institution can see. A customer with accounts at three banks and a brokerage has effectively proven their identity four separate times, using four separate processes, none of which talk to each other.

What Nepal Has Already Built: cKYC for Securities

Nepal has taken a first step toward centralising this process, though through a shared database rather than blockchain. The Central Depository System and Clearing Limited (CDSCL) operates a centralised KYC (cKYC) platform specifically for Nepal's securities market, allowing a customer's identity verification to be reused across participating brokers and depository participants rather than repeated at each one. Nepal Rastra Bank's Governor has separately announced plans to roll out a centralised KYC system for banks and financial institutions, alongside the central bank's CBDC development, positioning identity infrastructure and digital currency as connected pieces of the same modernisation push.

This is a meaningful improvement over the status quo, but it comes with a structural limitation worth understanding: a centralised database, however well run, is still a single point of failure and a single institution's responsibility to secure. If that central repository is breached, altered, or simply goes offline, every institution relying on it is affected at once.

Where Blockchain Changes the Picture

A blockchain-based KYC model addresses that structural weakness directly. Instead of one central database that every institution queries, a customer's verified identity credential would sit on a shared, tamper-evident ledger that multiple institutions can independently confirm without any single party controlling or being able to silently alter the record. Once a customer completes identity verification with one participating institution, that verification — not the underlying personal documents themselves, but a cryptographic proof that verification occurred — could be reused by any other institution on the network, with the customer's consent.

eSatya, Nepal's blockchain initiative under Rumsan Associates, has already explored this exact model through a proof-of-concept called Chino, a blockchain-based digital identity management system designed specifically to support reusable KYC. The core idea mirrors what international examples like Civic have demonstrated elsewhere: a secure identity platform where verification happens once and gets reused, rather than repeated, across multiple financial relationships.

The Bigger Vision: One Identity Rail, Not Five

Nepali policy commentary has pushed this idea even further, arguing that Nepal risks building several disconnected identity systems instead of one. Nepal's securities market already runs its own cKYC through CDSCL, the government's Nagarik app handles a separate layer of citizen digital services, and banks are now expected to adopt yet another centralised KYC system of their own. Without coordination, each of these becomes its own silo, duplicating cost and effort rather than solving the underlying problem.

The alternative proposed by technologists and policy commentators is a single self-sovereign identity (SSI) rail — a blockchain-based digital identity system a citizen controls directly, capable of serving KYC, land registry verification, healthcare records, voting, driving licences, and student records all through the same underlying credential, shared only with explicit consent each time. Rather than five separate government and financial identity systems each holding a partial picture of a citizen, one interoperable rail would let every sector plug into the same verified identity foundation.

What This Would Mean for an Ordinary Bank Customer

In practice, a functioning blockchain KYC system would mean completing identity verification once — likely at whichever bank or institution a person deals with first — and then simply authorising that same verified credential to be reused when opening a second bank account, applying for a brokerage account, or signing up for a licensed digital wallet. No repeated document submissions, no repeated in-person visits, and critically, no institution needing to trust another institution's internal records directly, since the blockchain layer itself provides the tamper-evident proof.

For migrant workers and their families — a huge share of Nepal's banking customer base — this matters more than it might first appear. Someone opening a new account after returning from years working abroad, or a family member managing remittance-linked services on someone else's behalf, currently faces the full weight of Nepal's KYC process every time a new financial relationship begins. A reusable, portable identity credential would meaningfully cut that friction.

Why This Hasn't Happened Yet

Coordination, not technology, is the real obstacle. A blockchain KYC network only delivers its full benefit if multiple banks, the securities regulator, cooperatives, and government identity systems agree to participate in a shared framework — a level of cross-institutional cooperation that is harder to achieve than building the underlying technology itself. Nepal's current trajectory of standalone centralised KYC systems, one per sector, reflects this challenge: it is far easier for a single regulator to build its own cKYC than for multiple regulators to agree on one shared blockchain-based identity standard together.

Regulatory clarity is a second hurdle. Any system storing or referencing identity data needs clear legal backing for how consent, data protection, and liability work when a credential verified by one institution is relied upon by another — questions Nepal's financial regulators are still working through even for the simpler centralised KYC models already underway.

The Realistic Path Forward

Nepal's most likely path is incremental rather than a single dramatic shift: centralised KYC systems, like CDSCL's model for securities and NRB's planned system for banks, will likely launch first, proving the basic value of shared identity verification. A blockchain layer connecting these systems — or replacing the centralised model with a distributed one — would be a logical next phase once institutions have already adjusted to the idea of not re-verifying every customer from scratch. Whether Nepal ultimately builds that next layer on blockchain specifically, or on some other shared architecture, the direction is already clear: filling out the same KYC form five times is a problem Nepal's financial sector is actively trying to solve.