Nepal's banking sector has quietly become one of South Asia's more impressive digital-payments stories — millions of mobile banking users, interoperable QR codes, and a real-time national payment switch moving money instantly between banks. But ask a different question — can a fintech app securely pull your transaction history from your bank, with your consent, to build you a better loan offer or a smarter budgeting tool — and the honest answer today is: not really, not yet. That's the open banking question. Here's where Nepal actually stands.
What Open Banking Means, Globally
Open banking is the idea that a customer's financial data — account balances, transaction history, payment activity — belongs to the customer, not just the bank that holds it. With explicit, revocable consent, that data can be securely shared through standardized APIs (Application Programming Interfaces) with authorized third-party providers, who can then build services on top of it: budgeting apps, alternative credit scoring, account aggregation, or direct account-to-account payments that bypass card networks entirely.
The model has matured fastest where regulation forced it. The European Union's PSD2 directive, in force since 2018, required EU and EEA banks to expose secure APIs to licensed third parties. India took a different but equally structured path with its Account Aggregator framework, creating a new category of regulated intermediary that routes consented data between banks and apps without ever storing it. The UK, Australia, Brazil, and a growing list of other markets have built their own variations. The common thread across all of them isn't the technology — APIs are a solved engineering problem — it's the regulatory mandate that forces banks to open up in the first place, on standardized terms, rather than leaving data-sharing to bilateral, one-off deals.
The Current State: How Closed and Siloed Nepal's Banking Data Still Is
Nepal's digital finance progress over the past several years has been genuinely significant. Mobile banking usage has reached over 24 million users, internet banking around 1.9 million, and e-wallet usage above 23 million, according to recent industry data. Nepal Clearing House's National Payment Switch — including the Real-Time Retail Payment Switch and the NEPALPAY QR system — has made bank-to-bank transfers, QR payments, and even early cross-border QR payments with India fast and interoperable. connectIPS alone has surpassed 1.28 million verified users, with transaction volumes climbing sharply year over year.
That progress, though, is almost entirely about moving money — not about sharing the data behind it. Payment interoperability and open banking are related but distinct problems. Nepal has solved the first: any wallet can now pay any interoperable merchant QR, and banks can settle with each other in real time. But there is no standardized, regulator-mandated framework today that lets a customer authorize a third-party fintech app to securely read their account data directly from their bank via API — the way PSD2 does in Europe or the Account Aggregator model does in India.
Industry commentary on Nepal's fintech sector has repeatedly flagged the same underlying issue: individual banks and financial institutions run on different, often incompatible technology stacks, with no common API standard between them. Without that standardization, any fintech wanting to build a product that reads data across multiple Nepali banks currently has to negotiate integration one bank at a time — a slow, expensive process that only well-capitalized players can realistically pursue, and one that leaves most of Nepal's 38-plus banks and financial institutions functioning as closed data silos even though many of them are individually quite digitally advanced.
Today, each Nepali bank is its own data island. Open banking would connect them through consent-based, standardized APIs.
The Potential Benefits: What Open Banking Could Unlock
If Nepal builds a genuine open banking framework, the upside touches nearly every part of retail and small-business finance:
- Better loan approvals through alternative credit data: A huge share of Nepal's population remains thin-file or unbanked from a formal credit-scoring perspective. Real transaction history — utility payments, remittance inflows, merchant sales — is often a far better predictor of repayment ability than a traditional credit file. Open banking data could let lenders underwrite small businesses and individuals who are creditworthy but currently invisible to formal credit scoring.
- Genuinely personalized financial apps: Budgeting tools, savings automation, and spending insights all work far better with real transaction data rather than manual entry. Today, that requires either screen-scraping (insecure, fragile) or building the tool inside a single bank's own app.
- Easier account switching and comparison: With standardized data access, a customer could let a comparison tool see their real transaction patterns and recommend a genuinely better-fitting account, loan, or savings product — rather than switching banks essentially blind, based on branch reputation or a relative's recommendation.
- Faster, cheaper account aggregation: Customers and small businesses managing accounts across multiple banks could see a unified financial picture in one place, instead of manually checking three or four separate apps.
- A genuine on-ramp for fintech innovation: Much of the most interesting fintech innovation globally — robo-advisors, automated savings, embedded lending — depends on programmatic access to real account data. Without it, Nepali fintechs are largely limited to building on top of payments rails rather than deeper financial services.
The Risks: Privacy, Security, and Consent Challenges
None of this comes free of risk, and the risks are exactly why mature open banking markets built regulation before adoption, not after.
Data Privacy in a Still-Developing Legal Landscape
Nepal's baseline privacy protection comes primarily from the Individual Privacy Act, but the country does not yet have a comprehensive, dedicated data protection law built specifically for the scale and sensitivity of financial-data sharing — the kind of purpose-built framework that GDPR provides in Europe or that India's Account Aggregator model was built around from day one. Opening up financial data without that foundational legal clarity first creates real exposure: who is liable if shared data is misused, how long can a third party retain it, and what happens when consent is withdrawn?
Security: A Bigger Attack Surface
Every additional party with access to financial data is an additional potential point of failure. Poorly secured APIs, weak authentication, or inadequately vetted third-party apps could turn open banking into a new vector for fraud and data breaches — a serious concern in a market still building out cybersecurity maturity across its banking sector broadly.
Consent That's Actually Informed
Meaningful consent requires customers to genuinely understand what they're authorizing — not a buried checkbox in a sign-up flow. Given that financial literacy initiatives in Nepal are still catching up to the pace of digital adoption, there's a real risk that "consent" becomes a formality rather than a genuine, informed choice, particularly for less digitally experienced customers in rural areas.
Uneven Bargaining Power Between Banks and Fintechs
Without a regulatory mandate, banks have limited commercial incentive to open up access to fintech competitors voluntarily — data is a competitive asset, and few incumbents give up an asset for free. This is precisely why open banking has, almost everywhere it has succeeded, required a regulator to force the issue rather than waiting for market cooperation.
The core tension: the same data-sharing that unlocks better financial products is also the thing that, mishandled, creates Nepal's next major data-privacy incident. Sequencing matters — regulation and security infrastructure need to lead, not follow, market adoption.
Signals from NRB and the Industry About Future Direction
There's no formal open banking mandate from Nepal Rastra Bank yet — but there are meaningful signals the groundwork is being laid, even if indirectly:
- A functioning fintech regulatory sandbox: NRB has already established a controlled environment where fintech startups can test new financial services under central bank oversight — precisely the kind of mechanism other markets have used to pilot open banking models before full regulation.
- Heavy investment in shared payment infrastructure: The National Payment Switch, RTGS-based settlement, and NEPALPAY QR show that NRB is comfortable building and mandating shared, interoperable digital infrastructure when it sees clear public benefit — the same institutional muscle open banking would require.
- Digital KYC and identity groundwork: Simplified, digital-first account opening and identity verification are foundational building blocks that a future consent and authentication framework for open banking would likely build on top of.
- Cross-border data and payment integration: NRB's authorization of cross-border QR payment interoperability with India shows a regulator willing to extend data and payment connectivity beyond domestic borders when the right framework is in place.
- Vocal industry advocacy: Fintech practitioners and commentators in Nepal have been increasingly public about the need for NRB to define common API standards and a clear open banking regulatory framework — a sign the demand-side pressure is building, even without a confirmed regulatory timeline yet.
Put together, these signals suggest Nepal has most of the technical and institutional prerequisites in place — but the specific, dedicated open banking mandate that would actually force banks to open standardized APIs has not yet been announced.
What Developers and Fintech Companies Are Watching For
For builders in Nepal's fintech space, a few concrete developments would signal that open banking is genuinely arriving rather than remaining a talking point:
- A published API standard from NRB or NCHL that all licensed banks and financial institutions would be required to implement, replacing today's bank-by-bank negotiation model.
- A licensing category for third-party providers (TPPs) — a formal regulatory status, similar to India's Account Aggregator entities, that lets fintechs legally request and handle consented financial data without operating in a grey area.
- A clear consent and revocation framework specifying exactly how customer authorization must be captured, displayed, and withdrawn — the legal backbone that would make data-sharing defensible and auditable.
- Expansion of the existing fintech sandbox to explicitly include open banking or account-aggregation use cases as a formal testing category.
- Signals from major commercial banks — any large bank publishing a developer portal or public API documentation would be an early, meaningful indicator that the market is moving ahead of, or in close coordination with, regulation.
How This Could Reshape Nepal's Competitive Landscape
If open banking does arrive in a well-regulated form, the competitive effects would likely unfold in stages. In the near term, larger banks with stronger existing data and infrastructure would have an advantage in built-in trust, but would also face new competition from fintechs finally able to build genuinely data-driven products without needing a banking license themselves. Mid-sized banks and finance companies, meanwhile, could use open banking as a way to compete with larger institutions by partnering with agile fintechs rather than trying to out-build them.
Longer term, the more interesting shift is toward embedded finance and banking-as-a-service — non-financial platforms (e-commerce sites, gig platforms, super-apps) embedding lending, savings, or payment features directly into their existing product, powered by open banking data in the background rather than by building banking infrastructure themselves. This is the pattern that has played out in more mature open banking markets, and there's little reason Nepal's already fast-growing digital economy wouldn't follow a similar trajectory once the regulatory pieces are in place.
๐ก The likely path forward
Nepal probably won't get a single dramatic "open banking launch" the way PSD2 arrived in Europe. More likely is an incremental build-out — sandbox pilots, gradual API standardization pushed by NCHL or NRB, and early account-aggregation-style products emerging from fintechs already closely coordinating with regulators — with the formal framework catching up to, rather than leading, the market's early experiments.
Final Thoughts
Nepal has already done the hard infrastructure work that many countries spend years building: a real-time national payment switch, widespread mobile and QR adoption, and a functioning fintech sandbox. What's missing isn't technical capability — it's the specific regulatory mandate that turns "banks could theoretically share data securely" into "banks must expose standardized, consented APIs to licensed third parties." Until that mandate exists, Nepal's banking data will remain digitally sophisticated but structurally closed. Whether that changes in the next year or the next five likely depends less on technology and more on how quickly NRB decides Nepal's next digital finance chapter should be written.
Discussion