Khalti Merchant Payment Guide: Accepting Wallet Payments in Nepal
By PayEurasia Team · 3 August 2026 · 6 min read
Last updated 4 August 2026
Khalti is one of the two wallets that matter in Nepal. This guide covers how merchant collections work, what to expect operationally, and how to reconcile NPR volume cleanly.
What Khalti is
Khalti is a licensed Nepali digital wallet used for top-ups, bill payments and online purchases. For merchants it provides a wallet debit flow with callback confirmation, supervised under Nepal Rastra Bank's payment framework.
Nepal is a compact but fast-digitising market. Two wallets, eSewa and Khalti, carry most consumer volume, while connectIPS and Fonepay link the banking system for larger transfers.
How the flow works
- The customer selects Khalti at checkout and the merchant creates a transaction with a unique reference.
- The customer authenticates in the Khalti app or web flow and approves the payment.
- A confirmation callback carries the terminal state and Khalti's own reference.
- The transaction is aggregated into the NPR settlement batch.
Timing and confirmation
Confirmation is normally fast, but as with any wallet rail the callback is asynchronous. Reconcile against the status endpoint rather than assuming the callback always arrives first.
Volumes are lower than the rest of the region, so operational discipline — clean reconciliation and predictable payouts — matters more than raw scale.
Limits and ticket sizes
Wallet KYC tiers cap balances and transaction sizes, so a checkout that also offers connectIPS or bank transfer will convert a wider range of customers.
This is why most Nepali checkouts present a wallet option and a bank option side by side rather than choosing one. Coverage for the full Nepal method set is described on the Nepal Payment Gateway page.
Reconciliation
Every Khalti transaction should carry three identifiers in your ledger: your order reference, the gateway reference and the rail reference returned by Khalti. With all three stored, a settlement statement can be matched line by line, refunds can be traced, and disputes can be evidenced without manual investigation.
Settlement for Nepal volume runs on T+1 in most cases. Build your daily close around that window rather than assuming same-day equivalence.
Common integration mistakes
- Presenting only one wallet and losing customers who hold the other.
- Not accounting for Bikram Sambat holidays in settlement expectations.
- Skipping reference storage, which complicates refunds.
- Testing only the success path before launch.
Merchant benefits
- Khalti acceptance through the same API as every other Nepal method
- Signed webhooks with idempotency and replay safety
- Line-level reconciliation data for finance teams
- Settlement on T+1 in most cases
- Fallback routing when an upstream connection degrades
Related guides and solutions
- Nepal Payment Gateway
- High Risk Payment Solution Nepal
- Solutions overview
- Cross-Border Payment Solutions
- Payment Infrastructure
- High-Risk Merchant Payment Processing
- Countries hub
Talk to our team
If you are evaluating acceptance in Nepal, the fastest way to get a useful answer is to share your vertical, expected monthly volume and required payout frequency. Our team can confirm which rails are available to your business, what documentation underwriting will ask for, and how quickly you can go live. Start with merchant onboarding or contact us directly.
Frequently asked questions
Should I support both eSewa and Khalti?
Yes. The two wallets have overlapping but distinct user bases, and supporting both measurably widens coverage.
How does NPR settlement work for foreign merchants?
Collections are held by a licensed local partner and settled onward, since outward remittance from Nepal is tightly controlled.
How fast do Khalti payments settle?
Settlement generally runs on a T+1 basis, subject to local banking calendars.
Talk to PayEurasia
Working in a high-risk vertical across South Asia? We can probably help.
Request integration →