Reconciling Online Payments and Avoiding Failed Transactions in Nepal

Digital payments have made selling easier across Nepal — a customer taps a few buttons in eSewa or Khalti, and the money lands in your account. Except when it doesn't. A payment shows "successful" on the customer's phone but never appears in your dashboard. A QR scan deducts the amount but the order stays "unpaid." During Dashain rush, you process 200 orders and the numbers simply don't add up at the end of the day.

This gap between what customers paid and what you can actually confirm is called reconciliation, and getting it right protects both your cash and your reputation. Here's how to track, match, and recover stuck or failed transactions in the real conditions Nepali shops operate in.

Why digital payments get stuck in Nepal

Failed and "pending" transactions are rarely about fraud. The usual culprits are mundane:

• Network timeouts. The customer's bank or wallet confirms the debit, but the callback to your store times out before it registers the payment. The money left their account; your system never heard back.
• Customer closed the app early. They paid in eSewa, then switched apps before being redirected back to confirm the order.
• Wallet vs. bank routing. Khalti and eSewa payments funded through a linked bank account (rather than wallet balance) can settle on a delay, so they appear "pending" for minutes or hours.
• Daily/transaction limits. A customer hits their NPR wallet or mobile-banking ceiling mid-checkout and the payment half-completes.
• Manual QR mismatches. When someone scans a static QR and types the amount themselves, they may enter NPR 1,500 instead of NPR 1,050 — a payment that "succeeded" but doesn't match any order.

Build a daily reconciliation habit

The single most important practice is closing your books every day, not every week. Pick a fixed time — many shop owners do it at night after shutters are down — and compare three things:

1. Your order/POS records — what you expected to be paid.
2. Your payment-gateway reports — eSewa and Khalti merchant dashboards both export daily settlement statements.
3. Your bank statement — what actually landed in your account, minus gateway fees.

Match them line by line. Anything in your gateway report that isn't in your bank deposit is a settlement still in transit. Anything marked paid by a customer but missing from your gateway report is a stuck transaction worth chasing. The faster you catch a mismatch, the easier it is to resolve while the transaction ID is fresh.

Always capture the transaction reference

Every eSewa and Khalti payment generates a reference or transaction code. Train your staff to record it — or better, let your system store it automatically against each order. When you contact support, the merchant code plus the transaction ID and exact NPR amount and timestamp is what gets a stuck payment traced in minutes instead of days.

Recovering stuck and failed transactions

When a customer insists they paid but your records disagree, work through this sequence calmly:

• Ask for proof first. Request a screenshot of the eSewa/Khalti success screen showing the amount, date, and transaction ID. A "pending" or "processing" screen is not a completed payment — explain the difference politely.
• Check your gateway dashboard. Search by amount and time window. Often the payment is there but unlinked to the order because the callback failed.
• Wait out genuine pending states. Bank-funded wallet payments can take time to settle. Don't refund or re-charge a "pending" payment immediately — you risk paying twice.
• Raise a ticket with the right details. eSewa and Khalti merchant support can confirm whether funds were captured and will reverse a failed debit back to the customer, usually within a few business days.
• Never ship before confirming. For COD-plus-prepaid or fully prepaid orders, hold dispatch until the payment shows confirmed on your side, not just on the customer's screen.

Don't forget COD reconciliation

Cash on delivery is still the backbone of Nepali e-commerce, and it has its own reconciliation problem. When a courier collects cash on your behalf, that money sits with the logistics company until they remit it — often weekly. Keep a separate ledger of COD orders marked "collected by courier" versus "remitted to us," and reconcile courier remittance statements the same way you reconcile gateway settlements. Failed or returned COD deliveries (RTO) should drop straight back into your unpaid column.

Preparing for festival-season volume

Dashain and Tihar can multiply your order count several times over, and that's exactly when reconciliation breaks down if you're doing it by hand. A few defenses help:

• Reconcile twice a day during peak weeks instead of once.
• Pre-write a short, friendly message template for "we're verifying your payment" so staff respond consistently.
• Keep a small buffer in your accounting for gateway fees and delayed settlements so a temporary gap doesn't look like a loss.
• Record the PAN/VAT-relevant details as you go — matched payments with clean transaction references make your monthly VAT filing far less painful than reconstructing it later.

Let your tools do the matching

Manual three-way reconciliation works, but it eats hours and invites errors as you scale. This is where an integrated platform earns its keep. With Saauzi, your online store, POS, and payment gateways (eSewa, Khalti, and bank) sit in one system, so each order is automatically tied to its transaction reference and payment status. Stuck or pending payments surface in your dashboard instead of hiding in three separate apps — which means you spend your evening confirming numbers, not hunting for them.

Your quick takeaway

Reconciliation isn't accounting overhead — it's how you make sure the money customers send actually reaches you. Start tonight: close your books daily, always capture the transaction ID, and never ship on an unconfirmed payment. Do those three things consistently, and stuck transactions become a quick fix instead of a costly mystery — even at the height of Dashain.