Open your ride-hailing app in Kathmandu today and you may notice something new sitting quietly next to the "Book a Ride" button: a wallet balance, a "Top Up" option, or a "Pay Later" feature. The same thing is happening inside e-commerce apps, food delivery platforms, and even messaging apps across Nepal. This is not a coincidence — it is a global trend called embedded finance, and it is quietly reshaping how Nepalis pay, save, and borrow, all without ever opening a traditional banking app.
In this article, we break down what embedded finance actually means, where you're already using it in Nepal (whether you realize it or not), why companies are racing to build it, what it means for you as a user, and the regulatory questions this trend raises for a country still building out its digital finance rulebook.
How embedded finance works: payment features (top-ups, wallets, "pay later") are built directly into the apps Nepalis already use daily.
Quick Navigation
What Is Embedded Finance?
Embedded finance is the practice of building financial services — payments, wallets, lending, insurance, or savings — directly inside apps and platforms whose core business is not banking. Instead of leaving a ride-hailing app to open eSewa, Khalti, or a mobile banking app to pay your fare, the payment happens natively, inside the same screen, in the same flow, without you ever noticing the handoff.
Think of it as the difference between a shop that tells you to "go pay at the bank next door" and a shop that simply has a till at the counter. Nepal's digital economy has spent the last decade normalizing standalone wallets like eSewa and Khalti. The next phase, already underway, is these payment capabilities disappearing into the background of every other app — a phenomenon widely known internationally as embedded finance or "banking-as-a-feature."
Embedded Finance in Action Across Nepal's App Ecosystem
This is not a theoretical trend. Across Kathmandu, Pokhara, and beyond, non-financial apps are already layering payment rails, wallets, and checkout financing on top of their core services.
E-Commerce Platforms
Nepali e-commerce apps have moved well past simple "cash on delivery" or redirect-to-gateway checkouts. Many now maintain an in-app wallet balance, offer store credit for returns and refunds, and increasingly experiment with "buy now, pay later" style instalment options at checkout — all designed to keep the transaction, and the customer's money, inside the platform.
Ride-Hailing Apps
Ride-hailing platforms operating in Nepal have added in-app wallets that let riders top up once and pay for multiple trips without re-entering payment details each time. Some are extending this further into driver-side features, such as instant payouts or fuel and maintenance advances tied to a driver's trip history and earnings inside the app.
Food and Grocery Delivery Apps
Delivery apps have followed the same playbook: in-app wallets, saved balances, cashback credited back into the app rather than paid out externally, and loyalty points that function like a closed-loop currency usable only within that platform.
The common thread across ride-hailing, e-commerce, and delivery apps in Nepal is simple: keep the money moving inside the app, rather than sending users elsewhere to complete a payment.
Why Companies Are Racing to Add Payment Features
This shift is not happening by accident. For app businesses operating on thin margins in a competitive Nepali market, embedded finance solves several problems at once.
User Retention
Every time a user leaves an app to pay through a third-party wallet or bank app, there is a risk they get distracted, face a failed transaction, or simply don't return. Keeping payment in-app removes that drop-off point entirely.
Rich Transaction Data
A wallet balance and payment history inside the app gives the company first-party data on spending habits, frequency, and preferences — data that used to belong entirely to banks or independent wallet providers.
New Revenue Streams
Payment features open doors to transaction fees, float income on stored balances, lending partnerships, and cross-selling insurance or credit products — revenue that has nothing to do with the app's original core service.
In short, payments are no longer just a checkout step; they are becoming a strategic layer that increases how "sticky" an app is and how much a company can earn from every user relationship, long after the original ride, delivery, or purchase is complete.
What This Means for You as a User
For everyday users in Nepal, embedded finance genuinely does solve real friction points that most people have experienced firsthand.
- Fewer app switches: You no longer need to jump between a ride-hailing app and a separate wallet app just to complete one payment.
- Faster checkouts: A saved in-app balance or one-tap payment method removes repetitive steps like re-entering card details or waiting for a redirect page to load.
- Bundled rewards: Cashback, loyalty points, and discounts often live directly inside the same wallet you're already spending from, making the value easier to track and use.
- Access for the underbanked: For users without a full banking relationship, an in-app wallet tied to a familiar service can be a simpler entry point into digital finance.
The experience, when it works well, feels less like "using a fintech product" and more like the app simply became more convenient overnight.
The Hidden Risks of Embedded Finance
The same convenience that makes embedded finance appealing also introduces risks that are easy to overlook until something goes wrong.
Fragmented Balances
A user active on a ride-hailing app, a delivery app, and an e-commerce app may end up with three, four, or more small, disconnected balances sitting idle across different platforms. Unlike a single bank account or a dedicated wallet, these balances are often not easily transferable, withdrawable, or trackable in one place — creating quiet, scattered pools of money that are easy to lose track of.
Unclear Accountability When Something Goes Wrong
If a payment fails, a refund doesn't land, or a wallet balance simply disappears after an app update, who is responsible? Is it the non-financial company that built the wallet feature, the underlying payment partner or bank powering it behind the scenes, or the app store that distributed it? Because embedded finance often relies on a licensed financial partner operating quietly behind the scenes of a familiar consumer brand, users may not even know who to contact when a problem arises — the customer support team for a delivery app is rarely equipped to resolve a financial dispute.
The Regulatory Grey Zone This Trend Raises in Nepal
Nepal's financial regulatory framework was largely built around banks, licensed payment service providers, and dedicated wallet operators like those regulated under Nepal Rastra Bank's payment system directives. Embedded finance complicates this picture in a few important ways.
- Who actually needs a licence? When a ride-hailing or delivery app adds wallet-like features, it raises the question of whether that company is now functioning as a payment service provider in practice, even if it partners with a licensed entity behind the scenes.
- Consumer protection standards: Traditional banks and licensed wallets in Nepal operate under specific consumer protection, grievance-handling, and disclosure requirements. It is not always clear whether embedded wallet features inside non-financial apps are held to the same standard.
- Data and money together: Regulators overseeing data privacy and regulators overseeing financial conduct may both have a stake in embedded finance products, since these features combine sensitive spending data with actual custody of user funds.
- Fund safeguarding: Where exactly is a user's in-app wallet balance held, and is it protected the same way a bank deposit or a licensed wallet balance is protected if the parent company faces financial trouble?
These are not hypothetical concerns; they mirror debates that regulators in India, Southeast Asia, and other emerging digital economies have already had to confront as embedded finance scaled faster than the rulebooks written for it.
Where Might This Trend Head Next in Nepal?
A few plausible directions stand out for Nepal's embedded finance landscape over the coming years.
- Consolidation around a few "super apps": Rather than dozens of apps each building their own small wallet, expect consolidation, where a handful of dominant platforms become the default embedded finance layer that smaller apps plug into.
- Deeper credit products: Expect more experimentation with in-app "buy now, pay later" and micro-lending, powered by the transaction history these platforms are already collecting.
- Clearer regulatory guidance: As adoption grows, it is likely that Nepal Rastra Bank and related regulators will need to issue clearer guidance specifically addressing embedded and non-bank-led payment features, rather than relying solely on frameworks built for traditional wallets and banks.
- Interoperability pressure: As users accumulate fragmented balances across multiple apps, pressure will likely grow for better interoperability, allowing money to move between platforms rather than sitting locked in silos.
Embedded finance in Nepal is still in its early, formative stage. For users, it offers a genuinely more convenient way to pay, save, and transact without leaving the apps they already use every day. For companies, it offers a powerful new lever for retention and revenue. But as payment features spread across ride-hailing, e-commerce, delivery, and messaging apps alike, the questions of accountability, fund safety, and regulatory oversight will only become more pressing. Understanding this shift now — before it becomes the default way Nepal pays — puts users, businesses, and policymakers in a far better position to navigate what comes next.
Frequently Asked Questions
Is embedded finance the same as a digital wallet like eSewa or Khalti?
Not exactly. eSewa and Khalti are dedicated, standalone financial platforms. Embedded finance refers to payment or financial features being built directly into a non-financial app — such as a ride-hailing or delivery app — often powered behind the scenes by a licensed financial partner.
Is it safe to keep a balance inside a ride-hailing or delivery app's wallet?
It depends on the safeguards the specific company has in place. Because these features are relatively new in Nepal, users should be cautious about leaving large balances in non-financial apps and should review how withdrawals, refunds, and disputes are actually handled before relying on them heavily.
Why don't companies just let users pay through their normal bank app?
Redirecting users away from an app to complete payment increases the chance of drop-off and disrupts the user experience. Keeping payment in-app improves conversion, retention, and gives the company valuable data and revenue opportunities.
Does Nepal Rastra Bank regulate embedded finance features directly?
Nepal Rastra Bank regulates licensed banks and payment service providers, and many embedded finance features rely on partnerships with such licensed entities behind the scenes. However, clear, specific guidance for embedded finance features built into non-financial apps is still developing.
Discussion