POS Software With eSewa & Khalti Integration for Nepali Shops

If you have been searching for POS software with eSewa Khalti support, you already know the daily problem: customers want to pay by digital wallet at the counter, but most billing systems in Nepal treat those payments as an afterthought. You scan a static QR taped next to the till, the customer pays, you squint at their phone to confirm the amount, and then at closing time you try to match a pile of eSewa and Khalti notifications against your sales register. This post explains how to accept wallet payments cleanly at the counter and reconcile them automatically, so your end-of-day cash-up actually balances.

Why generic POS software with eSewa Khalti handling falls short

Plenty of billing apps will let you record a sale and mark it as "paid by eSewa." That is not the same as integration. With a static QR sticker, the wallet has no idea which bill it belongs to, so three things go wrong:

• Wrong amounts slip through. A customer types NPR 450 instead of NPR 540, and nobody notices until the count is short.
• Reconciliation is manual. Someone has to open the eSewa and Khalti merchant dashboards, export the day's transactions, and tick them off against your sales one by one.
• Refunds and splits get messy. A part-cash, part-wallet bill during a busy Dashain evening rarely gets logged correctly.

For a single low-volume shop, manual matching is survivable. The pain grows fast once you add a second counter, a few staff, or food-delivery orders coming in alongside walk-ins.

What "proper" wallet acceptance looks like at the counter

A counter flow built for Nepal should do the following without slowing down the queue:

1. Ring up the bill first. Items, quantities, and the total in NPR are entered in the POS.
2. Generate a payment request for that exact bill. Whether the customer chooses eSewa, Khalti, or a FonePay-linked bank QR, the amount is locked to the invoice, so they cannot underpay or overpay by mistake.
3. Confirm on screen, not on the customer's phone. The POS shows "paid" when the wallet confirms, so your staff are not leaning over to read someone's notification.
4. Split tenders when needed. Part eSewa, part cash, or wallet plus a loyalty discount should all sit on one receipt.

This is the difference between merely accepting a wallet and integrating it. The second one is what makes the books reconcile themselves.

Cover the payment methods Nepali customers actually use

Wallets are only part of the picture. A realistic Nepali shop needs to handle a mix on any given day:

• eSewa and Khalti for wallet-first customers.
• FonePay / bank QR for customers paying straight from a mobile-banking app.
• IME Pay and other wallets where your customer base uses them.
• Cash, still the default in most neighbourhoods.
• Cash on delivery (COD) for online orders that turn into deliveries.

If your POS forces every non-cash sale into one vague "digital" bucket, you lose the ability to see how much came through each channel, which matters when you are settling with each provider.

Reconcile automatically instead of counting twice

Automatic reconciliation means each wallet payment is tied to its invoice the moment it clears, and the day's totals per method are ready without anyone exporting a spreadsheet. In practice that gives you:

• A clean end-of-day summary: cash drawer expected, eSewa total, Khalti total, bank-QR total, COD pending.
• Fast spotting of mismatches, like a wallet payment that came in but never got attached to a bill.
• Records that line up with what each provider's merchant statement shows, so settlement disputes are easy to resolve.

This is also where your tax life gets easier. If you are VAT-registered, your sales need to be defensible: every invoice carries the correct 13% VAT, your PAN/VAT number prints on the receipt, and your digital and cash sales add up to a number you can actually file with the IRD. Reconciled-as-you-go data beats reconstructing the month from notifications and memory.

Retail and restaurant are not the same counter

A clothing shop in New Road and a momo restaurant in Pokhara have different counters. Retail needs barcode scanning, variants like size and colour, and stock that drops as you sell. A restaurant needs table or token orders, KOT tickets to the kitchen, and the ability to add items to a running bill before the customer pays by Khalti on the way out. Good POS software handles both modes rather than forcing a restaurant to pretend it is a grocery store.

Online orders and delivery, joined to the same system

Many SMBs in Nepal now sell both over the counter and through an online store or Instagram. The trouble starts when those are two separate worlds: stock counted twice, wallet payments tracked in two places. Tie your online store to the same POS and the same eSewa/Khalti/FonePay setup, and a prepaid online order simply appears alongside your walk-in sales. For deliveries, you can mark orders as COD or prepaid and hand them to whichever courier you use, whether that is Pathao, an in-house rider, or a domestic parcel service, while the payment status stays accurate.

This matters most in the festival crush. During Dashain and Tihar, order volume spikes, more customers pay by wallet, and you are running discounts. A system that keeps counter sales, online orders, and every payment method in one reconciled ledger is the difference between a profitable festive season and a January spent untangling the books.

Where Saauzi fits

This is exactly the gap Saauzi is built for. It is a no-code platform where Nepali SMBs can run a POS for retail or restaurant, build an online store, and accept local digital payments, eSewa, Khalti, FonePay, IME Pay, bank transfer, and cash on delivery, with each wallet payment matched to its invoice so the day reconciles on its own. You set up VAT and your PAN/VAT details once, and your receipts and reports stay consistent across the counter and online. No developers, no stitching together three different tools.

The takeaway

Accepting eSewa and Khalti is easy. Doing it so your books are correct at closing time is the part that actually saves you money and stress. Look for a POS that locks the payment to the exact bill, keeps each method separated in its reports, applies the right VAT, and ties your online and delivery orders into the same ledger. Get that right before the next festival season and your busiest weeks become your easiest to reconcile.

If you want to set this up without code, start your shop with Saauzi at saauzi.com and have eSewa and Khalti payments reconciling automatically at your counter.