Comment Roundup: Biggest Digital Payment Frustrations from Readers

This post started from a simple observation: the comment section under our digital payment articles has been getting more active, not less, even as Nepal's fintech apps improve. Readers aren't just asking questions — they're venting specific, recurring frustrations that no single FAQ page seems to address. So we decided to do something useful with that energy: collect the most common complaints from app store reviews, social media, WhatsApp messages to our editorial team, and direct comments — and turn them into a structured resource that names what's broken and what the industry is actually doing about it.

What follows isn't a complaint list for its own sake. Each frustration is real, verified from multiple sources, and paired with an honest editorial assessment of whether it's being addressed, ignored, or is simply the expected growing pain of a fintech sector expanding faster than its backend infrastructure.

Frustration #1 — App Crashes During Peak Hours

This was the single most-mentioned complaint across every channel we looked at. The pattern is consistent: eSewa, Khalti, and mobile banking apps perform fine during off-peak hours but become slow, unresponsive, or crash entirely when transaction volume spikes.

The triggers reported are almost always the same: Dashain and Tihar cashback season, the first few days of a new month when salaries arrive, and specific high-traffic moments like government payment deadlines and popular event ticket sales. One eSewa user's review from early 2026 described the experience directly:

"The app does face performance issues during periods of high traffic. I have often experienced lag, and in some cases, the application becomes unresponsive or crashes entirely. These disruptions can be particularly frustrating when attempting to make time-sensitive payments, as transactions may fail or be delayed."

The frustration is compounded by timing — these crashes don't happen when nothing is at stake. They happen exactly when someone is standing at a counter, waiting to pay a Dashain bill, or trying to book the last available ticket for something.

Frustration #2 — Confusing Fee Structures

The second most-reported frustration isn't just about fees existing — it's about fees appearing in places users didn't expect them, often with no explanation of what the charge covers.

A notable pattern in the complaints involves charges on transactions that NRB's Payment System Directive explicitly says should be free for consumers. NRB's directive prohibits payment service providers from levying fees on domestic wallet-to-wallet transfers, mobile banking transactions, and QR payments. Yet multiple users reported charges appearing even within the same app's ecosystem.

One Trustpilot reviewer summarized it bluntly: "Charging in every small and big transaction, even within their own ecosystem. Kind of legal scammers." Whether or not that characterization is fair, the underlying point — that fee disclosures are opaque and sometimes inconsistent with what users understand the rules to be — is a recurring theme across dozens of separate reports.

A separate but related complaint involves the Khalti-IME Pay merger that took effect in 2026. Several IME Pay users reported confusion about whether their previous fee structures, limits, and terms were changing, and expressed frustration that the in-app communication around the migration wasn't clear enough.

Frustration #3 — Slow Customer Support Response

Customer support quality is where the most genuinely heated comments come from — and with some justification. The pattern described by users across platforms is remarkably consistent: call lines that are always busy, emails that go unanswered for weeks, and WhatsApp support contacts that reply with the same generic template regardless of the specific issue raised.

One Khalti user's review captured what many described: "I have been constantly sending them two emails and calling two times per day but still not getting better results. They don't reply." Another described a KYC account issue that remained unresolved for over a month despite daily follow-up attempts — leaving the user locked out of their own wallet balance.

The support gap is particularly acute for issues that require human judgment rather than a scripted response — account suspensions, failed KYC, and disputed transactions all fall into this category. These aren't problems a chatbot can resolve, and the human escalation pathway is unclear to most users.

Frustration #4 — Failed Transactions with No Clear Resolution

This frustration has a specific, anxiety-inducing shape: money leaves your wallet or bank account, the payment confirmation never arrives, and you are left in a state of genuine uncertainty about whether you paid, whether you'll be charged twice if you try again, and how long a refund will actually take.

The most striking example from our collection involved a reader who paid for five concert tickets through Khalti 35 days in advance, received neither the tickets nor a refund, and was then told — after weeks of follow-up — that they would need to pay again or forfeit their booking. Other reported scenarios include mobile recharge payments where the amount was deducted but the recharge never credited, and utility bill payments that disappeared without an acknowledgment record.

This frustration feeds directly into a broader trust problem: when a failed transaction leaves no visible paper trail and no timeline for resolution, the user's instinct is that the money is simply gone. For lower-income users especially, that uncertainty about even a small amount represents genuine financial stress, not a minor inconvenience.

The practical advice most users settle on — wait at least 24 hours before raising a dispute, since many auto-reverse — is reasonable, but it represents a gap that the industry hasn't closed: most users don't know this, and the in-app communication during a failed transaction almost never proactively says it.

Frustration #5 — KYC and Verification Hassles

KYC complaints take several distinct forms. The most common is repeated photo rejection with a generic error message and no specific guidance on what the actual problem is — leading users to resubmit the same documents five, six, or more times with no resolution.

A Trustpilot review that stood out described an eight-month KYC pending status despite multiple document resubmissions. The reviewer also raised a structural accessibility issue: "There are only a few countries to be selected on the country list, cannot even type there. Another issue is for females with hijab — the photo requires ears to be shown which is impossible." This points to an underlying problem that goes beyond slow processing: the KYC system's assumptions about what a valid ID photo looks like are not inclusive of the actual diversity of Nepal's users.

Non-resident Nepalis (NRNs) represent a specific pain point mentioned repeatedly. Multiple users described loading money into their eSewa or Khalti accounts successfully from abroad, then finding themselves unable to actually use those funds because their overseas-submitted KYC failed — leaving their own money effectively frozen.

Editorial Response — Which of These Are Being Addressed Industry-Wide?

It's worth being honest about what the industry is and isn't doing about these frustrations.

The frustrations in this roundup are not unique to Nepal — every country's fintech growth phase produces this exact list in roughly this order. What would move the needle in Nepal specifically is less about product features and more about communication: clearer in-app messaging during failures, published KYC processing timelines, and support escalation paths that users can actually find and use before their complaint is a month old.

Frequently Asked Questions

Tell Us Your Experience

The five frustrations above represent the patterns most visible from our existing data. We know there are more. If you've had a specific experience with a digital payment app in Nepal — whether a frustration, an improvement you've noticed recently, or something you wish the industry would fix — drop it in the comments below. The goal of this roundup is to be useful, not exhaustive, and reader additions make it more useful for everyone who finds it.

Reader quotes in this article are paraphrased from publicly available app store reviews, Trustpilot submissions, and social media comments. No individual user has been identified. Percentage "heat" figures are editorial estimates based on proportional frequency in our source data, not statistically sampled research. This post is for informational and community purposes and does not constitute advice regarding any specific payment service provider.